You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@aries.apache.org by "Christian Schneider (JIRA)" <ji...@apache.org> on 2017/04/13 10:03:41 UTC

[jira] [Updated] (ARIES-1662) Inconsistent behavior when an interceptor.preCall throws an exception

     [ https://issues.apache.org/jira/browse/ARIES-1662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Christian Schneider updated ARIES-1662:
---------------------------------------
    Fix Version/s: blueprint-core-1.8.0

> Inconsistent behavior when an interceptor.preCall throws an exception
> ---------------------------------------------------------------------
>
>                 Key: ARIES-1662
>                 URL: https://issues.apache.org/jira/browse/ARIES-1662
>             Project: Aries
>          Issue Type: Bug
>          Components: Blueprint
>            Reporter: Thomas Watson
>             Fix For: blueprint-core-1.8.0
>
>
> Depending on if there is only one interceptor or multiple interceptors the class org.apache.aries.blueprint.proxy.SingleInterceptorCollaborator or org.apache.aries.blueprint.proxy.Collaborator gets used.
> When org.apache.aries.blueprint.proxy.Collaborator is used and an interceptor.preCall throws an exception then that same interceptor has its postInvokeExceptionalReturn method called with a null token.  But if the org.apache.aries.blueprint.proxy.SingleInterceptorCollaborator is used then the interceptor is called with a token of org.apache.aries.blueprint.proxy.SingleInterceptorCollaborator.NON_INVOKED
> Before the performance improvement from ARIES-1319 interceptors always got a null token in this situation.  The behavior should be consistent and I think the token should remain null in this case since that was the prior behavior.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)