This week's giveaway is in the Android forum.
We're giving away four copies of Android Security Essentials Live Lessons and have Godfrey Nolan on-line!
See this thread for details.
The moose likes EJB and other Java EE Technologies and the fly likes JNDI server persistance Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Android Security Essentials Live Lessons this week in the Android forum!
JavaRanch » Java Forums » Java » EJB and other Java EE Technologies
Bookmark "JNDI server persistance " Watch "JNDI server persistance " New topic
Author

JNDI server persistance

Arvind Varma
Ranch Hand

Joined: Dec 24, 2002
Posts: 48
what happens to the value contained in the JNDI, if the server is down �
will it preserve the value or will it start afresh?
Lasse Koskela
author
Sheriff

Joined: Jan 23, 2002
Posts: 11962
    
    5
I don't think the JNDI spec defines "persistent entries" as such -- the JNDI server may ofcourse provide proprietary methods for defining persistent values.


Author of Test Driven (2007) and Effective Unit Testing (2013) [Blog] [HowToAskQuestionsOnJavaRanch]
Vinod John
Ranch Hand

Joined: Jun 23, 2003
Posts: 162
Originally posted by Arvind Varma:
what happens to the value contained in the JNDI, if the server is down �
will it preserve the value or will it start afresh?

JNDI is as such a standard API interface for java applications to access a naming/directory servies. The naming and directory service acts as a database (techincally they are only services to store/access the data) to store the data. Note that naming and directory service doesn't support transaction,so if you store something, it assumed to be there even if the transaction transaction is rolled back.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: JNDI server persistance
 
Similar Threads
Unable to find java:comp/ServerAdministrator
JNDI- Ejb Home
JNDI Initial Context
Where to configure the Resource bundles/properties files
Invalid Oracle URL specified error...