You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@jackrabbit.apache.org by Mark Phillips <ma...@mophilly.com> on 2010/12/09 23:50:39 UTC

newbie: understanding web.xml

As I work through the setup of my first jackrabbit on a server, I am wading through the files and docs. 

I see in the file web.xml a lot of commented out directives, as follows...

 <!--
        <init-param>
            <param-name>repository-config</param-name>
            <param-value>/WEB-INF/repository/repository.xml</param-value>
            <description>the repository config location</description>
        </init-param>
-->

Do I infer correctly that I need to create the physical paths, uncomment the directives, and deploy the application again?

 - mark

Re: newbie: understanding web.xml

Posted by Mark Phillips <ma...@mophilly.com>.
On Dec 14, 2010, at 9:26 AM, ChadDavis wrote:

> Did you look at the comments in the RepositoryStartupServlet?  I seem to
> recall that it is comments explain this boot process.

Thanks, Chad, I will review this file.

 - Mark

Re: newbie: understanding web.xml

Posted by ChadDavis <ch...@gmail.com>.
> I assumed the actual paths would be applied when the Tomcat manager was
> used to deploy the web app, with necessary files written into the "work"
> directory. However, that does not seem to be the case for these config
> files, as is hinted at in the following error message:
>
>  13.12.2010 10:11:06 *ERROR* RepositoryStartupServlet:
>    Repository startup configuration is not valid but a bootstrap config is
> specified.
>    (RepositoryStartupServlet.java, line 366)
>

Did you look at the comments in the RepositoryStartupServlet?  I seem to
recall that it is comments explain this boot process.

Re: newbie: understanding web.xml

Posted by Mark Phillips <ma...@mophilly.com>.
On Dec 9, 2010, at 3:06 PM, ChadDavis wrote:

> If I'm not mistaken, that is commented out because the default set up
> uses another alternative to locate it's repository.xml file.  In
> particular, there's a bootstrap.properties file.  But I don't know the
> details of this off the top of my head.  Someone else will though.

Thank you for the reply, Chad.

I can find bootstrap.properties, but it too appears to generic values. It also does not get written out during deployment, but remains only in the directory "templates".

I assumed the actual paths would be applied when the Tomcat manager was used to deploy the web app, with necessary files written into the "work" directory. However, that does not seem to be the case for these config files, as is hinted at in the following error message:

 13.12.2010 10:11:06 *ERROR* RepositoryStartupServlet: 
    Repository startup configuration is not valid but a bootstrap config is specified. 
    (RepositoryStartupServlet.java, line 366)

There are other errors, for example an error stating that "jackrabbit/repository.xml" cannot be found. I have confirmed that "repository.xml" cannot be found. Is this an error condition or is "repository.xml" a file I need to create?

I haven't taken to using a java console to issue various commands. My hope was the web app would do this for me. Perhaps I am being naive.

Any help warmly received.

 - Mark

Re: newbie: understanding web.xml

Posted by ChadDavis <ch...@gmail.com>.
On Thu, Dec 9, 2010 at 3:50 PM, Mark Phillips
<ma...@mophilly.com> wrote:
> As I work through the setup of my first jackrabbit on a server, I am wading through the files and docs.
>
> I see in the file web.xml a lot of commented out directives, as follows...
>
>  <!--
>        <init-param>
>            <param-name>repository-config</param-name>
>            <param-value>/WEB-INF/repository/repository.xml</param-value>
>            <description>the repository config location</description>
>        </init-param>
> -->
>

If I'm not mistaken, that is commented out because the default set up
uses another alternative to locate it's repository.xml file.  In
particular, there's a bootstrap.properties file.  But I don't know the
details of this off the top of my head.  Someone else will though.

> Do I infer correctly that I need to create the physical paths, uncomment the directives, and deploy the application again?
>
>  - mark