dcsimg
JNDI
1 posts in topic
Flat View  Flat View
TOPIC ACTIONS:
 

Posted By:   Varsha_Mathur
Posted On:   Thursday, May 9, 2002 11:38 PM

What actually JNDI looks for:
(a)Stub Object
(b)Skeleton Object
(c)Implementation Object
(d)Server Object

Re: JNDI

Posted By:   Bozidar_Dangubic  
Posted On:   Friday, May 10, 2002 06:07 AM

it depends varsha. it depends on the implementation and on how you define certain things. for instance, what is the definition of "Server Object"? there is no such thing as "Server Object" unless you define that every object which executes on the server is a "Server Object". in that case, the answer is d) because JNDI lookups are done on some server and therefore every object bound to JNDI is a server object. however, any one of a), b), c), or d) could be bound to a JNDI. JNDI is a naming a directory lookup interface. it allows developers to store object under certain name which clients of the object will use to retrieve it. now it probably does not make much sense to store Stub (I am guessing you are talking about RMI Stub) in the JNDI because it is a client Stub and has no purpose on the server, but nothing can prevent you from doing it since it is just another java class...
About | Sitemap | Contact