mapping classes on multiple joined tables

Hi, I'm having a problem with mapping classes on multiple joined tables on OJB 1.0.3. I am following the 'Advanced O/R' tutorial in the section 'Mapping Classes on Multiple Joined Tables'. I have 2 tables, one table is a child of the other: parent -- class-descriptor

status on 1.02 release?

Just checking if anyone knows the target date for 1.02? I am looking to upgrade but am afraid of the cache problem in 1.01. Ryan

RE: Problem with SQL Server and Ojb

I don't think you want to use that scheme on SQL server, it's never worked well for me, especially in multiple app server farm situations. I would use the StoredProcedureSequenceImpl or the Native one (haven't tried the native one myself though). Ryan -Original Message- From: Kevin Viet

ReportQuery and NVARCHAR/NTEXT?

Hi, I'm trying to use a report query on tables with NTEXT and NVARCHAR (MSSQL Server 2k), and I get a NullPointerException (I've verified the db-value I am selecting wasn't null): java.lang.NullPointerException at

force flushing items from cache?

I haven't seen anyone ask this, but in my plan to migrate from OJB 0.9.9 to 1.01. I've run into a bit of a problem manipulating the cache, due to changes in the caching between versions. In several cases we use database views as beans, and whenever we update the table behind the view we would

RE: OJB 1.0 RC4 in a multi-VM environment

Try using the sequence manager that uses a stored procedure 'oracle-style' (I think it's called SequenceManagerStoredProcedureImpl - what's what we are using with SQL Server 2000 (we have 4 app servers and other misc vms tied into it). I'd also recommend the jgroups/oscache distributed cache.

RE: ConnectionManager is already in transaction

I've had the same problems with the PB api too. What DB Are you using? The best way for me to get around it was to make wrapper methods that get and close broker connections, and to check the transaction state before trying to begin, commit, and abort a transaction. I'm using SQL Server 2k and the

RE: Network error- Socket closed

I too get these errors quite a bit. It looks like you are using SQL server, I am also. I am using the Opta2000 driver (commercial) from inetsoftware.de, and right now I've found best results using their pooled driver, turning off OJB's connection pool. I'm still trying to unravel this mystery, it

RE: Persistence brokers and threads..(again)

Armin, what version was this introduced in? I'm getting occasional db deadlocks in 0.9.9. Ryan -Original Message- From: Armin Waibel [mailto:[EMAIL PROTECTED] Sent: Thursday, March 20, 2003 6:28 AM To: OJB Users List; [EMAIL PROTECTED] Subject: Re: Persistence brokers and

RE: locking and sql server..(was 'is this an old .97 bug?')

of it. If I can contribute it back into the ojb code base it might save others this headache :) Ryan -Original Message- From: Ryan Vanderwerf Sent: Tuesday, March 11, 2003 5:40 PM To: [EMAIL PROTECTED] Subject: locking and sql server..(was 'is this an old .97 bug?') Hi there, I posted

RE: is this an old .97 bug? (sequencing) - happens in 0.9.9 too

(...) before broker.beginTransaction() the line(~45): broker.clearCache(); call 'bin\build.bat jar' to make the new jar files Any other results? regards, Armin - Original Message - From: Ryan Vanderwerf [EMAIL PROTECTED] To: OJB Users List [EMAIL PROTECTED] Sent: Wednesday, February 19, 2003 12:50

RE: ojb v0.9.9 problem

Sounds like repository.xml isn't in your classpath. -Original Message- From: Ferran Parra [mailto:[EMAIL PROTECTED]] Sent: Wednesday, February 19, 2003 11:25 AM To: OJB Users List Subject: ojb v0.9.9 problem Hi people, i have an error to try: db.open(repository.xml,

RE: is this an old .97 bug? (sequencing) - happens in 0.9.9 too

I've upgrades to 0.9.9 and I can verify this is still happening.I make a copy of a test table that I write to, and I have 2 servlet engines writing to the same database, the each instance of OJB of each server overwrites the OJB_HL_SEQ with conflicting values for each app server. This causes 2

RE: is this an old .97 bug? (sequencing)

I've checked out my primary keys, and that's definitely set up correctly. After further checking it appears to be happening on several tables that have their primary keys set correctly. It appears if the insert fails OJB is then retrying with an UPDATE. I'm going to turn on my spy.log and see if I

is this an old .97 bug? (sequencing)

I've experienced a weird problem in my servlet environment (caucho resin 1.2.6, RH8, sql server 2k, 0.9.7 using PB API) with the sequence manager. Until recently my application has run on 1 application server, with a grab size of 10 for sequences (I'm using the HI_LO seq manager) which was