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.
| Summary: | WSDL generation and validation bug | ||
|---|---|---|---|
| Product: | xml | Reporter: | kiran_bhumana <kiran_bhumana> |
| Component: | WSDL Tools | Assignee: | Shivanand Kini <skini> |
| Status: | VERIFIED FIXED | ||
| Severity: | blocker | ||
| Priority: | P2 | ||
| Version: | 5.x | ||
| Hardware: | All | ||
| OS: | All | ||
| Issue Type: | DEFECT | Exception Reporter: | |
| Attachments: |
incorrect child.wsdl
second time generated correct child.wsdl original child wsdl parent wsdl that is used to import |
||
Created attachment 32373 [details]
incorrect child.wsdl
Created attachment 32374 [details]
second time generated correct child.wsdl
Created attachment 32375 [details]
original child wsdl
Created attachment 32376 [details]
parent wsdl that is used to import
The given wsdl is not valid. the wsdl schema doesnot allow any extensibility elements to be on the top. The current wsdl.xsd(wsdl schema) used for validation allows adding extensibility element at the top, but not in mixed way. The extensibility elements should occur only at the top or at the bottom or both but not mixed. In case of invalid wsdl, the import statement is above the partnerlinktype definition. Hence the syntax validator gives that errormessage. In the second case, the model adds the import after the partnerlinktype, hence it passes(as per the current wsdl schema) The xsd needs to be changed to allow extensibility element in the bottom. Since this has to go into the wsdlmodel vaidator source which has already been frozen. i will change the xsd in netbeans55 but not for the beta. For the beta, there exists a workaround of deleting from source and adding it again as described in the bug description. *** Issue 81747 has been marked as a duplicate of this issue. *** On further checking with the WS-I basic profile 1.1, my above comments are not valid anymore. As per WS-I basic profile 1.1, elements need not be in sequence. So both cases are valid. I have checked in the new wsdl.xsd for validation. So with this change both wsdl's become valid. Verified on Windows XP NB Build 5.5 200608290000. |
Refer the attached WSDLs. Load the child_orig.wsdl and the parent.wsdl. Validation is fine. Import the parent.wsdl into the child_orig.wsdl, you will get the child.wsdl . It doesn't validate, It shows the following errors, C:\Documents and Settings\kbhumana\BpelModule1\src\f4\corrInvRec_child.wsdl:1: column:1 ERROR: cvc-complex-type.2.4.a: Invalid content was found starting with element 'types'. One of '{WC [##other:"http://schemas.xmlsoap.org/wsdl/"]}' is expected. C:\Documents and Settings\kbhumana\BpelModule1\src\f4 \corrInvRec_parent.bpel:59: column:16 ERROR: Not found propertyAlias for property "{CorrInvRecParent}property" usage for the associated variables type are in any WSDL definitions directly imported by the WS-BPEL process. C:\Documents and Settings\kbhumana\BpelModule1\src\f4\corrInvRec_child.wsdl:1: column:1 ERROR: cvc-complex-type.2.4.a: Invalid content was found starting with element 'types'. One of '{WC [##other:"http://schemas.xmlsoap.org/wsdl/"]}' is expected. C:\Documents and Settings\kbhumana\BpelModule1\nbproject\build-impl.xml:160: Found compilation errors. BUILD FAILED (total time: 2 seconds) Go to text mode, remove the import and the namespace that was just added. Go to the tree mode, and add the same import again. The generated file looks like child2.wsdl and there are no errors. I have been consistently been able to reproduce this.