Bug 779230 (SOA-1623)

Summary: JBossWS NullPointerException deploying JAX-WS endpoint with types in target namespace ending with '#'
Product: [JBoss] JBoss Enterprise SOA Platform 5 Reporter: Darran Lofthouse <darran.lofthouse>
Component: JBossWS, EAPAssignee: Darran Lofthouse <darran.lofthouse>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 5.0.0 ER3CC: dlesage
Target Milestone: ---   
Target Release: 5.0.2   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-1623
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-06-28 15:04:37 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Darran Lofthouse 2009-11-20 16:16:39 UTC 
Date of First Response: 2010-05-24 06:42:56
Workaround: Workaround Exists
Workaround Description: Deploying using an existing WSDL instead of leaving JBossWS to generate a new WSDL can bypass this.

project_key: SOA



Caused by: java.lang.NullPointerException
	at org.jboss.ws.tools.JavaToXSD.parseSchema(JavaToXSD.java:178)
	at org.jboss.ws.tools.wsdl.WSDL11Reader.processTypes(WSDL11Reader.java:415)
	at org.jboss.ws.tools.wsdl.WSDL11Reader.processDefinition(WSDL11Reader.java:180)
	at org.jboss.ws.tools.wsdl.WSDLDefinitionsFactory.parse(WSDLDefinitionsFactory.java:129)
	at org.jboss.ws.metadata.umdm.ServiceMetaData.getWsdlDefinitions(ServiceMetaData.java:293)
Comment 1 Darran Lofthouse 2009-11-27 13:21:14 UTC 
Workaround Description: Added: Deploying using an existing WSDL instead of leaving JBossWS to generate a new WSDL can bypass this.

Workaround: Added: [Workaround Exists]
Comment 2 Darran Lofthouse 2009-11-27 13:28:24 UTC 
Link: Added: This issue incorporates JBPAPP-3172
Comment 3 trev 2010-05-24 10:42:56 UTC 
included in EAP 5.0.1
Comment 4 David Le Sage 2010-06-02 05:13:59 UTC 
Can we please have some information on how this was fixed for the Release Notes?  Bullet-points are fine.
Comment 5 Darran Lofthouse 2010-06-02 08:46:21 UTC 
Release Notes: -
- Added detection for '#' characters and convert to '_' in schema namespace when generating a temporary file name to write the schema to based on it's namespace.
Comment 6 David Le Sage 2010-06-16 01:17:55 UTC 
Thanks for the info, Darran.  Draft text for the Release Notes states:



https://jira.jboss.org/jira/browse/SOA-1623

    A null pointer exception would occur when the user deployed a JAX-WS end-point with types in
    the target name-space that ended with #. To fix this problem, the software has been changed so
    that it now detects the presence of the # character and converts it to _ in the schema name-space.
    It does so at the point in time at which the temporary filename to which the schema is written is
    generated. (This filename is based on the schema's name-space.) As a result, the exception no
    longer occurs.
Comment 7 Boris Belovic 2010-06-28 15:04:37 UTC 
Verified in SOA-P 5.0.2 CR3.