Programming to use JMS and messaging directly > Programming to use asynchronous messaging >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 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 Version 5) are supported only to provide compatibility for applications that have already been implemented to use those interfaces.
Table 1. The Point-to-Point and Publish/Subscribe versions of 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
Related tasks
Programming to use message-driven beans
Develop applications to use JMS directly
Related
JMS and WebSphere MQ message structures