axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ellis Pritchard (JIRA)" <>
Subject [jira] Commented: (AXIS-1984) WSDL2Java should use xml commons resolver to resolve xs:import/include URIs
Date Wed, 11 May 2005 16:58:07 GMT
     [ ]
Ellis Pritchard commented on AXIS-1984:

Patch file xml-catalog.pch; all necessary patches (including test!) except addition of the
XML Commons resolver 1.1 jar which can be downloaded from the XML Commons Project (as resolver.jar),
and placed in ws-axis/java/lib (as xml-commons-resolver-1.1.jar).

Let me know what you think.

> WSDL2Java should use xml commons resolver to resolve xs:import/include URIs
> ---------------------------------------------------------------------------
>          Key: AXIS-1984
>          URL:
>      Project: Axis
>         Type: Improvement
>   Components: WSDL processing
>     Versions: 1.2
>  Environment: General (tested on Windows, Solaris)
>     Reporter: Ellis Pritchard
>  Attachments: 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 (
> 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 contact one of the administrators:
For more information on JIRA, see:

View raw message