BeanShell - Simple Java Scripting

On Apr 22, 2005, at 4:12 PM, Wes Nakamura wrote:

> When using appletviewer, it runs at about the speed I expect it to, not
> as fast as a regular applet, but not particularly slow either.  When I
> run it through Firefox, it can take many minutes to do enough swing
> manipulation to create a GUI.  The non-swing parts run at full speed,
> afaict.  I've also tried it on a Windows machine with both Firefox and
> Explorer, with the same result.

That's very strange.  I guess I'd make a minimal "swing speed test" and 
try to look at the timing there.

I am working on bug fixes now and I plan to look at the problems in 
running BeanShell in an applet, so I will try to look at this when I 
get there.


Pat

I've stripped down the script so it does nothing but create the GUI.  I
also created a strict java version of the script.  When I compile it and
run it, there are no slowdowns.  When I have beanshell interpret the
script, it runs very slowly. 

One thing I've noticed is that beanshell causes the applet to try to
load classes over the network, rather than using the local classpath or
jars listed in the applet tag.

By turning on tracing I've noticed this when initializing an interpreter:
("http://.../applet/dist" is the applet's codebase)

network: Connecting http://.../applet/dist/java/lang/bsh.class with proxy=DIRECT
network: Connecting http://.../applet/dist/java/lang/bsh.class with cookie " "
network: Connecting http://.../applet/dist/java/io/bsh.class with proxy=DIRECT
network: Connecting http://.../applet/dist/java/io/bsh.class with cookie " "
network: Connecting http://.../applet/dist/java/util/bsh.class with proxy=DIRECT
network: Connecting http://.../applet/dist/java/util/bsh.class with cookie " "
network: Connecting http://.../applet/dist/java/net/bsh.class with proxy=DIRECT
network: Connecting http://.../applet/dist/java/net/bsh.class with cookie " "
network: Connecting http://.../applet/dist/java/awt/bsh.class with proxy=DIRECT
network: Connecting http://.../applet/dist/java/awt/bsh.class with cookie " "
network: Connecting http://.../applet/dist/java/awt/event/bsh.class with proxy=DIRECT
network: Connecting http://.../applet/dist/java/awt/event/bsh.class with cookie " "
network: Connecting http://.../applet/dist/javax/swing/bsh.class with proxy=DIRECT
network: Connecting http://.../applet/dist/javax/swing/bsh.class with cookie " "
network: Connecting http://.../applet/dist/javax/swing/event/bsh.class with proxy=DIRECT
network: Connecting http://.../applet/dist/javax/swing/event/bsh.class with cookie " "


Since where it's looking (java.lang, java.io, java.util, java.net,
java.awt, java.awt.event, javax.swing, javax.swing.event) is the list of
automatically imported packages, it looks like it's either searching in
the wrong order or not finding bsh.  (Could this be because of how the
plugin handles reflection (which needs extra permissions granted)).

It also shows a lot of similiar connections when it tries to create a
swing component, trying to load the swing classes over the network.
Eventually it must look locally, because after awhile it does create the
component.  Apparently it even tries to load String and other standard
classes that way.

I'm not sure if this is the only reason for the slowdown.  There are
times when it appears to hang (with the CPU at 100%) and it never
continues.  I'm curious why the behavior is different when running the
plugin and running appletviewer.


On Sat, 23 Apr 2005, Patrick Niemeyer wrote:

| 
| On Apr 22, 2005, at 4:12 PM, Wes Nakamura wrote:
| 
| > When using appletviewer, it runs at about the speed I expect it to, not
| > as fast as a regular applet, but not particularly slow either.  When I
| > run it through Firefox, it can take many minutes to do enough swing
| > manipulation to create a GUI.  The non-swing parts run at full speed,
| > afaict.  I've also tried it on a Windows machine with both Firefox and
| > Explorer, with the same result.
| 
| That's very strange.  I guess I'd make a minimal "swing speed test" and 
| try to look at the timing there.
| 
| I am working on bug fixes now and I plan to look at the problems in 
| running BeanShell in an applet, so I will try to look at this when I 
| get there.
| 
| 
| Pat