[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [eclipselink-users] Null @Id again after query execution
|
Now that I'm in the office I've had a chance to look over EclipseLink
tests - a model similar to what you are using exists and is tested
nightly, so it is expected to work.
The flags you've narrowed it down to suggest it is a weaving issue,
though the problem itself has me believing it might have to do with
fetch or copy groups.
I could not find any bugs filed that seemed to relate to this issue.
You didn't mention which glassfish/EclipseLink version you are using
that shows the problem, so if possible, you might try a later nightly
version of EclipseLink in case refactoring or anther fix resolved the
issue.
Best Regards,
Chris
On 01/09/2012 1:11 PM, Laird Nelson wrote:
On Sat, Sep 1, 2012 at 1:03 AM, Christopher Delahunt
<christopher.delahunt@xxxxxxxxxx
<mailto:christopher.delahunt@xxxxxxxxxx>> wrote:
I'm not quite sure what the issue was but remember something
cropping up about having a mapped superclass extend an entity or
embeddable.
Oh believe me, this is definitely a weird hierarchy. Not really what
I'd choose to do in a green field.
I looked at paragraph 5 of section 3.5. of the JPA specification which
says (on a different issue):
Multiple entity classes and mapped superclasses in an inheritance
hierarchy may define listener classes and/or lifecycle callback
methods directly on the class.
The fact you can have "multiple" of these things "in an inheritance
hierarchy" in /any/ context suggests that it's legal to mix them into
the hierarchy. That's probably a leap, I grant you. I'll bring this up
on the expert group.
Thanks,
Laird
--
http://about.me/lairdnelson
_______________________________________________
eclipselink-users mailing list
eclipselink-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipselink-users
