Completely agree with this suggestion. The current situation is that we have a .war that's not going to be useful to anyone without modification. The repository.xml file that is contained within the .war makes the repository home to be the Tomcat/bin/repository directory. This is not a useful default. It's better to have no default setup and a clear error message that JNDI needs to be setup.
I like the idea of the service being able to recognise when there's no JNDI setup and prompt the user with an instructions page on how to get it done. However, this is going to need additional work. I'm entering a Jira now and will post the ID here. Would be great if you could add your vote after reviewing it. Regards, dave -----Original Message----- From: David Nuescheler [mailto:[EMAIL PROTECTED] Sent: Thursday, January 04, 2007 10:48 AM To: [email protected] Subject: Re: Overriding the repository home and config location doesn't work in Tomcat > 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 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - This message is intended only for the personal and confidential use of the designated recipient(s) named above. If you are not the intended recipient of this message you are hereby notified that any review, dissemination, distribution or copying of this message is strictly prohibited. This communication is for information purposes only and should not be regarded as an offer to sell or as a solicitation of an offer to buy any financial product, an official confirmation of any transaction, or as an official statement of Lehman Brothers. Email transmission cannot be guaranteed to be secure or error-free. Therefore, we do not represent that this information is complete or accurate and it should not be relied upon as such. All information is subject to change without notice.
