While the rest of the world seems to be getting high on WebLogic, Webshere or atleast Tomcat I’m still left low and with no-go on JServ!! Even the developers abandoned it like ages ago but the customers don’t seem to 
well “if it is, it is” – Karma what else can I say. What sucks the most is all the “cool” features like pooling, JNDI, EJB …. to hell I can’t even write JSP’s on JServ (not counting GNUJSp …. What the !!).
So now that the time has come for me to fix the connection pooling in my application, I thought I will reuse the pooling provided by mighty Oracle themselves. But what sucks is that I don’t have JNDI and without that all the coolness seems to fade 
. So I went around looking for independent JNDI implementation. I thought http://jakarta.apache.org/ would have one in their http://jakarta.apache.org/commons/ but alas it’s still stuck in Tomcat. I did not want to wade through all the dependencies to get that one working.
Looking around I found a couple of them(to be exact).
- http://www.osjava.org/simple-jndi/ Simple JNDI
- http://oocjndi.sourceforge.net/ OOC JNDI
The first as it says is quite simple. The author mentioned that it was used for unit testing, but me being me thought what the hell … lets get it working on a production environment (just kidding), but I did try and it did work. The problem in this JNDI lies in the lookup. Every time you do a lookup it creates a new DataSource. So the whole point of pooling is shot!
Movin on without much hope tried the OOC … but hope lives!! This thing almost seem to work for me. Has a decent xml configuration …supports all sorts of Sources and Factories too. But the only 1 thing missing is the shutting down of the pool as the container is not going to do it for me. I’ll have to write my own configuration reading and shutting down logic . Then I might as well read the configuration and bind the datasources manually. Might be a good exercise for me or should I delegate ;P ???
