JMS Section Index | Page 11

The JMS specification does not address these issues; hence, vendors are free to implement their own support, and many vendors do provide these services.

The server, message broker, or whatever it is called, functions as an intermediary. Suppose a distributed component wants to send (financial) stock information to one or more remotely located dis...more

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, howev...more

No. An Enterprise JavaBean implements arbitrary server-side functionality using a well-known component architecture. An Enterprise JavaBean is deployed within an EJB server on an arbitrary netwo...more

JMS-based communication is a potential solution in any distributed computing scenario in which you need to pass data, either synchronously or asynchronously, among distributed software components....more

There are several reasons. First, the JMS specification includes two popular messaging strategies: point-to-point and publish/subscribe. Many vendors are supporting this common framework; hence...more

Yes. Prior to JMS, Java software for various distributed computing environments, for example, the WebLogic server, the Aglet framework for mobile agents, SoftWired's iBus software, and many other...more

Message passing is a general term for a variety of strategies for high-level, structured interclient communication. For example, a mobile agent framework could provide classes and methods with wh...more

Java Message Service (JMS) is a specification for message passing and related operations among distributed software components. JMS vendors implement the specification, providing the requisite AP...more