isn't SELECT FOR UPDATE an Oracle-ism?
instead of either entity locking or S-F-U, why not use an optimistic
concurrency scheme, with verified updates? there was recently a nice
catfight on the EJB-INTEREST mailing list between several vendors on
this subject, the result of which seemed to be
Georg == Georg Rehfeld [EMAIL PROTECTED] writes:
Georg notifyAll seems to be MUCH better as of the docs:
Georg | The awakened threads will compete in the usual manner with |
Georg any other threads that might be actively competing to |
Georg synchronize on this object; for example, the
Jesper == Jesper Pedersen [EMAIL PROTECTED] writes:
Jesper You can say that methods in an interface are abstract, since
Jesper the interface doesn't contain an implementation.
Jesper But I see no reason for declaring them abstract, since the
Jesper abstract keyword only has meaning when
on a related note, can someone comment on dynaimc code downloading
problem and the proposed solution? I just recently started checking
out JBoss, and have generally been impressed. but the fact that
dynamic downloading just plain doesn't work is really, *really*,
unfortunate.
--
joe
