Title: RE: Precision Specifier
>I guess you are right. I will just have to do the caclulation to get the effect I want.
>BTW, I am having trouble applying the patch to the java file. It is a small file so could
> you plesae post the file or the patch instructions. I am using Solaris 7.
Su
Title: RE: Precision Specifier
Joe,
>I think the number after the comma should be the number of subparts required.
>
>eg.
>a.b.c.d
>{-2,2} => b.c
>{2,2} => c.d
>{-0,1} => a
Thanks for the feedback. Still I would hesitate to go that route as it has less functionality then the one orig
Title: RE: Precision Specifier
>This is pretty neat stuff.
Thanks.
>Are you aware of Python splicing? See section 3.1.2 in > http://www.python.org/doc/tut/node5.html
No, I wasn't, but it appears to be a similiar idea. My notation is admitedly a little strange but I wanted
Title: RE: Precision Specifier
I'd like to offer up a patch to PatternParser.java that changes the semantics of the precision modifier.
In particular, the current meaning is unchanged with new capabilities added. Semantics are now:
A positive integer indicates a substring starting with t
Title: Category formating question/proposal
The precision specifiers in the PatternLayout for category (%c) and calling class (%C) take a single integer which specifies that only that number of the right most components will be printed. I want to be able to print only the 4th component count
Title: RE: Re[2]: log4j and J2EE problem
>JV> My understanding from the Weblogic documentation,
>JV> http://e-docs.bea.com/wls/docs61///programming/packaging.html#1051556, is
>JV> that Weblogic uses two classloaders per application. One for EJBs and one
>JV> for the webapp with the webapp's
e) log4j does this runtime
determination. In fact this seemed to me to be one of the significant
differences between JSR47 and log4j. However, since this wasn't noted as a
difference in the "JSR47 vs. log4j" article I have doubt about my observation.
Are you log4j does this / cou
