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. I don't get the JAXbElementProvider part. Or is it something related with controlling the wadl generation? 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.
