David Lloyd [
http://community.jboss.org/people/dmlloyd] created the discussion
"Re: Remote txinflow: XID changes"
To view the discussion, visit:
http://community.jboss.org/message/632591#632591
--------------------------------------------------------------
Tom Jenkinson wrote:
> Jonathan Halliday wrote:
>
> > In either scenario, the administrator is going to need to keep a mapping file.
Either remoting node identifier to transaction manager node name (my preference) or EIS
name to EIS int key.
>
> That's not quite right. EIS names are scoped to the node and the mapping can be
maintained programmatically by e.g. the JCA xa recovery plugin registration code. The
nodeIdentifier is potentially enterprise (or at least data centre) scoped and needs manual
coordination and maintenance or some centralized/hierarchic registry service to manage
uniqueness. Than again so does allocation of a uniq string node name in the first place.
Agree with you here, the scope of the EIS name needs to be unique within the node, so it
can be shorter. I think I maybe wasn't 100% clear but what I mean for EIS name was
administrator would still need to keep a mapping of EIS JNDI name to EIS "short"
name which is what I meant by keeping a mapping file in that scenario. At the moment the
EIS name is read from the JCA configuration that says "jndi-data-source-name"
basically (typically). If we no longer use that value then basically an extra bit of
configuration (which I was terming mapping) must be held to say for XYZ data source it has
a JNDI name of "foo" and a XAResourceWrapper identifier of "bar" -
well, most likely a shorter version of foo ;)
From the Remoting perspective, the EIS name would most likely just be the full node name
of the calling node. If I mix these two up in the future, this is why. :)
--------------------------------------------------------------
Reply to this message by going to Community
[
http://community.jboss.org/message/632591#632591]
Start a new discussion in JBoss Transactions Development at Community
[
http://community.jboss.org/choose-container!input.jspa?contentType=1&...]