On May 6, 2012, at 2:37 AM, Mark Struberg wrote: >> In plain Tomcat or >> Jetty servers this needs to be configured in a container-specific way. > The problem with the container specific stuff is that every container serves > the xml configured datasource on a different location in JNDI! So you cannot > provide a container independent implementation that way :/
The portable way would be to declare your datasource properly via @Resource(name="java:app/Foo", type=DataSource.class) or via <resource-ref> xml. Most servers can map those references with little to no config. -David
