Yes, with a stateful session bean that makes sense.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3916706#3916706
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3916706
-
Well, does it make sense or not ? Anyone ?...
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3916658#3916658
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3916658
---
Hi
Ultimately, the bean is clustered to support clustering of an HTTPSession
carrying a remote reference to it. Does this make any sense ?
Thanks
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3915787#3915787
Reply to the post :
http://www.jboss.com/index.h
Look at the org.jboss.invocation.InvokerInterceptor. You can write a customized
version to avoid distribution, or write a custom load balancing policy. If you
care about where the calls are going, why is the bean clustered?
View the original post :
http://www.jboss.com/index.html?module=bb&op=
Thanks for answering.
Interesting. I had this (wrong) idea that cluster aware stubs would only be
available via HA-JNDI and that plain JNDI servers would still have old
non-cluster aware stubs.
This raises another problem. In this colocated scenario, it makes no sense to
redirect the request
Where you lookup a proxy should make no difference as the proxy is cluster
aware independent of how its obtained.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3915181#3915181
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=repl
