[GLASSFISH-2485] add target host and port arguments to appclient command-line Created: 23/Feb/07  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: standalone_client
Affects Version/s: 9.1pe
Fix Version/s: not determined

Type: Improvement Priority: Major
Reporter: ksak Assignee: Tim Quinn
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: All
Platform: All

Issuezilla Id: 2,485


Running an appclient component on a different machine than the server is an increasingly common
scenario. For those developers who choose to invoke the client container using the appclient
command rather than webstart, it would be good to add some optional target host / port arguments
to the appclient program.

That would represent a significant ease-of-use improvement over having to define a sun-acc.xml file,
set the host/port in the file, and then pass that to the command-line.

e.g. appclient -host host1 -port 3700 ...

Comment by Tim Quinn [ 23/Feb/07 ]

What about using a single option, perhaps something like -server, that would
accept a comma list of values of the form host:port? The user could then
specify a boot-failover list using -server host1:3700,host2:33700. This would
fully replicate that feature of the target spec in the sun-acc.xml file.

And it would be a bit simpler even for specifying a single host and port, saving
a bit of typing for -server host1:3700 (as opposed to -host host1 -port 3700).

Is "server" the best name for the option?

Comment by ksak [ 23/Feb/07 ]

That sounds ok as long as the simple case of one target is well documented/understood since that's the
90% scenario. We don't want people thinking the option only applies to some cluster scenario.

If we combine the host/port syntax , it would also be good to make the port portion optional since 3700 is
the default. Something like a comma separated list of [<host> | <host>:<port>]. (Seems reasonable to
require host if port is specified.)

That way I can just do appclient -server host1 ... and get the default of 3700 for port.

-server seems fine to me The only issue is whether people will confuse it with the java -server option
that controls the client vs. server mode for the JVM itself.

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk change to set fix version to "not determined" where the issue is open but the value is for a released version.

Generated at Thu Feb 23 07:54:15 UTC 2017 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.