lock() and tryLock() behavior in OJB 1.0.4

I was wondering what the behavior was when obtaining a WRITE lock on an object using the ODMG APIs in OJB 1.0.4. I expected that this call would reload the object from the database if there had been any changes commited before obtaining the WRITE lock. This doesn't seem to be the case in the code

RE: ODMG locking and read only references

-Original Message- From: Armin Waibel [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 21, 2006 5:00 AM To: OJB Users List Subject: Re: ODMG locking and read only references Hi Jean-Yves, Jean-Yves Sironneau wrote: > Hello, > > I would like to know if it's possible using ODMG to set au

ArrayIndexOutOfBoundsException in PersistenceBrokerAbstractImpl

I'm using ODMG and OJB 1.0.4. Any reason why I would be seeing the following exception? Looking at the code I could only see this possibly happening if more than one thread is accessing the array of temporateStateListeners. Thanks in advance for the help, --Phil 2006-02-09 03:14:48 StandardCo

Removing objects from 1:N relationships in OJB 1.0.4

I'm having a problem removing objects in a 1:N relationship in OJB 1.0.4 using OMDG. Assume you have an object Role that can have one or more Permission objects. If I lock just the Role object for WRITE, remove a Permission object from this Role, and then commit the transaction I'll get the foll

RE: OJB_HL_SEQ

Look at src/schema/ojbcore-schema.xml You can use torque to generate the SQL. -Original Message- From: Rick Roman [mailto:[EMAIL PROTECTED] Sent: Friday, January 20, 2006 5:07 PM To: OJB Users List Subject: OJB_HL_SEQ After upgrading to ojb-1.0.4 I am getting an error: [org.apache.oj

lazy loading and the ObjectReferenceDescriptor

I'm debugging an application that uses OJB 1.0.4 and when looking at the ObjectReferenceDescriptor the lazy boolean data member is set to 'false' even though the collection-descriptor this reference refers to has proxy set to 'true'. Does this seem right or could there be something else I'm missin

Configurable interface for LockManagers

I've created my own LockManager implementation for OJB 1.0.4 that implements the Configurable interface and I've added some of the properties this implementation needs to the OJB.properties file. By doing so I was hoping that my LockManager would be configured at some point, like in the LockManage