[
https://issues.apache.org/jira/browse/TUSCANY-544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12524150
]
Scott Kurz commented on TUSCANY-544:
------------------------------------
In my experience (admittedly not on the absolute latest version of the code),
it's not importing XSD per-se which is the problem.
In my experience, there are three issues with the WSDL/XSD pair here...
1) failed to put a targetNamespace on the <schema> element in WSDL types
2) You do an import into the same TNS as the WSDL TNS... the SDO-based
WSDL2Java tooling assumes you are going to do an include if you're referencing
an external XSD with the same TNS. The XSD2Java code I believe has the same
restriction.
But the BasicProfile says the style Sean pasted is legal.. and in fact
wsgen.bat will generate using this type of pattern in my experience.
3) Your element and types use the same QName.
I don't know which standard defines the behavior here...
------------------------------------------------------------------------------
So hopefuilly this clears up and narrows down where the problems lies a bit.
(not that I'm adding any code with these comments ;)
> WSDL2Java should support WSDLs with schema imports
> --------------------------------------------------
>
> Key: TUSCANY-544
> URL: https://issues.apache.org/jira/browse/TUSCANY-544
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA Tools
> Affects Versions: Java-SCA-M2
> Reporter: Ron Gavlin
> Assignee: Luciano Resende
> Fix For: Java-SCA-Next
>
>
> Many WSDLs choose to import schemas rather than embedding types inline. The
> tuscany WSDL2JavaGenerator does not currently support this type of usage.
--
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]
