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.
Please use the attached project (BPEL + Composite Application projects) to reproduce the problem. 1. Open the projects. 2. Build the BPEL project. 3. Build the Composite Application project. 4. Edit the Service Assembly. 5. Clone both output ports. Save the .casa file. 6. Edit the WSIT *client* configuration of the ISTSUserAuthService_Port port. Enter an arbitrary user name and password, and click OK to save your changes. 7. Edit the WSIT *client* configuration of the STSUserAuthServicePort port. This action causes the NPE. The exception occurs once one of the output ports is configured, and the other one is about to be configured. It does not actually matter which port is configured first. The exception is: java.lang.NullPointerException at org.netbeans.modules.websvc.wsitconf.ui.client.ClientView.<init>(ClientView.java:114) at org.netbeans.modules.websvc.wsitconf.ui.client.ClientTopComponent.doInitialize(ClientTopComponent.java:131) at org.netbeans.modules.websvc.wsitconf.ui.client.ClientTopComponent.addNotify(ClientTopComponent.java:154) at java.awt.Container.addNotify(Container.java:2500) at javax.swing.JComponent.addNotify(JComponent.java:4478) at java.awt.Container.addNotify(Container.java:2500) at javax.swing.JComponent.addNotify(JComponent.java:4478) at java.awt.Container.addNotify(Container.java:2500) at javax.swing.JComponent.addNotify(JComponent.java:4478) at javax.swing.JRootPane.addNotify(JRootPane.java:680) at java.awt.Container.addNotify(Container.java:2500) at java.awt.Window.addNotify(Window.java:467) at java.awt.Dialog.addNotify(Dialog.java:379) at org.netbeans.core.windows.services.NbPresenter.addNotify(NbPresenter.java:338) at java.awt.Window.pack(Window.java:485) at org.netbeans.core.windows.services.NbPresenter.initialize(NbPresenter.java:236) at org.netbeans.core.windows.services.NbPresenter.<init>(NbPresenter.java:166) at org.netbeans.core.windows.services.NbDialog.<init>(NbDialog.java:64) at org.netbeans.core.windows.services.DialogDisplayerImpl$1.run(DialogDisplayerImpl.java:130) at org.netbeans.core.windows.services.DialogDisplayerImpl$1.run(DialogDisplayerImpl.java:106) at org.openide.util.Mutex.doEventAccess(Mutex.java:1355) at org.openide.util.Mutex.readAccess(Mutex.java:268) at org.netbeans.core.windows.services.DialogDisplayerImpl.createDialog(DialogDisplayerImpl.java:105) [catch] at org.netbeans.modules.compapp.casaeditor.nodes.actions.WsitClientConfigAction$1.run(WsitClientConfigAction.java:205) at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209) at java.awt.EventQueue.dispatchEvent(EventQueue.java:461) at org.netbeans.core.TimableEventQueue.dispatchEvent(TimableEventQueue.java:104) at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:242) at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:163) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:157) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:149) at java.awt.EventDispatchThread.run(EventDispatchThread.java:110)
Created attachment 59874 [details] BPEL and Composite App projects
Reproduced using the currently latest NetBeans sierra build, #1545 (20080408).
reproduced on NB6.1 release build
Noel, The current WSIT client-side configuration design makes a copy of server wsdl, e.g., myService.wsdl, to the configuration directory and renames it as myServer.xml to store client-side WSIT configurations. In this case, there are two server wsdls with identical name in the bepl project: 1, src/localhost_8080/STS_UserAuth/STSUserAuthService.wsdl (defines: ISTSUserAuthService_Port) 2, src/localhost_9080/STSUserAuthService.wsdl (defines: STSUserAuthServicePort) These are two different wsdl files with the same name. The reported problem was caused by the skipping over the creation of second WSIT client side configuration file. Both of them have the same name STSUserAuthService.xml. A simple work around of this problem is to rename the second file as, e.g., STSUserAuthService9080.wsdl, to avoid the problem with identical configuration file name. This is how the current WSIT client-side configuration module works. We will not fix this problem, but will add it to the release note of WSIT support. Thanks, -- Tientien Li
Has this been added to the release notes?
i verified this was added to release notes for 6.1 gfesb release, accepting wontfix resolution and marking verified to cleanup QE queue.