Hi all,
I've finished the work on the deployment model.
There are some files not yet commited because this will break the
current build.
I will wait for the nuxeo5 release to commit all changes.
The deployment model support modularized deployment for both EAR and WAR
packages, so a WAR module can be
deployed as multiple war fragments that contribute to the master war
their configuration and can modify structure of the master war
using a set of install commands. This way they can add new resources,
classes, remove existing one, overwrite etc.
The configuration contributions and install commands are specified
inside a fragment descriptor file.
I've already added these descriptor files for each projects - but only
the part that is dealing with EAR config.
For war fragments we also need to add the part that is specifying
contributions to the master WAR.
This task should be done by the responsible of the module that need to
be modified -
because it requires to know which web resources are part of which fragment.
We will see together how this should be done.
Here is an example of a possible WAR fragment descriptor:
<?xml version="1.0"?>
<fragment>
<require>nuxeo.jar</require>
<!-- An extension to the EAR container configuration --!>
<extension target="application#MODULE">
<module>
<ejb>myFragment.jar</ejb>
</module>
</extension>
<!-- An extension to the web.xml config file -->
<extension target="web#CONTEXT-PARAM">
<context-param>
<param-name>javax.faces.DEFAULT_SUFFIX</param-name>
<param-value>.xhtml</param-value>
</context-param>
</extension>
<install>
<!-- Install web resources located in the "web" directory of
myFragment.jar -->
<unzip from="myFragment.jar" to="/nuxeo.war" prefix="web">
<include>web/**</include>
</unzip>
</install>
</fragment>
Bogdan
_______________________________________________
ECM mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/ecm
