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

[Thönnes Thönnes (JIRA)]

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

Thönnes Thönnes commented on WFLY-7133:
---------------------------------------

[~ggam], in the documentation I also read that automatic configuration can be done:

{quote}
Automatic activation of resource adapter archives
A resource adapter archive can be automatically activated with a configuration by including an META-INF/ironjacamar.xml in the archive.

The schema can be found at http://docs.jboss.org/ironjacamar/schema/ironjacamar_1_0.xsd
{quote}

This works fine for me. But with regard to a list of available resource adapter to get an overview and to fine tune configuration -- I completely agree with you.
But then the ticket title is misleading.


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