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.

Bug 116310 - REGRESSION: NPE on validating WSDL
Summary: REGRESSION: NPE on validating WSDL
Status: VERIFIED FIXED
Alias: None
Product: xml
Classification: Unclassified
Component: WSDL Model (show other bugs)
Version: 6.x
Hardware: PC All
: P1 blocker (vote)
Assignee: Sherry Weng
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-09-21 13:35 UTC by Andrei Chistiakov
Modified: 2007-09-25 16:00 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andrei Chistiakov 2007-09-21 13:35:18 UTC
Reproduced in build 20070921092706 (continuous build).

To reproduce the bug:
- create BPEL Module;
- add PurchaseOrder schema into it;
- create a WSDL. While creating, select one-way operation, set ns:purchaseOrder input element, set Document Literal
binding subtype;
- validate the WSDL.

java.lang.NullPointerException
	at
org.netbeans.modules.xml.wsdl.model.extensions.soap.validation.SOAPComponentValidator.ensureUniqueParts(SOAPComponentValidator.java:696)
	at
org.netbeans.modules.xml.wsdl.model.extensions.soap.validation.SOAPComponentValidator.visit(SOAPComponentValidator.java:635)
	at
org.netbeans.modules.xml.wsdl.model.extensions.soap.validation.SOAPComponentValidator.validate(SOAPComponentValidator.java:144)
	at org.netbeans.modules.xml.xam.spi.Validation.validate(Validation.java:78)
	at org.netbeans.modules.xml.validation.ValidationOutputWindowController.validate(ValidationOutputWindowController.java:64)
	at org.netbeans.modules.xml.validation.ValidateAction$RunAction.run(ValidateAction.java:90)
	at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:539)
[catch] at org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:964)
Comment 1 Shivanand Kini 2007-09-21 19:29:14 UTC
Soap component validator related.
Reassigning.
Comment 2 Noel Ang 2007-09-21 21:58:46 UTC
Investigating.
Comment 3 Noel Ang 2007-09-22 00:34:19 UTC
The NB WSDL Wizard is generating invalid WSDL.

Confirmed/reproduced in build 20070921210033.

Following the steps given to reproduce the issue, the following are observed:

1. The generated binding references its portType with no namespace qualification (red portion is missing):
        <binding name="newWSDLBinding" type="tns:newWSDLPortType">

2. The part definition references its type with no namespace qualification (red portion is missing):
       <part name="part1" type="ns:purchaseOrderType"/>

Correcting these errors results in a successful validation.

The NPEs need to be plugged, but the validation errors are unavoidable given that the generated WSDL is invalid.
Comment 4 Noel Ang 2007-09-22 00:35:34 UTC
To clarify, the "tns:" and "ns:" qualification for the portType and part type references are missing, and had to be
added manually.
Comment 5 Sherry Weng 2007-09-24 22:23:53 UTC
The WSDL wizard seems to create an invalid WSDL with the purchase order schema, so the WSDL validation should still 
report errors. However, the NPE issue is fixed.
Comment 6 Andrei Chistiakov 2007-09-25 16:00:18 UTC
Verified in build 200709250000.