Originally posted by Inuka Vincit:
... or call the TableChanged method of the Jtable if your data in the table is stored some other way.
Originally posted by Anton Golovin:
Hi, Yanxin.
I do think the mystery of 44/80 has been solved: it is given when someone does not check for record still existing after the waiting to unlock - in the lock method.
Originally posted by Steve Taiwan:
Dear Zhou.
I am in thin client camp.
As a j2ee designer, i think 3 tier makes more sense, dosne't it?
If I fail due to 3 thier, I will feel disappointed at sun very much.
Originally posted by Anton Golovin:
This thread should be very useful to current test-takers: we have located the common mistake about the locking mechanism. It is in the lock method and comes after the record to lock comes unlocked and is available for locking. Then, before locking, one should check if the record still exists, as the previous thread might have deleted it. Hope this helps people who have not turned their assignment in, and also those who failed but could pass with their locking getting more points.
Originally posted by Anton Golovin:
Mike, as someone who has concurrently did his assignment as you did yours, I offer my heartfelt congratulations on your successful completion of the certification.
How long did it take you to get it back? The reason I ask is that the assignment I submitted went to the assessor today, and I am trying to get a handle on the waiting![]()
Anton.
Originally posted by Robert Chisholm:
Do you have any idea why the General Considerations score is so low?
What was your choices.txt file like?