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.
I am trying to invoke an external WS from my BPEL service, however, the Operation of my Invoke activity keeps 'resetting' back after I change the operation within the property editor. The operation name I want to use is "SimpleCancelWithHeader". I am creating the input and output variables for this. When I go back into the property editor it is still 'linked' to the "HelloWorld" operation. See screenshot for further clarification. Is the error shown in the attached screenshot due to this? It seems to be mapped correctly in the underlying BPEL source. Alaska project is attached.
Created attachment 37425 [details] Alaska screenshot showing multiple problems
Created attachment 37426 [details] Alaska NetBeans project test case
The problems mentioned in this bug seem to be caused by the incorrect handling of the variable selection. I could observe the following exception when following the description scenario: Annotation: Missing resource from class: org.openide.util.NbBundle$PBundle Annotation: Key which was not found: ERR_INCORRECT_MESSAGE_TYPE java.util.MissingResourceException: Can't find resource for bundle org.openide.util.NbBundle$PBundle, key ERR_INCORRECT_MESSAGE_TYPE at java.util.ResourceBundle.getObject(ResourceBundle.java:386) at java.util.ResourceBundle.getString(ResourceBundle.java:346) at org.openide.util.NbBundle.getMessage(NbBundle.java:623) at org.netbeans.modules.bpel.properties.editors.controls.MessageConfigurationController.chooseVariable(MessageConfigurationController.java:353) at org.netbeans.modules.bpel.properties.editors.controls.MessageConfigurationController.access$500(MessageConfigurationController.java:89) at org.netbeans.modules.bpel.properties.editors.controls.MessageConfigurationController$5.actionPerformed(MessageConfigurationController.java:247) at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1995)
I've investigated the project and it seems I found the reason. The process has the namespace with prefix "ns3", which is used by 3 WSDL files. And all this files are imported by the process. It is allowed theoretically but as I suppose it's not a good practice. Anyway, sharing the same namespace by several files requires that there aren't ambiguities of definitions. But they are take place in the project. Actually the operation "SimpleCancelwithHeader" is defined 3 times (in each WSDL file). I've noticed that if remove the optional attribute "portType", then the dialog start work better. portType="ns3:Cancel_policySoap" So I suppose the portType can be internally used by the BPEL model for resolving the ambiguities and I think it's wrong behaviour. I think everything should work the same depend on presence or absence of the portType attribute. I think the problem with the dialog doesn't have the P2 priority. But I see another problem. I think the XML validation process has to provide more specific diagnostic to be able to resolve such situations.
BTW the mentioned "Missing resource" doesn't significant matter here. But I fixed it anyway.
http://www.netbeans.org/issues/show_bug.cgi?id=86958 http://enterprise.netbeans.org/specs/bpel/StaticAnalysisRules.html see rule SA00014 In reality this is duplicate of 86958. About port type : you are right about procedure resolving with portType. It uses portType attribute. I didn't find any prohibition of usage portType if it is defined. If you can point to me place in specification where such prohibition exists then I will change implementation. Without strong authoritative point to specification our opinions are just our opinions.
Will look at 86958 after Beta *** This issue has been marked as a duplicate of 86958 ***