This is probably quite expense on resources during use, but it does what I'
d originally wanted and produces info on the method called.
[%{method}]
could result in, for example:
[com.adolos.taskmanager.TaskBin.createHashMapKey(TaskBin.java:142)]
Stuart.
changes.patch
Description: Binary data
On Tuesday, July 24, 2001, at 02:32 pm, Stuart Roebuck wrote:
Apologies,
My last patch is based on a misinterpretation of the original code. This
doesn't give the method from which the LogEvent was called: only the
Class.
It's still useful, but the names of my methods and the field are
inappropriate.
Stuart.
On Tuesday, July 24, 2001, at 02:02 pm, Stuart Roebuck wrote:
I've just added in a 'method' field for PatternFormatter based on the
code added to Cocoon today by Sylvain Wallez. It adds the facility to
display the complete path of the calling method in the log, e.g.:
(%{method})
could result in:
(com.adolos.MyStuff.myMethod)
I've tried to make the changes so that there is no additional overhead
if this field is not displayed.
It works for me!
-------------------------------------------------------------------------
Stuart Roebuck [EMAIL PROTECTED]
Lead Developer Java, XML, MacOS X, XP, etc.
ADOLOS <http://www.adolos.com/>
