Hi all,

I'm trying to get Tomee working with Jersey 2.0, and am making little
progress.

There seems to be little information about how to do this, with the notable
exception of this blog entry
http://www.fdmtech.org/2012/07/tomee-1-0-jersey-jax-rs-cdi/ (which is using
older versions of Tomee and Jersey).

Essentially, I am using Tomee (not jax-rs, or plus) 1.6.0-SNAPSHOT, and
Jersey 2.0.

I have setup a pom.xml, and using the tomee-maven-plugin have made
reasonable progress in setting up the dependencies, making sure the libs
are copied to the tomee instance, and using a custom conf/system.properties
to configure the 'LookupExtensionInBeanManager' directive (as per the blog
reference).

However, on startup I see no Jersey references what so ever, and certainly
not the expected scanning of annotated resources.  I have tried various of
the Jersey deployment options (
https://jersey.java.net/documentation/latest/user-guide.html#deployment)
without success.

I was wondering if the
'com.sun.jersey.server.impl.cdi.LookupExtensionInBeanManager' was subject
to any renaming in latter Tomee versions, but couldn't find anything
obvious.

I must be missing something, and I suspect I need to be making the tomee
instance *aware* of Jersey in some way.  Any steer willingly received...

Attached is the bare bones of the project, that illustrates the issue.

Thanks in advance

Paul

Attachment: tomeejersey.tar.gz
Description: GNU Zip compressed data

Reply via email to