On 08/12/11 03:55, laksu wrote:
Sounds great.
I have wrapped all the required output into a single custom class using
subclasses as necessary. It now generates the xsd at wadl query. This also
optimizes bandwidth by omitting unnecessary fields.
The url:
http://pathToMyMethod?_wadl&_type=xml
returns the xsd I require, but it is wrapped in<application><grammar>
elements. If I can get the plain xsd with wadl queries, along with the
@XSISchemaLocation annotation, in that case that will be the perfect
solution.
As I said earlier on, WADL is of no use in this case as Excel can't
understand it, you need to get that schema available as a resource which
xsi:schemaLocation or xsi:noNamespaceSchemaLocation pointing to it.
Extract the generated schema from WADL and save it, say to,
schemas/products.xsd, which is relative to the root of the web
application, and then use XSISchemaLocation to refer to it using that
relative path:
https://cwiki.apache.org/confluence/display/CXF20DOC/JAX-RS+Advanced+XML#JAX-RSAdvancedXML-XSISchemaLocation
I don't get the JAXbElementProvider part. Or is it something related with
controlling the wadl generation?
Please see the above link, it's to do with affecting the absolute
reference to a given schema resource
Cheers, Sergey
Thank you very much
--
View this message in context:
http://cxf.547215.n5.nabble.com/automatic-schema-generation-for-a-RS-method-tp5033048p5057660.html
Sent from the cxf-user mailing list archive at Nabble.com.
--
Sergey Beryozkin
Talend Community Coders
http://coders.talend.com/
Blog: http://sberyozkin.blogspot.com
