At least it's encapsulated

David_Vallner

package cinna.bar.utils;

public class ExceptionUtils  {
        public static void soapLogAndThrow(RemoteException e, Log log) throws FluffyKittensIntoBlender { /* ... */ }
}

Now I wonder how'd the culprit find out the "right" name for this while missing out on all the results that say "Don't do this", "Well, you might want to do this, but only when...", "[BUG #123456] Clean up exception handling to not do this" etc.

Being the guy maintaining the GUI bits [1], I'm not too happy about having unrelated crap spam the console six times. (As opposed to three times, all over the place, with no useful exception messages or stacktraces due to crappily homegrown exception chaining, that I get right now. Codebases dating to JDK 1.1 are SO UCH FUN.)

DV

[1] I.e.: I get the blame [2] for anything breaking if it pops up an error dialog)
[2] Middle management looking sad like kicked puppies in my general direction.

merreborn

I found that fairly incoherent.

campkev

then you did better than me. I found it completely incoherent.

I Fluffy that totally Kittens

bob_ardkor

<font size="-1">Exception is fluffy kitten. With wing blender. No quack.
</font>

tchize

i can't imagine the client if he sees the GUI telling him

"Some error occured, server throwed FluffyKittensIntoBlender: no bag or river found"

joe_bruin

@David Vallner said:

(..Incoherent gibberish..)

What?

icklemichael

I think it says:

The only context you ever hear the phrase 'log and throw' is in sentences like 'Never log and throw as you'll get the same message logged 6 times, obscuring the root cause of the problem and generally irritate everyone who uses your code'.

I was somewhat surprised to find that one of my colleagues wrote a method called logAndThrow, the naming implied he was familiar with this anti-pattern and it's problems, yet decided to go ahead and implement it anyway.

Our code is littered with Hashtables and Vectors.

My boss is a dog.

When I don't catch exceptions I get blamed.

iwpg

@icklemichael said:

I was somewhat surprised to find that one of my colleagues wrote a method called logAndThrow, the naming implied he was familiar with this anti-pattern and it's problems, yet decided to go ahead and implement it anyway.

Because no-one would ever think of using the word "and" without outside influence....