On Nov 1, 2012, at 7:24 PM, j0naht_at_yahoo.com wrote:
> Thanks for the reply, Marek! It seems like JBoss does not like
> anonymous classes in Servlet code for some reason. I ended up giving
> up on Jersey 2.0 for now and just going with the standard servlet 3.0
> method of doing asynchronous services. We have jersey 1.13 running
> just fine in JBoss and there were a lot of code changes and dependency
> conflicts to figure out to upgrade to jersey 2.0.
Have you checked our compatibility module?
https://github.com/jersey/jersey/tree/master/ext/servlet-portability
We know it's a lot of changes. Majority of the changes are however inevitable due to the lot of stuff being provided by new JAX-RS 2.0 APIs now. It's however true that we need to spend some time on improving our migration guide...
> For anyone that
> comes along after me that is attempting to do this, here is where I
> left it. It seems that you need to create a special jboss module for
> jersey 2.0 like these guys did here to use apache cxf jax-rs
> implementation
>
> http://fandry.blogspot.gr/2012/05/rest-api-with-cxf-and-spring.html
Thanks for the pointer. I don't think we'll have enough free cycles to provide JBoss support soon. But it looks like a nice small project for an external contribution if a volunteer is found.
>
> They were seeing the same type of error as you can see on the jboss
> forums here
>
> https://community.jboss.org/message/747718
Will have a look, thanks.
Marek