Thanks for that link -- it was exactly what I was looking for...a way to include my jetty-env.xml in the development mode launch.
However, after reading the article and seeing how complex the set up is...and thinking about your comment about always using the exact same server for development as for production I think I am going to punt on this idea and just use my own server. We already have a Maven cargo configuration that runs our server app with Tomcat and Jetty. Thanks again for the help though. Dave On Wednesday, December 14, 2011 9:50:01 AM UTC-5, Jens wrote: > > See: > > http://webtide.intalio.com/2011/08/gwt-and-jndi/ > > or a bit older link: > > http://humblecode.blogspot.com/2009/05/gwt-16-using-jndi-datasource.html > > Seems like it should be doable although I haven't tried it myself as I > prefer to use the exact same server for development as for production, so I > am always using -noserver. > > -- J. > > > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/X-TK4pIbJEQJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
