Conceptually at least, :-) if you have Jpox compatible with Equinox (Eclipse OSGi), you are plain OSGi, even if you are using the plugin.xml.
The plugin.xml provides you an extended programming model through extensions, but the Eclipse core runtime (the extension registry) is moving to be just a set of bundles that could be installed on any OSGi implementation. I don't know if it has been done already or it is still in the process of being done. In other words, using plugin.xml is nothing more or less than using the Servlet engine or the SCR for instance. These are extensions to the core OSGi programming model, using extra runtime frameworks installed as bundles of the core OSGi framework. In simpler terms, Jpox is therefore OSGi bundles, it just depends on some other bundles to be present... nothing unusual in the OSGi world :-) Hope this helps. Best regards, Olivier Gruber, Ph.D. Persistent & Distributed Object Platforms and Frameworks IBM TJ Watson Research Center Erik Bengtson <[EMAIL PROTECTED]> 09/07/2006 09:55 AM Please respond to felix-dev@incubator.apache.org To felix-dev@incubator.apache.org cc Subject Re: Info on OSGi migration of Apache projects Jpox (jpox.org) not from Apache, but licensed as. JPOX is a JDO / JPA implementation. We have it ready for Eclipse OSGi (We use the plugin.xml) and non OSGi containers, but would like to have it compatible with Felix too. Quoting Piero Campanelli <[EMAIL PROTECTED]>: > Hi > I have read about that some projects of Apache Consortium are switching > toward an OSGi based architecture. > > At the moment I built this list: > - James > - Cocoon > - Geronimo > - Tuscany > > do you know if is there any other project? > > Thank you > > > -- > Piero Campanelli > http://blog.pierocampanelli.info >
