mkalen 2005/04/06 07:30:24 Modified: . Tag: OJB_1_0_RELEASE release-notes.txt Log: Update release notes. Swap "-" to "*" for easy copy/paste of JIRA-generated release notes lists. Revision Changes Path No revision No revision 1.54.2.41 +43 -6 db-ojb/release-notes.txt Index: release-notes.txt =================================================================== RCS file: /home/cvs/db-ojb/release-notes.txt,v retrieving revision 1.54.2.40 retrieving revision 1.54.2.41 diff -u -r1.54.2.40 -r1.54.2.41 --- release-notes.txt 3 Apr 2005 02:40:57 -0000 1.54.2.40 +++ release-notes.txt 6 Apr 2005 14:30:24 -0000 1.54.2.41 @@ -7,6 +7,48 @@ provides transparent transactional persistence for Java Objects against relational databases. OJB provides ODMG and JDO interfaces. +More information is available at http://db.apache.org/ojb + +Please refer to our issue tracker for more details on issues with id [OJB-xxx] +http://issues.apache.org/jira/secure/BrowseProject.jspa?id=10700 + + +--------------------------------------------------------------------- +Release 1.0.4 +--------------------------------------------------------------------- +NEW FEATURES: +* [OJB-6] - Support for stored procedures returning ResultSet. + +NOTES: + +CHANGES: + +BUG FIXES: + +KNOWN ISSUES: +* Auto-Detection for insert/update objects checks to avoid DB queries the PK fields of the object. + If at least one PK field is 'NULL' or if primitive field '0', OJB assume the object is new and + needs insert. This will be configurable in next upcoming version. Workaround for PB-api: use method + PB#store(Object obj, ObjectModification mod) to state update or insert. +* Batch handling doesn't work properly with optimistic locking. This will be fixed + in version 1.1 +* Subqueries are not extent aware. see QueryTest#testSubQueryAgainstExtents +* When a class mapped on multiple joined tables was used in a reference only objects + of the base type class will be instantiated, e.g. a Company class has + a 1:n reference 'employees' to a base class Employee and class Manager extends Employee, + then 'employees' only contains objects of type Employee even if the real type was Manager. + See in OJB test suite ...broker.InheritanceMultipleTableTest#testInheritancedObjectsInCollectionReferences + Same problem occur when query the base class, then OJB only returns objects of base type instead + the real type. +* Managed Environment: When run OJB in managed environment and using PBStateListener, the call of + PBStateListener#beforeClose(PBStateEvent event) is made twice when + a PB instance was closed in a JTA-tx (for the first time when PB.close() was called + in bean on the PB handle, second time when the JTA-tx completes) +* otm-api: The OTM API has a known caching issue and should not be considered for code used + in production environments. The future of the OTM layer will be subject for discussion on the + OJB developers list, if you are using it - please subscribe to ojb-dev and make your voice heard. +* Oracle9i platform: when using statement batching, there is a 2k limit on BLOB + 4k limit on CLOB. + --------------------------------------------------------------------- Release 1.0.3 --------------------------------------------------------------------- @@ -780,8 +822,3 @@ - connection problem when using PBKey only with jcdAlias name (e.g. PBKey("myAlias")), now the user and password set in the repository file was used. - add jcdAlias support for tutorial 1+2 - - -More information is available at http://db.apache.org/ojb - -Copyright (c) 2000 - 2005 Thomas Mahler, et al.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
