Community
Participate
Working Groups
Build Identifier: 20100917-0705 Setting the value of the persistence unit property 'eclipselink.exclude-eclipselink-orm' to false or setting the checkbox of 'Exclude unlisted EclipseLink XML mapping file' to default or unchecked status doesn't lead the persistence unit to include the created EclipseLink mapping files. This works for the EclipseLink mapping file with the default name 'eclipselink-orm.xml' though. Reproducible: Always Steps to Reproduce: 1. Create a JPA project 2. Open persistence.xml and go to 'XML Mapping Files' on the General tab to make sure the value of 'Exclude unlisted EclipseLink XML mapping file' is false 3. Right-click the META-INF folder and select New -> EclipseLink Mapping File 4. Give the mapping file a name that is different from the default one 5. Go back to the opened persistence.xml and then go to the JPA Structure view to check if the created EclipseLink mapping file is included.
I believe the functionality is correct here, but the wording of the check box label could be made more clear. The property is only supposed to apply to the special default eclipselink-orm.xml with that name. From the EclipseLink API: /** * The <code>"eclipselink.exclude-eclipselink-orm"</code> property * configures the exclusion of an EclipseLink ORM mapping file for a * specific persistence unit. By default the first file found at the * resource name: "META-INF/eclipselink-orm.xml" is processed and overrides * configurations specified in annotations, and standard mapping files. */ public static final String EXCLUDE_ECLIPSELINK_ORM_FILE = "eclipselink.exclude-eclipselink-orm"; We also need to fix the docs, they are confusing as well: http://help.eclipse.org/galileo/index.jsp?topic=/org.eclipse.jpt.doc.user/task_manage_persistence.htm
Moving JPA specific bugs to new JPA component in bugzilla.
Targeting to Juno release.
How about we change "unlisted" to "default"? "Default" seems to better represent what this property is configuring. Rick, Copying you on this so you can update the user docs as necessary.
Updated docs/help to reflect new field name.
Fixed in M2.
Verified in build S-3.5.0M5-20130206143825 that the build contains a newer version of the help with the updates. To view steps to verify this issue go to http://wiki.eclipse.org/Dali_3.3_M2_Release