On 8 February 2012 04:14, Scott Marlow <smarlow(a)redhat.com> wrote:
On 02/07/2012 10:25 AM, Sanne Grinovero wrote:
>
> On 7 February 2012 15:21, Scott Marlow<smarlow(a)redhat.com> wrote:
>>
>> On 02/07/2012 10:07 AM, Sanne Grinovero wrote:
>>>>>
>>>>> I'm not that worried about OGM (unless someone wants double
buffering
>>>>> ;), its more about users wanting to package in different versions
in
>>>>> Hibernate (newer/older).
>>>
>>> Even if someone wanted double buffering, OGM was already upgraded to
>>> use Hibernate 4, so this doesn't apply.
>>>
>>>
>>
>> I think it depends on whether OGM will always work with the Hibernate
>> 4.x version that is used in AS 7.x. If OGM moves forward (Hibernate
>> version wise) and starts requiring a different version than the one that
>> is static wired into the Infinispan module, the user might want multiple
>> Hibernate 4.x versions to be wired into the Infinispan module. I'm not
>> sure but if Infinispan has multiple versions of Hibernate in its
>> classpath, that probably would interfere with the custom commands (I
>> would think).
>
>
> Good point. It's unlikely for OGM to need a 2nd level cache, but this
> reasoning applies to Hibernate Search as well, for which we often
> depend on a newer version of Core than what is provided by the AS.
How hard would it be to allow a different way of passing the custom commands
in? Would this be a short term change in the next few weeks or longer term?
Sorry I'm not sure I understood what you are proposing. How do you
suggest it should work?
--Sanne