Why not just put a dynamic proxy in front of your service layer and log them there.
-----Original Message----- From: Murtaza Goga [mailto:[EMAIL PROTECTED] Sent: Freitag, 23. März 2007 13:04 To: user-java@ibatis.apache.org Subject: RE: Logging SQL statements It would. You could extend the FileAppender in Log4J and filter out the selects. Not as elegant but it would work. -----Original Message----- From: K1RUHA [mailto:[EMAIL PROTECTED] Sent: Friday, March 23, 2007 7:37 AM To: user-java@ibatis.apache.org Subject: RE: Logging SQL statements But this approach will also generate log messages for SELECT statements. I was thinking about getting sql statements in DAO and then log them depending on configuration parameter. Goga, Murtaza wrote: > > If you are using Log4J, you can add an appender and route the logged sql > activity from iBatis into a separate file. The category I believe is > "java.sql." > > > > ________________________________ > > From: K1RUHA [mailto:[EMAIL PROTECTED] > Sent: Friday, March 23, 2007 6:59 AM > To: user-java@ibatis.apache.org > Subject: Logging SQL statements > > > > Hello. I'd like to use iBATIS in our project, but I have one requierent, > that I don't know if it supports. I need to log SQL statements that > modify database (UPDATE and DELETE) into separate file. So I need some > approach to get these statements in my Java code. Would you mind tell me > if iBATIS can do this? Thanx, Kiryl > > ________________________________ > > View this message in context: Logging SQL statements > <http://www.nabble.com/Logging-SQL-statements-tf3453072.html#a9632495> > Sent from the iBATIS - User - Java mailing list archive > <http://www.nabble.com/iBATIS---User---Java-f370.html> at Nabble.com. > > > -- View this message in context: http://www.nabble.com/Logging-SQL-statements-tf3453072.html#a9632994 Sent from the iBATIS - User - Java mailing list archive at Nabble.com. This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you.
