Has anyone seen this?
I've got beanshell running embedded in an applet (by signing the applet
and using a .java.policy file - not ideal, but I'm working with that for
now). I'm using beanshell to, well, do everything. The applet
basically just embeds beanshell, and I do everything from a beanshell
script, including creating the GUI (by passing the content pane to
beanshell and adding swing components to it there).
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.
I added some logging statements to see if I could figure out where the
delay was, but there appears to be no particular place where it's slow -
it's just slow everywhere when dealing with swing. A simple expression
like setting a border on a jcomponent can take several seconds to
Anyone know how I could track this down? I'm trying to think what would
be different between the appletviewer and the plugin. Permissions,