Btw, I'd rather go with Paul's suggestion to modify AS7 Infinispan subsystem.
Also, reverting to the old way of using the cache as a notification bus won't work as
is because it relied on using the same cache as for entiies/collections, and it relied on
5.0.x or before logic that caches could be both transactional and non-transactional.
So, the only way to deal with this would be to have 1 extra cache per entity/collection to
deal with this evictions, which is sucky to say the least…
Cheers,
On Feb 8, 2012, at 4:25 PM, Galder Zamarreño wrote:
Scott, what do you suggest doing instead then? Without the commands,
evictAll invalidation won't work.
Are you suggesting that I revert back to using the cache as a notification bus so that
regions are invalidated?
On Feb 8, 2012, at 4:13 PM, Scott Marlow wrote:
>
http://lists.jboss.org/pipermail/infinispan-dev/2012-February/010125.html has more
context.
>
> Since there are no easy/quick fixes that can be applied at this time, to remove the
AS7 Infinispan dependency on the Hibernate-Infinispan module, I think we should avoid
depending on the service loader way to supply the custom commands (in the
Hibernate-Infinispan module), at least until this can be addressed elsewhere.
>
> I propose that the Hibernate-Infinispan second level cache should not use the Service
Loader to pass custom commands into Infinispan. If we agree, I'll create a jira for
this.
>
> Scott
--
Galder Zamarreño
Sr. Software Engineer
Infinispan, JBoss Cache
--
Galder Zamarreño
Sr. Software Engineer
Infinispan, JBoss Cache