Re: [eclipselink-users] EclipseLink 1.1.0

[Gordon Yorke <gordon.yorke@xxxxxxxxxx>]

These pages should be considered dynamic.  At this stage in the development of this particular feature the document reflects what has been done.  Other pages for other features at different levels of development should reflect what stage the development is at.

Historical Session support is a deferred requirement for Uni-direction One To Many Mapping.  It is mentioned in the document because it is functionality that we would like to add.  However, ss this functionality is not a must have for this feature it has been deferred from this release and has yet to be targeted for a future release.  If it is important to you file an enhancement request and vote for it.  Popularity of functionality helps us plan release targets.
--Gordon

Magnus Heino wrote:

Enhancements in JPA include:
 - a new 1:M mapping without that doesn't require a back pointer or a separate join table to hold the associations.

Reading this page http://wiki.eclipse.org/EclipseLink/Development/JPA2.0/uni-directional_onetomany_mapping I don't understand if HistoryPolicy is supported or not? Should these development pages be read as the way things probably will be implemented, or the way they were implemented?

 Implementation sequence#3 on that page says that Historical Sessions should be supported. A bit further down it reads that "History Policy is not supported with this mapping.". Without a history policy, no historical sessions afaik? Is the support for historical sessions there, if not, will it be there in the near future, or never?

/Magnus

_______________________________________________
eclipselink-users mailing list
eclipselink-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipselink-users