On Oct 13, 2009, at 2:09 PM, Felipe Gaścho wrote:
> yes sir.. then I see three options here:
>
> 1) to not include the libs and keep the project Glassfish deployable
> only...
> 2) to include the libs and also change the persistence provider to
> Hibernate, leaving a choice to the customer to deploy on Glassfish or
> in JBoss (at least the two major OSS servers)
Note that Jersey's EE 6 integration support is only guaranteed to work
with GlassFish.
> 3) to use Maven profiles to offer all this options, eventually leaving
> the GF-only distribution as deafult.......
>
> thanks for the tips..
>
> * a bit concerned about the "issue" of having both container and
> jersey libs available.. it shouldn't cause problems, isn't it ?
>
Sometimes it can work. It all depends on the different versions of
Jersey. The main problem is due to META-INF/service files. Although
the order loading the files can be determined by the class delegation
property the contents cannot be filtered. So a version x of Jersey may
attempt to load version y components.
All in all i think we need to remove META-INF/services from Jersey and
use some other technique.
Paul.