[infinispan-issues] [JBoss JIRA] (ISPN-2766) Improve and adapt notification model to fit JSR107 notification model

[Galder Zamarreño (JIRA)]

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

Galder Zamarreño commented on ISPN-2766:
----------------------------------------

To summarise some of the issues highlighted in the mailing list:
* When an entry is created, no cache entry updated/modified events must be fired. Since JSR-107 notifications only support one callback, this should be done after the event, but with CacheEntryModified event, you only know if the event was for an entry created or not when isPre=false. Adding an isCreated() to CacheEntryModifiedEvent should just work.
                
> Improve and adapt notification model to fit JSR107 notification model
> ---------------------------------------------------------------------
>
>                 Key: ISPN-2766
>                 URL: https://issues.jboss.org/browse/ISPN-2766
>             Project: Infinispan
>          Issue Type: Sub-task
>          Components: Listeners
>    Affects Versions: 5.2.0.CR3
>            Reporter: Vladimir Blagojevic
>            Assignee: Galder Zamarreño
>             Fix For: 6.0.0.Final
>
>
> Out current notification (listener) model does not fit JSR 107 notification model and thus needs a slight adaptation in order to implement JSR 107. 
> More specifically the problem is with JSR107 CacheEntryCreatedListener and CacheEntryExpiredListener.
> The first one is not easy to implement because we need both key/value pair for jsr listener and our CacheEntryCreatedEvent does not provide value. 
> The second is related to CacheEntryExpired event. True, spec is not rigorous that such an event has to be fired immediately after an entry has expired but eventually (which might be on access). However, we do not have such an event at all as of now.
>   

--
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