Uploaded image for project: 'EJB 3.0'
  1. EJB 3.0
  2. EJBTHREE-1002

EJB3-based version of the RetryInterceptor

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • None
    • Clustering
    • None

      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.

            pferraro@redhat.com Paul Ferraro
            bstansbe@redhat.com Brian Stansberry
            Votes:
            5 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: