This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Open the attached projects and edit the samlCLCA and edit the service assembly. right click stockquotesoap soapconnection and select webservices/client attributes. click browse on the samlcallback handler, the user is unable to add the saml call back handler class.
Created attachment 59072 [details] client project
Created attachment 59073 [details] server project
Created attachment 59074 [details] client comp app
Created attachment 59075 [details] messages.log
Netbeans version: Product Version: NetBeans IDE Dev (Build 200803200007) - Java CAPS Enabled Java: 1.6.0_02; Java HotSpot(TM) Client VM 1.6.0_02-b06 System: Windows Vista version 6.0 running on x86; Cp1252; en_US (nb) Userdir: C:\JavaCAPS6\.netbeans\caps
duplicate of 126214 which is fixed now.
Marked as duplicate in comments. Changing status to duplicate.
*** This issue has been marked as a duplicate of 126214 ***
Retested with Product Version: NetBeans IDE Dev (Build 200804100130) - Java CAPS Enabled Java: 1.6.0_03; Java HotSpot(TM) Client VM 1.6.0_03-b05 System: SunOS version 5.10 running on x86; ISO646-US; en (nb) Userdir: /Users/lautz/sierrabuilds/EA3Candidate/.netbeans/caps Steps performed: 1. Download and unzip all attached files. 2. Open the projects in the Project pane. 3. Open the CASA editor for the samlCLCA service assembly. 4. Rt. click the stockquotesoap SOAP WSDL port and choose Edit Web Service Attributes -> Client Configuration. 5. Click the Browse button for SAML Callback Handler. => Nothing happens.
Downgrading to P2, because I don't think this is a NB 6.1 stopper. Also, issue 126214, which this is supposed to duplicate, is a P2.
Jennifer, Please read the instructions I added on Mar 10 19:03:19 2008 in the comment section of IZ#126214. I think you missed the steps 1 and 2 in testing 131097. A Java callback project is needed to configure the SAML callback handler property in the WSIT client configuration. -- Tientien Li
I will downgrade this to a P3, because the user gets no feedback about why browse does nothing. The procedure for having this feature work somewhat properly is described in issue 126214, which has been verified to work as described in that issue.
Changed target milestone.