On Wed, 2011-12-28 at 16:52 +0100, armhold wrote:
I moved the config file to src/test/jetty/jetty-env.xml because I didn't want
it deployed with my production war file. It was really the two property
settings I was missing. You might not even need the properties if you are
using the
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.version1.5.3/wicket.version
jetty.version7.5.0.v20110901/jetty.version
I moved the config file to src/test/jetty/jetty-env.xml because I didn't want
it deployed with my production war file. It was really the two property
settings I was missing. You might not even need the properties if you are
using the jetty-maven-plugin; I did because I'm running Start#main()
Has anyone got a JNDI config that works with Start.java under Wicket 1.5 (and
therefore Jetty 7.5)?
I've got JNDI working fine for my production Tomcat deployment, but can't
seem to figure out which incantations are needed to get it working with
Jetty for development/testing (I use Start.java to
The server complains about a missing value for jndi context factory.
Where do you define that value?
The Sanity Resort http://sanityresort.blogspot.com/
Am 27.12.2011 19:41, schrieb armhold:
Has anyone got a JNDI config that works with Start.java under Wicket 1.5 (and
therefore Jetty 7.5)?
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();
