[jboss-jira] [JBoss JIRA] (WFLY-4011) Resource adapter config properties cannot be changed without two reloads

[Scott Van Wart (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-4011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Scott Van Wart updated WFLY-4011:
---------------------------------
    Attachment: remove-add.txt
                remove-reload-add.txt


My two attempts at non-interactively updating an inbound RA config property in the resource-adapters subsystem.

> Resource adapter config properties cannot be changed without two reloads
> ------------------------------------------------------------------------
>
>                 Key: WFLY-4011
>                 URL: https://issues.jboss.org/browse/WFLY-4011
>             Project: WildFly
>          Issue Type: Enhancement
>          Components: JCA
>    Affects Versions: 8.1.0.Final
>         Environment: Ubuntu 14.0.4 64-bit; JDK 1.8.0_25; Wildfly 8.1.0.Final standalone
>            Reporter: Scott Van Wart
>            Assignee: Jesper Pedersen
>            Priority: Minor
>              Labels: cli, resource-adapter
>         Attachments: remove-add.txt, remove-reload-add.txt
>
>
> I have a RAR deployed within an EAR file and it defines a config property "host" in the resource-adapter subsystem.  I followed the binding instructions here:
> https://docs.jboss.org/author/display/WFLY8/Resource+adapters
> If I want to change the "host" configuration property, I need to do the following:
>   1. Remove the configuration property.
>   2. Reload
>   3. Add the configuration property back.
>   4. Reload
> The "value" attribute of the config property isn't writable (JCA doesn't communicate config property changes during runtime): https://issues.jboss.org/browse/WFLY-3729
> Trying to add the property again after removal results in an error as Wildfly believes the attribute still exists if you haven't reloaded since removal.
> This makes scripting a resource adapter property change difficult, as the "reload" command returns immediately and a script must wait an unknown amount of time for the management interface to become available before it can issue new commands.



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)