]
Jeff Mesnil moved EAP7-1013 to WFLY-10493:
------------------------------------------
Project: WildFly (was: EAP 7 Planning Pilot)
Key: WFLY-10493 (was: EAP7-1013)
Issue Type: Feature Request (was: Requirement)
Workflow: GIT Pull Request workflow (was: EAP Agile Workflow
2.0)
Component/s: JMS
(was: JMS)
(was: OpenShift)
Target Release: (was: 7.2.0.GA)
Jirban PT Community Docs (CD): (was: TODO)
Jirban PT Product Docs (PD): (was: New)
Jirban PT Test Dev (TD): (was: TODO)
Jirban PT Docs Analysis (DA): (was: TODO)
Jirban PT Test Plan (TP): (was: TODO)
Jirban PT Analysis Document (AD): (was: TODO)
Writer: (was: Chuck Copello)
Support JMS Java EE resources definition for remote Artemis-based
broker
-------------------------------------------------------------------------
Key: WFLY-10493
URL:
https://issues.jboss.org/browse/WFLY-10493
Project: WildFly
Issue Type: Feature Request
Components: JMS
Reporter: Jeff Mesnil
Assignee: Jeff Mesnil
The Java EE7 specifies annotation and XML configuration to define JMS resources
(connection factories, queues and topics), for example the application can use
https://docs.oracle.com/javaee/7/api/javax/jms/JMSDestinationDefinition.html to define a
JMS destination.
This support is provided by the messaging-activemq subsystem.
If the resourceAdapter property is not specified, the resources are created by the
Artemis broker embedded in WildFly.
If the resourceAdapter property is specified, the messaging-activemq subsystem delegates
to IronJacamar that uses the Resource Adapter's admin objects to create the JMS
resources.
There is one use case that is not supported by the current state: define JMS resources to
communicate with a remote Artemis-based broker (such as AMQ 7).
This RFE addresses this missing use case.