[
https://jira.nuxeo.com/browse/NXP-6649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julien Carsique updated NXP-6649:
---------------------------------
Description:
Configuration templates content needs:
- factorization (too much duplicated resources)
- conditional inclusions
For instance, there are few changes in default-repository-config.xml depending
on the database. In the same file, there are options specific to the binary
storage.
Having the database type used in the templates list is a consequence of the
current non-flexibility, it would be nice to get rid of that.
There seems to be two solutions:
- using a template engine such as Freemarker
- introduce "fragments": replacing a parameter with a block containing
parameters, the block being called a "fragment" and its name being
parameterized.
Being compliant with previously existing custom templates would be better.
was:
Configuration templates content needs:
- factorization (too much duplicated resources)
- conditional inclusions
For instance, there are few changes in default-repository-config.xml depending
on the database. In the same file, there are options specific to the binary
storage.
There seems to be two solutions:
- using a template engine such as Freemarker
- introduce "fragments": replacing a parameter with a block containing
parameters, the block being called a "fragment" and its name being
parameterized.
> Improve configuration templates flexibility
> -------------------------------------------
>
> Key: NXP-6649
> URL: https://jira.nuxeo.com/browse/NXP-6649
> Project: Nuxeo Enterprise Platform
> Issue Type: New Feature
> Components: Configuration
> Reporter: Julien Carsique
> Assignee: Julien Carsique
>
> Configuration templates content needs:
> - factorization (too much duplicated resources)
> - conditional inclusions
> For instance, there are few changes in default-repository-config.xml
> depending on the database. In the same file, there are options specific to
> the binary storage.
> Having the database type used in the templates list is a consequence of the
> current non-flexibility, it would be nice to get rid of that.
> There seems to be two solutions:
> - using a template engine such as Freemarker
> - introduce "fragments": replacing a parameter with a block containing
> parameters, the block being called a "fragment" and its name being
> parameterized.
> Being compliant with previously existing custom templates would be better.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.nuxeo.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
ECM-tickets mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/ecm-tickets
