[jboss-jira] [JBoss JIRA] (WFLY-6073) WFLY-3551 addition of bv subsystem breaks mixed domain

[Brian Stansberry (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-6073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Stansberry resolved WFLY-6073.
------------------------------------
    Resolution: Won't Fix


I've changed my mind on this.

If a profile including old ee xsd versions is included in a WF 10 domain.xml, there could be two possible scenarios:

1) User wants to migrate that profile for use on WF 10 servers.
2) User wants the profile for use on legacy servers.

If I make the change envisioned here, case 1) will break, as BV will not be in the profile, and the user may not even notice.

If I don't make the change the user will get errors using the profile on the legacy slaves, but they can fix this by removing the subsystem.

Basically, we can't always know the best way to migrate and sometimes need to pick.

WFCORE-1311 was different, as an IO worker is always needed, and the question there was just how to declare the config. Here, BV may or may not be wanted.

> WFLY-3551 addition of bv subsystem breaks mixed domain
> ------------------------------------------------------
>
>                 Key: WFLY-6073
>                 URL: https://issues.jboss.org/browse/WFLY-6073
>             Project: WildFly
>          Issue Type: Bug
>          Components: Domain Management, EE
>    Affects Versions: 10.0.0.CR5
>            Reporter: Brian Stansberry
>            Assignee: Brian Stansberry
>             Fix For: 10.0.0.Final
>
>
> Same problem as WFCORE-1311 -- to assist migration, a ProfileParsingCompletionHandler adds an extension that a legacy slave won't understand.
> I'll do the same thing as I did with WFCORE-1311 -- only do this for a standalone server.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)