"bstansberry jboss.com" wrote : A minor limitation
of this is the tpc/target map is stored as a static field in
the invoker proxy. So, if two beans involved in the tx use
different proxy types (say unified and pooled), the chosen
server won't be the same. There's no real good way around
this, since use of different proxy types implies different
invokers on the server side, and hence different sets of
targets.
|
| The above comment is meant for the tiny fine print at
the bottom of the documentation of this.
As far as 4.2 is concerned, JRMP/Pooled and Unified invokers
exist although the default ones are Unified. JRMP/Pooled are
legacy so is there any reason why customers would want to
use these? I'd expect for Unified to be at least as good as
JRMP/Pooled, but I can see customers wanting to stick their
environment to what it was like in 4.0.x, i.e. having as
less changes as possible.
I haven't checked the trunk codebase, but the descriptors in
trunk don't even show the JRMP/Pooled invokers.
To sum up, +1 on fine print
View the original post : http://www.jboss.com/index.html?
module=bb&op=viewtopic&p=4080071#4080071
Reply to the post : http://www.jboss.com/index.
html?module=bb&op=posting&mode=reply&p=4080071
a>
_______________________________________________
jboss-dev-forums mailing list
jboss-dev-forums lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-dev-foru
ms
|