You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@jackrabbit.apache.org by "Boden, David" <da...@lehman.com> on 2007/01/02 14:18:31 UTC
Overriding the repository home and config location doesn't work
in Tomcat
The .war deployment documentation
http://jackrabbit.apache.org/doc/deploy/howto-model1.html doesn't quite
work for me. The Tomcat resource that I setup doesn't cause the
repository home or the repository config xml file settings to be
updated.
I'd appreciate some feedback if someone has experienced the same
teething problems. Maybe a spelling mistake in the documentation? Does
anyone have this simple use case working successfully?
Question details are posted here:
http://wiki.apache.org/jackrabbit/QuestionsAndAnswers
- Dave
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
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.
RE: Overriding the repository home and config location doesn't
work in Tomcat
Posted by "Boden, David" <da...@lehman.com>.
I've removed the issue from the Questions and Answers page. It is now in
Jira:
http://issues.apache.org/jira/browse/JCR-697
Please comment / vote on this issue as you feel appropriate.
Thanks,
Dave
-----Original Message-----
From: Boden, David
Sent: Thursday, January 04, 2007 11:07 AM
To: 'users@jackrabbit.apache.org'
Subject: RE: Overriding the repository home and config location doesn't
work in Tomcat
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:david.nuescheler@gmail.com]
Sent: Thursday, January 04, 2007 10:48 AM
To: users@jackrabbit.apache.org
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.
RE: Overriding the repository home and config location doesn't
work in Tomcat
Posted by "Boden, David" <da...@lehman.com>.
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:david.nuescheler@gmail.com]
Sent: Thursday, January 04, 2007 10:48 AM
To: users@jackrabbit.apache.org
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.
Re: Overriding the repository home and config location doesn't work in Tomcat
Posted by David Nuescheler <da...@gmail.com>.
> 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
RE: Overriding the repository home and config location doesn't
work in Tomcat
Posted by "Boden, David" <da...@lehman.com>.
Thanks Marcel.
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... (?)
My use case is that I want to use Jackrabbit to host a Maven 2
repository within my company. So, ideally I want to:
* Download the Jackrabbit .war file.
* Configure Tomcat to use LDAP authentication and point it at my
company's LDAP server.
* Create my own repository.xml file which points to my AccessManager
implementation (which goes to my company's SingleSignOn service for
authorization).
* Set the repository home directory, where all the working files will
be placed and the location of the repository.xml file. Ideally, this
would be done in JNDI.
If I have to put together my own Jackrabbit .war file, I consider that I
have my "developer" hat on when I only really want to have my
"Jackrabbit user" hat on.
Regards,
Dave
-----Original Message-----
From: Marcel Reutegger [mailto:marcel.reutegger@gmx.net]
Sent: Wednesday, January 03, 2007 4:25 PM
To: users@jackrabbit.apache.org
Subject: Re: Overriding the repository home and config location doesn't
work in Tomcat
Boden, David wrote:
> The .war deployment documentation
> http://jackrabbit.apache.org/doc/deploy/howto-model1.html doesn't
> quite work for me. The Tomcat resource that I setup doesn't cause the
> repository home or the repository config xml file settings to be
> updated.
>
> I'd appreciate some feedback if someone has experienced the same
> teething problems. Maybe a spelling mistake in the documentation? Does
> anyone have this simple use case working successfully?
>
> Question details are posted here:
> http://wiki.apache.org/jackrabbit/QuestionsAndAnswers
Please do not use the wiki to just post just the question. rather ask on
the mailing list and then put both question and answer on the wiki.
Thanks.
But anyway, the answer is now on the wiki ;)
regards
marcel
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
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.
Re: Overriding the repository home and config location doesn't work
in Tomcat
Posted by Marcel Reutegger <ma...@gmx.net>.
Boden, David wrote:
> The .war deployment documentation
> http://jackrabbit.apache.org/doc/deploy/howto-model1.html doesn't quite
> work for me. The Tomcat resource that I setup doesn't cause the
> repository home or the repository config xml file settings to be
> updated.
>
> I'd appreciate some feedback if someone has experienced the same
> teething problems. Maybe a spelling mistake in the documentation? Does
> anyone have this simple use case working successfully?
>
> Question details are posted here:
> http://wiki.apache.org/jackrabbit/QuestionsAndAnswers
Please do not use the wiki to just post just the question. rather ask on the
mailing list and then put both question and answer on the wiki. Thanks.
But anyway, the answer is now on the wiki ;)
regards
marcel