[
https://issues.apache.org/jira/browse/TUSCANY-1645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fuhwei Lwo updated TUSCANY-1645:
--------------------------------
Attachment: 1645.patch
This patch should handle null namespace now. If <xsd:schema> doesn't have any
content defined like TUSCANY-544.wsdl, you should set CodeGen tool's
-schemaNamespace option to all to generate the imported XSDs. If <xsd:schema>
has content defined but without targetNamespace, its target namespace URI will
be URI of the schema document and will be code generated without specifying
-schemaNamespace=all.
I also added simpleNoTns.xsd to toolsTest project to test the #2 codegen
scenario above. The #1 scenario requires a fix on sdo plugin project to allow
passing in -schemaNamespace option plus other options. A new JIRA will be
opened.
I also need to fix SDOFactoryClass.javajet to generate correct
addXSDMapping(String[] xsdMappings, String annotationSource) signature within
createXSDMetaData() so the generated files can be compiled.
> XSD2JavaGenerator failed to gen on the wsdl files with only <xsd:import>
> element in <xsd:schema>
> ------------------------------------------------------------------------------------------------
>
> Key: TUSCANY-1645
> URL: https://issues.apache.org/jira/browse/TUSCANY-1645
> Project: Tuscany
> Issue Type: Bug
> Components: Java SDO Tools
> Affects Versions: Java-SDO-1.0
> Environment: WinXP
> Reporter: Fuhwei Lwo
> Fix For: Java-SDO-Next
>
> Attachments: 1645.patch, 1645.patch, EchoService_schema1.xsd,
> TUSCANY-544.wsdl
>
>
> NullPointerException was thrown when a WSDL with XSD definition like below
> was used by the XSD2JavaGenerator. In this case, there is no targetNamespace
> was specified in the <xsd:schema>
> <types>
> <xsd:schema>
> <xsd:import namespace="http://test/";
> schemaLocation="EchoService_schema1.xsd"/>
> </xsd:schema>
> </types>
> This problem was derived from SCA JIRA TUSCANY-544 and related to SDO JIRA
> TUSCANY-1327.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
