Jersey is natively supported only by Glassfish. Jersey provides it’s own API that extend the JAX-RS. JAX-RS 2.0 API is not supported before Jersey 2.23.1.
RESTEasy instead is bundled with JBoss/Wildfly and completely integrated as per the requirements of Java EE (RESTEasy JAX-RS).
You will therefore not need any add'l libraries when deploying a JAX-RS Application to Wildfly using RESTEasy.
Refering to jersey 1.16 this is a quite old version which will probably cause issues in a WildFly environment with Java SE 8. And migrating to Jersey 2 would mean some work (Chapter 28. Migration Guide) as well.
I therefore think the only practicable option is to migrate to RESTEasy when moving to WildFly.
I wanted to confirm that this approach is not viable.
- disable all jax-rs in wildfly
- load jersey jars from application (i.e. in ear file)
This is the approach the team used for Jboss 4
Clearly it's suboptimal..just delays upgrade work, but I wanted to understand why it would not succeed in wildly.
thanks and best regards