Win a copy of The Little Book of Impediments (e-book only) this week in the Agile and Other Processes forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Handling remote exception

 
luis veron
Ranch Hand
Posts: 35
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello,
Currently, I am in the process of sorting out my "exception handling" in my assignment. Just wan't to asked you guys on how did you handle remote exceptions. I have just read the RMI specs and noticed that there were a lot of exception hat can happen my invoking a remote method/invocations. Do you just display a message to the client that there were some problem connecting (and need to try again later) or do you just "halt" (Syste.exit()) the apps. Is there a better way to solve this kind of scenario?
I really appriciate your reply.
Luis
 
Aleksey Matiychenko
Ranch Hand
Posts: 178
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I don't think halting the client application is ever a good idea.
I am going to display a message box that indicates a ptoblem and gives user some option. For example you can offer a user to switch to a local mode if you cannot connect to remote database. Or give a user an option to print data for future reference and then exit the application.

 
luis veron
Ranch Hand
Posts: 35
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks Alek!
Yeah, I think you're right that halting the client apps is not a good idea. But I think the users should be informed also that the connection is closed (cut), something like that so that they will not try to request a search/booking.
Just my thought.
Luis
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic