[MAGNOLIA-2210] jackrabbit: update configuration files Created: 27/Jun/08  Updated: 23/Jan/13  Resolved: 03/Jul/08

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: None
Fix Version/s: 3.6

Type: Improvement Priority: Blocker
Reporter: Philipp Bärfuss Assignee: Jan Haderka
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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)
Date of First Response:

 Description   

We should add new configuration files for the bundled PMs and should make the derby one the default.

To avoid to many files we could introduce the processing of the file similar to what we do for our own files (replacing ${var}). The problem is that jackrabbit needs an existing file and we would have to write the processed file to the filesystem. The main benefit would be that you don't need different files for author and public instance.



 Comments   
Comment by Magnolia International [ 02/Jul/08 ]

started with r16325

Comment by Jan Haderka [ 03/Jul/08 ]

Added bundle configurations for mysql and derby. Changed default config to bundled derby. As for replacing things in the files on-the-fly I'm leaving this out for now. First we should not write back into the webapp FS more then necessary and JR 1.5 is supposed to have better support for JNDI to obtain the datasource which would remove need for multiple files (and for keeping password in them).

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