[jboss-jira] [JBoss JIRA] (WFLY-7209) Operation to list installed Resource Adapters
Guillermo González de Agüero (JIRA)
issues at jboss.org
Thu Sep 29 13:17:00 EDT 2016
[ https://issues.jboss.org/browse/WFLY-7209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13300531#comment-13300531 ]
Guillermo González de Agüero commented on WFLY-7209:
----------------------------------------------------
>From what I saw, it seemed to me that the resource adapter was automatically activated even without the ironjacamar.xml descriptor. I'll have to check it.
My use case is to list the currently deployed resource adapters (activated or not). As it currently works, in the web console you have to specify the deployment or module name by manually typing. This would basically allow graphical UIs to show a list of possible candidates, like it works for JDBC drivers.
As a side note, the resource-adapters subsystem is not listed on deployments (https://wildscribe.github.io/Wildfly/10.0.0.Final/deployment/index.html). Are there any technical reasons for that? Is it only present when there's an iconjacamar.xml descriptor present?
> Operation to list installed Resource Adapters
> ---------------------------------------------
>
> Key: WFLY-7209
> URL: https://issues.jboss.org/browse/WFLY-7209
> Project: WildFly
> Issue Type: Feature Request
> Components: JCA
> Reporter: Guillermo González de Agüero
> Assignee: Stefano Maestri
> Fix For: 10.1.0.Final
>
>
> Currently there's no way to list all the installed Resource Adapters. Only configured resource adapters can be queried. However, they are automatically enabled at deployment time.
> I propose to add a new operation to list installed RAs and their configuration, similar to the one available for JDBC drivers. This would allow HAL to provide a wizard of available options when configuring them.
> The command would be something like: /subsystem=resource-adapters:installed-resource-adapters-list()
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
More information about the jboss-jira
mailing list