[
https://issues.jboss.org/browse/JGRP-1750?page=com.atlassian.jira.plugin....
]
Bela Ban commented on JGRP-1750:
--------------------------------
[~ammous] Not sure I understand the need for an AddressGenerator to be set in a bridge.
Meanwhile, I created an {{ExtendedAddress}} and {{SiteUUID}} and {{SiteMaster}} are both
subclasses of it, so you can add any data to them.
I modified UnicastTestRpc slightly and used a config containing RELAY2, and data added to
a SiteUUID is actually seen at the receiving end in a different site.
Do you have a small test case that shows your problem ?
(This is on branch JGRP-1750)
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