Which made me wonder, why would I want to use Glassfish (in the sense that I'm interested, but I don't really understand why it might make my life easier). From what I read it's Sun's open-source derivate of Apache's Tomcat, thus I imagine it's a good (or great) quality product. But since I don't know its strengths and weaknesses, I don't know when it would be wise to choose Glassfish over another server. Could anyone elaborate ?
Why use Glassfish instead of Apache
What I want is a simple way to load and store settings, one that works across different app servers and OSes, doesn't require any confguration by the user, and . The Java Preferences API would be ideal - but seems broken under Glassfish 3.1.
GlassFish – Wikipedia, wolna encyklopedia
Once you have started the utility it accepts two commands: show
and exit. The show command will list out every JAR file that is still
open and will display the stack trace from which it was opened. Note
that a single jar file may be opened from more than one place, so you
may see multiple traces for a given JAR. Note also that if you
deploy the app and then use the show command you will see a large
number of stack traces. This is normal, because those JARs are
legitimately still open while the app is deployed. What will be of
interest is the set of stack traces after a redeployment or
undeployment fails. You can issue the show command as many times as
The exit command detaches from the debugger in the
GlassFish JVM and exits.
As I said, there are some rough
edges. For example, if you stop GlassFish the utility will report
this but does not automatically exit. When you then give it the exit
command it throws an exception because it tries to disconnect from
the GlassFish JVM even though the connection is no longer in place.
apache or glasfish widely used ..