[ https://issues.jboss.org/browse/WFLY-2428?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2428: ----------------------------------------------- Ondrej Chaloupka <ochaloup(a)redhat.com&gt; made a comment on [bug 1012044|https://bugzilla.redhat.com/show_bug.cgi?id=1012044] Hi Stefano, You are right and the fix works well. I'm sorry for not putting my intention clearly. I failed the issue from the point of view of the regression against the EAP 6.1.1.GA. In the past release there was needed to use archive name as pointer for the mdb resource adapter name. I mean this works under 6.1.1 (and does not work for 6.2.0). <subsystem xmlns="urn:jboss:domain:ejb3:1.4"> <mdb> <resource-adapter-ref resource-adapter-name="wmq.jmsra.rar"/> <bean-instance-pool-ref pool-name="mdb-strict-max-pool"/> </mdb> ... <subsystem xmlns="urn:jboss:domain:resource-adapters:1.1"> <resource-adapters> <resource-adapter id="wmq-jms-ra-id-name"> <archive>wmq.jmsra.rar</archive> This regression was the original reason of filling this bug. Neverless the prior fix came with another type of problem I was still thinking about the original one. If you consider the current behavior correct then I'm fine with verify the issue. I just worried about different behavior between EAP 6.1.1 and 6.2.0 versions. Thanks Ondra -- 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