-
Bug
-
Resolution: Done
-
Blocker
-
8.0.0.Beta-CR1, 8.0.0.Beta
-
None
-
False
-
None
-
False
-
-
-
-
-
-
-
message-destination-type is ignored in deployment descriptor for MDB. message-destination-type can be set to values {jakarta.jms.Queue}} or {jakarta.jms.Topic}} and should specify type of destination for MDB.
Example of such an ejb-jar.xml:
<?xml version="1.0" encoding="UTF-8"?> <ejb-jar xmlns="http://xmlns.jcp.org/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/javaee http://xmlns.jcp.org/xml/ns/javaee/ejb-jar_3_2.xsd" version="3.2"> <!-- Define the message-driven bean --> <enterprise-beans> <message-driven> <ejb-name>SimpleMdb</ejb-name> <ejb-class>SimpleMdb</ejb-class> <transaction-type>Container</transaction-type> <messaging-type>javax.jms.MessageListener</messaging-type> <message-destination-type>javax.jms.Topic</message-destination-type> </message-driven> </enterprise-beans> </ejb-jar>
This was not hit with Artemis/AMQ7 resource adapter as it's able to derive type of destination when not set. This is the reason why TCK 10 tests do not fail. But IBM MQ 9 resource adapter is not doing it and relies on it to set type of destination.
This issue is causing failure in TCK 10 test for IBM MQ 9 RA (this is where it was observed by there are many more - TBD):
com/sun/ts/tests/jms/ee/mdb/xa/MDBClient.java#Test2
- is cloned by
-
WFLY-18380 message-destination-type in ejb-jar.xml is ignored
- Closed