Jakarta Messaging 3.0

This feature enables the configuration of resource adapters to access messaging systems using the Jakarta Messaging API. This feature also enables the configuration of Jakarta Messaging connection factories, queues, topics, and activation specifications. Any Jakarta Messaging resource adapter that complies with the Jakarta Connectors 2.0 specification can be used.

Enable this feature

To enable the Jakarta Messaging 3.0 feature, add the following element declaration into server.xml, inside the featureManager element:

<feature>messaging-3.0</feature>

Feature configuration elements

• activationSpec
• adminObject
• application
• applicationManager
• applicationMonitor
• authData
• classloader
• classloading
• connectionFactory
• connectionManager
• javaPermission
• jmsActivationSpec
• jmsConnectionFactory
• jmsDestination
• jmsQueue
• jmsQueueConnectionFactory
• jmsTopic
• jmsTopicConnectionFactory
• kerberos
• library
• resourceAdapter
• transaction

Standard API packages provided by this feature

• jakarta.jms
• jakarta.resource
• jakarta.resource.cci
• jakarta.resource.spi
• jakarta.resource.spi.endpoint
• jakarta.resource.spi.security
• jakarta.resource.spi.work

Liberty API packages provided by this feature

• com.ibm.ws.jca.cm.mbean

Features that this feature enables

• connectors-2.0
• xmlBinding-3.0

Supported Java versions

• JavaSE-1.8
• JavaSE-11.0
• JavaSE-17.0
• JavaSE-21.0
• JavaSE-24.0

Platform Versions

• jakartaee-9.1

Features that enable this feature

• jakartaee-9.1

Develop a feature that depends on this feature

If we are developing a feature that depends on this feature, include the following item in the Subsystem-Content header in your feature manifest file.

io.openliberty.messaging-3.0; type="osgi.subsystem.feature"