Hi Michael,
"Kerschbaum Michael " <[EMAIL PROTECTED]> wrote on 10/09/2008 04:31:15
AM:
> The Problem is now that the application itself wont't work anymore.
> Is there a possibility to restart or watch the RunnableQueue, and in
> case of such an error?!
The simplest way to reboot the RunnableQueue would be to
set the document back to the canvas:
canvas.setDocument(canvas.getDocument());
You can know the runnnablequeue is dead by
calling 'getThread()' on the UpdateManager's RunnableQueue
if it returns null then it has died.
> I mean i have to find the modification of the dom tree outside of
> the updateManager, but I would like to have a fail back, and a quick
> solution to this problem ?
A slightly better short term solution would be to
protect the RunnableQueue from runnableInvoked throwing
an exception (adding a try cache block to the RunnableQueue).
BTW to find the problem you might try instrumenting the
DOM so that various methods check the current thread to see
if it matches the UpdateManager's RunnableQueue Thread
(assuming an UpdateManager is associated with the DOM).
I would add the code to batik.dom.AbstractElement.setAttribute
and setAttributeNS, as well as batik.dom.AbstractParentNode.appendChild
That should check the most likely problems.
