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?
Alex
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
