[TUSCANY-2481] NPE when WSDL types has <schema> minus @targetNamespace with an xsd:import

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Java-SCA-1.3
• Fix Version/s: Java-SCA-1.3
• Component/s: SCA Java Runtime
• Environment: r673392
• Assignee: Simon Nash
• Reporter: Scott Kurz
• Created: 17/Jul/08 18:53
• Updated: 18/Sep/10 11:37
• Resolved: 25/Jul/08 10:59

Description

WIth a WSDL types with no @targetNamespace, like the following:

<schema xmlns="http://www.w3.org/2001/XMLSchema">
<import namespace="http://helloworld" schemaLocation="Hello.xsd"/>
</schema>

we get:

java.lang.NullPointerException
at org.apache.tuscany.sca.binding.ws.axis2.Axis2ServiceProvider.updateSchemaRefs(Axis2ServiceProvider.java:519)
at org.apache.tuscany.sca.binding.ws.axis2.Axis2ServiceProvider.addSchemas(Axis2ServiceProvider.java:511)
at org.apache.tuscany.sca.binding.ws.axis2.Axis2ServiceProvider.createWSDLAxisService(Axis2ServiceProvider.java:478)
at org.apache.tuscany.sca.binding.ws.axis2.Axis2ServiceProvider.createAxisService(Axis2ServiceProvider.java:369)
at org.apache.tuscany.sca.binding.ws.axis2.Axis2ServiceProvider.start(Axis2ServiceProvider.java:256)
at org.apache.tuscany.sca.binding.ws.axis2.Axis2ServiceBindingProvider.start(Axis2ServiceBindingProvider.java:65)
at org.apache.tuscany.sca.core.assembly.CompositeActivatorImpl$3.run(CompositeActivatorImpl.java:618)
at java.security.AccessController.doPrivileged(AccessController.java:193)
at org.apache.tuscany.sca.core.assembly.CompositeActivatorImpl.start(CompositeActivatorImpl.java:616)
at org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.init(DefaultSCADomain.java:258)

The problem seems to be the fact that our wsdlDefinition ends up with an XSDefinition corresponding to the null NS. This XSDefinition, then, has no XMLSchema object associated with it, producing the NPE above. I can see in the debugger that we have an XSDefinition with empty ("") NS, which has no problem; we have an XMLSchema for empty NS.

But apparently this style of authoring <types> presents a problem.

Note that BP1.1 R2105 says this is valid, and also that wsgen produces WSDL in this style.