Invalid Option handling

[gandriotakis]

Is it possible to handle or ignore an invalid option in a ServerApplication? It appears that when one is encountered the application just exits.

[gandriotakis]

I really need some help here. I am going to need to bypass the framework option handling and build my own unless there is a better option. It seems very unfriendly to just exit if the user enters a typo. I would expect at least an exception that could be caught and handled.

[fbraem]

You can catch UnknownOptionException

[gandriotakis]

The exception is thrown from OptionSet::getOption method. The application level method that can catch it is the application run method which is hidden in the startup macro where it is too late to recover

I guess I will have to use my own startup. Even at that the only way to recover is to modifiy the arguments and try again. I would prefer to be able to just skip over invalid arguments (and possible log an error).

[mv2020]

I'm also having problems with this. The options processing throws exceptions way too generously and early, resulting in "Unknown option specified: X" for any undefined options. I think it should process what it can and pass any unhandled options directly to the overridden main(ArgVec const&) method. The library shouldn't swallow up the unhandled options and die. What if you want to pass options through to some subprocess (like I currently want to)? I tested this with both the Application and ServerApplication classes, and the behavior is the same in both in the 1.5-dev code.