Bug 364946

Description Bear Giles 2011-11-28 08:04:59 EST

Build Identifier: 

Enhancement request: support direct configuration of JNDI Resources (e.g., programmatically or via spring beans containing references, etc.) or clear documentation of why this isn't possible.

Rationale: I'm using Jetty + H2 for testng integration testing and following the convention that all of my working files are in a unique directory. The directory is nuked if all tests are successful but left in place for a post-mortem if there's a failure. This approach doesn't work if values are hardcoded, e.g., the location of the H2 backing file.

There's one work-around of creating the jetty.xml or jetty-env.xml file on the fly but that's ugly. (More precisely I would be putting it into a string and then using creating an InputStream for it but that's a detail.)  I believe there's also a workaround in setting system properties and using property placeholders in my spring configuration file - I already need this to specify the location of the database but the "don't repeat yourself" philosophy says it would be better to have a bean reference than repeating the exact connection information.

Why it may not work: I don't know the details of how well the JNDI resources (e.g., data sources) play with the threading model used by the jetty server. Maybe the server has to open the resources itself. If so it would be nice to have this clearly documented so people won't waste time trying to figure out how to do it.

BTW I am using version 8.0.

Reproducible: Always

Steps to Reproduce:
N/A - enhancement request.