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 154637 - Failed to Create WSDL with NPE
Summary: Failed to Create WSDL with NPE
Status: VERIFIED FIXED
Alias: None
Product: xml
Classification: Unclassified
Component: WSDL Tools (show other bugs)
Version: 6.x
Hardware: All All
: P1 blocker (vote)
Assignee: Shivanand Kini
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-12-04 18:26 UTC by rpoon
Modified: 2009-04-29 23:28 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Test Files (43.73 KB, application/octet-stream)
2008-12-04 18:29 UTC, rpoon
Details

Note You need to log in before you can comment on or make changes to this bug.
Description rpoon 2008-12-04 18:26:27 UTC
Build:  \\thumper\50builds\gfesb\v2\soarelease\promoted\fcs\fcs2

When creating a new WSDL on Open-Solaris using the above build, the NPE exception was then encountered.

Step to recreate the problem:

1)Create a new Java Library project (Java/Java Class Library)
2)Create a new JAXB binding (using the provided xsd file)
3)Create new WSDL document, and choose to create ‘Abstract WSDL’
4)Change the default value (xsd:String) of ‘Element Or Type’ for Input Message Part Name to something non-default (ie. 
Short)
5)Do the same for the Output Message Part Name.
6)The NPE will occur as you’re trying to save the WSDL.

(See attached xsd file, description file with screen shot, and Message.log file)
Comment 1 rpoon 2008-12-04 18:29:37 UTC
Created attachment 74550 [details]
Test Files
Comment 2 rpoon 2008-12-04 18:48:03 UTC
User is unable to save/create the WSDL when using the Complex type:

1)Create a new Java Library project (Java/Java Class Library)
2)Create a new XML Document using the provided xsd file
2)Create a new JAXB binding (using the provided xsd file)
3)Create new WSDL document, and choose to create ‘Abstract WSDL’
4)Change the default value (xsd:String) of ‘Element Or Type’ for Input Message Part Name to something non-default (ie. 
Complex element from step2)
5)Do the same for the Output Message Part Name.
6)The NPE will occur and user is unable to create/save the WSDL with this NPE.
Comment 3 rpoon 2008-12-04 23:17:11 UTC
Please note that the above scenario only uses JAXB binding to illustrate the problem.  Other than JAXB binding (i.e. 
Web Service client - that created using WSDL with imported XSD, for example) the problem can also be recreatable.
Comment 4 Shivanand Kini 2009-01-08 19:27:47 UTC
Fixed in soa-dev
Comment 5 jlautz 2009-04-29 23:28:31 UTC
Verified on Glassfish ESB 2.1 on windows Vista:
PRODUCT_BUILD=20090429-0723
NETBEANS_BUILD=200904151427
NETBEANS_VERSION=6.5.1
SOA_BUILD=090429

I can perform both scenarios without encountering a NullPOinterException.