-
Improvement
-
Resolution: Fixed
-
Major
-
3.6.3, 4.0
-
None
-
-
Yes
-
Empty show more show less
On some application servers is very useful to have the property configurer use also servlet context attributes and/or parameters to choose what configuration file should be loaded.
This is mainly a WebSphere issue, because one of the "recommended" cluster configuration is to have multiple jvm instances on the same server. (I'm not trying to say this is a good or bad choice, I only found it on some servers) With the current property configurer there is no way to have a different configuration for each jvm, because the only difference is the "com.ibm.websphere.servlet.application.host" attribute in servlet context. This particular attribute obviously works only for WebSphere, but with the simple path I attached you could use any other servlet context attribute or parameter.
- is related to
-
MAGNOLIA-2829 magnolia.properties should be loadable outside the webapp foldr
- 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-3521 PropertyInitializer should be pluggable.
- Closed