jsr339-experts@jax-rs-spec.java.net

[jsr339-experts] Re: [jax-rs-spec users] Re: Re: Fwd: Re: Re: Re: Re: HEADS-UP, IMPORTANT: Problems with JAX-RS interceptors

From: Marek Potociar <marek.potociar_at_oracle.com>
Date: Fri, 18 May 2012 21:37:11 +0200

On May 18, 2012, at 3:06 PM, Bill Burke wrote:

> We decided that:
>
> * There would be no automatic HTTP method based on method signature
>
> Don't think we decided on anything else. Could be just as simple as taking the method or class name as-is or converting it to lower case. I don't see we need to get fancy.

Ok. Can you come up with a more concrete proposal (for the Path default value) covering the scenarios bellow and how to deal with common code patterns like get/set prefixes, etc. so that we can some solid ground for further discussion?

Thanks,
Marek

>
> On 5/18/12 7:40 AM, Marek Potociar wrote:
>> Please remind me: Did we arrive to any conclusion of what the value
>> should be in that case?
>>
>> I m particularly curious for use-cases when an empty @Path annotation is
>> applied to:
>>
>> - resource class
>> - sub-resource method
>> - sub-resource locator
>>
>> Marek
>>
>> On May 17, 2012, at 5:13 PM, Bill Burke wrote:
>>
>>> Unrelated: Any way you can make the value() of @Path optional so we
>>> can start prototyping CoC based on discussions we had last year?
>>
>
> --
> Bill Burke
> JBoss, a division of Red Hat
> http://bill.burkecentral.com