https://issues.apache.org/bugzilla/show_bug.cgi?id=45721
--- Comment #6 from Paul Smith <[EMAIL PROTECTED]> 2008-09-02 14:57:28 PST ---
In regards to the non-English locales, how exactly does one configure the JVM
to use non-English stack traces? Looking at the Throwable.printStackTrace()
there's a hard-coded 'at':
public void printStackTrace(PrintStream s) {
synchronized (s) {
s.println(this);
StackTraceElement[] trace = getOurStackTrace();
for (int i=0; i < trace.length; i++)
s.println("\tat " + trace[i]);
....
So I don't think there's any locale issue to worry about here. I tend to agree
with James that having this as the default behaviour is a really good thing,
but probably going to be controversial (50% love it, 50% will rant on the list
that they hate it and demand to change the default behaviour - I think it's
just one of those things).
For this reason I would tend to agree with Curt that leaving the default
behaviour as it is is probably the safer option initially (log4j 2.0 however
could be different ball game). EnhancedPatternLayout maybe more flexible
generally. The other option to consider is having the option enabled/disable
in the DOMConfiguration layer as 'log4j.debug' is tuned:
e.g. in log4j.xml:
<log4j:configuration debug="false" threshold="debug" enhancedStackTraces="true"
...
Having both a general log4j configuration and EnhancedPatternLayout would cover
all flexibilities (a general log4j environment switch, as well as per-layout
options as needed).
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
