> TRACE messages are *not* for the developer -- they are for the user...
Everyone is entitled to their own opinion and I disagree with that statement 100%. Trace is there to aid a developer in fixing a problem after the fact. In an environment where it takes a user 20 hours to hit a problem, a developer needs some information to debug the problem. Not all problems can be debugged using a debugger. Another problem with localized trace messages is that they are localized.... :-) This is a problem when a Japanese user hits a problem and they want a non-Japanese speaking/reading developer (one of us) to diagnose the problem. -- Thanks, Rick On Fri, Apr 9, 2010 at 11:26 AM, Pinaki Poddar <[email protected]> wrote: > > TRACE messages are *not* for the developer -- they are for the user (under > duress and using them as the last resort to figure out a problem) and they > must be localized. > > During development a developer may temporarily use whatever mechanics to > suit his/her style -- but once the development is complete, then cleaning > the workspace is part of the work process. > > > ----- > Pinaki > -- > View this message in context: > http://n2.nabble.com/DISCUSS-localized-trace-messages-tp4877982p4878105.html > Sent from the OpenJPA Developers mailing list archive at Nabble.com. >
