[
https://issues.jboss.org/browse/JGRP-1750?page=com.atlassian.jira.plugin....
]
Bela Ban commented on JGRP-1750:
--------------------------------
{{JChannel.setAddressGenerator()}} is very simple now: it doesn't have to take into
account already installed address generators, as all address generators are now stored in
a list.
When the address is generated, if no or only 1 generators are installed, we use it to
generate the address. If we have multiple address generators, we let all of them create an
address. If one of them doesn't create an {{ExtendedUUID}}, we discard it.
Then the first {{ExtendedUUID}} is taken and the data and flags of all other addresses is
added to the first address, which will be returned.
RELAY2 : Address formats are not relayed.
-----------------------------------------
Key: JGRP-1750
URL:
https://issues.jboss.org/browse/JGRP-1750
Project: JGroups
Issue Type: Feature Request
Affects Versions: 3.4.1
Reporter: Karim AMMOUS
Assignee: Bela Ban
Fix For: 3.5
When defining a relay channel, we haven't the ability to set an AddressGenrator.
Indeed, the Relayer uses its own AddressGenerator providing addresses of type SiteUUID.
This is particularly embarrassing in the following case: when we define a customized
address format (like CanBeSiteMasterTopology or TopologyUUID) for members of two Sites A
and B, address format is lost by crossing relay. Address type of messages sent by A to B
are seen as SiteUUID at B side.
Suggestions:
- Making address format "relayable" ?
- Using the same (or an extended format) AddressGenerator of site Channel
--
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