I've just commited changes in the way nxthemes components are deployed:
* NXThemesCore
- nxthemes-core.jar (core)
* NXThemesJSF
- nxthemes-jsf.ear (JSF resources with a /nxthemes web uri. It will
contain some seam components including a central place for putting
remote.js)
- nxthemes-jsf-lib.jar (JSF/myfaces components)
* NXThemesFragments
- nxthemes-fragments.jar (theme fragments registered as nxruntime
extensions)
* NXThemesJSFFilters
- nxthemes-jsf-filters.jar (jsf filters, views registered as nxruntime
extensions)
* NXThemesEditor
- nxthemes-jsf-editor.ear (the theme editor with a web context of
/nxthemes-jsf-editor)
It contains some seam components
all ear/jars are standalone (they are deployed in
/opt/jboss/server/default/deploy) except nxthemes-jsf-lib.jar which
needs to be included in the end-user application (in that case
nuxeo.ear) like tomahawk.jar . It contains the JSF / myfaces components,
the application provides myfaces-api.jar
nxthemes-jsf-editor.ear can be deployed optionally (without it there is
no theme editor, but the rendering of themes still works)
redeploy the url-comparator on nxruntime, to update the deployment
order, and run a 'ant deploy-with-deps' on Nuxeo/
/JM
_______________________________________________
ECM mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/ecm
