• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Paul Clapham
  • Jeanne Boyarsky
  • Junilu Lacar
  • Henry Wong
Sheriffs:
  • Ron McLeod
  • Devaka Cooray
  • Tim Cooke
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Frits Walraven
  • Tim Holloway
  • Carey Brown
Bartenders:
  • Piet Souris
  • salvin francis
  • fred rosenberger

Configuration and Properties

 
Ranch Hand
Posts: 317
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi there,

I have some questions relation to the configuration. And here we go:
i) If an exception was thrown (e.g. wrong port, no server available, etc. ) during the attempt to connect to the server, I show an error message and exit the configuration dialog. What do you say? Is this ok, any must criterion I have to look for? Should I give the user the opportunity to change the setting? But that would be additional work
ii) If a remote exception was thrown, I display an error message, which is not very precise ("network error. please wake up the administrator :-)"). I thought, that the user can't do anything with the exception message, so he should always shout for the administrator.
iii) If the property file is not accessible (broken, wrong permissions), I show a warning message. Afterwards the configuration continues or the application starts. I figured, that a property file error is not a serious one. Not so serious to disallow the application to start.

Looking for your answers.
cheers
Bob
 
Bartender
Posts: 3648
16
Mac OS X Firefox Browser Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Bob, these threads will help
RemoteException?
client/server startup

The whole idea is once the config is saved, that's it. If these were the wrong config then the user wouldn't able to start the app. They would manually need to find that properties file and delete it then start all over. Therefore, it is best all error checking is done before saving to properties file.

About shouting for administrator during remote client startup... if the network server isn't running, network clients can't connect then yeah the admin is needed.
 
Bob Wheeler
Ranch Hand
Posts: 317
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi K.,
thanks for answering.

K. Tsang wrote:Hi Bob, these threads will help
RemoteException?
client/server startup


thanks for the links. I looked for answers for my Q (i) and (ii), which matches my work the best and I found it from Roel: Roel's answer. I know I'm lazy

K. Tsang wrote:
The whole idea is once the config is saved, that's it. If these were the wrong config then the user wouldn't able to start the app. They would manually need to find that properties file and delete it then start all over. Therefore, it is best all error checking is done before saving to properties file.


MMh, I can't follow you here. What you mean by "wrong" config and why should you then delete the property file? The only reason to manually delete or edit the property file is, then the property file is not accessible, e.g. wrong permissions, other accessible error.
I do the following in that case: until the user manually edits/deletes the property file, the user should still be able to run the app. He can't load or store the entered configuration data (all fields are always empty by start up), but he is able to run the app. At least that's how I am doing. Of course he gets a warning message each time the application starts.

cheers
Bob
 
The knights of nee want a shrubbery. And a tiny ad:
Devious Experiments for a Truly Passive Greenhouse!
https://www.kickstarter.com/projects/paulwheaton/greenhouse-1
    Bookmark Topic Watch Topic
  • New Topic