On Thu, Apr 22, 2010 at 6:04 AM, Paul Sandoz [via Jersey]
<ml-node+4941923-1318496615-210534_at_n2.nabble.com> wrote:
> Annotate the class with @Provider and make sure it gets registered.
Thank you for responding.
Another question related to registration. The JAX-RS specification
obviously talks a lot about Application. But then it talks about a
lot of optional classpath scanning features that providers may wish to
implement. Then the Java EE 6 specification says that every optional
deployment/registration feature in JAX-RS must be supported by a Java
EE 6 container.
I am interested (at this point) only in getting my application running
in Java EE 6, and for all sorts of reasons do not want to define my
own Application class (I'd rather have my providers and resources
discovered). If I simply plunk my .war file containing my resource
and provider classes down, will they all get recognized?
> Application-based providers will take precedence over Jersey-based
> providers.
That is good to know.
> Can you send me a reproducible test case?
I'll do my best.
Best,
Laird
--
View this message in context: http://jersey.576304.n2.nabble.com/MessageBodyWriter-woes-tp4939544p4942177.html
Sent from the Jersey mailing list archive at Nabble.com.