[jboss-jira] [JBoss JIRA] (WFLY-1874) Inconsistent access control response structures

[Kabir Khan (JIRA)]

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

Kabir Khan commented on WFLY-1874:
----------------------------------

So the problem with needing a reboot/restart is for it to appear to be a problem in the DS subsystem. When adding the DS is is not enabled. However due to how the datasources subsystem marshals and parses things, after a reboot the new DS appears as enabled. I have fixed that for https://issues.jboss.org/browse/WFLY-1893

The management registration overrides only get registered for enabled datasources, which is why it does not appear in the list when just added as enabled=false, following a reboot enabled=true so it appears in the list. So the question is if we should always add the override so it appears in the list, or if we should make it appear in the list by other means.
                
> Inconsistent access control response structures
> -----------------------------------------------
>
>                 Key: WFLY-1874
>                 URL: https://issues.jboss.org/browse/WFLY-1874
>             Project: WildFly
>          Issue Type: Feature Request
>          Components: Domain Management
>            Reporter: Heiko Braun
>            Assignee: Kabir Khan
>             Fix For: 8.0.0.Beta1
>
>         Attachments: standalone-full-ha.xml
>
>
> Compare the access control meta data for the different rrd() requests:
> a) https://gist.github.com/heiko-braun/6229507
> b) https://gist.github.com/heiko-braun/6229497
> It happens on a system with two datasources confgured (ExampleDS & Test). You can find the server config attached to this issues.
> What we are looking for is a reliable response structure, without any ambiguity.

--
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