Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

Does JMS require the Java Naming and Directory Interface (JNDI)?

April 26, 2017directory interface Java JMS JNDI naming require

0

Posted

Does JMS require the Java Naming and Directory Interface (JNDI)?

1 Answer

0

Posted

Location: http://www.jguru.com/faq/view.jsp?EID=778 Created: Nov 10, 1999 Modified: 1999-11-10 16:23:38.421 Author: Jerry Smith (http://www.jguru.com/guru/viewbio.jsp?EID=9) No, but… JNDI provides network-oriented look-up services for distributed objects (among other things). It’s possible to implement, as well as use, JMS software without JNDI. In general, however, JNDI provides critical services for JMS-based software because it’s important to be able to locate (programmatically) JMS services implemented in objects called factories. For example, applications that communicate via JMS must set up communication pathways that involve destinations (topic areas and queues), connections, sessions, and so on. JNDI makes it easy for an application to locate, for example, a connection factory for the appropriate vendor’s JMS middleware, which can then provide a connection, which can provide a session, and so on, all relative to the JMS server that’s associated with that connection factory.