Florent Guillaume wrote:
On 7 Dec 2006, at 20:07, Bogdan Stefanescu wrote:
Hi Jean Marc,
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?)
2. integrate nxthemes inside nuxeo5 EAR
3. make a unique nuxeo EAR for nxthemes (nxthemes.nxp) - you can
benefit thus of deployment preprocessing available in a nuxeo EAR.
One use case to keep in mind is the install of several instances of
the nuxeo5 webapp in a single JBoss server. They will require an
instance of nxthemes each (with a different webapp url prefix). It
would be nice if configuring for that didn't involve hairy jar
unzipping/rezipping.
Florent
lots of things would break because nxthemes resources are mapped against
/nxthemes/lib ..., the editor expects a /nxthemes-jsf-editor/ url for
getting its resources.
if the problem is the deployment order, I'm not even sure that it
matter if nxthemes-jsf.ear is deployed before nxthemes-jsf-editor.ear or
the opposite ... They're independent applications, so the deployment
order shouldn't matter.
are you sure that it doesn't work, Bogdan, if nxthemes-jsf.ear is
deployed after nxthemes-jsf-editor.ear? (nxthemes-jsf-editor.ear is an
optional application)
/JM
_______________________________________________
ECM mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/ecm
