[infinispan-issues] [JBoss JIRA] (ISPN-5152) Custom interceptor with Position.OTHER_THAN_FIRST_OR_LAST causes CacheManager start to fail

RH Bugzilla Integration (JIRA) issues at jboss.org
Thu Apr 2 08:14:31 EDT 2015


    [ https://issues.jboss.org/browse/ISPN-5152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13055698#comment-13055698 ] 

RH Bugzilla Integration commented on ISPN-5152:
-----------------------------------------------

Dave Stahl <dstahl at redhat.com> changed the Status of [bug 1182561|https://bugzilla.redhat.com/show_bug.cgi?id=1182561] from VERIFIED to CLOSED

> Custom interceptor with Position.OTHER_THAN_FIRST_OR_LAST causes CacheManager start to fail
> -------------------------------------------------------------------------------------------
>
>                 Key: ISPN-5152
>                 URL: https://issues.jboss.org/browse/ISPN-5152
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Core, Listeners
>    Affects Versions: 7.1.0.Beta1
>            Reporter: Jiří Holuša
>            Assignee: Pedro Ruivo
>             Fix For: 7.2.0.Beta1
>
>
> Use case (done via declarative config, but doesn't matter):
> 1) Add CustomInterceptor1 with position="FIRST"
> 2) Add CustomInterceptor2 with position="LAST"
> 3) Add CustomInterceptor3 with position="OTHER_THAN_FIRST_OR_LAST"
> Expected that order of interceptors 1, 3, 2, or at least it would work. Unfortunately, this configuration fails during start of CacheManager with:
> org.infinispan.commons.CacheConfigurationException: ISPN000225: Custom interceptor 'testpackage.CustomInterceptor3' doesn't specify a position
> Thus (and by looking at the code), option OTHER_THAN_FIRST_OR_LAST doesn't do anything.



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)



More information about the infinispan-issues mailing list