Answer Posted / rajkumar siripuram
JNDI is the Java Naming and Directory Interface. It's used
to separate the concerns of the application developer and
the application deployer. When you're writing an application
which relies on a database, you shouldn't need to worry
about the user name or password for connecting to that
database. JNDI allows the developer to give a name to a
database, and rely on the deployer to map that name to an
actual instance of the database.
For example, if you're writing code that runs in a Java EE
container, you can write this to get hold of the data source
with JNDI name "Database":
DataSource dataSource = null;
try
{
Context context = new InitialContext();
dataSource = context.lookup("Database");
}
catch (NamingException e)
{
// Couldn't find the data source: give up
}
Note there's nothing here about the database driver, or the
user name, or the password. That is configured inside the
container.
JNDI is not restricted to databases (JDBC); all sorts of
services can be given names. For more details, you should
check out the Sun tutorial on the subject.
link|flag
RAJKUMAR SIRIPURAM
| Is This Answer Correct ? | 9 Yes | 1 No |
Post New Answer View All Answers
What is the procedure of ejb container to handle exceptions?
Is functional programming stateless?
What is EJB server?
What is an entity and its types?
What optimization could I use if the ejb container is the only point of write access to the database?
Explain ejbhome and ejbobject in ejb?
What is backing bean?
Why do we use ejb?
What ejb means?
What are the callback annotations for entity bean?
What is session facade in ejb?
Define ACID Properties?
In what format is the conversational data written to the disk?
What do you mean by ejb ql?
What is message-driven bean?
