You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tiles.apache.org by "Antonio Petrelli (JIRA)" <ji...@apache.org> on 2009/09/27 20:48:48 UTC
[jira] Closed: (TILES-457) Add a modular initializer
[ https://issues.apache.org/struts/browse/TILES-457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Antonio Petrelli closed TILES-457.
----------------------------------
Resolution: Fixed
> Add a modular initializer
> -------------------------
>
> Key: TILES-457
> URL: https://issues.apache.org/struts/browse/TILES-457
> Project: Tiles
> Issue Type: New Feature
> Components: tiles-extras
> Affects Versions: 2.2.0
> Reporter: Antonio Petrelli
> Assignee: Antonio Petrelli
> Fix For: 2.2.x
>
>
> A modular initializer, i.e. a TilesInitializer that loads "modules of configuration" would be an interesting features.
> This initializer could work as an "initializer of the initializers:
> For each MANIFEST.MF file that it finds, it tries to find a:
> Tiles-Initializers
> property, that is a comma-separated list of initializer classes. These initializers will be then instantiated and executed one after the other.
> The MANIFEST.MF files include the one defined inside a WAR too (inside META-INF at WAR level and at WEB-INF/classes/META-INF level).
> Every "child initializer" can set it's own application context, container and container key.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.