Christian Koeberl wrote:
followup. Strange thing is - looking at the actuall log4j.Logger - it
has an isTraceEnabled, so I'm really unclear as to why this would
happen.
The problem is the log4j lib in the Jetty ext directory - replace it with
the newer log4j (1.2.12 or higher) version.
Hi,
I just started using Tapestry, and was working a little past the
tutorial. I pulled in the snapshot code and my app broke,
particularly around commons-logging no longer being imported as a
transative dependency.
I declared
public RequestFilter buildTimingFilter(final
followup. Strange thing is - looking at the actuall log4j.Logger - it
has an isTraceEnabled, so I'm really unclear as to why this would
happen.
Christian.
On 12-Sep-07, at 10:01 AM, Christian Gruber wrote:
Hi,
I just started using Tapestry, and was working a little past the
followup. Strange thing is - looking at the actuall log4j.Logger - it
has an isTraceEnabled, so I'm really unclear as to why this would
happen.
The problem is the log4j lib in the Jetty ext directory - replace it with
the newer log4j (1.2.12 or higher) version.
--
Chris
On 9/12/07, Christian Koeberl [EMAIL PROTECTED] wrote:
followup. Strange thing is - looking at the actuall log4j.Logger - it
has an isTraceEnabled, so I'm really unclear as to why this would
happen.
The problem is the log4j lib in the Jetty ext directory - replace it with
the newer log4j
I ran into this myself; I've updated the docs to explain, but haven't
republished. I'm republishing now. Expect updates on the web site in an
hour or two.
On 9/12/07, Massimo Lusetti [EMAIL PROTECTED] wrote:
On 9/12/07, Christian Koeberl [EMAIL PROTECTED] wrote:
followup. Strange thing
