I have another idea about that. I am not so experienced in OSGi from from what I undersatnd, we can think of OSGi as the platform upon which we develop enterprise components or services which provide the facility to host enterprise components.
So what I think that is better is that to develop OpenEJB to be able to be deployed on an OSGi platform to provide managing and running services for EJB components bundled as an OSGi bundles. So the developer now thinks in terms of being developing JEE components deployed as OSGi bundles expecting that the OSGi bundles has an EJB_CONTAINER service to handle requests delivered to these components. Not that other way of providing OSGi inside of OpenEJB. On Wed, Nov 12, 2008 at 7:50 PM, Dain Sundstrom <[EMAIL PROTECTED]> wrote: > On Nov 11, 2008, at 1:41 PM, David Blevins wrote: > >> 3) sure we could potentially add a container/openejb-osgi module to put >> OSGi specific stuff if we need it. > > If the integration is really small (a couple of classes), we can add an > optional dependency to openejb-core. > > -dain > -- ---- Thanks - Mohammad Nour - LinkedIn: http://www.linkedin.com/in/mnour ---- "Life is like riding a bicycle. To keep your balance you must keep moving" - Albert Einstein
