Mailing-List: contact ojb-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "OJB Developers List" <ojb-dev@db.apache.org>
Received-SPF: pass (hermes.apache.org: local policy)
Mime-Version: 1.0 (Apple Message framework v619.2)
In-Reply-To: <4214B80E.40501@apache.org>
References: <dfddf8d5ce7ede3ec828065a33c5435b@apache.org>
 <4214B80E.40501@apache.org>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <61d6eb97ddf9c30cc69e7f116b60596d@chariotsolutions.com>
Content-Transfer-Encoding: 7bit
From: Brian McCallister <brianm@chariotsolutions.com>
Subject: Re: [OJB 1.1] Status?
Date: Thu, 17 Feb 2005 10:41:02 -0500
To: "OJB Developers List" <ojb-dev@db.apache.org>

On Feb 17, 2005, at 10:28 AM, Armin Waibel wrote:

> I found new problems with the odmg dirty/new/deleted object detection 
> mechanism. There are problems with proxy objects (and other stuff). I 
> don't find a "simple fix" or workaround for these problems, think we 
> have to rework this stuff.
> There is a test case called ObjectImageTest (bad name I know ;-)). All 
> tests are commented out. Run these tests to get an impression of the 
> problem.
> I locally started with an odmg rework, but first I wanted to complete 
> the new kernel locking handling.
>
> So the PB-api is ready for release, but the odmg-api has things to fix 
> (e.g. still outstanding m:n bug fixing).

As these have been here for a while, can we push 1.0.2 with these 
problems documented in order to release the other fixes that have been 
made?

-Brian


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