Indeed, it is alwayse good, since all the big application server editors say their next java middleware architecture will be OSGI based (application server beeing just one "service"): Bea,Websphere, jonas, Geronimo... My question is : is the today bundle model of Nuxeo framework already compliant to these soon comming OSGI platform ? Or does it still need some adaptations ? Maybe it is obvious since the components can be deployed on equinox, but it is to understand ...
thanks Alain On 4/10/07, Florent Guillaume <[EMAIL PROTECTED]> wrote:
That's cool, reusing existing OSGi features is always good. Florent On 7 Apr 2007, at 15:23, Bogdan Stefanescu wrote: > > I've also removed any jar name from deployment files. So now you > can rename the jars without > breaking nuxeo5. > From now you *must* use the OSGi Bundle-SymbolicName as the bundle > identifier in <require> tags > instead of the jar name. > > Bogdan > > Bogdan Stefanescu wrote: >> >> If you update from svn please remove existing nuxeo.ear prior to >> deploying the application >> >> >> nuxeo.ear was restructured. Now moduels are placed inside >> directories as follow: >> >> - system - contains runtime and jboss adapter bundles. This is the >> only required group of bundles >> - core - contains the repository bundles >> - platform - contains all the platform bundles >> - themes - contains nuxeo theme bundles >> - plugins - contains external bundles not part of nuxeo5 platform >> This should be used by contributors / client projects to deploy >> their extensions >> - The root directory contains now only nuxeo.jar, nuxeoweb.jar and >> nuxeo.war >> - config - contains configuration files. NXRuntime component >> configuration are now supporting the >> -config.xml extensions. All NXRuntime xml components file >> should be renamed using -config.xml >> -bundle.xml notation is deprecated. >> >> - datasources - contains datasources >> - lib contains static libraries (you no more need to define >> fragments for these libraries) >> >> Files in datasources and lib are deployed first >> Then regular bundles are deployed using the dependency info from >> deployment-fragment.xml >> At the end configuration files are deployed. >> >> Bogdan >> >> _______________________________________________ >> ECM mailing list >> [email protected] >> http://lists.nuxeo.com/mailman/listinfo/ecm >> > > _______________________________________________ > ECM mailing list > [email protected] > http://lists.nuxeo.com/mailman/listinfo/ecm > -- Florent Guillaume, Director of R&D, Nuxeo Open Source Enterprise Content Management (ECM) http://www.nuxeo.com http://www.nuxeo.org +33 1 40 33 79 87 _______________________________________________ ECM mailing list [email protected] http://lists.nuxeo.com/mailman/listinfo/ecm
_______________________________________________ ECM mailing list [email protected] http://lists.nuxeo.com/mailman/listinfo/ecm
