Community
Participate
Working Groups
If you run a (swing) application inside ajbrowser, and you close the window on that application, the ajbrowser as a whole closes. I experienced this behavior running the figure editor example.
The AJBrowser only has rudientary support for executing applications, and does not spawn the application in a new VM. As a result, when Swing applications dispose themselves they also dispose AJBrowser. I've documented this limitation in the programming guide. The obvious work-around is to run from the command-line with the same classpath that the browser uses. This should be considered an enhancement request for AJBrowser to run applications in a new VM. I'm lowering the priority of that to P4 for now.
No immediate plans to upgrade ajbrowser, so I'm marking this as "LATER" for potential reconsideration in the future.
We could also remove the "Run" button from ajbrowser. But this behavior isn't that bad and still allows people to run apps, so RESOLVED LATER sounds right.
LATER/REMIND bugs are being automatically reopened as P5 because the LATER and REMIND resolutions are deprecated.
