[jboss-jira] [JBoss JIRA] (WFLY-2403) Cannot disable Datasource or XADatasource in standalone and domain modes

RH Bugzilla Integration (JIRA) jira-events at lists.jboss.org
Mon Nov 11 12:33:05 EST 2013


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

RH Bugzilla Integration commented on WFLY-2403:
-----------------------------------------------

Brian Stansberry <brian.stansberry at redhat.com> made a comment on [bug 970679|https://bugzilla.redhat.com/show_bug.cgi?id=970679]

The CLI command clearly indicates the intent that the datasource be enabled:

[standalone at localhost:9999 /] data-source add --name=Test2 --driver-name=h2 --enabled=true --jndi-name=java:jboss/datasources/Test2 --connection-url=jdbc:h2:mem:test2;DB_CLOSE_DELAY=-1

A big part of the point of high level CLI commands is they should hide all the low level details from the user. So if the intent of the high level command was the datasource should be enabled in the runtime when the command returns, there's a bug that needs fixing.

There's a general issue with CLI high level commands not providing all the response data to the user that low level commands do. But that's beyond the scope of this particular issue.

@Martin: Is the Comment 10 behavior a regression, or something that never behaved the way you expect?
                
> Cannot disable Datasource or XADatasource in standalone and domain modes
> ------------------------------------------------------------------------
>
>                 Key: WFLY-2403
>                 URL: https://issues.jboss.org/browse/WFLY-2403
>             Project: WildFly
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Stefano Maestri
>            Assignee: Stefano Maestri
>
> Description of problem:
> Cannot disable a Datasource or XADatasource in standalone mode. It's back to enabled state after server reload.
> Version-Release number of selected component (if applicable):
> 6.1
> How reproducible:
> Always
> Steps to Reproduce:
> Use the http management interface or the CLI
> 1.Create a Datasource of XADatasource
> 2.Disable it
> 3.The response indicates a server reload is required
> 4.Execute the reload operation
> Actual results:
> The datasource is back to enabled state
> Expected results:
> The datasource should be in disabled state

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the jboss-jira mailing list