Escaffre Alain wrote:

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 ...

A JAR is OSGi compliant if it contains an OSGi MANIFEST. From this point of view Nuxeo modules are OSGI compliant bundles. Now, whether a Nuxeo bundle will run correctly in a standard OSGI framework is another question. Nuxeo5 application need some refactoring to be able to run on an OSGi platform. So nuxeo bundles as individual artifacts will be loaded correctly in an OSGi framework. But the Nuxeo5 application as a whole will not run on an OSGI platform because some MANIFEST.MF are not 100% correct (Manifest headers like Export-Packages are not filled - and because of this classes inside the bundle will not be visible outside)
Anyway these are problems that can be fixed in a few days of work.

Nuxeo already have some bundles that are running on OSGi frameworks like runtime and core bundles and some of the platform bundles. All the bundles that are used by Apogee are running correctly on OSGi frameworks. (Apogee RCP application is based on these bundles)

May be the biggest runtime difference between the JBoss framework and an OSGi framework is the class loading mechanism which is totally
different.

Bogdan

thanks


Alain

On 4/10/07, *Florent Guillaume* < [EMAIL PROTECTED] <mailto:[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] <mailto:[email protected]>
    >> http://lists.nuxeo.com/mailman/listinfo/ecm
    >>
    >
    > _______________________________________________
    > ECM mailing list
    > [email protected] <mailto:[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] <mailto:[email protected]>
    http://lists.nuxeo.com/mailman/listinfo/ecm



_______________________________________________
ECM mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/ecm

Reply via email to