No, JNDI is quite separate from JDBC. java.sql and javax.sql contain the JDBC APIs in Java; javax.naming is JNDI. JNDI is just a directory service and nothing to do with databases. It's a way to locate resources -- like a JDBC DataSource. J2EE containers usually use it to expose the resources that the container has configured. You don't have to use JNDI to use JDBC, but your container may expose JDBC resources through it. That's why JNDI is mentioned at all in Mahout.
You can't use JNDI in any program. It's not part of J2SE, but part of J2EE. You would never use it unless you needed to -- like in writing a web app. On Sun, Apr 22, 2012 at 11:17 PM, Lance Norskog <[email protected]> wrote: > JNDI is the basic library for representing JDBC connection > specifications. You can use it from any program.
