Naim wrote:
it s really compliqued your application
Yes, it is a complex application. Like any other ECM application but may be more. This additional complexity comes from one of our requirements: to be able to add or remove a component from the application without rebuilding then the application. (Ideally we should do this even at runtime - to be able to add a new module or remove existing ones without restarting the application - but this is not yet possible - I hope it will be in future). But this is not supported by J2EE specs so we are forced to do some preprocessing on the EAR to generate the configuration files from the current existing modules each time JBoss starts. This add an additional complexity to the application -> each module (or bundle) have a deployment descriptor (a file OSGI-INF/deployment-fragtment.xml) which is specifying how the component should be installed in the application (which config files it patches, which are its requirements - this means module that need to be deployed before it etc.) But if you understand how it works then all this stuff will seem much simpler to you. It is not so complicated as it seems... You should only understand the mechanism. Unfortunately we haven't much docs on this topic, but you can ask for help on the list .
Bogdan
2007/4/7, Bogdan Stefanescu <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>>: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 -- Naim IT Business EngineerPhone: 0033 (0) 668 674 310
_______________________________________________ ECM mailing list [email protected] http://lists.nuxeo.com/mailman/listinfo/ecm
