Program termination on invalid conf

[androklis]

In case of an invalid conf file, SW terminates. We could implement the following:

• If no gui is enabled then we will use a System Scanner to prompt the user enter a path to the file.
• If gui is enabled then JFileChooser will prompt user to choose a config file.

I have tested the above implementations and everything worked fine.

What happens for multiple config files?

[gtrianta1965]

There are many factors that can result in an invalid configuration file. The first thing the program can do is to try to recover by supplying a default value (e.g. Timeout contains letters instead of digits). At the same time a warning is displayed.

If a problem is detected during processing of an individual service then the error is displayed: ERROR: service with id 23 has an invalid configuration. Skipping service 23.

If there is an unrecoverable error then the program stops and informs user

I think this is the best we can do now. One day we will implement a nice UI for configuration file!!! But this will be in the paid version of service watcher. One potential issue that we might have in the future is to introduce so many parameters and configuration options that it will be impossible to create a decent configuration file from scratch unless you have a 35 pages manual or you have a PHD.

[androklis]

Or if someone has Oracle Service Watcher certification

[gtrianta1965]

I haven't thought of that. Coming soon....

[gtrianta1965]

The infamous OSWC!

[androklis]

Another one acronym to remember