I noticed that the Test case is using a TestTwo Object, vs a PersistentDynaBean in the real life case. And the fault seems to be in the PersistentDynaBean. But I can't figure out where.
Regards, Steve
Michael Nash JGlobal.com wrote:
Steve:
I've not seen this behaviour, but I'm certainly going to dig into it. The error on the face of it is trying to say that it doesn't have all the pieces of the primary key - but why doesn't it is the question.
We have a unit test for this too, so perhaps it's not sufficiently comprehensive to catch this issue - in which case the right thing would be to expand the unit test until it fails, then fix the code so it doesn't....
(Thanks for getting it into the bugtracker too)
Mike
Michael Nash
JGlobal Ltd Next-Generation Web Application Development and Open Source Support
http://www.jglobal.com
Bahamas Commerce and Trade Offshore eCommerce Hosting and Business Services http://www.bahamascommerce.com
-- Java/J2EE Developer/Integrator Co-Chair, Dallas/FortWorth J2EE Sig 214-724-7741
http://keelframework.org/documentation Keelgroup mailing list [EMAIL PROTECTED] http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com
