can you post a test case that illustrates this problem? If you do, I'll take a look at
it, otherwise it'll be a while before I can get to rebuilding the test case manually.
Maybe there is something in the test suite already that is pretty close and you can
just edit it to illustrate the issue.
cheers,
Matthew
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Fri 1/10/2003 7:08 AM
To: OJB Users List
Cc: [EMAIL PROTECTED]
Subject: Re: Odd 0.9.8 "bug"
I haven't seen any replies to this, and I'm still interested in one...
Thanks
David
|---------+--------------------------->
| | David.Corbin@equ|
| | ifax.com |
| | |
| | 01/08/2003 11:45|
| | AM |
| | Please respond |
| | to "OJB Users |
| | List" |
| | |
|---------+--------------------------->
>------------------------------------------------------------------------------------------------------------------------------------------------|
|
|
| To: [EMAIL PROTECTED]
|
| cc:
|
| Subject: Odd 0.9.8 "bug"
|
|
|
>------------------------------------------------------------------------------------------------------------------------------------------------|
We just upgrade to 0.9.8 from 0.9.4. We've found one thing which we
*think* is a bug in OJB. (It's definately a change in behavior).
We have an A and several B's. The A class descriptor has a collection
descriptor to B, and the B class descriptor has a reference descriptor to A
In 0.9.4, we would lock A, and if there were any new Bs, they would be
assigned an OID automatically, and committed to the database when A was
committed.
In 0.9.8, we find new Bs are given an OID, but they are not written to the
database. However, shortly afterwards (apparently after we do some
seemingly un-related write), we find the new Bs have been written out.
What's going on? Here are the choices I see:
0.9.8 has a bug.
- or -
0.9.4 had a bug that is not fixed. (we have to lock the new B's manually to
get them committed)
Thanks.
David
This message contains information from Equifax Inc. which may be
confidential and privileged. If you are not an intended recipient, please
refrain from any disclosure, copying, distribution or use of this
information and note that such actions are prohibited. If you have
received this transmission in error, please notify by e-mail
[EMAIL PROTECTED]
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
<<winmail.dat>>
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
