Thanks for the pointers.
If we do not want "Resource doclet" support in the generated wadl can we
skip it and just pass
Only the "applicationDocsStream" and the "grammarsStream" parameters as
shown below ?
@Override
public List<WadlGeneratorDescription> configure() {
return generator( WadlGeneratorApplicationDoc.class )
.prop( "applicationDocsStream", "application-doc.xml" )
.generator( WadlGeneratorGrammarsSupport.class )
.prop( "grammarsStream", "application-grammars.xml" )
.descriptions();
}
-----Original Message-----
From: Marc.Hadley_at_Sun.COM [mailto:Marc.Hadley_at_Sun.COM]
Sent: Wednesday, September 30, 2009 5:43 PM
To: users_at_jersey.dev.java.net
Subject: Re: [Jersey] wadl with XSD
See the description of how to achieve this here:
http://wikis.sun.com/display/Jersey/WADL
Marc
On Sep 30, 2009, at 7:09 PM, Suchitha Koneru (sukoneru) wrote:
> Hello Jersey Users,
> Is there a way to generate wadl with XSD ? Typically
> the wadl generated does not have reference to XSD of the JAXB
> objects being returned by the restful service APIs
> For example the following restful service API
> public AlertPrefInfo getAlertPref( @QueryParam("custID") String
> custID){
> return DummyDataProvider.getAlertPrefInfo();
> }
>
> Has the entry shown below in the application. wadl . The restful
> client should be made aware of the XSD for the java
> POJOAlertPrefInfo ? How do we accomplish it.
>
> <resource path="getAlertPref">
> <method name="GET" id="getAlertPref">
> <request>
> <param
xmlns:xs="
http://www.w3.org/2001/XMLSchema
> " type="xs:string" style="query" name="custID"/>
> </request>
> <response>
> <representation mediaType="application/xml"/>
> </response>
> </method>
> </resource>
>
> Thanks,
> Suchitha
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_jersey.dev.java.net
For additional commands, e-mail: users-help_at_jersey.dev.java.net