I just got embedded Jetty JNDI support working, to allow me to debug GeoServer JNDI data source configurations in Eclipse with an external jetty.xml to configure a connection pool. Yes, my recent exposure to JNDI has driven me mad with power.
I needed to add jetty-plus and jetty-naming, which draw in geronimo and derby, and a few lines to web-app Start.java. The dependencies are test-phase only, so should not increase bloat. I am not sure all this is needed; I will try to pare it back. Jetty doesn't bother with requiring resource-ref in web.xml, so things are a bit easier than expected. Any objections? Who is responsible for maintaining web-app Start.jar? -- Ben Caradoc-Davies <[email protected]> Software Engineer, CSIRO Exploration and Mining Australian Resources Research Centre 26 Dick Perry Ave, Kensington WA 6151, Australia ------------------------------------------------------------------------------ Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
