Glen,

I'm sure we can setup our schema's to be HTTP-GETable via static files,
but the reason I asked is that I thought I recalled seeing a single 
"?wsdl" request actually coming across the wire as two separate 
requests, one for the wsdl and one for the imported schema.  It could 
have been an older CXF code base.

   -Chris W.

-----Original Message-----
From: Glen Mazza [mailto:[email protected]] 
Sent: Monday, January 05, 2009 11:05 AM
To: [email protected]
Subject: Re: CXF query URL for schema-only?


JSR-224 defines the ?wsdl suffix--something all JAX-WS implementations
need to support.  I don't think it defines any other suffix--a search of
that document on "?" might give you the answer.

If needed, your client can manually process the wsdl it downloads for
the specific parts (wsdl:types, wsdl:messages, etc.) that it cares
about. 
Normally developers of SOAP clients don't need to get into that level of
detail.  Note however, your WSDL can import multiple XSD's, so those
would need to be downloaded and parsed as well.

Glen


Wolf, Chris (IT) wrote:
> 
> I know there are several special query strings for WSDL and 
> JavaScript, i.e. :
>  
> http://host/service?wsdl
> http://host/service?js
> 
> ...but I thought there was also one for getting the schema part of the

> WSDL, i.e. something like http://host/service?xsd (that doesn't work) 
> Is this true?  What are all the special query URLs unserstod by JAX-WS

> and/or CXF?
> 
> Thanks,
> 
>     -Chris W.
> --------------------------------------------------------
> 
> NOTICE: If received in error, please destroy and notify sender. Sender

> does not intend to waive confidentiality or privilege. Use of this 
> email is prohibited when received in error.
> 
> 

--
View this message in context:
http://www.nabble.com/CXF-query-URL-for-schema-only--tp21293483p21293719
.html
Sent from the cxf-user mailing list archive at Nabble.com.
--------------------------------------------------------

NOTICE: If received in error, please destroy and notify sender. Sender does not 
intend to waive confidentiality or privilege. Use of this email is prohibited 
when received in error.

Reply via email to