Contents |
Transfer 1.1 Release Candidate 2 Release Notes
The following outlines the compatibility issues, enhancements and bug fixes that have been made for the 1.1 Release Candidate 2 release of Transfer.
Please see Installation and Updating on how to install and update your version of Transfer.
To determine the version of your install of Transfer, run the following code:
<cfoutput> #transferFactory.getVersion()# </cfoutput>
API Changes
- TQL Query Object's setCacheEvaluation() now defaults to 'true', rather than false.
- The TransferObject and TransferObjectProxy methods __getLoadedObject(), __getIsProxy() and __getIsLoaded() that were introduced in RC1, have been changed to getLoadedObject(), getIsProxy() and getIsLoaded() respectively.
Enhancements
- #to13 - OnDiscard Performance Enchancement
- #to19 - Introspection and statistics for caching layer
- #to30 - Cache setting - accessedminutestimeout
- #to36 - Configure o2m/m2m/m2o compositions to load TransferObject Proxies
- #to40 - cascade* operations should be in their own Transaction
- #to44 - Requirement of 1 objectDefinition in transfer.xml not required
- #to48 - Cache statistics introspection
- #to50 - Make TQL cache.setCacheEvaluation(true) by default
- #to53 - Use a Java POJO for Memento.cfc
- #to56 - Convert all 'web-inf.cftags.component' to 'any'
- #to66 - getDatasource() and getTransaction(), available in Decorators
Bug Fixes
- #to42 - Request/Session scope caching may not clear properly on CF8
- #to43 - Bug in listByPropertyMap() with an non empty struct, but all null values
- #to45 - Lazy load locking should be named per composition
- #to52 - Lazy loading fails with a parent with a compositeid
- #to57 - Memory leak with None/Request/Session scoped caching
- #to58 - Cascade Delete will skip non loaded lazy m2o and parent o2ms
Categories:
Wiki Menu
User Login