[infinispan-issues] [JBoss JIRA] (ISPN-2341) event.isPre has a counter intuitive behaviour

[Mircea Markus (JIRA)]

     [ https://issues.jboss.org/browse/ISPN-2341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mircea Markus updated ISPN-2341:
--------------------------------

        Description: 
When the listener is notified with (event.isPre == false), the change that triggered the event is not visible to the user as the notification happens before exiting the EntryWrappingInterceptor.

For all types of notifications, when event.isPre==false, the modification should be visible into the cache. OTHO when event.isPre == true the modification shouldn't be visible.

  was:
When the listener is notified with (event.isPre == false), the change that triggered the event is not visible to the user[1] as the notification happens before exiting the EntryWrappingInterceptor.

For all types of notifications, when event.isPre==false, the modification should be visible into the cache. OTHO when event.isPre == true the modification shouldn't be visible.

    Forum Reference: https://community.jboss.org/thread/205515

    
> event.isPre has a counter intuitive behaviour
> ---------------------------------------------
>
>                 Key: ISPN-2341
>                 URL: https://issues.jboss.org/browse/ISPN-2341
>             Project: Infinispan
>          Issue Type: Feature Request
>          Components: Listeners
>    Affects Versions: 5.1.7.Final
>            Reporter: Mircea Markus
>            Assignee: Mircea Markus
>             Fix For: 6.0.0.Final
>
>
> When the listener is notified with (event.isPre == false), the change that triggered the event is not visible to the user as the notification happens before exiting the EntryWrappingInterceptor.
> For all types of notifications, when event.isPre==false, the modification should be visible into the cache. OTHO when event.isPre == true the modification shouldn't be visible.

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