Hi,
Feel free to file a JIRA with a reproducible test case. Even better,
attach a patch. ;-)
Craig
On Mar 5, 2011, at 12:46 PM, Jean-Baptiste BRIAUD -- Novlog wrote:
Hi,
2 persistent classes :
A
B extends A.
A have the primary key : id.
I was using fetch plan to include id but with the
+1 gets my vote.
Go ahead an open a JIRA and a patch would be nice. :)
Thanks,
Rick
On Sat, Mar 5, 2011 at 2:46 PM, Jean-Baptiste BRIAUD -- Novlog <
j-b.bri...@novlog.com> wrote:
> Hi,
>
> 2 persistent classes :
> A
> B extends A.
>
> A have the primary key : id.
>
> I was using fetch plan
Hi,
2 persistent classes :
A
B extends A.
A have the primary key : id.
I was using fetch plan to include id but with the wrong class.
I badly added a fetch plan for B.class, id.
id was null, because it was finally not included in the fetch plan.
This is OK but when I build the fetch plan, why n
You can use the following project as an example:
https://github.com/baboune/Simple-JPA
Everything works fine as long as I use EhCache only. As soon as Terracotta
is enabled through ehcache.xml then doing the following:
- Create a company
- Update the name of the company
generate the above excepti
I'm not sure why spring is serializing EntityManagers... regardless this is
definitely a bug. I'm guessing you're in the tire kicking phase so if you
continue using OpenJPA you should read some info on Entity enhancement[1].
Using this property [2] in your persistence.xml is not recommend.
[1] htt
