-
Improvement
-
Resolution: Fixed
-
Major
-
None
When looking up magnolia.properties [1] files, we're using the current host name, as well as the webapp folder name (i.e the last element of the path in which the webapp is deployed) - which is not necessarily the servlet context path for the webapp.
Using the webapp's context path might help in a bunch of situations (while developing I often have a context path differing from the webapp's name. same goes when deploying multiple apps under different vhosts of a single tomcat, for instance; some appservers deploy their webapps in folder whose name doesn't correspond to the contextPath either)
Unfortunately, javax.servlet.ServletContext#getContextPath is only available since the 2.5 version of the Servlet API. Can we update ?
(marking this as fix-for 4.3, only in the case we can quickly decide on upgrading the servlet api dependency, in which case adding this should be trivial)
- is depended upon by
-
MAGNOLIA-5155 Remove redundancy of magnolia-test-public-webapp
- Closed
-
MGNLEE-294 Remove redundancy of magnolia-ee-test-public-webapp
- Closed
- is related to
-
MAGNOLIA-2644 Allow property initializer to use also servlet context attributes.
- Closed
-
MAGNOLIA-3303 Upgrade to Servlet API 2.5
- Closed
-
DOCU-264 Document new possibility of using context path for resolving location of magnolia.properties
- Closed
-
MAGNOLIA-3516 Allow PropertyInitializer to also use system and environment properties.
- Closed
-
MAGNOLIA-3521 PropertyInitializer should be pluggable.
- Closed