[jboss-jira] [JBoss JIRA] (WFLY-2956) Port version 1.6 of the management schema upstream.

[Brian Stansberry (JIRA)]

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

Brian Stansberry commented on WFLY-2956:
----------------------------------------

FYI: to solve the linear progression issue I evaluated simply dropping 1.6 and making it a 2.1. It won't work due to 1 attribute: "http-upgrade-enabled" on the http-interface elements. :(

I'm tempted to switch EAP 6 HTTP management to undertow.

Just kidding; I have many other higher value tasks.
                
> Port version 1.6 of the management schema upstream.
> ---------------------------------------------------
>
>                 Key: WFLY-2956
>                 URL: https://issues.jboss.org/browse/WFLY-2956
>             Project: WildFly
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Domain Management
>            Reporter: Darran Lofthouse
>            Assignee: Darran Lofthouse
>            Priority: Critical
>             Fix For: 9.0.0.CR1
>
>
> EAP will be introducing version 1.6 of the management schema, this needs porting upstream.
> At the same point the coding convention we have adopted has been based around a linear progression of the configuration schemas, when version 1.5 was ported this still worked as 1.5 contained a subset of the changes that went into 2.0.  
> 1.6 is going to be a special case as it will build on 1.5 so is already a subset of 2.0 but will also only contain a subset of changes that go into 3.0 - the risk however is our switch statements are built around dropping into a default block that is hit for all schema versions not explicitly listed.

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