[jboss-jira] [JBoss JIRA] (WFLY-4755) datasource:enable() operation lacks reload-requires state

[Stefano Maestri (JIRA)]

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

Stefano Maestri commented on WFLY-4755:
---------------------------------------

Well, I'm going to reject this issue for various reasons:

- both operations and attribute are deprecated because it's the RUNTIME stage concepts enabled/disabled to be deprecated and it will be removed from upstrema very soon w/ WFLY-4294
- it's correct to don't require a reload enabling a DS in disabled state. The bug could be on attribute, not in operation. It's in fact deploying a new DS, don't need to kill connections or whatever
- it's correct to require a reload on an enabled resource if you don't use {allow-resource-service-restart=true}. It need to kill connections and other things.

Feel free to contact me w/ private email/chat if you need any further depp dive on what is changing in DSes w/ WFLY-4294
regards
S.

> datasource:enable() operation lacks reload-requires state 
> ----------------------------------------------------------
>
>                 Key: WFLY-4755
>                 URL: https://issues.jboss.org/browse/WFLY-4755
>             Project: WildFly
>          Issue Type: Bug
>          Components: JCA
>            Reporter: Harald Pehl
>            Assignee: Stefano Maestri
>
> Executing {{:disable()}} on an enabled datasource sets the {{reload-requires}} state. This is in sync with changing the attribute directly using {{:write-attribute(name=enabled,value=false}} (which is deprecated).
> However {{:enable()}} on a disabled datasource does not set the {{reload-requires}} state. Whereas {{:write-attribute(name=enabled,value=true}} does.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)