On 28/08/12 19:40, Bill Burke wrote:
>
>
> On 8/28/2012 12:43 PM, Marek Potociar wrote:
>>
>> In Jersey users typically use it to provision (fully-initialized and
>> properly scoped) sub-resource instances
>
> I just not certain this is a job for JAX-RS.
>
That was my concern too when it was discussed, or rather, I was not sure
it was in 'spirit' of JAX-RS to get some explicit JAX-RS 'specific'
initialization code mixed up with the rest of the application code
>> , regardless of what container
>> manages each particular instance, using the
>> ResourceContext.getResource(...) method. Another problem the users are
>> facing is that in many cases if a user wants to support more complex URI
>> spaces, it would make a lot of sense to leverage the JAX-RS matching
>> engine to internally "find" a proper resource instance or information
>> about it. For those cases the ResourceContext contains the matchXxx()
>> methods that expose the matching engine to the end user.
>>
>
> I've had the case that we implemeted where users want to do something
> like a Servlet.forward(), but I don't think this is the same thing. Can
> you give some examples of each match method? I'm just not understanding
> how it would be used.
>
>
Same here
Thanks, Sergey
--
Sergey Beryozkin
Talend Community Coders
http://coders.talend.com/
Blog: http://sberyozkin.blogspot.com