[
https://issues.apache.org/jira/browse/OWB-570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg resolved OWB-570.
-------------------------------
Resolution: Won't Fix
Assignee: Mark Struberg (was: Gurkan Erdogdu)
I again looked at the interceptors spec and it is NOT said that the container
must take care of this! A user could store away the InvocationContext parameter
himself and 'restore' it prior to re-trying.
> Interceptors must support retry
> -------------------------------
>
> Key: OWB-570
> URL: https://issues.apache.org/jira/browse/OWB-570
> Project: OpenWebBeans
> Issue Type: Bug
> Components: Interceptor and Decorators
> Affects Versions: 1.0.0
> Reporter: Marius Bogoevici
> Assignee: Mark Struberg
> Fix For: 1.2.0
>
>
> Noticed when using OWB 1.0, apparently the issue is not fixed in 1.1 by
> looking at the code.
> In the Interceptors specification it is said that around-invoke and
> around-timeout interceptors are allowed to catch and suppress exceptions and
> recover by calling proceed(). Essentially this means that the state of the
> InvocationContext and associated interceptor chain must be restored to the
> state before the execution of the proceed() method, so that the following
> interceptors execute consistently upon recovery.
> However, the InvocationContext will not reset the state upon returning from
> the call (in the try block), which means that all the interceptors that have
> successfully executed in the initial call will be omitted on recovery.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
