It looks like you are trying to add items to a Set. You will get these casting
exceptions if your classes do not implement the IComparable interface. If they
do implement the interface, then it is another issue.
-Original Message-
From: Rick Curtis [mailto:curti...@gmail.com]
Sent: Thu
Hi Stella,
I did some looking and created a JIRA issue [1] for possible further work. I
haven't found any workaround but there are chances for the relaxation in future
versions of OpenJPA.
If you are still interested, what database are you using?
Cheers,
Milosz
[1] http://issues.apache.org/ji
Hello, this question is probably best answered by Michael Dick:
Does this code expose/represent bug 1365, or it is something new?
public void testNonUnique() throws Exception {
EntityA a1 = setup.insertA("1");
EntityB b1 = setup.insertB("1");
EntityB b2 = setup.insertB("2");
a1.getChildren().add
Great. Glad to hear that you're back in business. I've created a JIRA [1]
for this issue just in case we resurrect the subclassing support to a
first-class citizen. :-)
Thanks,
Kevin
[1] https://issues.apache.org/jira/browse/OPENJPA-1462
On Fri, Jan 15, 2010 at 10:15 AM, Kurt T Stam wrote:
Thanks so much Kevin, that did the trick. Some of the issues you
mentioned where introduced by me not copying right from the
jUDDI project, but the main issue is that the openjpa-plugin simply does
not run for some reason. Anyway it is no longer leaking now! I learned a
lot from this exercise. A
I had some similar issues when loading a large number of data records that
included some joins, I found that if I called the clear function on he
EntityManager every x records it resolved my issue, also solved my OOM
issues also.
Hth
Chris
-Original Message-
From: Christopher Giblin [
Hi
Will adding a version and locking properties to the entities help with this
matter?
cheers, Håkon
2010/1/13 Håkon Sagehaug
> Hi Simone,
>
> The update does not raise any exceptions. I have no version on the entity,
> and not configured locking. I read alittle about locking, does it also app
Hi,
Solved. Problem was that both sides of the bi-directional relationship were
not being assigned before persisting, just one side :
user.getGroups().add(group);
The following fixed the problem:
user.getGroups().add(group);
group.getUsers().add(user);
Interesting that by restarting the a
