Talk:Example Actionclass

A little trap I see in this code (although it was very helpful):

lockResource triggers the EVENT_RESOURCE_MODIFIED too, so you might end up in loop here that ultimately ends in stack overflow. Not sure if there are scenarios where a modified resource isn't already locked. Maybe the unlocking shoots this event too, but I guess most changes occur before that. Anyway, I solved my problem by not locking anything before manipulating the resource. If you manipulate another resource than the that shoots the initial event, think about some control structures.

EP 14:24, 3 December 2009 (CET)