title: Re-throwing RuntimeExceptions after catching Checked Exceptions
body: <p>In Java it is observed that there is a convention of re-throwing a <code>RuntimeException</code> just after handling a <code>Checked Exception</code>.</p>
  
  <p>This way has both good and bad consequences. When the compiler forces something to be handled via a <code>Checked Exception</code>, the developer can just get rid of it by catching it and re-throwing it as a <code>RuntimeException</code>.</p>
  
  <p>Can someone explain if this scenario can be considered as a good practice? If so, would this approach be less error prone or would it make the code base unstable?</p>