On Oct 16, 2008, at 5:40 AM, "Matt Raible" <[EMAIL PROTECTED]> wrote:
On Wed, Oct 15, 2008 at 9:12 PM, Alex Coles <[EMAIL PROTECTED]> wrote:Just a handful of related issues to my original issue here -- getting JNDI working well with AppFuse. Left on my list is creating the equivalent context.xml files to get things working with the cargo plugin. I noticed AppFuse by default includes a resin-web.xml file, but with the contents commented out. This resin-web.xml appears to use filtering to pull in ${jdbc.url} and ${jdbc.username}, etc. The same isn't working for the jetty-env.xml and currently, I've had to hard code the connection values in there. Does filtering work with the maven-jetty-plugin?If you're using "mvn jetty:run-war", it should be. Filtering for anything under src/main/webapp is done in the maven-war-plugin I believe. Matt
Since I ran appfuse:full-source I generally use mvn jetty:run as opposed to run-war, as it speeds up my development workflow.
I guess I need to test if filtering works with run-war. With mvn jetty:run, I am thinking it may not be possible?
Alex --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
