[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=13294798#comment-13294798 ] 

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

After reviewing how detected deployed JDBC drivers are made available at runtime (via :installed-drivers-list), I think what's needed there is just the same. A new operation that exposes all the available resource adapters (that would include ActiveMQ, JBDC and JavaMail ones I guess):
/subsystem=datasources:installed-resource-adapters-list()

Just with that, HAL would be able to present a user with a list of "available" resource adapters and its current settings, with an option to make the configuration persistent by applying it to the management model.


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