Hi all,
I've finished first part of tests and integration of the new deployment
model.
I've also found an ugly workaround to control sub-deployments deploy order.
I've added a new target "deploy-ecm" to each project needed to run a
minimal nuxeo ecm (without web layer)
To deploy at once all needed modules run the target "deploy-ecm-all"
from NXCoreFacade.
Be sure to remove any old nuxeo deployment. The custom URL comparator is
no more needed.
The integration is not completely done (I need to integrate the web
layer) so you need to use the old deployment model
for testing your work.
Anyway if you want to test the new model, before deploying the
application (by running "deploy-ecm-all") you need to modify 2 files:
1. /NXJBossRuntime/src/org/nuxeo/runtime/jboss/ds-template.xml
You need to change the following line:
<rar-name>NXCore.rar</rar-name>
and replace it with
<rar-name>nuxeo.ecm#NXCore.rar</rar-name>
This is due to the specs of J2EE datasource deployment that require to
hard-code the name of the RAR declaring the resource adapter ..
2. /NXCoreFacade/test/resources/JNDILocations.properties
and other similar files.
Replace DocumentManager mapping with:
DocumentManager=DocumentManagerBean/remote
This is beacause the JNDI binding name changes (the EAR name is no more
prepended to the name - may be because EJB3 impl. is
considering the bean is not part of an EAR since the archive name is
ending in .ecm and not in .ear)
Anyway this should be fixed by using EJB3 annotations on the class to
specify what JNDI binding to use instead - this will avoid
binding changes when the ear is renamed.
These files are not modified in svn because it will break the current
deploy model.
After deploying you will have 2 new packages inside deploy directory of
jboss:
1. nuxeo.deployer (that contains the custom EAR deployer and NXRuntime)
2. nuxeo.ecm (the nuxeo EAR -> using an .ecm extension to be able to
bind it to the nuxeo deployer)
nuxeo.ecm contains the modules needed to run a minimal ECM app: (listed
in the order of their deployment)
NXCoreAPI.jar
NXCore.jar
NXCore.rar
NXJCRConnector.jar
NXCoreFacade.jar
NXDirectory.jar
NXSQLDirectory.jar
NXUserManager.jar
NXUserManagerImpl.jar
NXLoginModule.sar
loginconfig-service.xml
demo-ds-bundle.xml
CoreDirectories-bundle.xml
All the modules listed have their project build already updated
(deploy-ecm targets).
I've tested that deployment with the remote core API tests and it is
working correctly.
Bogdan
_______________________________________________
ECM mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/ecm
