Now that OSGi is an integral part of Glassfish (and other enterprise
servers) and a good amount of work has gone into making it quite easy to
build "hybrid EJBs" that leverage all the niceties of both a J2EE and OSGi
container, are there general "do's and don'ts" when integrating 3rd party
bundles into a J2EE container? For example, J2EE frowns upon a user
spawning and managing their own threads inside the context of an EJB as the
container provides its own pooling and control of such things. However, now
that Glassfish sits inside an OSGi container, is it legitimate to
build/integrate a pure OSGi bundle that handles some low level external
communications ( sockets, multiple threads, whatever...) that can then
directly communicate with some hybrid bundles inside the container via OSGi
service registry.
Essentially Im trying to get a feel for if its architecturally kosher to
bypass something like building your own JCA adapter to communicate with an
external legacy business process in favor of a pure OSGi bundle that
communicates with that same external business process and leverages the OSGi
container to feed the data into the hybrid EJBs. I know its physcially
possible, just trying to get a feel from the community as to what they
thought...
Thanks!
--
[Message sent by forum member 'cdiebner']
View Post: http://forums.java.net/node/883407