AnsweredAssumed Answered

custom behaviour class/object implementation

Question asked by aweber1nj on Jul 13, 2012
Latest reply on Jul 16, 2012 by aweber1nj
From what I can tell, my custom behavior class gets instantiated only once, and that same java object is then re-used across all the calls for all the nodes I've tested with (whether it re-runs on the same node, or whether it's an entirely different node).

I'm curious as to how this would scale, and will it cause a severe bottleneck when possibly hundreds or thousands of users are trying to manage their documents and they might all be waiting for the same, single, instantiated java object to execute the registered policies?

Is there some kind of threshold or threading involved that I haven't seen yet?  If so, are there any additional rules to writing correct behaviors such that they remain thread-safe?

Thanks in advance,