aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jean-Baptiste Onofré ...@nanthrax.net>
Subject Re: Revert jpa container to jpa 2.0 support?
Date Tue, 16 Sep 2014 11:53:53 GMT
I agree Christian, good point.

As we "import" javax.persistence* but implement the interface, we should 
provide one impl per version.

Regards
JB

On 09/16/2014 01:49 PM, Christian Schneider wrote:
> I am fine with you tackling this.
>
> I think the reason why we have a problem here is that we implement the
> interface. Adding methods is compatible as long as you use an interface.
> If you implement it then it is the other way round.
> Then e.g. removing a method is compatible. So in our case we probably
> can not simply use normal compatibility rules. I think it is a special
> case as we wrap the impl. So probably separate impls on our side are the
> way to solve this as you proposed.
>
> Christian
>
>
>
>
> Am 16.09.2014 13:09, schrieb Jean-Baptiste Onofré:
>> By the way, it's weird that JPA 2.1 is not backward compatible with
>> JPA 2.0: the interfaces contains the same methods (plus some addition).
>>
>> Do you have an use case to test ?
>>
>> Regards
>> JB
>>
>> On 09/16/2014 10:57 AM, Christian Schneider wrote:
>>> Hi all,
>>>
>>> we have the issue https://issues.apache.org/jira/browse/ARIES-1234 in
>>> aries jpa container.
>>>
>>> The current release of jpa container fixes some quite critical bugs but
>>> is now incompatible to aries jpa 2.0.
>>> I propose we revert back to the code before the jpa 2.1 upgrade, then do
>>> a new release that just contains the fixes.
>>>
>>> We can then work on some support for jpa 2.1 that is compatible or
>>> advise people to use different jpa container versions depending if they
>>> want jpa 2.1 or 2.0 support.
>>>
>>> wdyt?
>>>
>>> Christian
>>>
>>
>
>

-- 
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Mime
View raw message