I have run into more problems. When I try to run osascript through
runtime.exec in a java program it appears to go into la-la land. I see
no activity, and it also appears that the interface is hung. I am able
to trace the plugins call to the browser, but when I use osascript it
appears to hang on the 1st call and all subsequent calls don't appear
in
the trace, as if the plugin is hung and not processing any more
requests. Not the behavior using the open command or calling the
browser
directly. There I can see trace records everytime I call the plugin.
The
call statement looks OK in the trace. And I have no problem with
identical calls in the apple script editor or issuing the commands in
the terminal shell. Is there something different about the way
osascript
is executed when called from within a program?
I have seen osascript hang when trying to execute
the "display dialog" OSAX. This occurs whether the
script is launched by runtime.exec or by typing it
in the Terminal. If run from the Script Editor, or
from a compiled script it works fine, it only fails
when run via osascript. You don't say what, exactly
is hanging (the Java process, osascript, or the
scripted application/web browser), but it sounds
like its the browser, in which case this may not
be the problem. I discovered this when trying to
debug a script called via runtime.exec and the
osascript command, and I inserted display dialog
commands to give me feedback on what it was doing.
When I pulled them out, it worked fine.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Java-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/java-dev/email@hidden
