Migrating from JCA to OSGI Is it a good idea?

I have a JCA adapter for connecting to EIS. Is it a good idea to replace the adapter with an OSGI module?

The features I need are

1. Access the OSGI module from ejb3
2. Access the OSGI module from CDI beans
3. Access the OSGI module from a servlet
4. Support declarative transaction mangement

5. Propogate security context from ejb to osgi module

   • I dont use conection pool开发者_如何学运维ing.
   • I dont use Common Client interface

What are the cons of moving from JCA to OSGI module ?

The cons of moving are:

• JCA is a Java EE standard - you can use a properly written connector in any Java EE container. Osgi is also a standard but not (yet) for Enterprise Applications and their frameworks.
• All your listed "features" (I would call them "requirements") are tightly coupled to Java EE: EJB3, CDI, Servlet, TXN management and security are all done or provided by the various Java EE subsystems. You will have to dive deeply into the Java EE specs to provide the appropriate glue code.

This boils down to: A lot of error-prone work for no good reason. So my question would be: What are the pros for moving (in your case of course)?