• 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 Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

throwing exceptions

 
Ranch Hand
Posts: 42
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi folks,
In my remote implementation of DataInterface I have a method :
public void lock(int record) throws RemoteException,IOException{
...
}
Although RemoteException IS an IOException I explicitly stated it because I find that the client programmer should be able to distinct network troubles from an invalid record number.
Is this bad practice ? I mean, should I just throw an IOException and achieve the ability to distinct the causes in some other way ?
Thanks
A
 
ranger
Posts: 17347
11
Mac IntelliJ IDE Spring
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
How about throwing RemoteException and DatabaseException
RemoteException will handle that IO stuff,
and DatabaseException will handle invalid record number stuff.
Mark
 
reply
    Bookmark Topic Watch Topic
  • New Topic