Ian,

That's very interesting.  As I replied to Glen, I thought I had recalled
the
behavior you mentioned by looking a protocol trace of a single HTTP-GET
of
a wsdl with imported schema.  I suppose the case I was recollecting 
was where the schema was in a different namespace then the wsdl.   

I was hoping to be able to perform a standalone, schema-only request
via "?xsd" even if the imported schema was in the same namespace.

One issue we have with the dynamically assembled wsdl (via "?wsdl")
is that the schema section only contains types that are actually
referenced from the common schema import file, rather then whole
schema.

  -Chris W.




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

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)

CXF only does this when it has to in order to produce a complete and
well-defined WSDL.  If you have JAXB objects in a different XML
namespace from your service then I believe CXF will create the ?wsdl
such that it imports one or more ?xsd schemas for the bits in the
different namespaces, but if everything is in one namespace then it's
all contained in the one ?wsdl and there's no need for imported ?xsd
documents.  In any case, the schema or schemas you get from ?xsd will
not include any types whose namespace matches that of the WSDL, those
types will be defined inline.

Ian

-- 
Ian Roberts               | Department of Computer Science
[email protected]  | University of Sheffield, UK
--------------------------------------------------------

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