R: Questions: High/Low Sequence Manager

2003-10-01 Thread Farnea Massimiliano
2. The sequence-name for my implementations are diffent, one is referenced only in the repository.xml, while I got direct access to the second in my application code. Sorry, I don't understand that. Can you explain more. I use a Sequence Manager (SequenceManagerHighLowImpl) normally for

Questions: High/Low Sequence Manager

2003-09-29 Thread Farnea Massimiliano
Hi all, I'm using in my application two implementation (extension) of the SequenceManagerHighLowImpl, one for managing primary keys and the last for generating an application protocol number sequence. I've choosen the SequenceManagerHighLowImpl because I might have more than a JVM pointing the

R: Problem with repository.xml when upgrading from RC2 to RC3

2003-06-17 Thread Farnea Massimiliano
We haver an app running ok under Tomcat 3.3 JVM 1.3.1, OJB RC2 When we upgrade to OJB RC3, we could not initialize the OJB broker. The error is U should upgrade configuration files too: OJB.properties, repository.dtd and repository.xml. Check the differences with the files released with

R: R: SequenceManagerHighLowImpl: trouble on rc3 - SOLVED?

2003-06-03 Thread Farnea Massimiliano
a, Just to check: are you saying that it is possible to use the latest JDBC driver (that comes with Oracle 9.x) with Oracle 8.1.7? Do you have a link to more information about possible issues doing this? Thanks, I'm using the classes12-g.zip (i'm still on JDK1.3) JDBC Driver for Oracle 9.2

R: SequenceManagerHighLowImpl: trouble on rc3

2003-05-29 Thread Farnea Massimiliano
Hi, strange! Could you post a test case or add a test to one of the existing test cases to reproduce your problem? Yes it's strange, I noticed a couple of thing ... that could be wrong: First of all, the problem seems the storing of the HighLowSequence object. The maxKey attribute is a 'long'

R: cache confusion

2003-03-10 Thread Farnea Massimiliano
So I switched to using the ObjectCacheEmptyImpl until I understood caching better. But *even* *then* I found that objects were not always refreshed from the database. This was *totally* unexpected. I finally had to put a broker.clearCache() just after opening my transactions in order to

NEWBIE: cannot update object with ODMG

2003-03-06 Thread Farnea Massimiliano
I'm testing the ODMG layer with this example: /** * Update the Traente instance on the database */ public void update() { Database db = odmg.newDatabase(); // the current DB Transaction tx = null; //open database try {

R: NEWBIE: cannot update object with ODMG

2003-03-06 Thread Farnea Massimiliano
-Messaggio originale- Da: Guido Beutler [mailto:[EMAIL PROTECTED] Inviato: giovedì 6 marzo 2003 13.08 A: OJB Users List Oggetto: Re: NEWBIE: cannot update object with ODMG Hi, - Original Message - From: Farnea Massimiliano [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday