Issue number: entity-persistence update
Obtained from: TopLink
Submitted by: Tom Ware
Reviewed by: TopLink Team
- Added tests for metadata complete feature.
- Metadata complete feature (without tests).
- Annotation updates. Part 3 (and final part) of the AssociationOverride
support.
- Added support for association overrides
- Now access, schema and catalog values overridden at the
entity-mappings level will be passed into the annotations processor -
meaning that global persistence unit defaults can be overridden by
entity-mapping defaults for each entity listed in a given ORM XML
instance document. Package default value defined in entity-mappings is
passed along also.
- Support for persistence unit defaults and metadata-complete. These
values are processed and set, but the EJB Annotations processor does not
make use of them yet. Also updated the test instance documents based on
the final XSD. Created a DefaultXMLCBListener class to allow creation of
default listeners (to be used in both annotation and XML processing)
using class/method names in the pre-deploy stage, then loaded with the
correct classloader in the deploy stage.
- Annotation updates. Part 2 of the AssociationOverride support.
- fixed glassfish issue 245
- fixed glassfish issue 243 and added test to EntityManagerJUnitTestSuite
- Changed/added/removed persistence APIs in alignment with the Java
Persistence spec. Changed TopLink to only support extended persistence
context. Fixed some bugs discovered through this exercise.
- added stubbed out version of entityTransaction.setRollbackOnly() and
entityTransaction.getRollbackOnly() for API completeness
Tested with full glassfish build, entity-persistence-tests, ejb30
persistence devtests and quick look