This one time, at band camp, Ebersole, Steven said:
ES>I have done some further research into this issue and have found the
ES>following :
ES>1) By placing print statements in the Company's addEmployee() method, I have
ES>verified that Castor is really calling addEmployee with employees whose
ES>company attribute does not match the company upon which the method is being
ES>called. An example is "Adding companyPerson [id=2101, emp.comp.id=1] for
ES>this company [id=6]"
ES>
ES>2) Removing the add methods and allowing access to only set methods had
ES>interesting results. Castor called setEmployees, for example, 3 times for
ES>each company, one time with the correct number "sandwiched" between two
ES>calls with the incorrect counts.
Steve,
This sounds like some very odd behavior. Can we see some of your
objects to see the implementation of the setters as well as a other
objects using these setters?
The reason I asked if you were using a key generator is because
people have reported some problems with them and I'm just curious
to know if you get the same results in a test without the key
generators.
Bruce
--
perl -e 'print unpack("u30","<0G)U8V4\@4VYY9&5R\"F9E<G)E=\$\!F<FEI+F-O;0\`\`");'
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
