Follow up question is: I consider this to be a bug / oversight. It should be a very simple use case to take the .war deployment and configure it without reaching inside the .war file and changing files. A great number of users will want to deploy Jackrabbit in this fashion. If people agree, I'll file a bug report... (?)
I agree, and support your reporting of an issue.
I could envision that a "blank/unconfigured/misconfigured" .war file prompts the user initially with some configuration form to enter mainly the repository-home and possibly other configuration options, that are then stored for future restarts of the .war file. Do you think that something like this makes sense? regards, david
