• Shuffle
    Toggle On
    Toggle Off
  • Alphabetize
    Toggle On
    Toggle Off
  • Front First
    Toggle On
    Toggle Off
  • Both Sides
    Toggle On
    Toggle Off
  • Read
    Toggle On
    Toggle Off
Reading...
Front

How to study your flashcards.

Right/Left arrow keys: Navigate between flashcards.right arrow keyleft arrow key

Up/Down arrow keys: Flip the card between the front and back.down keyup key

H key: Show hint (3rd side).h key

A key: Read text to speech.a key

image

Play button

image

Play button

image

Progress

1/4

Click to flip

4 Cards in this Set

  • Front
  • Back
What is JNDI?
JNDI is the J2EE standard for naming and directory access.
What are the two parts of JNDI?
1) An application-level interface used by the application components to access naming and directory services, and 2) a service provider interface to attach a provider of a naming and directory service.
OK, but really, what's the point of JNDI? Why use it?
JNDI helps separate the concerns of the application *developer* from the application *deployer*. In a J2SE app, named resources (database lookups, passwords, authentication settings, etc.) would normally reside in a properties file. But this becomes messy in large web server apps, which often are staged from development to testing to UAT to production. If you use JNDI, you can change the properties without touching the application, and vice versa.
Who is responsible for implementing a JNDI naming context?
The application container. In fact, to be fully compliant with the J2EE 5 spec, an application container must supply access to a JNDI context.