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.
Seen on Windows XP with NB 55 061005 and JDK 1.5.0_07: 1. Create a BPEL project and copy in at least 2 schemas, each of which define different namespaces and elements and types with different names. 2. Open a valid WSDL file (as created by the WSDL wizard). 3. Open a new Create New Port Type dialog. 4. Leave all the defaults, except change the part type or element for the input message to an element from the first schema. 5. Click OK. 6. Open the Create New Port Type dialog again. 7. Leave all the defaults, except change the part type or element for the output message to an element from the second schema. 8. Click OK. ==> Run XML Validate. The validation fails, saying that the type specified from the first schema "is not a valid xml schema type available in this wsdl file." ==> Look at the WSDL source, and note that the prefix ns: has been switched to represent the second schema. ==> The same problem occurs when the Create New Operation dialog is used. Attached are: Original WSDL file, WSDL file after step 5, WSDL file after step 8, and validation errors.
Created attachment 34951 [details] Newly-created WSDL file.
Created attachment 34952 [details] WSDL after step 5
Created attachment 34953 [details] WSDL after step 8
Created attachment 34954 [details] First Schema used in scenario (copied into project)
Created attachment 34955 [details] Second Schema used in scenario.
Created attachment 34956 [details] Validation errors seen after XML validation after step 8
The changes for this bug fix looks good.
Fixed this in release55_dev and release55 Fix reviewed by Ritesh.
Verified in the build 061009_1 and still I could reproduce the problem and the validation error
I am not able to reproduce this. Jennifer, can you try to reproduce this?
Jennifer wrote: I couldn't reproduce it. I happily watched the ns, ns0, and (for fun) ns1 prefixes get assigned to each newly-imported schema as I defined the new port types. skini: changing this to fixed
Verified on Windows XP with NB 55 061009_1 and JDK 1.5.0_07: When I perform the steps of the schema, as each new port type is defined, the schema that is implicitly imported to make an element type available is assigned an available default namespace ns, then ns0, then ns1, etc. What might be confusing to the user, is that it looks like issue 86684 has not been fixed yet.