> I think of "java -jar glassfish.jar" as a simple way to start an "embedded"
> app server.
Errr. I don't think "java -jar glassfish.jar" starts app server in an embedded
mode. At best, "java -cp your-classes:glassfish.jar ..." would start GF
in an embedded manner when a class from "embedding" VM calls the main/other
method on Appserver class that's the embedded API. Only that ensures that
application server starts in a "given" process.
Doing java -jar "glassfish.jar" is not the way to start embedded app server,
it will always launch a VM of its own (which means it is not embedded).
> For some people it's easier to understand what it does than
> the magic that is "asadmin start-domain".
For those, we introduced a script named "startserv" that starts the default
server and I bet 95% of these users should be happy with it.
> Anyway, I believe we intend to continue to deliver this capability,
> so someone ought to fix it to be consistent with start-domain.
I really wonder why, in the light of the above. More ways to start implies
more paths to test ...