2011/3/28 Cédric Beust ♔ <[email protected]>

> By the way, here is something that happens fairly frequently around me (it
> just occurred to me that this was relevant to our current discussion).
>
> Someone writes a Spring-based functionality, deploys it and it blows up
> with hundreds of lines of stack trace in the unique way that Spring apps
> usually do. The developer analyzes the stack trace, finds the culprit,
> decides that this exception is not really an error, goes back to the source,
> adds a catch and reruns his app.
>
> I don't really care about the details of the solution, but this kind of
> scenario is exactly what I want to avoid.
>
>
I'll freely admit that this is a diversion, but... isn't that an argument
against Spring, far more than being an argument in favour for Checked
Exceptions?

Avoiding Spring's more excessive stack traces is certainly a laudable goal,
but does it really justify the entire language "feature"?  Especially given
the pain I've had tracking down bugs in some code because Spring swallowed
an exception and re-threw a different one without the vital error
information I needed - an anti-pattern that I attribute directly to checked
exceptions.



> --
> Cédric
>
>  --
> You received this message because you are subscribed to the Google Groups
> "The Java Posse" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected].
> For more options, visit this group at
> http://groups.google.com/group/javaposse?hl=en.
>



-- 
Kevin Wright

gtalk / msn : [email protected]
<[email protected]>mail: [email protected]
vibe / skype: kev.lee.wright
quora: http://www.quora.com/Kevin-Wright
twitter: @thecoda

"My point today is that, if we wish to count lines of code, we should not
regard them as "lines produced" but as "lines spent": the current
conventional wisdom is so foolish as to book that count on the wrong side of
the ledger" ~ Dijkstra

-- 
You received this message because you are subscribed to the Google Groups "The 
Java Posse" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/javaposse?hl=en.

Reply via email to