[jboss-jira] [JBoss JIRA] (WFLY-7133) Automatically define resource adapter for deployed RARs

[Guillermo González de Agüero (JIRA)]

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

Guillermo González de Agüero commented on WFLY-7133:
----------------------------------------------------

[~jthoennes] Yes, but you have to manually define it in the subsystem in order to see it. And for that you have to manually configure it. And if it comes with an ironjacamar.xml, it doesn't make sense to manually reconfigure it, potentially with different and wrong settings. But I guess what I requested is not technically viable at all. If the adapter would be created at deployment time, it would also need to be deleted when undeploying. Doesn't seem very robust.

I created the ticket before checking how the JDBC drivers par work. After that I realized that the new operation I mention could do the trick. I've created WFLY-7209 for that.

> Automatically define resource adapter for deployed RARs
> -------------------------------------------------------
>
>                 Key: WFLY-7133
>                 URL: https://issues.jboss.org/browse/WFLY-7133
>             Project: WildFly
>          Issue Type: Feature Request
>          Components: JCA
>    Affects Versions: 10.1.0.Final
>            Reporter: Guillermo González de Agüero
>            Assignee: Jesper Pedersen
>
> Deploying a RAR file enables the resource adapter for the server, but in order to configure it, you must manually add it to the Resource Adapters subsystem. This is error prone (you can put in invalid "archive name" for the resource adapter and it doesn't complaint) and little user friendly.
> From a user perspective and from what can be read from the documentation (https://docs.jboss.org/author/display/WFLY10/Resource+adapters), it seems like the resource adapter is not enabled unless you explicitly define it.
> It would be very simpler if RA deployments would be detected and registered as it's done for deployed JDBC drivers.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)