-
Improvement
-
Resolution: Won't Fix
-
Neutral
-
None
-
4.3.8, 4.4.1
-
None
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.
- is depended upon by
-
MAGNOLIA-3541 Inconsistency in properties naming (at least for "server name")
- Closed
- is related to
-
MAGNOLIA-3530 Deprecate SystemProperties and PropertiesInitializer, provide cleaner and more ioc and test-friendly replacements
- Closed
-
MAGNOLIA-2644 Allow property initializer to use also servlet context attributes.
- Closed
-
MAGNOLIA-3094 Also use contextPath when resolving magnolia.properties files at startup
- Closed
-
MAGNOLIA-3516 Allow PropertyInitializer to also use system and environment properties.
- Closed
-
MAGNOLIA-3530 Deprecate SystemProperties and PropertiesInitializer, provide cleaner and more ioc and test-friendly replacements
- Closed