[
https://issues.apache.org/jira/browse/AXIS-1984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Veithen updated AXIS-1984:
----------------------------------
Fix Version/s: 1.4.1
Assignee: Andreas Veithen
> WSDL2Java should use xml commons resolver to resolve xs:import/include URIs
> ---------------------------------------------------------------------------
>
> Key: AXIS-1984
> URL: https://issues.apache.org/jira/browse/AXIS-1984
> Project: Axis
> Issue Type: Improvement
> Components: WSDL processing
> Affects Versions: 1.2
> Environment: General (tested on Windows, Solaris)
> Reporter: Ellis Pritchard
> Assignee: Andreas Veithen
> Fix For: 1.4.1
>
> Attachments: wsdl4j.pch, xml-catalog.pch, xml-catalog.pch
>
>
> Currently WSDL2Java assumes that the schemaLocation URI specified in an XML
> Schema <xs:import> or <xs:include> element is either a URL or a file path; it
> would be a vast improvement if it could use the Apache XML Commons project's
> Catalog based Resolver instead
> (http://xml.apache.org/commons/components/resolver/).
> It is not always possible to specify a file or URL location which is constant
> and useable across development, test and live systems, so the ability that
> XML Catalogs give to map arbitrary URIs or URI prefixes to alternative paths
> is invaluable when creating portable and authoritative XML Schema/WSDL
> service definitions.
> The functionality could also be usefully (but in practice less importantly)
> employed in <wsdl:import> elements.
> Implementation should allow a root catalog to be specified on the command
> line (WSDL2Java), and should pick up the configured catalog(s) (<xmlcatalog>
> elements) from the Ant environment (axis-wsdl2java Ant task).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
