[JBoss JIRA] (WFLY-7133) Automatically define resource adapter for deployed RARs
by Guillermo González de Agüero (JIRA)
[ https://issues.jboss.org/browse/WFLY-7133?page=com.atlassian.jira.plugin.... ]
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)
9 years, 7 months
[JBoss JIRA] (WFLY-7209) Operation to list installed Resource Adapters
by Guillermo González de Agüero (JIRA)
Guillermo González de Agüero created WFLY-7209:
--------------------------------------------------
Summary: 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: Jesper Pedersen
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)
9 years, 7 months
[JBoss JIRA] (WFCORE-1821) Failures in ModuleOpsCompletionTestCase
by Brian Stansberry (JIRA)
Brian Stansberry created WFCORE-1821:
----------------------------------------
Summary: Failures in ModuleOpsCompletionTestCase
Key: WFCORE-1821
URL: https://issues.jboss.org/browse/WFCORE-1821
Project: WildFly Core
Issue Type: Bug
Components: Test Suite
Reporter: Brian Stansberry
Assignee: ehsavoie Hugonnet
Failed tests:
ModuleOpsCompletionTestCase.testModuleAddCompletionSuggestions:56->testSuggestion:146->testSuggestion:153 expected:<[org, ibm, io, javax, org, sun]> but was:<[ibm, io, javax, org, sun]>
There's already a PR that's probably meant to fix this but it isn't passing CI. I'm going to @Ignore this test.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (WFCORE-1820) Use MRR-driven capability registration for the management interface capabilities
by Brian Stansberry (JIRA)
Brian Stansberry created WFCORE-1820:
----------------------------------------
Summary: Use MRR-driven capability registration for the management interface capabilities
Key: WFCORE-1820
URL: https://issues.jboss.org/browse/WFCORE-1820
Project: WildFly Core
Issue Type: Enhancement
Components: Domain Management
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Priority: Minor
Currently the registration of runtime capabilities for the management interfaces is being done in the add handlers instead of by the MRR. This is fragile as it's non-standard and makes it more difficult to add other capabilities, since registering via the handler turns off registration via the MRR.
WFCORE-1819 is needed to fix this.
This is arguably a bug but I'll call it an enhancement for now. It's just making the code better.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (WFCORE-1819) Allow collections kept by SimpleResourceDefinition.Parameters to be appended
by Brian Stansberry (JIRA)
Brian Stansberry created WFCORE-1819:
----------------------------------------
Summary: Allow collections kept by SimpleResourceDefinition.Parameters to be appended
Key: WFCORE-1819
URL: https://issues.jboss.org/browse/WFCORE-1819
Project: WildFly Core
Issue Type: Enhancement
Components: Domain Management
Reporter: Brian Stansberry
Assignee: Brian Stansberry
The Parameters object is meant to be built with a builder and then passed into SimpleResourceDefinition constructors. It is useful for scenarios where RD's are based on subclassing to let the superclass *add* items to the passed in set of access constraints, capabilities and incorporating capabilities instead of forcing the subclass constructor itself to manually read existing values, create new collections with added values, and then re-set the overall collection.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months