arminw 2005/02/19 15:46:18
Modified: . Tag: OJB_1_0_RELEASE release-notes.txt
Log:
no message
Revision Changes Path
No revision
No revision
1.54.2.25 +10 -8 db-ojb/release-notes.txt
Index: release-notes.txt
===================================================================
RCS file: /home/cvs/db-ojb/release-notes.txt,v
retrieving revision 1.54.2.24
retrieving revision 1.54.2.25
diff -u -r1.54.2.24 -r1.54.2.25
--- release-notes.txt 7 Feb 2005 20:42:43 -0000 1.54.2.24
+++ release-notes.txt 19 Feb 2005 23:46:17 -0000 1.54.2.25
@@ -19,6 +19,7 @@
handle with copies of cached objects). More detailed information see
'object cache' reference guide in docs.
NOTES:
+- Don't forget to replace the old repository.dtd and OJB.properties file
(both files changed).
- If you plan to use OJB with an J2SE version older than 1.4, then you have
to
replace the Geronimo jars with the corresponding ones from Sun's J2EE SDK.
This
is because Geronimo is a J2EE 1.4 implementation and thus dependant upon
@@ -30,6 +31,8 @@
more info see docs section 'sequence manager'
- Recommended to read the updated 'object cache' reference guide to reflect
on the changes made in
caching behavior.
+- By default a new locking implementation was used for odmg, to enable the
old deprecated odmg-locking,
+ please see comments in OJB.properties file.
CHANGES:
- Minor changes in the repository.dtd. Add element object-cache to metadata
interface and abstract class
@@ -40,7 +43,7 @@
- Remove redundant ObjectCache implementations (ObjectCacheSoftImpl,
ObjectCacheUnlimitiedImpl), same
behavior is possible with ObjectCacheDefaultImpl.
- Remove undocumented 'ObjectCacheFilter' (used to filter out whole packages
or classes from being cached).
- Filter out packages or classes is still possible, please see 'object
cache' reference guide.
+ Filter out packages or classes from being cached is still possible, please
see 'object cache' reference guide.
- !!!In managed enviroments the org.odmg.Transaction#abort() call no longer
throws an
TransactionAbortedExceptionOJB, instead OJB does internal cleanup and set
used
JTA-tx to setRollbackOnly if possible. Thus the client does no longer get
an RemoteException.
@@ -49,18 +52,15 @@
several classes to the same table ("ojb-conrete class" feature), now only
the fields of the
associated class were performed in RowReader instead invoking all fields
of the table used by
the mapped classes.
-- Introduce new locking-package in kernel api, adapt odmg-locking stuff and
remove unused
- classes from org.apache.ojb.odmg.locking package. Adapt own LockMap
implementations to new
- package of LockMap.
+- Introduce new locking-package in kernel api. Now top-level api like
odmg-api can use a kernel
+ lock manager to provide locking. Adapt odmg-locking to the new lock
management and declare old locking stuff
+ in org.apache.ojb.odmg.locking package as deprecated. Add support for
apache's commons-transaction locking part.
- Use of database identity column (SequenceManagerNativeImpl). Move assign
of PK values from
PersistenceBrokerImpl to JdbcAccessImpl#executeInsert. Remove usage of
SequenceManager#setReferenceFKs,
will be handled by OJB in same way as without usage of database identity
column.
-- Method signature changes in
- org.apache.ojb.broker.locking.LockMap#removeWriter/Reader. Adapt own
LockMap implementations.
- odmg-api: Introduced new object reordering implementation (replaces old
algorithm
in ObjectEnvelopeTable).
-
BUG FIXES:
Please refer to our Bug tracking site
(http://issues.apache.org/scarab/servlet/scarab/)
under http://issues.apache.org/scarab/servlet/scarab/issues/id/OJBxxx
@@ -90,6 +90,8 @@
stuff in #beforeCompletion()
- odmg-api: Assign FK for 1:1 relations when persistent objects are written
to DB, instead when objects
were locked.
+- odmg-api: Mixing of pessimistic and optimistic locking should be possible.
Now all lock calls on objects
+ with optimistic locking enabled will be ignored.
KNOWN ISSUES:
- odmg-api: If a user exchange already existing objects in 1:n references
without changing the size
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
