[
http://jira.magnolia-cms.com/browse/MAGNOLIA-3521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grégory Joseph updated MAGNOLIA-3521:
-------------------------------------
Fix Version/s: 5.0
> PropertyInitializer should be pluggable.
> ----------------------------------------
>
> Key: MAGNOLIA-3521
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3521
> Project: Magnolia
> Issue Type: Improvement
> Components: core
> Affects Versions: 4.3.8, 4.4.1
> Reporter: Danilo Ghirardelli
> Assignee: Philipp Bärfuss
> Fix For: 5.0
>
>
> I don't know if it's un der refactoring right now, but just in case, I'm
> adding this.
> Most of the patch I submitted on this topic would have been simply avoided if
> the PropertyInizializer class could be specified somehow. It would be nice to
> have the PropertyInitializer class set (optionally) in the web.xml just like
> the magnolia.initialization.file. Something like
> magnolia.property.initialization.class = my.package.MyOwnPropertyInitializer.
> So Magnolia will delegate to the given class the property init, maybe with a
> fallback to the default one (more or less the current one). This shuold cover
> also most of the corner cases in configuration without overriding the
> PropertyInitializer each time.
> Maybe it could even be restored the simpler PropertyInitializer as the
> default one, leaving the contextpath/attribute/system extension to another
> class.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
