I believe you either extend ApplicationPath or one which extends one of Jersey's implementations, eg. PackagesResourceConfig and then annotate it with @ApplicationPath. I think the former method is implementation neutral, while the latter is Jersey specific.
-Noah
On Sep 2, 2011, at 11:45 AM, Leonardo wrote:
> Thanks for the link! so all i need to do is to extend Application[1]
> and annotate with ApplicationPath[2]?
>
> i'll test and post, it's nice to see the specification supporting the
> "no xml" configuration.
>
> [1]http://jsr311.java.net/nonav/releases/1.1/javax/ws/rs/core/Application.html
> [2]http://jsr311.java.net/nonav/releases/1.1/javax/ws/rs/ApplicationPath.html
>
> 2011/9/2 N W <emailnbw_at_gmail.com>:
>> Try looking at using the @ApplicationPath [1].
>>
>> -Noah
>>
>> [1] - http://jersey.java.net/nonav/documentation/latest/user-guide.html#d4e212
>>
>> On Sep 2, 2011, at 10:26 AM, Leonardo wrote:
>>
>>> Hello everyone i have a question:
>>>
>>> as far as i know jersey comes bundled inside glassfissh so my ear will
>>> have little footprint. In the early days i used to configure JAX-RS
>>> following those steps (or something like this):
>>>
>>> http://www.vogella.de/articles/REST/article.html#first_servletdispatcher
>>>
>>> but with JEE 6 i am able to not use an web.xml file so, how can i do
>>> this configuration using the @WebServlet annotation? just extend
>>> ServletContainer will do the job?
>>>
>>> thanks in advance.
>>>
>>> ps: when using JAX-WS the annotated classes gets scanned and published
>>> automatically, will such kind of feature be available to JAX-RS too?
>>
>>