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. -- 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.
