Insane Programming Java ramblings and finds on the net

The danger of nested exceptions in Java Webstart applications

Everyone knows the following snippet:

try
{
   // snip
}
catch(SomeCheckedException ex)
{
   throw new RuntimeException("Hey, some exception occurred", ex)
}

It's your standard 'I hate checked exceptions, let's transform them into unchecked ones'. Sometimes, you won't even notice it happening. Using Spring and Hibernate, checked exceptions are a rare thing to encounter, since the framework nicely encapsulates them into unchecked ones. But there's a hidden danger lurking within these exceptions. See that second parameter in the exception? It's that one that can cause some problems when dealing with WebStart applications connecting to a remoted back-end somewhere.