[jira] Resolved: (TUSCANY-2479) Problems with bottom-up J2W code when cross-NS class-to-class reference exists; issue with systemID used by XMLSchema code for corresponding xsd import

["Scott Kurz (JIRA)" <de...@tuscany.apache.org>]

     [ https://issues.apache.org/jira/browse/TUSCANY-2479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Scott Kurz resolved TUSCANY-2479.
---------------------------------

    Resolution: Fixed

Thanks Simon, my original test is working now as well.

> Problems with bottom-up J2W code when cross-NS class-to-class reference exists;  issue with systemID used by XMLSchema code for corresponding xsd import
> --------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: TUSCANY-2479
>                 URL: https://issues.apache.org/jira/browse/TUSCANY-2479
>             Project: Tuscany
>          Issue Type: Bug
>          Components: Java SCA Data Binding Runtime
>            Reporter: Scott Kurz
>            Assignee: Simon Nash
>         Attachments: 2479.test.diff
>
>
> If I go bottom-up from Java, with class my.pkg1.MyClass dependent on my.pkg2.OtherClass, the Interface2WSDLGenerator will produce XMLSchema objects in such a way that the schemaLocation on the import doesn't work.
> As an immediate cause, I can see the code in JAXBTypeHelper.DOMResolverImpl doing:
>         public Result createOutput(String ns, String file) throws IOException {
>             DOMResult result = new DOMResult();
>             result.setSystemId(ns + file);
> This is what produces the XmlSchemaException with message "The system cannot find the file specified." 
> I'll attach a patch to allow for recreate.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.