[ https://issues.jboss.org/browse/WFLY-9360?page=com.atlassian.jira.plugin.... ] Jeff Mesnil commented on WFLY-9360: ----------------------------------- TCK 7 tests that are fixed by the Generic JMS RA 2.0.1.Final: * [core.queueConnection] * fixed by https://github.com/jms-ra/generic-jms-ra/pull/20 * [core.topicConnection] * fixed by https://github.com/jms-ra/generic-jms-ra/pull/20 * [jms.ee.ejb.sessionTtests] * clientID not set on the pooled-connection-factory dscf => requires change to the standalone-full-tck7 configuration * [jms.ee.mdb.xa] * NOT FIXED * related to JBEAP-13128 - Tibco 8 XA CF does not allow to create plain JMS Context * session will be non-xa or xa depending on an active tx. But Tibco 8 XA CF can not create plain JMS Context (that is created when the managed connection will create JMS resources (session & jms * [core20] * JMSSecurityException fixed by https://github.com/jms-ra/generic-jms-ra/pull/21 * [ee20.cditests] * some are NOT FIXED (caused by JBEAP-13128 - Tibco 8 XA CF does not allow to create plain JMS Context) -- This message was sent by Atlassian JIRA (v7.2.3#72005)