As I SAID in the previous answer, the JDBC stands for Java Database Connectivity and provides APIS and guidelines to connect a database from Java, while JNDI stands for Java Naming and Directory Interface and provides a logical structure for retrieving resources e.g. database, messaging queues, enterprise Java beans without knowing their physical place e.g. host or port. You can register a resource with JNDI and then rest of your application COMPONENT can access them using JNDI name. The database connection pool is the most common resource accessed via JNDI in web SERVERS like Tomcat or WebLogic.

As I said in the previous answer, the JDBC stands for Java Database Connectivity and provides APIs and guidelines to connect a database from Java, while JNDI stands for Java Naming and Directory Interface and provides a logical structure for retrieving resources e.g. database, messaging queues, enterprise Java beans without knowing their physical place e.g. host or port. You can register a resource with JNDI and then rest of your application component can access them using JNDI name. The database connection pool is the most common resource accessed via JNDI in web servers like Tomcat or WebLogic.