If you are using Jersey then url to wadl would be something like http://localhost:8080/applicationname/application.wadl You may need to add the resource base into the url e.g. http://localhost:8080/applicationname/resources/application.wadl
With a good RESTful service, it’s not necessary to generate WADL (let alone the much-less-well-fitting WSDL) for it because it will self-describe. By “self-describe” I specifically mean that it will deliver documents describing all the (relevant) resources published by the service, and that using a standard HTTP OPTIONS request on any of these will produce … Read more
WADL (Web Application Description Language) WADL is a standard to describe HTTP-based web applications. So WADL can be seen as an HTTP equivalent of WSDL 1.1. WSDL (Web Services Description Language) WSDL 2.0 can be used to describe HTTP Web services and thus competes with WADL. But it has a wider scope. XRD (eXtensible Resource … Read more
1.14-SNAPSHOT should allow you to do this: public class SampleWadlGeneratorConfig extends WadlGeneratorConfig { @Override public List<WadlGeneratorDescription> configure() { return generator( WadlGeneratorApplicationDoc.class ) .prop( “applicationDocsStream”, “application-doc.xml” ) .generator( WadlGeneratorGrammarsSupport.class ) .prop( “grammarsStream”, “application-grammars.xml” ) .prop(“overrideGrammars”, true) // !!! .generator( WadlGeneratorResourceDocSupport.class ) .prop( “resourceDocStream”, “resourcedoc.xml” ) .descriptions(); } } when overrideGrammars is set to true, Jersey generated … Read more
The purpose of WADL is to define a contract. Contract specifies how one party can call another. When you create a web application from scratch, you don’t need contract and WADL. When you integrate your system with the other system and you can communicate clearly with their development team, you don’t need contract and WADL … Read more