Emmanuel Venisse wrote:
> what do you have in your jetty.xml?
My jetty.xml is completely unmodified from what shipped with jetty.
Then, I have jetty-archiva.xml with content as below, and am invoking
jetty as:
java -jar start.jar etc/jetty.xml etc/jetty-archiva.xml
<Configure id="Server" class="org.mortbay.jetty.Server">
<Array id="plusConfig" type="java.lang.String">
<Item>org.mortbay.jetty.webapp.WebInfConfiguration</Item>
<Item>org.mortbay.jetty.plus.webapp.EnvConfiguration</Item>
<Item>org.mortbay.jetty.plus.webapp.Configuration</Item>
<Item>org.mortbay.jetty.webapp.JettyWebXmlConfiguration</Item>
<Item>org.mortbay.jetty.webapp.TagLibConfiguration</Item>
</Array>
<Call class="org.mortbay.jetty.webapp.WebAppContext"
name="addWebApplications">
<Arg><Ref id="contexts"/></Arg>
<Arg>../webapps</Arg>
<Arg>org/mortbay/jetty/webapp/webdefault.xml</Arg>
<Arg><Ref id="plusConfig"/></Arg>
<Arg type="boolean">True</Arg>
<Arg type="boolean">False</Arg>
</Call>
<Call class="java.lang.System" name="setProperty">
<Arg>derby.system.home</Arg>
<Arg><SystemProperty name="java.io.tmpdir"/></Arg>
</Call>
<New class="org.mortbay.jetty.plus.naming.Resource">
<Arg>jdbc/users</Arg>
<Arg>
<New class="org.apache.derby.jdbc.EmbeddedDataSource">
<Set name="DatabaseName">target/database</Set>
<Set name="user">sa</Set>
<Set name="createDatabase">create</Set>
</New>
</Arg>
</New>
<New class="org.mortbay.jetty.plus.naming.Resource">
<Arg>jdbc/shutdown</Arg>
<Arg>
<New class="org.apache.derby.jdbc.EmbeddedDataSource">
<Set name="DatabaseName">target/database</Set>
<Set name="user">sa</Set>
<Set name="shutdownDatabase">shutdown</Set>
</New>
</Arg>
</New>
</Configure>
> Max Bowsher a écrit :
>> Emmanuel Venisse wrote:
>>> you need to put derby jar in jetty lib
>>
>> Done that. It's starting up fine.
>>
>> However, on the first HTTP request, it all falls over (exception below).
>> Therefore, I'm hoping for a known-good config to identify what I'm doing
>> wrong.
[snipped exception]
>>> Max Bowsher a écrit :
>>>> Does anyone have a working configuration of Archiva deployed on Jetty,
>>>> for which they'd be willing to share the Jetty config files?
>>>>
>>>> (I'm referring to deployment on a standalone Jetty, here, rather than
>>>> testing via maven-jetty-plugin).
>>>>
>>>> I've tried to get this working myself, but only succeeded by
>>>> configuring
>>>> the JNDI datasource stuff via WEB-INF/jetty-env.xml. When I try to move
>>>> that configuration to the main Jetty config so that I do not have to
>>>> poke around inside the Archiva war, I can't get the JNDI bindings to
>>>> work right.
