[jboss-jira] [JBoss JIRA] (WFLY-7871) Decouple backup/site name from the name of the corresponding resource

[Galder Zamarreño (JIRA)]

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

Galder Zamarreño commented on WFLY-7871:
----------------------------------------

I was wondering whether, to be consistent we could name backup's {{site}} as {{site-name}}. Since normally backup site-name and remote-site site-name would be the same. E.g.

{code}
<backups>
    <backup name="remote" site-name="${...}" strategy="SYNC"/>
</backups>
 
<relay site="local">
    <remote-site name="local" site-name="${...}" channel=".."/>
    <remote-site name="remote" site-name="${...}" channel=".."/>
</relay>
{code}

WDYT?

> Decouple backup/site name from the name of the corresponding resource
> ---------------------------------------------------------------------
>
>                 Key: WFLY-7871
>                 URL: https://issues.jboss.org/browse/WFLY-7871
>             Project: WildFly
>          Issue Type: Feature Request
>          Components: Clustering
>    Affects Versions: 10.1.0.Final
>            Reporter: Paul Ferraro
>            Assignee: Paul Ferraro
>             Fix For: 11.0.0.Beta1
>
>
> Currently, the site names defined in the JGroups subsystem RELAY2 protocol, and the backup names defined in the Infinispan subsystem do not allow expressions, since these name are used for the corresponding resource paths. To simplify the use of cross-site replication (specifically, to allow each site to use an identical domain.xml/standalone.xml), we can support expressions if we decouple the site name from the resource name.
> e.g. 
> {noformat}
> <backups>
>     <backup name="remote" site="${...}" strategy="SYNC"/>
> </backups>
> <relay site="local">
>     <remote-site name="local" site-name="${...}" channel=".."/>
>     <remote-site name="remote" site-name="${...}" channel=".."/>
> </relay>
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)