[jax-rs-spec users] [jsr339-experts] Re: Default Servlet Mapping?

From: Marek Potociar <>
Date: Wed, 14 Mar 2012 16:51:15 +0100

Hi Sergey,

FWIW, this is not an attempt to force a convention upon the community. The goal is to just provide a fall-back
convention when a custom mapping is not (yet) specified to make life of JAX-RS developers easier. IOW, certain cases
where a JAX-RS implementation would refuse to deploy earlier due to an unresolved application mapping would start
working with this convention in place.


On 03/14/2012 04:45 PM, Sergey Beryozkin wrote:
> Hi Santiago
> On 14/03/12 15:37, Santiago Pericas-Geertsen wrote:
>> Hello Experts,
>> We've done some work in Section 2.3.2 to better explain the integration with the Servlet container and its
>> pluggability framework. Unfortunately, there are still some cases --in the absence of @ApplicationPath-- in which a
>> servlet mapping must be specified in a DD.
>> Shall we define a default servlet mapping for JAX-RS 2.0? JSF uses "/faces/*", for example. How about "/webapi/*"
>> for us?
> I've no experience with JSF, I'm assuming the users are not calling /faces directly/explicitly.
> '/webapi/*' sounds ok as far as the name of uri pattern is concerned, may be "/rs/*" is also possible, but IMHO users
> will in most cases expect some custom mappings ? Unless we expect that some convention will be formed by the community,
> similar to "/services/*" with SOAP
> Cheers, Sergey
>> -- Santiago