[OJB] Issue #OJB180 modified

[Martin Kal?n <ma...@curalia.se>]

You can view the issue detail at the following URL:

    http://nagoya.apache.org/scarab/issues/id/OJB180

Type
 Defect

Issue ID
 OJB180 (Error storing nested object with oracle)

Modified by
 Martin Kalén
 martin.kalen@curalia.se (martin.kalen@curalia.se)

The following modifications were made to this issue:
---------------------------------------------------------------------

Resolution set to "Invalid"
Status changed from "New" to "Unconfirmed"

Reason:
Nested objects works fine with OJB1.0RC from CVS as of 2004-02-23.

Persisting a collection of items mapped with "collection-descriptor" in the repository is done automatically when enlisting the top level object in an ODMG transaction like:
 Transaction tx = odmg.newTransaction();
 tx.begin();
 tx.lock(object, Transaction.WRITE);
 tx.commit();

You need to provide (pseudo-)code and describe your O/R mappings and db-tables if you are still able to reproduce this behaviour with the latest source from CVS.

---------------------------------------------------------------------
This message is automatically generated by the Scarab
issue tracking system.  For more information:
http://scarab.tigris.org/



---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org