Glen Simmons wrote:
On Tue, 01 Mar 2005 07:09:16 -0500, Thomas DeWeese
<[EMAIL PROTECTED]> wrote:
I would look carefully at the stack trace that is creating
menus to try and figure out who is trying to create them.
Here's the stack trace when calling JSVGComponent.loadSVGDocument:
JavaBug> bt
0: com.apple.mrj.application.SystemMenu.createAppleMenu() line -1
[...]
10: java.awt.Toolkit.getEventQueue() line 1145
11: java.awt.EventQueue.isDispatchThread() line 434
12:
org.apache.batik.swing.svg.JSVGComponent$BridgeUserAgentWrapper.getXMLParserClassName()
Very helpful. I would try running the JDK in 'headless' mode.
No custom anything. And I would have to disagree that the problem is
somewhere else in my code since the code that I pasted was pretty much
all of the code in the app. From the above backtrace, I'm thinking
it's a Mac AWT implementation / Batik interaction problem, but I'm not
sure what to do about it.
The menu creation was a red herring (note that Batik is really not
creating the menu, doing anything with AWT would appear to cause this).
I'm a little curious why this locks up your application, but anyways
I am hoping that you can run the JDK in headless mode and avoid this
issue. If not you will have to find a way to get the Java AWT toolkit
to play nicely with your application (after all, the drawing in Batik
is done using AWT/Java2D so if you can't boot the toolkit you won't
be able to draw anything).
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
