persistence@glassfish.java.net

[Fwd: [Issue 486] Problem with abstract _at_Entity and _at_Id in b41]

From: Sanjeeb Kumar Sahoo <Sanjeeb.Sahoo_at_Sun.COM>
Date: Wed, 29 Mar 2006 23:09:34 +0530

Hi Mike,

Would you mind having a look at this issue? The latest update suggest
that user must specify @Inheritance in a class to indicate that that
class is the root of the inheritance hierarchy. Why is this the case?
Why can't root be identified by the persistence provider runtime by
walking up the tree?

Thanks,
Sahoo

attached mail follows:



https://glassfish.dev.java.net/issues/show_bug.cgi?id=486



User pkrogh changed the following:

                What |Old value |New value
================================================================================
              Issue type|DEFECT |ENHANCEMENT
--------------------------------------------------------------------------------
                Priority|P3 |P4
--------------------------------------------------------------------------------




------- Additional comments from pkrogh_at_dev.java.net Wed Mar 29 15:48:07 +0000 2006 -------
This bug seems to be about the provider determining that inheritance is implied
without specifying the @Inheritance annotation. This is not defined in the
spec, and I believe that it was not the intention of the spec. The
@Inheritance tag defines that Inheritance is needed.

It seems like a nice usability feature, but it would potentially require the
provider to walk the whole hierarchy instead of just looking for @Inheritance.

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe_at_glassfish.dev.java.net
For additional commands, e-mail: issues-help_at_glassfish.dev.java.net