Hi,
I'm also using wicket 1.5 and jetty 7.5 (eclipse's) with mortbay's
eclipse plugin of the same version, and I had no need to add those
properties you mention.
>From my pom.xml:
<wicket.version>1.5.3</wicket.version>
<jetty.version>7.5.0.v20110901</jetty.version>
<dependency>
<groupId>org.eclipse.jetty.aggregate</groupId>
<artifactId>jetty-all-server</artifactId>
<version>${jetty.version}</version>
<scope>provided</scope>
</dependency>
<plugin>
<groupId>org.mortbay.jetty</groupId>
<artifactId>jetty-maven-plugin</artifactId>
<version>${jetty.version}</version>
...
[the rest is what wicket quickstart brings]
...
</plugin>
In src/main/webapp/WEB-INF/jetty-env.xml - which is found without
problems:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE Configure PUBLIC "-//Mort Bay Consulting//DTD Configure//EN"
"http://jetty.mortbay.org/configure.dtd";>
<Configure class="org.eclipse.jetty.webapp.WebAppContext">
<New id="db" class="org.eclipse.jetty.plus.jndi.Resource">
<Arg>jdbc/db</Arg>
<Arg>
<New class="oracle.jdbc.pool.OracleDataSource">
<Set name="DriverType">thin</Set>
<Set
name="URL">jdbc:oracle:thin:@[ip]:1521:[db]</Set>
<Set name="User">[user]</Set>
<Set name="Password">[pw]</Set>
<Set name="connectionCachingEnabled">true</Set>
<Set name="connectionCacheProperties">
<New class="java.util.Properties">
<Call name="setProperty">
<Arg>MinLimit</Arg>
<Arg>5</Arg>
</Call>
<!-- put the other properties
in here too -->
</New>
</Set>
</New>
</Arg>
</New>
<New id="solrHome" class="org.eclipse.jetty.plus.jndi.EnvEntry">
<Arg>solr/home</Arg>
<Arg type="java.lang.String">solr/home</Arg>
<Arg type="boolean">true</Arg>
</New>
</Configure>
I found the mix of eclipse and mortbay packages annoying. When copying
examples you always have to take care not to overlook package names that
do not fit into your version setup...
Cheers,
Chantal
On Wed, 2011-12-28 at 04:37 +0100, armhold wrote:
> Thanks to a hint from Christian Huber I got it working.
>
> System.setProperty("java.naming.factory.url.pkgs",
> "org.eclipse.jetty.jndi");
> System.setProperty("java.naming.factory.initial",
> "org.eclipse.jetty.jndi.InitialContextFactory");
>
> EnvConfiguration envConfiguration = new EnvConfiguration();
> URL url = new File("src/test/jetty/jetty-env.xml").toURI().toURL();
> envConfiguration.setJettyEnvXml(url);
>
> bb.setConfigurations(new Configuration[]{ new WebInfConfiguration(),
> envConfiguration, new WebXmlConfiguration() });
>
>
>
> Full details here:
> http://blog.armhold.com/2011/12/28/how-to-get-jndi-working-with-wicket-1-5-and-jetty-7-5/
>
>
> --
> View this message in context:
> http://apache-wicket.1842946.n4.nabble.com/Using-JNDI-from-Jetty-Start-java-tp4237903p4238955.html
> Sent from the Users forum mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
