Application configuration using Apache Commons Configuration
Registered by
Ralf Claussnitzer
Goobi should make use of JNDI service (or Tomcat Contexts) for bootstrap configuration instead of deploying it along with the distributable. This enables to keep configuration separate the build and prevents from deploying a false configuration to a production server. Production servers can share configurations. As a fall-back, path to configuration files might be given as context parameter.
Blueprint information
- Status:
- Not started
- Approver:
- Ralf Claussnitzer
- Priority:
- Undefined
- Drafter:
- Ralf Claussnitzer
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Approved
- Series goal:
- Accepted for 1.8
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
JNDI is a pure naming service. As long as configurations are not deployed via LDAP systems, JNDI should not be used for configuration anyway.
Using Tomcat application contexts is a better fit for passing configuration options.
Any configuration approach should provide sensible defaults as well.
Apache Commons Configuration should be used consistently.
(?)
