[ http://issues.apache.org/jira/browse/AXIS2-484?page=all ]
Ajith Harshana Ranabahu resolved AXIS2-484:
-------------------------------------------
Resolution: Fixed
Verified to work with the WSDL in Axis2-557
The following work flow was successful
* Generate server side code with the given WSDL
* compile and build the aar with ant jar.server target
* host that aar in Axis2
* go to service?wsdl link and give that URL as the URL for the codegen
* generate client side code from the WSDL hosted in the service
* build the client jar by ant jar.client
> Relative SchemaLocations for Xml Schema Imports in WSDL
> -------------------------------------------------------
>
> Key: AXIS2-484
> URL: http://issues.apache.org/jira/browse/AXIS2-484
> Project: Apache Axis 2.0 (Axis2)
> Type: Bug
> Components: wsdl
> Versions: 0.94
> Environment: WinXP, Tomcat 4, 5, Websphere 6
> Reporter: Johan Andersson
>
> If an xml schema import (xsd:import) is added in the WSDL, Axis2 will go
> looking for that import in locations the developer has no control over.
> It seems that Axis2 parses the WSDL into an object structure server side when
> the service is first loaded.
> If a relative schema import is in the WSDL the parser (WSDL4J) will try to
> load the import off the filesystem relative to where the jvm (application
> server) started.
> Then this fails the WSDL will not be available for download/consumption from
> the Axis2 server.
> It seems (not sure) a possible solution could be to set a context root for
> WSDL4J to work with.
> Preferably this would be the logical "services" context in the webapp so that
> the relative path would work for both WSDL4J parsing the WSDL serverside and
> for a webservice consumer downloading the WSDL and imports.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
