Hi Daniel Take a look at RESTEasy's JSAPIWriter [1] and how it was integrated with tapestry-resteasy [2] I think you will find everything you need in there.
If you need even more discoverability than that I'd recommend to use something like Swagger [3] 1: https://svn.code.sf.net/p/resteasy/svn/trunk/jaxrs/resteasy-jsapi/src/main/java/org/jboss/resteasy/jsapi/JSAPIWriter.java 2: http://svn.codehaus.org/tynamo/trunk/tapestry-resteasy/src/main/java/org/tynamo/resteasy/JSAPIRequestFilter.java 3: http://jira.codehaus.org/browse/TYNAMO-231 ;-) Cheers. Alejandro. On Thu, Oct 31, 2013 at 8:16 AM, Daniel Jue <teamp...@gmail.com> wrote: > Hi, I have a bunch of rest services, across a couple modules. One of the > rest services is a meta type of service, where the methods (via > parameter-less @Get requests) return things like canonical values/enums > used as query values elsewhere in the system. > > > Anyway, some member(s) of our team like to change the rest paths around and > this breaks the JS front end of course. > > Is there a way to collect: > > 1) The rest services paths for each service (i.e. the @Path value on the > class) > 2) The individual resources' paths (i.e. the @Path on the methods) > > Oh and I guess knowing the root rest path as defined in your module would > be nice too. > > > If I had the complete or relative paths to the individual methods, that > would solve my problem 100%. > > The plan is to then expose the available paths through a method under the > meta rest service. > > It's not really HATEOAS, I just want to keep the JS guys and back end guys > from stabbing each other (myself included) --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
