Web, is fine. More importantly is where is the XSD and WSDL placed in
the Axis2 deployment model? Resources directory, wsdl directory?
TestService
--->wsdl
--->TestService.wsdl
--->TestService.xsd
--->resources
--->TestService.wsdl
--->TestService.xsd
Just trying to *do* the standard thing. UDDI enabled.
wsdl.exe http://myhost/services/TestService.wsdl
for a .NET example
Thanks again for any and all input
-----Original Message-----
From: don t [mailto:[EMAIL PROTECTED]
Sent: Friday, November 14, 2008 5:49 PM
To: [email protected]
Subject: Re: Standard for publishing custom WSDL/XSD using axis2
Hi, are you asking about how to specify schema location in your WSDL
during
runtime? I believe absolute HTTP URL such as
schemaLocation="http://foo.com/foo.xsd"; is best. Relative URL may not
work
correctly and file paths don't work at all at runtime.
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-axis
2-tp20486488p20509610.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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
