RE: Swing question: How to exit without System.exit()?

Somebody correct me if I'm wrong, but I believe the event dispatch thread
will terminate after you close and dispose all top-level windows/frames,
etc.

> -----Original Message-----
> From: Vacuum Joe [mailto:vacuumjoe <at> yahoo.com]
> Sent: Tuesday, October 31, 2006 11:23 AM
> To: nbusers <at> netbeans.org
> Subject: [nbusers] Swing question: How to exit without System.exit()?
> 
> I notice that many Swing apps have a Quit button and the action of the
> Quit button does something like System.exit(0).  This is widely-done but
> it's bad.  Very few Java classes should ever use System.exit() because it
> makes it difficult to call them from other apps.  In other words, with a
> well-written Swing app, I should be able to call the main() method of its
> main class and use it and then quit from it without causing the rest of
> the JVM to exit.
> 
> Any suggestions on how to do this?
> 
> Thanks
> 
> 
> 
> 
> 
> 
> __________________________________________________________________________
> __________

RPM repositories

hi, does anybody know where the RPM repositories are for Netbeans?

Re: Re: Slightly off topic: LAF for KDE

Bryan:

I won't be using anything GNOME based anytime in the near future so I
don't care what it looks like.  Yes, the other IDE is based on SWT
pollution which was a colossal IBM waste of resources for the Java
world.  And while GNOME garners all the corporate support for some
reason, we users, those who have a choice, keep choosing KDE for the
most part.  Of course nobody ever accused corporations of having the
customer's best interest in mind.

Chuck

> >>
> >
> FWIW, the GTK+ LAF looks like gnome.
> Check out:
> http://www.gnusolaris.org/gswiki/ScreenShots?webnail=JDK1.6-NetBeans-JavaApp&action=show
>
> Here you see NetBeans, RiskDimenions on Nexenta (Ubuntu + OpenSolaris)
>
> That being said, I use KDE/Ocean.
> Just wanting to see a match between java apps and the OS...
> The other IDE boasts native look and feel but it looks like gnome on
> KDE, too ;)
> -Bryan
>

Re: Swing question: How to exit without System.exit()?

Vacuum Joe wrote:
> I notice that many Swing apps have a Quit button and the action of
> the Quit button does something like System.exit(0).  This is
> widely-done but it's bad.  

Since you are the first person I have heard voice this sentiment in the 
past ten years, I think your view isn't widely held.  How about instead 
saying "it doesn't work well with my current design." 

> Very few Java classes should ever use
> System.exit() because it makes it difficult to call them from other
> apps.  In other words, with a well-written Swing app, I should be
> able to call the main() method of its main class and use it and then
> quit from it without causing the rest of the JVM to exit.

That's not true, as Swing apps are generally designed to be standalone 
desktop applications, and finishing via System.exit() is what normal 
standalone applications do.  What you describe would be better supported 
by applets -- it's fairly easy to write an applet container if you want 
to run multiple applications within a single JVM instance.

> Any suggestions on how to do this?

In theory (as in, I've never tried it), substitute 
Thread.currentThread().interrupt() for System.exit() from within the 
window closing (or any other) event handler.

Tom

Re: Swing question: How to exit without System.exit()?

Re: Re: 100% CPU for Add Operation in Web Service

Porting from Netbeans 3.5 to 5.5 using SVN

I am attempting to port my application from 3.5 to 5.5. I has proved to be 
challenging. 

I am using svn and when I checkedout from svn I would end up with a folder 
called my_web_app and that became my project folder in netbeans.

My application was developed in mostly 3.5 the folder structure is as follows:

my_web_app
	|
	-->index.jsp
	|
	-->jsp subfolder
				|	
				-->jsp files
	|
	-->WEB-INF
			|
			-->classes
					|
					-->subfolder
							|	
							-->subfolder
									|
									-->java files

I use to mount my_web_app as an svn mount point and all was fine. I see that a 
new project in netbeans will create several quick links for you to your libs 
and other server and project resources (web.xml etc...).

To port my project I created a new project to get everything set up the right 
way. I then deleted the web folder it created and symbolic linked to my svn 
working copy. The reason I did this is because svn wanted to create a folder 
under Web_Pages in the project navigator called my_web_app and then dump the 
files that I think needed to be in Web_Pages root.

Anyhow it builds like nothing is wrong but it is actually not building 
anything at all. It states that: Invalid Package Declaration

Now I can see that it does not have a propper classpath here but I cannot see 
how to fix it. I have been fighting with this for 3 or 4 days and am getting 
no where.

Any help?

Thanks

Re: Swing question: How to exit without System.exit()?

Can't quite agree Tom. I would think it is common to call one swing class
from another. I have dozens of these within the application I am currently
working on. These are not multiple applications but a single one instead.
A few of my classes are also stand alone and many of the others could
well be if desired.

Working in Netbeans, I create most new classes as JFrames. Then, in
the main class, I don't do anything except submit an invocation of the
constructor to the event queue, the code that Netbeans generates. That
way, I can call its constructor from another class and get exactly the same
behavior.

The only difference required for such a JFrame of this sort is that it must
know how it was instantiated. If the class is called from another class I
use a different constructor that set a property telling it that it is not a 
stand
alone class. When it is time for the class to exit, I check this property. 
If
it was invoked through its main, I call system.exit(). Otherwise, I call
dispose().

This has worked very well for me. In the case of extending a JPanel, I
only do that when it will be used in a JDialog so no main method is ever
needed.

You might give that a try.

Bayless

----- Original Message ----- 
From: "Tom Ball" <Tom.Ball <at> Sun.COM>
To: <nbusers <at> netbeans.org>
Sent: Tuesday, October 31, 2006 6:21 PM
Subject: Re: [nbusers] Swing question: How to exit without System.exit()?

> Vacuum Joe wrote:
>> I notice that many Swing apps have a Quit button and the action of
>> the Quit button does something like System.exit(0).  This is
>> widely-done but it's bad.
>
> Since you are the first person I have heard voice this sentiment in the 
> past ten years, I think your view isn't widely held.  How about instead 
> saying "it doesn't work well with my current design." 
>
>> Very few Java classes should ever use
>> System.exit() because it makes it difficult to call them from other
>> apps.  In other words, with a well-written Swing app, I should be
>> able to call the main() method of its main class and use it and then
>> quit from it without causing the rest of the JVM to exit.
>
> That's not true, as Swing apps are generally designed to be standalone 
> desktop applications, and finishing via System.exit() is what normal 
> standalone applications do.  What you describe would be better supported 
> by applets -- it's fairly easy to write an applet container if you want to 
> run multiple applications within a single JVM instance.
>
>> Any suggestions on how to do this?
>
> In theory (as in, I've never tried it), substitute 
> Thread.currentThread().interrupt() for System.exit() from within the 
> window closing (or any other) event handler.
>
> Tom
> 

Re: Profiler 5.5 doesn't install!

Re: Swing question: How to exit without System.exit()?

It isn't good best practice "not" to call System.exit
when an application needs to end.  The reason is
different things can happen in a thread including the
AWT threads.  For instances, where one needs to
cleanup they should register shutdown hooks or design
their own mechanism to register actions for shutdown. 
See Runtime.addShutdownHook.  This way no matter if a
Thread is hanging (not stuck in some loop but just not
going away completely...maybe hung on a monitor some
how) the application can cleanly exit.  

I've had different applications where a little bug
here or there which you might not be able to simply
recode down in the JRE could cause the AWT thread or
some other thread you have written to not exit
correctly at times.  When that happens the user exit
the system without kill or the windows task manager. 
Again it could be something as simple as a bug with a
monitor you can't easily debug or figure out.  You may
even have a situation come up where you have to use
halt by starting a thread to watch the shutdown
process.  If you are letting others run code in your
application you do not know what types of Threads they
create and what they do with them in that code...or
their bugs.  See:
http://java.sun.com/j2se/1.5.0/docs/api/java/awt/doc-files/AWTThreadIssues.html

For the case where one needs something run instead
such as a script, a plug-in, or some kind of work flow
the designer of the application can create any types
of hooks and interfaces they would like for the system
to be able to use.  These would not be multiple
applications running inside of the same VM however.  

They would simply be something conforming to some form
of a specification designed for the system.  Like Tom
Ball mentioned one could create an Applet container. 
An Applet container is nothing more than a system
which expects pieces/plug-ins/what ever you want to
call them to conform to a specification so external
code can be executed in it's environment.  This allows
them to be initialized ran and stopped.  A web
application is the same kind of thing.  

Just like in a C++ application.  One can create a
plug-in architecture.  These pieces can run inside the
application.  They just need to conform to some
specification.  If those pieces exit the process then
the process dies.  Java has all the
precreated/packaged/etc protections built in for an
application as the programmer can setup a
SecurityManager to block plug-ins/pieces from calling
certain methods, and these methods can be limited to
certain "trusted" code.

Wade

--- Danilo Costa <danilocosta <at> gmail.com> wrote:

> Hi Joe,
> 
> your question makes sense. You should actually
> dispose the frames when they
> are closed, and when the last one is disposed, the
> VM exits.
> 
> You can do it using setDefaultCloseOparation in
> JFrame method
>
http://java.sun.com/j2se/1.5.0/docs/api/javax/swing/JFrame.html#setDefaultCloseOperation(int)
> 
> Cheers
> 
> 
> On 10/31/06, Vacuum Joe <vacuumjoe <at> yahoo.com> wrote:
> >
> > I notice that many Swing apps have a Quit button
> and the action of the
> > Quit button does something like System.exit(0). 
> This is widely-done but
> > it's bad.  Very few Java classes should ever use
> System.exit() because it
> > makes it difficult to call them from other apps. 
> In other words, with a
> > well-written Swing app, I should be able to call
> the main() method of its
> > main class and use it and then quit from it
> without causing the rest of the
> > JVM to exit.
> >
> > Any suggestions on how to do this?
> >
> > Thanks
> >
> >
> >
> >
> >
> >
> >
> >
>
____________________________________________________________________________________
> > Cheap Talk? Check out Yahoo! Messenger's low
> PC-to-Phone call rates
> > (http://voice.yahoo.com)
> >
> >
> 
> 
> -- 
> "...YOU CANNOT KNOW THE MEANING OF YOUR LIFE UNTIL
> YOU ARE CONNECTED WITH
> THE POWER THAT CREATED YOU..."
> Shri Mataji Nirmala Devi
>