Try putting WSDL and XSD under META-INF of your aar archive file. For example
testservice.aar
--->META-INF
--->TestService.wsdl
--->TestService.xsd
In TestService.wsdl you need only include the xsd filename in schemaLocation
<xs:include schemaLocation="TestService.xsd"/>
After deployment the wsdl URL is something like this using your own port and
service name
http://localhost:8080/axis2/services/TestService?wsdl
And the schema URL using xsd parameter to pick the schema you want to browse
http://localhost:8080/axis2/services/TestService?xsd=TestService.xsd
Kurt Kavanaugh wrote:
>
> I have a number of Document based web services. Separate XSD document
> imported into my WSDL.
>
>
>
> All is well. I can use the WSDL in the .NET world, IBM world all the
> clients work.
>
>
>
> What I can't figure out, yet. Is where to put the WSDL so that it is
> picked up via a URL whilest in Axis2.
>
>
>
> The <URI>/services/serviceName?wsdl picks uses the JSP file to infer the
> WSDL, but the generated WSDL knows nothing of the XSD, as could be
> expected, how could it?
>
>
>
> Next stop is to set a break point on the incoming in the AxisServlet and
> see what gives.
>
>
>
> Note, XSD conformance is a must, with regards the request and reponse
>
>
>
> Thanks in advance
>
>
>
> Kurt
>
>
>
--
View this message in context:
http://www.nabble.com/Standard-for-publishing-custom-WSDL-XSD-using-axis2-tp20486488p20551040.html
Sent from the Axis - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
