[infinispan-dev] (additional use case for WF8) Removing Infinispan dependency on the Hibernate-Infinispan module in 4.x

[Sanne Grinovero]

My very personal opinion is that if the user requires to "bring his
own" Hibernate jars it is fair enough to require in turn that he
should bring his own cache implementations as well.

It would be nice if we could test that one could then use different
versions of Infinispan & JGroups, properly isolated from the ones WF
provides.

In an ideal world such a different Infinispan version should have the
option to reuse the "main" JGroups channel managed by the AS... but I
realize that is still a long way to go.

Sanne

On 3 June 2013 18:37, Scott Marlow <smarlow at redhat.com> wrote:
> Hi,
>
> I'm responding to this *old thread* to say that Paul's clustering magic
> changes in AS7 resolved the dependency between the AS7 static Infinispan
> module and the Hibernate-Infinispan module.  *Thanks Paul* and others
> for jumping through hoops for that. :)
>
> However, in WF8, I'm catching up on fixing bugs that prevented Hibernate
> 4.x jars from being packaged with the application.  With my local fixes,
> I found that if the Hibernate jars are packaged with the application,
> the WF8 Infinispan module will *not be able to* load the
> Hibernate-Infinispan services (since the application deployment is not
> visible to Infinispan service loading).
>
> Should we push on getting WF8 application deployments that contain the
> Hibernate jars to work with the WF8 (system level) Infinispan module?
>
> Thanks,
> Scott
>
> On 02/08/2012 10:27 AM, Galder Zamarreño wrote:
>> Btw, I'd rather go with Paul's suggestion to modify AS7 Infinispan subsystem.
>>
>> 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
>>>
>>>
>>> _______________________________________________
>>> infinispan-dev mailing list
>>> infinispan-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/infinispan-dev
>>
>> --
>> Galder Zamarreño
>> Sr. Software Engineer
>> Infinispan, JBoss Cache
>>
>
> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/infinispan-dev