Apache commons CLI not parsing as expected?

Question

public static void main(String[] args) {

    Options options = new Options();
    Option hostOption = Option.builder("h")
            .longOpt("host")
            .required(false)
            .build();

    Option portOption = Option.builder("p")
            .longOpt("port")
            .required(false)
            .type(Number.class)
            .build();

    Option serviceNameOption = Option.builder("n")
            .longOpt("service_name")
            .required(false)
            .build();

    options.addOption(hostOption);
    options.addOption(portOption);
    options.addOption(serviceNameOption);

    String serviceName = "dbservice"
    String host = "localhost";
    int port = 7512;
    CommandLineParser parser = new DefaultParser();
    Server server = new Server();
    try {
        CommandLine cmd = parser.parse(options, args);
        if(cmd.hasOption("host")) {
            host = cmd.getOptionValue("host");
            System.out.println(host); //gets in here but prints null
        }
        if (cmd.hasOption("port")) {
            port = ((Number)cmd.getParsedOptionValue("port")).intValue();
            System.out.println(port); // gets in here but throws a null pointer exception

        }
        if (cmd.hasOption("service_name")) {
            serviceName = cmd.getOptionValue("service_name");
            System.out.println(serviceName); // gets in here but prints null
        }
    } catch(Exception e) {}
 }

I am using Apache commons cli library to parse command line args however it doesn't seem to parse as expected. Not sure what I am missing here?

I invoked in many different way just to see if it works and the below is one of them java -jar dbservice.jar --host localhost --port 7514. What is the right way to invoke anyway? I dont see that in the documentation

I believe if you are going to take an option (such as localhost or port number), you have to specify to the guilder that it is takes an argument. Try adding .hasArg(true) to the builder before the .build(). — KevinO
– KevinO, Commented Mar 22, 2016 at 22:48

KevinO · Accepted Answer · 2016-03-22 23:02:27Z

2

In order for the Option to accept an argument, the hasArg(true) must be passed to the builder. For each of the options, add a ".hasArg(true)". Modifying your code with this argument and running a test case resulted in the expected output.

    Option hostOption = Option.builder("h")
        .longOpt("host")
        .required(false)
        .hasArg(true)
        .build();

answered Mar 22, 2016 at 23:02

KevinO

4,4234 gold badges29 silver badges38 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

user1870400 Over a year ago

It worked for you? How did you pass the command line arguments?

KevinO Over a year ago

I passed the arguments using the long form: --host localhost --port 1234 after I made the code change.

kisna · Accepted Answer · 2016-03-25 20:57:10Z

0

For the first time users, hasArg() is confusing, you would assume by default, that without specifying hasArg(), at least one argument will be taken to create an option. Passing a value '--opt val' without hasArg() silently ignores the val as if nothing is passed, well, if no hasArg() is specified then it should fail because something was passed instead of ignoring. May be, there should be a strict mode?

edited Mar 25, 2016 at 20:57

answered Mar 25, 2016 at 20:48

kisna

3,1771 gold badge28 silver badges33 bronze badges

Collectives™ on Stack Overflow

Apache commons CLI not parsing as expected?

2 Answers 2

2 Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

2 Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related