Network Deployment (Distributed operating systems), v8.0 > Reference > Developer detailed usage information
JMS interfaces
WAS supports applications that use JMS 1.1 domain-independent interfaces (referred to as "common interfaces" in the JMS specification) and JMS 1.0.2 domain-specific interfaces.
With JMS 1.1, the preferred approach for implementing applications is to use common interfaces because they provide a simpler programming model than domain-specific interfaces. Also, applications can create both queues and topics in the same session and coordinate their use in the same transaction. Common interfaces are parents of domain-specific interfaces.
Domain-specific interfaces (provided for JMS 1.0.2 in WAS v5) are supported only to provide compatibility for applications that have already been implemented to use those interfaces.
The point-to-point and publish/subscribe versions of JMS common interfaces. The first column of the table lists the JMS common interfaces. The second column lists the point-to-point versions of the JMS common interfaces. The third column lists the publish/subscribe versions of the JMS common interfaces.
JMS common interfaces Point-to-point interfaces Publish/subscribe interfaces ConnectionFactory QueueConnectionFactory TopicConnectionFactory Connection QueueConnection TopicConnection Destination Queue Topic Session QueueSession TopicSession, MessageProducer QueueSender TopicPublisher MessageConsumer QueueReceiver,
QueueBrowserTopicSubscriber For more information about JMS interfaces, see the JMS documentation at http://java.sun.com/products/jms/docs.html.
Program to use message-driven beans
Program to use JMS and messaging directly
Program to use asynchronous messaging