Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipselink-dev] Opinion request: Persisting non-entity subclass of Entity

Hi James,

  Could you review the patch for proposed fix?


JAMES.SUTHERLAND@xxxxxxxxxx wrote:
I can be useful in cases.  Perhaps at a minimum keep an InheritancePolicy option to allow the existing functionality.

I think we used to rely on this functionality for CMP generated subclasses.

-----Original Message-----
From: TOM.WARE@xxxxxxxxxx Sent: Tuesday, June 17, 2008 1:17 PM
To: Dev mailing list for Eclipse Persistence Services
Subject: [eclipselink-dev] Opinion request: Persisting non-entity subclass of Entity

Hi Folks,

   I am wondering if anyone has an opinion about the following:

   At the moment, EclipseLink does not throw an exception when you persist a
subclass of an Entity that is not annotated as an Entity.  Instead, it treats it
as though it is the superclass and persists the superclass.

   The following bug has been entered because of this issue:

   Note: Although the bug claims we throw the incorrect exception in this case,
my recreation of this issue shows we continue without any issue at all.

   It seems that although the EclipseLink behavior actually allows some
additional use cases not supported by the spec, this behavior is, strictly
speaking, a spec violation.

   Does anyone have an opinion about whether we should keep the current behavior
as an option?

Thanks in advance,
eclipselink-dev mailing list
eclipselink-dev mailing list

Back to the top