UpdateManager

[Archie Cobbs <ar...@dellroad.org>]

There seems to be a bug in the UpdateManager suspend() and resume()
methods in Batik 1.5.1.

The bug is that a thread can invoke and return from both suspend()
and resume() before the suspension has even taken effect, and then
the resume() seems to get lost.

E.g., my code looks like this:

	System.out.println("SUSPENDING");
	um.suspend();

	.. do some stuff ..

	System.out.println("RESUMING");
	um.resume();

I also have an UpdateManagerListener which prints the events.
The output when it works correctly is:

	SUSPENDING
	listener: update manager was suspended
	RESUMING
	listener: update manager was resumed

The output when it fails is:

	SUSPENDING
	RESUMING
	listener: update manager was suspended

..and then no updates until further notice!

The goal here: I'm trying to disable updates while making a bunch
of changes, so that all the changes can take effect at once, improving
speed.

Thanks,
-Archie

__________________________________________________________________________
Archie Cobbs      *        CTO, Awarix        *      http://www.awarix.com

---------------------------------------------------------------------
To unsubscribe, e-mail: batik-users-unsubscribe@xml.apache.org
For additional commands, e-mail: batik-users-help@xml.apache.org