Re: Class name org.apache.logging.log4j.LoggingException

2013-09-23 Thread Ralph Goers
IO (input/output) is a verb (or at least some kind of action). That said, regardless of whether the noun vs verb argument makes any sense I still don't think renaming is necessary. Raph On Sep 23, 2013, at 4:27 PM, Gary Gregory wrote: > Hi Ralph, > > I don't buy the noun vs. verb argument. W

Re: Class name org.apache.logging.log4j.LoggingException

2013-09-23 Thread Gary Gregory
Hi Ralph, I don't buy the noun vs. verb argument. What about IOException and SQLException? By that argument we'd have SQLingExcption and IOingException ;) There are plenty of Exception and Exception. IllegalStateException is another good one, it denotes state, not that you are doing something. Bot

Re: Class name org.apache.logging.log4j.LoggingException

2013-09-23 Thread Ralph Goers
I don't really like "Log4jException". Log4j is a noun while Logging is a verb - it is not meant to imply an exception that applies to all of org.apache.logging but an exception performing logging within Log4j. As such, its current name and package seem quite appropriate to me. Ralph On Sep 23,

Re: Class name org.apache.logging.log4j.LoggingException

2013-09-23 Thread Ralph Goers
I don't really like "Log4jException". Log4j is a noun while Logging is a verb - it is not meant to imply an exception that applies to all of org.apache.logging but an exception performing logging within Log4j. As such, its current name and package seem quite appropriate to me. Ralph On Sep 23,

Class name org.apache.logging.log4j.LoggingException

2013-09-23 Thread Gary Gregory
Hi All: I would expected a LoggingException to be in the org.apache.logging package and be used by all org.apache.logging logging solutions, of which there is only one now: Log4j, In org.apache.logging.log4j, I would expect us to have a Log4jException. I propose: (1) renaming org.apache.logging