axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lori VanGulick (JIRA)" <>
Subject [jira] Updated: (AXIS2-1087) CLONE -Problem with resolving imported schemas from WSDL11ToAxisServiceBuilder
Date Wed, 30 Aug 2006 16:17:24 GMT
     [ ]

Lori VanGulick updated AXIS2-1087:

    Attachment: WIImport.ear

I have attached WIImport.ear which contains wars with various combinations of imported schemas
and wsdls with relative and absolute addresses.  In particular I have been looking at WIImport5.war
for absolute addresses and WIImport6.war for relative addresses.

The way I have been testing this is by exploding the war and running a JUnit testcase which
runs WSDL11ToAxisServiceBuilder against the wsdl file from the war.  I have also attached which contains the testcase and my customized WSDLLocator.  Note that the testcase
contains hardcoded references to the location of my wsdl file, so you will need to change
that if you want to run the test.

> CLONE -Problem with resolving imported schemas from WSDL11ToAxisServiceBuilder
> ------------------------------------------------------------------------------
>                 Key: AXIS2-1087
>                 URL:
>             Project: Apache Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: core
>            Reporter: Lori VanGulick
>         Assigned To: Ajith Harshana Ranabahu
>            Priority: Blocker
>         Attachments:, WIImport.ear
> When importing nested schemas with a relative path, I have noticed a problem with the
base URI that the WSDL11ToAxisServiceBuilder passes to the getXMLSchema method. Considering
the structure:
> WEB-INF/wsdl/porttype/Echo.wsdl
> and
> WEB-INF/wsdl/xsd/Echo.xsd
> If Echo.wsdl has an import statement like "../xsd/Echo.xsd", the schema will fail to
import. The issue seems to be that the WSDL11ToAxisServiceBuilder passes the string "WEB-INF/wsdl"
as the base URI. This causes the implementation of the
not to be able to resolve the relative location with the base URI. I wanted to point out this
problem, and I am not looking for an immediate patch.

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:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message