[jboss-jira] [JBoss JIRA] (WFCORE-4882) Broken 'domain.xml' after migration of <host-scoped-roles> leading to 'Boostrap error' in HAL

[Chao Wang (Jira)]

    [ https://issues.redhat.com/browse/WFCORE-4882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14005967#comment-14005967 ] 

Chao Wang commented on WFCORE-4882:
-----------------------------------

Looking at the feedback on https://github.com/wildfly/wildfly-core/pull/4105 It seems that an empty list is allowed. Thus, HAL is broken (since 3.0.0.Final) in such configuration. It's not able to properly display the console as a result, see:

 !Screenshot.png|thumbnail! 

I probably should use this one to just fix the inconsistent information in XSD and open another HAL issue for the bug in console  (cc [~harald.pehl] )

> Broken 'domain.xml' after migration of <host-scoped-roles> leading to 'Boostrap error' in HAL
> ---------------------------------------------------------------------------------------------
>
>                 Key: WFCORE-4882
>                 URL: https://issues.redhat.com/browse/WFCORE-4882
>             Project: WildFly Core
>          Issue Type: Bug
>          Components: Management, Server
>    Affects Versions: 11.0.0.Final
>            Reporter: Chao Wang
>            Assignee: Chao Wang
>            Priority: Major
>         Attachments: Screenshot.png
>
>
> When migrating a domain configuration  from JBoss EAP 7.1.6 having a broken {{<host-scoped-roles>}} configuration, the resulting {{domain.xml}} on EAP 7.2 is broken as well.
> JBoss EAP 7.1 is relaxed during accessing the HAL and simply ignores the broken configuration, whereas JBoss EAP 7.2 will not allow access to the HAL and report a *_Bootstrap error_*.
> The {{jboss-server-migration.[sh|bat]}} should identify this broken configuration and *deny* the migration of it.



--
This message was sent by Atlassian Jira
(v7.13.8#713008)