Bogdan Stefanescu wrote:
Hi Jean Marc,
Hi
I reworked the deployment model of nuxeo5 so now the custom
URLComparator used to control the deployment order (declared in
conf/jboss-service.xml) is obsolete.
The order is controlled by the nuxeo5 custom EAR deployer.
Anyway I cannot remove the URLComparator because nxthemes EARs are
using it to deploy in correct order (the nxthemes-jsf-editor.ear
should be deployed after nxthemes-jsf.ear)
My question is how can we solve this (to be able to remove the custom
URLComparator)?
I see several solutions:
1. make a unique EAR for nxthemes (there is a reason to use 2 EARs?)
that's more or less detailed here:
http://lists.nuxeo.com/pipermail/ecm/2006-November/000357.html
http://lists.nuxeo.com/pipermail/ecm/2006-October/000205.html
basically the editor is a separate application, and nxthemes is
separated into different logical layers (core, fragments, filters, ).
Some of these layers are deployed as .ear files because they can't be
deployed as .jar files.
the advantage is that nxthemes can be integrated into any application
without writing a line of xml configuration except for the theme definition.
2. integrate nxthemes inside nuxeo5 EAR
that would require a lot of rewriting ... and a lot of extra boilerplate
configuration code in nuxeo5
3. make a unique nuxeo EAR for nxthemes (nxthemes.nxp) - you can
benefit thus of deployment preprocessing available in a nuxeo EAR.
it sound better, how does it work practically? add a new build target in
nuxeo5?
/JM
Bogdan
_______________________________________________
ECM mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/ecm
