[jboss-jira] [JBoss JIRA] (WFLY-6504) [Migration operation] wrong resource address in migration warning

[Jeff Mesnil (JIRA)]

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

Jeff Mesnil moved JBEAP-4130 to WFLY-6504:
------------------------------------------

              Project: WildFly  (was: JBoss Enterprise Application Platform)
                  Key: WFLY-6504  (was: JBEAP-4130)
             Workflow: GIT Pull Request workflow   (was: CDW with loose statuses v1)
          Component/s: JMS
                           (was: Domain Management)
                           (was: JMS)
                           (was: Migration)
       Target Release:   (was: 7.backlog.GA)
    Affects Version/s: 10.0.0.Final
                           (was: 7.0.0.ER7)


> [Migration operation] wrong resource address in migration warning
> -----------------------------------------------------------------
>
>                 Key: WFLY-6504
>                 URL: https://issues.jboss.org/browse/WFLY-6504
>             Project: WildFly
>          Issue Type: Bug
>          Components: JMS
>    Affects Versions: 10.0.0.Final
>            Reporter: Jeff Mesnil
>            Assignee: Jeff Mesnil
>
> Say I take EAP 6.4 default {{standalone-full.xml}} and add a discovery group like this:
> {code:xml}
> <subsystem xmlns="urn:jboss:domain:messaging:1.4">
>     <hornetq-server>
>         ...
>         <discovery-groups>
>              <discovery-group name="my-discovery-group">
>                 <group-address>224.0.1.105</group-address>
>                 <group-port>56789</group-port>
>              </discovery-group>
>         </discovery-groups>
>         ...
>     </hornetq-server>
> </subsystem>
> {code}
> This is the only change I make to the configuration file. Then I try to migrate the {{messaging}} subsystem, expecting a migration warning that I should use the {{socket-binding}} attribute.
> The warning appears indeed:
> {code}
> [standalone at localhost:9999 /] /subsystem=messaging:migrate
> {
>     "outcome" => "success",
>     "result" => {"migration-warnings" => [
>         "WFLYMSG0084: Can not migrate attribute group-address from resource [
>     (\"subsystem\" => \"messaging-activemq\"),
>     (\"server\" => \"default\"),
>     (\"discovery-group\" => \"my-discovery-group\")
> ]. Use instead the socket-binding attribute to configure this discovery-group.",
>         "WFLYMSG0084: Can not migrate attribute group-port from resource [
>     (\"subsystem\" => \"messaging-activemq\"),
>     (\"server\" => \"default\"),
>     (\"discovery-group\" => \"my-discovery-group\")
> ]. Use instead the socket-binding attribute to configure this discovery-group."
>     ]}
> }
> {code}
> But the resource addresses in the warning are wrong. They refer to the {{messaging-activemq}} subsystem, which clearly isn't what I'm migrating _from_, it's what I'm migrating _to_.
> I understand from the code that the DMR structure of the old subsystem model is very close to the structure of the new subsystem model, which is why these warning are produced on an already translated structure, but it generates wrong warnings.
> CC [~mnovak].



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