> From: Marcus Crafter [mailto:[EMAIL PROTECTED]] > > > setCommandQueue( null ) won't work to disable async though, > we would > > need > > something like setSynchronousInitialization( true ). > > Why wouldn't it work ? It seems like AbstractContainer was built > to handle if the command queue was null (it checks for > null before > queueing operations). > > Was there a technical reason why it wouldn't work, or > did you mean > that the actual operation of passing null to the > setCommandQueue() > method wasn't obvious enough ?
Setting the CommandQueue to be null is not obvious enough. What we need is the ability to explicitly turn it on and off. Most likely through a config parameter: <fortress init-policy="lazy"/> <fortress init-policy="async"/> Or something along those lines. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
