[jboss-jira] [JBoss JIRA] (WFLY-2393) deprecate messaging's -jms.xml deployment
[
https://issues.jboss.org/browse/WFLY-2393?page=com.atlassian.jira.plugin....
]
Stuart Douglas commented on WFLY-2393:
--------------------------------------
The EE deployment descriptors do not provide the same functionality, as -jms.xml files can
be deployed directly, while EE descriptors can only be deployed as part of an archive.
deprecate messaging's -jms.xml deployment
-----------------------------------------
Key: WFLY-2393
URL: https://issues.jboss.org/browse/WFLY-2393
Project: WildFly
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JMS
Affects Versions: 8.0.0.Beta1
Reporter: Jeff Mesnil
Assignee: Jeff Mesnil
Fix For: 8.0.0.CR1
JMS destinations can be deployed using a non-standard -jms.xml description files.
With JMS 2.0 and Java EE7, the same can be achieved in a standard portable way using
jms-destination in Java EE deployment descriptors.
Deprecate the non-standard -jms.xml with a message stating to use the standard descriptor
deployment instead.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira