Hi Frans,
you are right about the SecurityException (SE). That one should never happen since all the SE throwing methods (
unlock,
delete,
update) are called in atomic methods like
bookContractor where the lock cookie obtained in previous steps and again used in the SE throwing methods.
And since the very last data methods are all synchronized no other
thread can step in between and throw the SecurityException.
So, tell me what shall I do with the SE? Shall I do a printStackTrace() at db layer level?