[MAGNOLIA-2829] magnolia.properties should be loadable outside the webapp foldr Created: 31/Jul/09  Updated: 23/Jan/13  Resolved: 03/Aug/09

Status: Closed
Project: Magnolia
Component/s: core
Affects Version/s: None
Fix Version/s: 4.0.3, 4.1.1

Type: Bug Priority: Major
Reporter: Magnolia International Assignee: Magnolia International
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MAGNOLIA-2644 Allow property initializer to use als... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

PropertiesInitializer currently attemps to load all paths passed to it (the magnolia.initialization.file context param) as relative to the rootPath of the webapp. In many environments, it would be useful to let users have this file outside the webapp, letting them adjust settings without touching the webapp (which could be a non-exploded war file, and you wouldn't really feel comfortable messing about with temp/work files on the appserver would you)

It might also be useful to be able to load it off the classpath, while we're at it, but that'd be another issue.



 Comments   
Comment by Danilo Ghirardelli [ 04/Aug/09 ]

It would have been very nice to have also config file loaded depending on servlet context attributes, as in the attached patch. May be handy if you need to deploy the same application to different application servers.

Generated at Mon Feb 12 03:40:31 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.