[jboss-jira] [JBoss JIRA] (WFLY-2383) resource-adapter id attribute has to match ra name otherwise MDB is not deployed

[RH Bugzilla Integration (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-2383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12922391#comment-12922391 ] 

RH Bugzilla Integration commented on WFLY-2383:
-----------------------------------------------

Ondrej Chaloupka <ochaloup at redhat.com> made a comment on [bug 1012044|https://bugzilla.redhat.com/show_bug.cgi?id=1012044]

Ok, it seems that this works for creating modules but this does not work for archive deployments.

You have to set the id of resource adapter to name of archive with or without ".rar". Otherwise the rar is not loaded for the MDB.
But I would suppose that it should be possible to set whatever string to the id.
At least it worked in EAP 6.1.1.GA.

When you configure resource adapter as archive then you can set it like:
<subsystem xmlns="urn:jboss:domain:ejb3:1.4">
 <mdb>
  <resource-adapter-ref resource-adapter-name="activemq.file.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="activemq.file">
  <!-- OR <resource-adapter id="activemq.file.rar"> -->
   <archive>activemq.file.rar</archive>
                
> resource-adapter id attribute has to match ra name otherwise MDB is not deployed
> --------------------------------------------------------------------------------
>
>                 Key: WFLY-2383
>                 URL: https://issues.jboss.org/browse/WFLY-2383
>             Project: WildFly
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Stefano Maestri
>            Assignee: Stefano Maestri
>
> The resource-adapter id has to have the same name as the ra archive has. Otherwise the the MDB is not deployed. 

--
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