Re: [dali-dev] JavaCacheableHolder2_0 implemented by AbstractJavaEntity

[Karen Butzke <karen.moore@xxxxxxxxxx>]

Dimitry,

You're in luck, I just fixed this on 4/13 as Brian noticed that our 2.0 
implementation was leaking into 1.0.  Now there is a check for 
isJpa2_0Compatible() before the cast to JpaFactory2_0.  If it's not JPA 
2.0 compatible then a null Object is built.

Our design plan here is to have our internal context model implement 1.0 
and 2.0 and use the interfaces to differentiate between the two.  With 
the massive amount of model explosion that was occurring due to multiple 
spec levels (3.0 spec is already in the works) we decided this was the 
lesser of 2 evils to use checks for JPA spec compatibility.  We are open 
to suggestions in this area :)

Thanks,
Karen

On 4/23/2010 5:43 AM, Dmitry Geraskov wrote:
> Also GenericJavaEntity  make the initialization in constructor, and 
> this is wrong - should use build method.
>
> 23/04/2010 12:40, Dmitry Geraskov wrote:
> > Hi, guys,
> >
> > In Dali 2.3 JavaCacheableHolder2_0 implemented by AbstractJavaEntity. 
> > Is this not a mistake?
> > I ask because it marked as "2_0" so probably not expected to be 
> > supported by all jpa implementations?
> > Also I noticed that GenericJavaEntity make cast JpaFactory to 
> > JpaFactory2_0 to build an instance of JavaCacheable2_0.
> >
> > Thanks,
> > Dmitry Geraskov.
> > _______________________________________________
> > dali-dev mailing list
> > dali-dev@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/dali-dev
> _______________________________________________
> dali-dev mailing list
> dali-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/dali-dev