Community
Participate
Working Groups
When setting EclipseLink 2.4.x/2.5.x platform to a JPA project that has an EclipseLink 2.5 mapping file, a validation error is given complaining mapping file does not have supported content for this JPA platform. The purpose for us to have EclipseLink 2.4.x/2.5.x could be allowing user to use EclipseLink 2.5 library for JPA 2.0 support, but it is confusing at the first sight that an EclipseLink 2.5.x platform does not support EclipseLink 2.5 mapping file.
Not sure exactly what we want to do with this one yet, but targeting to M7 so we can keep track of any work done to help with this.
The majority of the new elements inside the EcipseLink 2.5 ORM XML schema relate to JPA 2.1 functionality. As a result, if the user is specifically selecting JPA 2.0, it is probably best that they are limited to the 2.4 based EclipseLink ORM XML. As a result this is "As designed" and is an issue of documentation.
Verified in build I-3.5.0-20130425165816 that when you create a JPA 2.0 project with EL platform 2.4/2.5 and then select EL 2.5 Library and then create EclipseLink ORM mapping file the mapping file will be version 2.4. If you change to version to 2.5 you will receive an error in the problems pane stating that Mapping file eclipselink-orm.xml does not have supported content for this JPA Platform. To view steps to recreate go to http://wiki.eclipse.org/Dali_3.3_M7_Release