Note that if you'd like to control the order in which this pre-processing is done, you can add a require tag in the fragment, naming the bundle that should be deployed before yours: Sample copy of the bundle web/nuxeo.war resources to the final $NUXEO_HOME/nxserver/nuxeo.war/ directory: Sample contribution to the $NUXEO_HOME/nxserver/nuxeo.war/WEB-INF/web.xml file, using slot STD-AUTH-FILTER (check the file at $NUXEO_HOME/nxserver/META-INF/templates/web.xml for the complete list of slots) This file can contain ANT-LIKE commands and XML contributions to the target templating file. To do that, you can place a file named deployment-fragment.xml in your jar inside the OSGI-INF directory.
Looked up in the application code import .Framework
The template directory usually holds Java property files with corresponding configuration variables and values. Some Nuxeo packages hold pre-computed templates, ready for activation. This is useful to define profile-like configurations, so that a given server can quickly be reconfigured for a given target environment:Ī template can be activated by creating a directory in the $NUXEO_HOME/templates directory: the corresponding directory name can then be used as an identifier and be listed in the nuxeo.templates variable, inside the $NUXEO_HOME/bin/nf file. The Configuration Template System is used to generate configuration files: Deploy Nuxeo Runtime Configurations and Bundles.The Nuxeo Platform deployment is incremental: the startup process involves different phases.