Hi Shawn,
I use a different approach using (in a different context)
+) P6Spy as JDBC proxy driver
+) Log4J to write the P6SPY logs to a SocketAppender
+) SQLProfiler (http://www.jahia.net/jahia/page597.html) which visualize
the JDBC access
This week it helped me to trace an escaping problem related to the JDBC
driver internals ... :-)
Cheers,
Siegfried Goeschl
[EMAIL PROTECTED] wrote:
Hi all,
I'm trying to facilitate the SQL queries called by Jetspeed. In
the TRP, I setup log4j to do so.. but I still don't see the queries or
errors. I know I'm getting an error because I get an SQL exception when
logging in (i'm using the DB2/400 as a test database).
Here's my entry in TRP:
services.LoggingService.system.destination.file=/WEB-INF/log/jetspeed.log
services.LoggingService.system.className=org.apache.turbine.services.logging.FileLogger
services.LoggingService.system.level=DEBUG
From what I've read this should be good enough to send the queries to
jetspeed.log. Anyone else encounter this or know another approach?
______________________
Shawn Haworth
LWSI/WebDev Programmer
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
