correct way to turn EAR module into OSGI bundle
Posted
by
Osw
on Stack Overflow
See other posts from Stack Overflow
or by Osw
Published on 2011-01-16T09:53:36Z
Indexed on
2011/01/17
10:53 UTC
Read the original article
Hit count: 259
Greetings to all!
There is a necessity to turn part of EAR (namely - war) into OSGI bundle and retain it's interoperability. Glassfish 3.0.1 already has osgi-web-container
module and I succeeded to deploy standalone OSGI war.
But in case of of ex-enterprise war it looks a bit difficult to me.
- What do I do with EJB calls from
inside future OSGI war? Is it enough
to replace
@EJB
injections with true JNDI lookups? - What about APIs and libraries shared across EAR? I could split and rearrange them, but still I will have at least one jar needed by both EAR and OSGI war. Duplicate, make it as OSGI-bundle itself and make it available to ear somehow, place it GF domain's library path?
- Any other ideas, advices which could make that hybrid working?
Many thanks in advance,
Osw
© Stack Overflow or respective owner