== Use Error Codes ==
What about using something like a hash code (for example of the current
stack trace) as error code? These would then automatically serve as hash
tags for Google searches. That is, errors pasted into a discussion forum
would be indexed by Google. Searching for 'Error
I wouldn't call it error code, then: every time something changes
either in the calling code or in the code throwing the exception,
you'll get a different hash code.
Dominique
On Mon, Mar 1, 2010 at 10:32 AM, Michael Dürig michael.due...@day.com wrote:
== Use Error Codes ==
What about using
On Mon, Mar 1, 2010 at 9:32 AM, Michael Dürig michael.due...@day.com wrote:
What about using something like a hash code (for example of the current
stack trace) as error code? These would then automatically serve as hash
A good sample to deal with error messages:
Dominique Pfister wrote:
I wouldn't call it error code, then: every time something changes
either in the calling code or in the code throwing the exception,
you'll get a different hash code.
Agreed, the stack trace might be too unstable. But I still like the idea
of using something cryptic
On Sun, Feb 28, 2010 at 16:41, Thomas Müller thomas.muel...@day.com wrote:
== Use Error Codes ==
Currently exception message are hardcoded (in English). When using
error codes, exception messages could be translated. I'm not saying we
should translate them ourselves, but if somebody wants to,
For Jackrabbit 3, I would like to improve exception handling. Some ideas:
== Use Error Codes ==
Currently exception message are hardcoded (in English). When using
error codes, exception messages could be translated. I'm not saying we
should translate them ourselves, but if somebody wants to, he
