[ https://issues.jboss.org/browse/WFLY-10339?page=com.atlassian.jira.plugin... ] Paul Ferraro edited comment on WFLY-10339 at 5/22/18 5:01 PM: -------------------------------------------------------------- [~eduda] I do not intend to require a migration operation. This change should be entirely achievable using normal resource/operation transformations and operation translations. [~jmesnil] I'll plan to address this for WF14. {quote}Could I suggest that we keep the <broadcast|discovery>-group for the JGroups implementation (which is the default we use)?{quote} I would actually recommend against that. Using new path names for both resources makes it easy to distinguish between a legacy CLI command and one intended for the current version of the model - especially since the resource in question heavily relies on optional attributes. This way we can replace the add/remove operation handling with an implementation that redirects/translates the operation to the correct path address. WDYT? was (Author: pferraro): [~eduda] I do not intend to require a migration operation. This change should be entirely achievable using normal resource/operation transformations and operation translations. [~jmesnil] I'll plan to address this for WF14. {quote}Could I suggest that we keep the <broadcast|discovery>-group for the JGroups implementation (which is the default we use)?{quote} I would actually recommend against that. Use new path names for both resources makes it easy to distinguish between a legacy CLI command and one intended for the current version of the model - especially since the resource in question heavily relies on non-required attributes. This way we can replace the add/remove operation handling with an implementation that redirects/translates the operation to the correct path address. WDYT? -- This message was sent by Atlassian JIRA (v7.5.0#75005)