I think this is a valid concern. My understanding is that the OSGi community is working hard on this as they are working on specifications for a Web Container in OSGi with requirements like Java EE compliant web container in OSGi. They are also working on specifications for JNDI in OSGi, transaction in OSGi, JPA in OSGi, etc.
Lin > Also, OSGi does not really play nicely with the usual JEE way to discover > implementations through the MANIFEST/services entries. That's kinda what > we've tried to solve in servicemix specs, though I'm not sure if that really > applies everywhere because I would imagine the classloaders for EARs are not > really OSGi classloaders ...
