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.
correlation wizard runs into exception when I add correlation for Receive1 and Invoke1 activities in SynchronousSample java.lang.NullPointerException at org.netbeans.modules.bpel.properties.editors.WizardUtils.wsdlContainsPropertyAlias(DefineCorrelationWizard.java:2067) at org.netbeans.modules.bpel.properties.editors.DefineCorrelationWizard$WizardDefineCorrelationPanel$CorrelationDataHolder.createPropertyAlias(DefineCorrelationWizard.java:1235) at org.netbeans.modules.bpel.properties.editors.DefineCorrelationWizard$WizardDefineCorrelationPanel$CorrelationLinker.createPropertyAlias(DefineCorrelationWizard.java:1041) at org.netbeans.modules.bpel.properties.editors.DefineCorrelationWizard$WizardDefineCorrelationPanel.createCorrelationPropertiesAndPropertyAliases(DefineCorrelationWizard.java:972) at org.netbeans.modules.bpel.properties.editors.DefineCorrelationWizard$WizardDefineCorrelationPanel.makeCorrelations(DefineCorrelationWizard.java:870) at org.netbeans.modules.bpel.properties.editors.DefineCorrelationWizard$WizardDefineCorrelationPanel.validate(DefineCorrelationWizard.java:844) at org.openide.WizardDescriptor$6.run(WizardDescriptor.java:1268) at org.openide.WizardDescriptor.lazyValidate(WizardDescriptor.java:1313) at org.openide.WizardDescriptor.access$1200(WizardDescriptor.java:119) at org.openide.WizardDescriptor$Listener.actionPerformed(WizardDescriptor.java:1964) Caused: java.lang.reflect.InvocationTargetException at sun.reflect.GeneratedMethodAccessor132.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.openide.util.WeakListenerImpl$ProxyListener.invoke(WeakListenerImpl.java:449) Caused: java.lang.reflect.UndeclaredThrowableException at $Proxy18.actionPerformed(Unknown Source) at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1995) at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2318) at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:387) at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:242) at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:236) at java.awt.Component.processMouseEvent(Component.java:6038) at javax.swing.JComponent.processMouseEvent(JComponent.java:3265) at java.awt.Component.processEvent(Component.java:5803) at java.awt.Container.processEvent(Container.java:2058) at java.awt.Component.dispatchEventImpl(Component.java:4410) at java.awt.Container.dispatchEventImpl(Container.java:2116) at java.awt.Component.dispatchEvent(Component.java:4240) at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4322) at java.awt.LightweightDispatcher.processMouseEvent(Container.java:3986) at java.awt.LightweightDispatcher.dispatchEvent(Container.java:3916) at java.awt.Container.dispatchEventImpl(Container.java:2102) at java.awt.Window.dispatchEventImpl(Window.java:2429) at java.awt.Component.dispatchEvent(Component.java:4240) at java.awt.EventQueue.dispatchEvent(EventQueue.java:599) at org.netbeans.core.TimableEventQueue.dispatchEvent(TimableEventQueue.java:104) at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:273) at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:183) at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:177) at java.awt.Dialog$1.run(Dialog.java:1039) at java.awt.Dialog$3.run(Dialog.java:1091) at java.security.AccessController.doPrivileged(Native Method) at java.awt.Dialog.show(Dialog.java:1089) at org.netbeans.core.windows.services.NbPresenter.superShow(NbPresenter.java:835) at org.netbeans.core.windows.services.NbPresenter.doShow(NbPresenter.java:869) at org.netbeans.core.windows.services.NbPresenter.run(NbPresenter.java:857) at org.netbeans.core.windows.services.NbPresenter.run(NbPresenter.java:108) at org.openide.util.Mutex.doEventAccess(Mutex.java:1355) at org.openide.util.Mutex.readAccess(Mutex.java:268) at org.netbeans.core.windows.services.NbPresenter.show(NbPresenter.java:842) at java.awt.Component.show(Component.java:1419) at java.awt.Component.setVisible(Component.java:1372) at java.awt.Window.setVisible(Window.java:801) at java.awt.Dialog.setVisible(Dialog.java:979) at org.netbeans.modules.bpel.properties.editors.DefineCorrelationWizard.showWizardDialog(DefineCorrelationWizard.java:266) [catch] at org.netbeans.modules.bpel.nodes.actions.DefineCorrelationAction$1.run(DefineCorrelationAction.java:88) at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209) at java.awt.EventQueue.dispatchEvent(EventQueue.java:597) at org.netbeans.core.TimableEventQueue.dispatchEvent(TimableEventQueue.java:104) at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:273) at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:183) at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:173) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:168) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:160) at java.awt.EventDispatchThread.run(EventDispatchThread.java:121)
Created attachment 63145 [details] project for reproducing issue
Murali, what build did you use ?
This scenario works for me on: Product Version: NetBeans IDE Dev (Build 080622) Java: 1.5.0_14; Java HotSpot(TM) Client VM 1.5.0_14-b03 System: Windows XP version 5.1 running on x86 I tried to reproduce this bug on NB build 080622 and I wasn't able to do this. My steps were: 1. Unzip the attached project, open it 2. Open WizardCorrelationProperties.wsdl, delete definitions of: <vprop:property name="wzrd_prop_simpleElement_simpleElement" type="xsd:string"/> <vprop:propertyAlias propertyName="tns:wzrd_prop_simpleElement_simpleElement" ...> <vprop:query>/ns0:simpleElement</vprop:query> </vprop:propertyAlias> 3. Open SynchronousSample.bpel. On BPEL diagram use popup menu for Receive1, select "Define Correlation..." 4. Select Invoke1 from the list "Initiating Messaging Activity", click Next 5. Create a link from the left node simpleElement to the same right one, click Finish. Result (in the SynchronousSample.bpel): - correlation set was created correctly <correlationSets> <correlationSet name="wzrd_set_Invoke1_Receive1" properties="tns:wzrd_prop_simpleElement_simpleElement"/> </correlationSets> - was added to Invoke1 <correlations> <correlation set="wzrd_set_Invoke1_Receive1" initiate="yes"/> </correlations> - was added to Receive1 <correlations> <correlation set="wzrd_set_Invoke1_Receive1" initiate="no"/> </correlations> Please, check this scenario on the latest build.
I am using NB6.1 packaged with JavaCAPS6 JVM version is java version "1.6.0_02" Java(TM) SE Runtime Environment (build 1.6.0_02-b06) Java HotSpot(TM) Client VM (build 1.6.0_02-b06, mixed mode, sharing) I am fine with testing on the latest version, please point me to latest version/download link.
Here you are the link: http://bits.netbeans.org/download/trunk/nightly/
Now I've checked this issue on 2 NB 6.1 builds: 1. The official NB 6.1 build 05/30/2008 from http://download.netbeans.org/netbeans/6.1/final/ Product Version: NetBeans IDE 6.1 (Build 200805300101) Java: 1.6.0_03; Java HotSpot(TM) Client VM 1.6.0_03-b02 System: Windows XP version 5.1 running on x86 2. NB 6.1 FCS build 04/21/2008 from http://smetiste.czech.sun.com/builds/netbeans/6.1/fcs/latest/ Product Version: NetBeans IDE 6.1 (Build 200804211638) Java: 1.6.0_03; Java HotSpot(TM) Client VM 1.6.0_03-b02 System: Windows XP version 5.1 running on x8 I can't reproduce this bug - everything works fine.
Murali, may I ask you to post the data from the NetBeans' about screen? It's accessible from NetBeans->About NetBeans on a Mac, I believe the same for Windows is Help->About.
Created attachment 63388 [details] NB aout screen
I am able to reproduce the issue with http://download.netbeans.org/netbeans/6.1/final/. Please note that I have installed 'ALL' version. My OS is Microsoft Windows XP Professional Version 2002 Service Pack 3 Here is my observations 1. It generates "WizardCorrelationProperties.wsdl", adds "import" to BP. But no correlation set is added. 2. Content of WizardCorrelationProperties.wsdl is printed below. propertyAlias/query is invalid. When a WSDL message part is defined as an element, query should not be generated. <?xml version="1.0" encoding="UTF-8"?> <definitions xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" name="WizardCorrelationProperties.wsdl" targetNamespace="http://enterprise.netbeans.org/bpel/WizardCorrelationProperties" xmlns:tns="http://enterprise.netbeans.org/bpel/WizardCorrelationProperties" xmlns:vprop="http://docs.oasis-open.org/wsbpel/2.0/varprop" xmlns:ns0="http://localhost:12000/repository/repository1/BP10AsyncService/BPAsyncServiceRecv"> <import namespace="http://localhost:12000/repository/repository1/BP10AsyncService/BPAsyncServiceRecv" location="BPAsyncServiceRecv.wsdl"/> <import namespace="http://localhost:12000/repository/repository1/BP10AsyncService/BPAsyncServiceInvoke" location="BPAsyncServiceInvoke.wsdl"/> <types> <xsd:schema targetNamespace="http://enterprise.netbeans.org/bpel/WizardCorrelationProperties"> <xsd:import namespace="http://localhost:12000/repository/repository1/BP10AsyncService/BPAsyncServiceRecv" schemaLocation="BPAsyncServiceRecv.wsdl"/> </xsd:schema> </types> <vprop:property name="wzrd_prop_simpleElement_simpleElement" type="xsd:string"/> <vprop:propertyAlias propertyName="tns:wzrd_prop_simpleElement_simpleElement" messageType="ns:Message1" part="value1"> <vprop:query>/ns0:simpleElement</vprop:query> </vprop:propertyAlias> </definitions>
I have updated JDK on my machine to 1.6.0_06, issue still exists. java version "1.6.0_06" Java(TM) SE Runtime Environment (build 1.6.0_06-b02) Java HotSpot(TM) Client VM (build 10.0-b22, mixed mode, sharing) I am also attaching NB log
Created attachment 63392 [details] log with the exception NB version and JDK version
I've found out the reason of this issue. NPE is caused by invalid content of the "WizardCorrelationProperties.wsdl". It ALREADY CONTAINS the appropriate property alias (the same one has to be generated by correlation wizard): <vprop:propertyAlias propertyName="tns:wzrd_prop_simpleElement_simpleElement" messageType="ns:Message1" part="value1"> and this property alias is incorrect - the value of the attribute "messageType" has the namespace "ns:" instead of the correct value "ns0:". So, when wizard tried to check whether a generated property alias already exists or not, the value of object related to the attribute "messageType" was null due to incorrect namespace. My mistake was: when I tried to reproduce this bug, I always removed wrong property alias and then invoked correlation wizard. In this case wizard worked without any problem. Now this bug has been fixed in trunk: http://hg.netbeans.org/main?cmd=changeset;node=332a2ec6dbf5 An information dialog with warning message will appear instead of NullPointerException. Please, verify it on NB build being equal or later than 080628...: http://bits.netbeans.org/download/trunk/nightly/latest/
I've checked this issue on: Product Version: NetBeans IDE Dev (Build 080627) Java: 1.5.0_14; Java HotSpot(TM) Client VM 1.5.0_14-b03 System: Windows XP version 5.1 running on x8
Retested with Product Version: NetBeans IDE Dev (Build 200807030007) Java: 1.6.0_06; Java HotSpot(TM) Client VM 10.0-b22 System: Windows XP version 5.1 running on x86; Cp1252; en_US (nb) ------------------------------------- here are the validation errors I got, attaching new project. XML validation started. C:/Documents and Settings/mpottlapelli/My Documents/NetBeansProjects/Correlation/CorrelationInvokeRecv/CorrelationInvokeRecv/src/SynchronousSample.bpel:75,8 WARNING: The variable "OperationIn1" is initialized and not used. C:/Documents and Settings/mpottlapelli/My Documents/NetBeansProjects/Correlation/CorrelationInvokeRecv/CorrelationInvokeRecv/src/BPAsyncServiceRecv.wsdl:6,54 ERROR: s4s-elt-schema-ns: The namespace of element 'definitions' must be from the schema namespace, 'http://www.w3.org/2001/XMLSchema'. C:/Documents and Settings/mpottlapelli/My Documents/NetBeansProjects/Correlation/CorrelationInvokeRecv/CorrelationInvokeRecv/src/BPAsyncServiceRecv.wsdl:6,54 ERROR: s4s-elt-invalid: Element 'definitions' is not a valid element in a schema document. C:/Documents and Settings/mpottlapelli/My Documents/NetBeansProjects/Correlation/CorrelationInvokeRecv/CorrelationInvokeRecv/src/BPAsyncServiceRecv.wsdl:6,54 ERROR: src-import.2: The root element of document 'BPAsyncServiceRecv.wsdl' has to have the namespace name 'http://www.w3.org/2001/XMLSchema' and the local name 'schema'. C:/Documents and Settings/mpottlapelli/My Documents/NetBeansProjects/Correlation/CorrelationInvokeRecv/CorrelationInvokeRecv/src/WizardCorrelationProperties.wsdl:17,8 ERROR: Can not find the element "ns:simpleElement" at the namespace "http://localhost:12000/repository/repository1/BP10AsyncService/BPAsyncServiceRecv". Expression: "/ns:simpleElement" C:/Documents and Settings/mpottlapelli/My Documents/NetBeansProjects/Correlation/CorrelationInvokeRecv/CorrelationInvokeRecv/src/SynchronousSample.bpel:123,16 ERROR: Property "wzrd_prop_simpleElement_simpleElement" does not have a propertyAlias defined for the message where the correlation set "wzrd_set_Invoke1_Receive1" is being used. 5 Error(s), 1 Warning(s). XML validation finished. In addition I have noted a regression, when "BPAsyncServiceWrapper" WSDL (partnerLinkType associated with two roles) is dropped on BPEL editor it is creating partner link but it is not recognizing the second role.
Created attachment 63965 [details] new project with build errors
Please follow these steps to reproduce the issue. 1. Create synchronous sample based on Samples/SOA/Synchronous BPEL Process 2. Add BPAsyncServiceRecv.wsdl and BPAsyncServiceInvoke.wsdl to the project 3. Create a WSDL, import BPAsyncServiceRecv and BPAsyncServiceInvoke WSDLs, define a PLT with two roles. 4. DnD WSDL on to BP canvas, create a PL with my role and partner role. 5. DnD Receive and Invoke activities and configure them. 6. Initiate correlation wizard from Recv, and select Invoke as initiating activity. Do the mapping and associate at "simpleElement". 7. Build the project.
Created attachment 63966 [details] WSDL to be implemented
Created attachment 63967 [details] WSDL to be invoked
Correlation wizard is very critical tool in defining correlation. When this is broken it creates usability issues. So I am increasing priority to P1 so that it is available as patch 3
This bug is resolved and its status has been changed to "Fixed" because the original problem "correlation wizard runs into exception" is not reproduced since June 27. New bug, related to the messages, which were added since July 5, has been created: http://www.netbeans.org/issues/show_bug.cgi?id=141299 ============================================================================================= I've found out the reason of this issue. NPE is caused by invalid content of the "WizardCorrelationProperties.wsdl". It ALREADY CONTAINS the appropriate property alias (the same one has to be generated by correlation wizard): <vprop:propertyAlias propertyName="tns:wzrd_prop_simpleElement_simpleElement" messageType="ns:Message1" part="value1"> and this property alias is incorrect - the value of the attribute "messageType" has the namespace "ns:" instead of the correct value "ns0:". So, when wizard tried to check whether a generated property alias already exists or not, the value of object related to the attribute "messageType" was null due to incorrect namespace. My mistake was: when I tried to reproduce this bug, I always removed wrong property alias and then invoked correlation wizard. In this case wizard worked without any problem. Now this bug has been fixed in trunk: http://hg.netbeans.org/main?cmd=changeset;node=332a2ec6dbf5 An information dialog with warning message will appear instead of NullPointerException. Please, verify it on NB build being equal or later than 080628...: http://bits.netbeans.org/download/trunk/nightly/latest/ I've checked this issue on: Product Version: NetBeans IDE Dev (Build 080627) Java: 1.5.0_14; Java HotSpot(TM) Client VM 1.5.0_14-b03 System: Windows XP version 5.1 running on x86
tested and verified using Build 200810080102 and able to create successfully.