Solved the issue finally... Turned out that I was forgetting to set
the deck's key's parent property to "user" properly, and thus the deck/
card combination was forming one entity group and the user was another
group. I still don't get why this had the odd effect of loading user
object with an in-
Same thing, but...
I tried wrapping both the initial makepersistent() call and then the
query in transactions, without changing anything else:
I get this, which I hope is related to my original issue:
javax.jdo.JDOFatalUserException: Illegal argument
NestedThrowables:
java.lang.IllegalArgumentEx
Okay, I see. In my case it is a List not a Set ... but I think that
really makes no difference.
What I think is strange is that you initialize the fields:
@Persistent(defaultFetchGroup = "true", mappedBy = "_Parent")
@Element(dependent = "true")
private Set _Cards = new HashSet();
Thanks for the suggestion...
I did try that exact code and sad to say it didn't help, just returned
a 0-size collection. I'm still trying to figure this out...
On Mar 7, 10:58 am, Toby wrote:
> Hello Mike,
>
> have you tried touching them before you close the query?
> I had similar problem and
Hello Mike,
have you tried touching them before you close the query?
I had similar problem and only solved it by calling the getter for the
owned collection before detaching the results.
if (results.iterator().hasNext()) {
for (Product fp : results) {
