]
Shaun Appleton updated EJBTHREE-1002:
-------------------------------------
I have received a customer request for this fix.
EJB3-based version of the RetryInterceptor
------------------------------------------
Key: EJBTHREE-1002
URL:
https://jira.jboss.org/jira/browse/EJBTHREE-1002
Project: EJB 3.0
Issue Type: Feature Request
Components: Clustering
Reporter: Brian Stansberry
Assignee: Paul Ferraro
Looking for a conceptual equivalent to the EJB2 RetryInterceptor -- ability to
reestablish a valid remoting client when the current FamilyClusterInfo does not contain
any valid targets.
If the approach is analogous to the RetryInterceptor case, what would be registered in
JNDI is the FamilyClusterInfo itself (rather than the EJB2 Invoker). Looking this up in
JNDI would provide the current list of targets.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: