[jboss-jira] [JBoss JIRA] Commented: (JBAS-3765) AOP-based version of RetryInterceptor

[Galder Zamarreño (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBAS-3765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12461257#action_12461257 ] 

Galder Zamarreño commented on JBAS-3765:
----------------------------------------

A workaround for the lack of this feature would for EJB3 clients to retry JNDI lookup on a catch section.

> AOP-based version of RetryInterceptor
> -------------------------------------
>
>                 Key: JBAS-3765
>                 URL: https://jira.jboss.org/jira/browse/JBAS-3765
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Clustering, EJB2, EJB3, Remoting
>            Reporter: Brian Stansberry
>            Assignee: Galder Zamarreño
>             Fix For: Backlog
>
>
> The (Single)RetryInterceptor only works for EJB 2.  Need to:
> 1) Create a version that uses the AOP interceptor model rather than org.jboss.invocation.
> 2) Ensure all proxy factories bind an InvokerLocator in JNDI and include in the proxy metadata the location of the binding.
> 3) Add the interceptor to the various interceptor stack configs.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira