Re: [eclipselink-users] Complicated MappedSuperclass/AccessType question

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

Re: [eclipselink-users] Complicated MappedSuperclass/AccessType question

From: Laird Nelson <ljnelson@xxxxxxxxx>
Date: Wed, 17 Aug 2011 08:56:20 -0400
Delivered-to: eclipselink-users@xxxxxxxxxxx
List-archive: <https://dev.eclipse.org/mailman/private/eclipselink-users>
List-help: <mailto:eclipselink-users-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/eclipselink-users>, <mailto:eclipselink-users-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/options/eclipselink-users>, <mailto:eclipselink-users-request@eclipse.org?subject=unsubscribe>

On Wed, Aug 17, 2011 at 8:15 AM, Guy Pelletier <guy.pelletier@xxxxxxxxxx> wrote:

The behavior you describe is indeed intentionally implemented that way in EclipseLink as this is also our interpretation of the spec as well (and we confirmed with direct discussions with members of the spec committee beforehand).

Thanks, Guy; I'll file a Hibernate bug.

Best,
Laird

Follow-Ups:
- Re: [eclipselink-users] Complicated MappedSuperclass/AccessType question
  - From: Laird Nelson

References:
- [eclipselink-users] Complicated MappedSuperclass/AccessType question
  - From: Laird Nelson
- Re: [eclipselink-users] Complicated MappedSuperclass/AccessType question
  - From: Laird Nelson
- Re: [eclipselink-users] Complicated MappedSuperclass/AccessType question
  - From: Guy Pelletier

Prev by Date: Re: [eclipselink-users] Complicated MappedSuperclass/AccessType question
Next by Date: Re: [eclipselink-users] Upgrading from 2.1.3 to 2.3.0
Previous by thread: Re: [eclipselink-users] Complicated MappedSuperclass/AccessType question
Next by thread: Re: [eclipselink-users] Complicated MappedSuperclass/AccessType question
Index(es):
- Date
- Thread

Breadcrumbs