×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
James and everyone --
Here is my post to the JTOpen team:
When connecting via a java program running off platform and using an AS400
object which does not specify a user id or password, an AWT Dialog box
generally pops up soliciting the user to enter a user id and password. The
dialog box contains an OK button and a cancel button. When either button is
pressed, the actionPerformed method of AS400SignonDialogAdapter (which has
been set as a listener on each button) is fired. Unfortunately, the action
performed method simply sets the visible property of the Dialog to false so
that the dialog box disappears from the screen. However, the Dialog is never
disposed off or made nondisplayable. This causes some AWT threads to hang
around. Since the threads are non-daemon threads, the java application never
ends on its own unless it calls System.exit().
Should the actionPerformed method instead call Dialog.dispose or at least
set displayable to false or something to cause the non-daemon threads to
end?
Also see
http://java.sun.com/j2se/1.4.2/docs/api/java/awt/doc-files/AWTThreadIssues.h
tml
And here is the reply:
Thanks for pointing this out. This would explain why some of our
command-line unit tests have needed to call System.exit() at the end.
I'll investigate.
midrange.com
