Wow...now this adds another dimension, excellent! The exception names might get a bit long then...maybe the exception name should be just an md5 of the aggregated info (package, class name, method, input variables, VM stack, moon phase etc.) with a utility that would rebuild the full exception class name with a double reverse hashed lookup.
I mentioned the md5 approach a while back on the Jackrabbit list [1]: an advantage of md5 is that it would automatically serve as hash tag for search engines: searching for an md5 would lead to forum posts/FAQs/mailing lists/manuals where the issue is discussed. Searching for md5s would result in much fewer false positives than searching i.e. for "SlingException". To see what I mean Google for "error 0x800cccdd" and for "error 1" and compare the results.
Of course some care would have to be taken to include the correct information in the md5 in order not to be overly specific or general.
Michael [1] http://markmail.org/message/zthaqbeciu7lom6z
