In the .9.8 release, the PersistenceBrokerImpl. ssertFkAssignment(..) function was added. If the actual object reference object is null, the foreign key value itself is also set to null. This was always a vague point about the behavior and some of our code, especially during object creation, only sets the foreign key, empties the object from the cache, and requeries to get the fully materialized object.
After upgrading to 9.8, a lot of our code ceased to work properly and I have the feeling many other people will run into the same issue. In order to please everyone, I'm suggesting the following: * Add a nullizeforeignkey (or something like it) attribute inside the <reference-descriptor> or the <foreignkey> tag inside it. Something like: <reference-descriptor name="ojb" class-ref=" " refresh="true" nullieforeignkey="false"> or <foreignkey field-id-ref="1" nullieforeignkey="false"/> </reference-descriptor> Please tell me if you're interested in having me write that code. Thanks Caster -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
