> Spawning scripts via java, that start a java command has some issues
> related to in/out processing ( password echo, log file content streamed
> to an IDE output area,..) and process control (you get the script
> process, not the spawned java process).
Hmmm. So you want to control the process handle for GlassFish so you can
control its life cycle from within NetBeans?
> I can dig into the NetBeans list archive to find more info but this has
> caused hell situations at some point of time...
Please do.
At any rate, your reasons seem to be different from Bill's "perceived
simplicity of a Java command".
I agree, there were quirks with "asadmin start-domain", but switching to
java -jar because of that is rather inexplicable.
BTW, NB bundles with GF V2 -- do we not have "asadmin start-domain" there?
Are there bugs currently unsolved on NB Issue Tracker because of that?