Community
Participate
Working Groups
While processing orm.xml, MetadataProject.processSequencing discards/doesn't register declared sequences that are not referenced by meta-data. This means that those sequences are not available for use in Customizers that run after meta-data processing is complete. For example, in: <?xml version="1.0" encoding="UTF-8"?> <entity-mappings...> <sequence-generator name="primaryid-generator" sequence-name="PRIMARY_ID"/> <sequence-generator name="secondaryid-generator" sequence-name="SECONDARY_ID"/> <entity class="model.Person"> <table name="TEST_PERSON"> </table> <attributes> <id name="id"> <generated-value generator="primaryid-generator"/> </id> ... </entity-mappings> If only primaryid-generator were reference by a generated-value element, then secondaryid-generator will not be registered on the login. We should retain all declared meta-data so it is available through native API.
Further, there should be API to obtain any declared Sequence by name. In the current implementation the name is used during the processing of the orm.xml and then discarded. So if we were to retain all declared sequences we'd need to associate them with their names somehow.
Setting target and priority. See the following page for the meanings of these fields: http://wiki.eclipse.org/EclipseLink/Development/Bugs/Guidelines
This bug fix did not make the cut off for 2.0.0. We are deferring the bugs to Future where we can properly sort them all together based on community votes and severity. We will then assign them accordingly to future patch sets and releases.
Changing the priority of the bugs that have been recently triaged to future. Targetting them to P2 will differentiate them from the P3s that have been triaged into future earlier.
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink
