RE: OJb sequence manager - Force computation of unique values

2004-02-05 Thread Ziv Yankowitz
PROTECTED] Sent: Wednesday, February 04, 2004 7:53 PM To: OJB Users List Subject: Re: OJb sequence manager - Force computation of unique values Hi, Ziv Yankowitz wrote: Folks, we are using the High/Low sequence manager implementation and we try to compute the id in advance with the following

RE: OJb sequence manager - Force computation of unique values

2004-02-05 Thread Ziv Yankowitz
Users List Subject: Re: OJb sequence manager - Force computation of unique values Hi, from your stack trace Caused by: org.apache.ojb.broker.TransactionNotInProgressException: ConnectionManager is NOT in transaction at org.apache.ojb.broker.core.PersistenceBrokerImpl.abortTransaction

Re: OJb sequence manager - Force computation of unique values

2004-02-05 Thread Armin Waibel
Source) ... 53 more thanks again for all the help. -Original Message- From: Armin Waibel [mailto:[EMAIL PROTECTED] Sent: Thursday, February 05, 2004 11:24 AM To: OJB Users List Subject: Re: OJb sequence manager - Force computation of unique values Hi, from your stack trace Caused

OJb sequence manager - Force computation of unique values

2004-02-04 Thread Ziv Yankowitz
Folks, we are using the High/Low sequence manager implementation and we try to compute the id in advance with the following code : PersistenceBroker broker = ((HasBroker) tx).getBroker(); Identity oid = new Identity(object, broker); we encounter in the following error error :

Re: OJb sequence manager - Force computation of unique values

2004-02-04 Thread Armin Waibel
Hi, Ziv Yankowitz wrote: Folks, we are using the High/Low sequence manager implementation and we try to compute the id in advance with the following code : PersistenceBroker broker = ((HasBroker) tx).getBroker(); Identity oid = new Identity(object, broker); we encounter in the following error