Well I was just using that as an example. My actual test project is 22, which, if I take out the one to one relationships I explained in my last post, works fine. The project loads, and the systems load fine, and it acts as expected. I was just trying to load the other two classes automatically, and that's when it broke.
-----Original Message----- From: Stein M. Eliassen [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 15, 2003 11:13 AM To: [EMAIL PROTECTED] Subject: Re: [castor-dev] unexpected stop... Nick Stuart wrote: > Now the only thing is that the modelDims and manual fields aren't > vectors/collections because they are one to one relationships to SystemDims. > When I go to call db.load(Project.class, new Integer(0)) it just hangs there > with nothing being spit out or errors called or anything, it just overflows. > I can't seem to debug it correctly either to find out where it stops inside > castor. Whenever I go to step into db.load it just spits me to some odd > place in my code. Short term fix would be just make the fields vectors, > knowing that there is never going to be more then one value in there, but I > would like to do "correctly" and be sure that there could only ever be one > value in the code, even the db is setup to allow only one. > Do you have a Project with id==0 ? Perhaps Castor have a bug when identity equals zero... Stein ----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [EMAIL PROTECTED] with a subject of: unsubscribe castor-dev ----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [EMAIL PROTECTED] with a subject of: unsubscribe castor-dev
