+1 to Nick's suggestion and let's see what our users say. :) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Chris Mattmann, Ph.D. Chief Architect Instrument Software and Science Data Systems Section (398) NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 168-519, Mailstop: 168-5th floor Email: [email protected] WWW: http://sunset.usc.edu/~mattmann/ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Adjunct Associate Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
-----Original Message----- From: Nick Burch <[email protected]> Reply-To: "[email protected]" <[email protected]> Date: Monday, May 19, 2014 1:07 PM To: "[email protected]" <[email protected]> Subject: Re: JAXRS, endpoints and a / welcome page - any ideas why it's broken? >On Mon, 19 May 2014, Sergey Beryozkin wrote: >>> I think it might be good to push them into a common path prefix. Though >>> /unpack/unpacker seems a bit unwieldy... >> >> If we do introduce "/unpack" then may be we can drop "/unpacker", and >>have >> two methods with "/" & "/all", so users will work with "/unpacker" & >> "/unpack/all" > >Won't /unpack/{id} clash with /unpack/all/{id}, or is that safe? > >>>> If it only had 1 resource method then we'd just push that method's >>>> Path up and update the method's Path to "/", but it has 2 methods. >>> >>> I suppose worst case we could create an abstract parent, put most of >>>the >>> logic there, then have two classes one per method? >> >> Introducing the inheritance will not change the target URI > >Nope, but it will let us specify the path on the class so avoid the / >clash we have now. Not so clean though... > >>> Maybe we should post to users@, and see if anyone says they do? >> >> Sounds good, please ask or I can do it, let me know please > >As our jaxrs guru, can you? :) > >Nick
