Comments on Vinod Singh: JNDI lookup on Tomcat and JBoss using Spring

hey Matt, you are absolutely right. jboss-web.xml ...

2011-12-21T20:14:58.489+05:30

hey Matt, you are absolutely right. jboss-web.xml really saved my day. Thank you.

The first anon commenter actually has the correct ...

2010-04-07T21:16:44.840+05:30

The first anon commenter actually has the correct answer. You should be defining your resource mappings in your web xml.. then upon deployment to the application server (Jboss, WAS, etc) you should be binding the resource declaration with the app server's specific jndi tree. I know it is all the rage to be more "portable" than jee but writing a class like this is really unnecessary. Of course this requires that you use the indirection already built into the jee spec. I feel like developers don't usually get this one right because they aren't usually in charge of deploying many applications on an app server. The step (putting resources in web.xml) feels unnecessary to developers because they don't really get why you should do it.

Thanks for this post. I was having a nightmare wit...

2009-06-03T16:43:45.284+05:30

Thanks for this post. I was having a nightmare with this issue across different app servers but this has made things very clear to me now. I ended up using the jboss-web.xml solution of mapping the jndi name in Jboss.
Thanks!

You could also use a SimpleJndiBeanFactory where y...

2009-05-20T22:59:04.395+05:30

You could also use a SimpleJndiBeanFactory where you can specify if you want the java:comp/env to be added or not, with the setResourceRef method, see the Spring API.

My intention is to make it work across application...

2008-12-27T13:24:00.000+05:30

My intention is to make it work across application servers without any changes. The jboss-web.xml is JBoss specific stuff, which I do not want.

Or you could use the more standard way of declarin...

2008-12-27T06:31:00.000+05:30

Or you could use the more standard way of declaring the resource-ref jdbc/myDatasource in web.xml and adding a jboss-web.xml that maps the ref to a global jndi name. Now both containers are using the jndi name java:/comp/env/jdbc/myDatasource.