On Feb 9, 2010, at 7:15 PM, FSauer_at_dsthealthsolutions.com wrote:
>
> Sorry for replying to my own post here, but I just had this idea
> related to my previous post that I think is worth sharing.
>
> public Response relateFoo(@QueryParam("fooUrl") FooResource
> aFooResource) {
> // the jersey container will process the fooUrl
> parameter in order to come up with the FooResource parameter
> }
>
> I think this would be a nice addition to jersey and in line with the
> HATEOAS ideas floating around. If resources are identified by uris,
> then we should be able to consume a uri and map it back to a resource.
>
> Does this make sense?
Yes.
> Would it be hard to do?
>
Hmm.... my guess moderately hard. Jersey will need the concept of an
internal request. Plus there are all sorts of edge cases like what to
do with filters and exceptions. It will likely take a couple of days
to get everything neat and tidy.
This issue is becoming a popular one so i feel obliged to take it
on :-) just not this week, next week!
Paul.