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.
When I tried to add sxeh:FaultMessage from catch, it inserted one import statement given below into the BPEL editor <import namespace="http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling" location="http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling" importType="http://schemas.xmlsoap.org/wsdl/"/> The above import statement caused validation error and stopped the BPEL project from deploying. The validation error is given below. E:/space/jdev/sp201017/paths/jbidev/jbi/shasta/engines/bpel/nb/POJOCallsBpel/src/PojoException_StaticMethods/PojoException_StaticMethodsProcess.bpel:15,4 ERROR: If a namespace attribute is specified on an <import> then the imported definitions must be in that namespace. Steps to reproduce: 1) Create a new bpel project and in that bpel project, add a fault handler 2) Add a catch to the fault handler and the right click on catch and choose properties. 3) In properties dialog, click on the FaultVariableType ... button and bring up the fault variable type dialog 4) In the fault variable type dialog, choose "faultMessage" under "FaultMessage" and press ok. Now go to the BPEL editor and you can see the above import statement added. Now, if you press the validate button, you'll get the above validation error. NB Build: 200911291800 GFESB 2.2 build: 20091206-0720
Created attachment 92281 [details] Fault Variable Type Dialog
Created attachment 92282 [details] Import Statement and Error Message Screenshot
Some additional information When I MANUALLY COPIED the "ErrorHandling.xsd" file to my BPEL Project and changed the import statement, there was no validation error. I have made 2 changes to the import statement a) changed the location b) changed the import type from WSDL to XmlSchema OLD IMPORT STATEMENT ==================== <import namespace="http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling" location="http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling" importType="http://schemas.xmlsoap.org/wsdl/"/> MODIFIED IMPORT STATEMENT ========================= <import namespace="http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling" location="../ErrorHandling.xsd" importType="http://www.w3.org/2001/XMLSchema"/>
fixed in gfesbv23: 4e7e079e52f2 fixed in gfesbv22: 0e46d83cbd4d
Verified in the build :- #PRODUCT #-------------------- PRODUCT_NAME=Glassfish ESB PRODUCT_BUILD=20091210-0720 PRODUCT_VERSION=2.2 Followed the steps mentioned above. No import statements were added. I was able to build and deploy and test the project successfully. Hence closing this issue. Attached is the project to test the scenario.
Created attachment 92402 [details] Project attached