[jboss-jira] [JBoss JIRA] Updated: (JBAS-2837) When using Cache Invalidation Framework don't remove from cache the specific bean that was changed

[Brian Stansberry (JIRA)]

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

Brian Stansberry updated JBAS-2837:
-----------------------------------

    Fix Version/s: Backlog
                       (was: No Release)


"Backlog" is correct Fix Version; "No Release" is for stuff that logically doesn't belong to a release.

> When using Cache Invalidation Framework don't remove from cache the specific bean that was changed
> --------------------------------------------------------------------------------------------------
>
>                 Key: JBAS-2837
>                 URL: https://jira.jboss.org/jira/browse/JBAS-2837
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Clustering, EJB2
>            Reporter: Brian Stansberry
>            Assignee: Brian Stansberry
>             Fix For: Backlog
>
>
> Currently if an entity bean is modified, the CIF not only invalidates the cache for any local beans in the same invalidation group, but also removes the bean that was changed from the cache.  This reduces the usefulness of commit option A.
> See forum thread for details.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira