On 21/11/06, Carfield Yim <[EMAIL PROTECTED]> wrote:
> While I am using ibatis with wicket now because my boss like it, I
> found it missing some feature those are useful for me
...
> 2) This is hard for me to check the actual SQL running, I can never
> able to figure out how log4j showing SQL in my log. It just show a lot
> of garbage log from wicket.
You're missing one of the strong points (for me) of iBatis! Simply
enable Debug level logging for the java.sql loggers,
e.g.
log4j.logger.java.sql=DEBUG
or if you want to fine tune it...
log4j.logger.java.sql.Connection=DEBUG
log4j.logger.java.sql.Statement=DEBUG
log4j.logger.java.sql.PreparedStatement=DEBUG
log4j.logger.java.sql.ResultSet=DEBUG
and all becomes very clear!
For Wicket, I typically set that to Info, or if I need to check things
at more detail, I find that setting
wicket.util.resource = Info
wicket.util.thread.Task = Info
often worth doing to reduce the noise!
/Gwyn
> In my opinions, if you really have a choice, pick a caching framework
> you like and using JDBCTemplate is actually nicer than a lot of those
> ORM framework
>
> On 11/20/06, Jean-Baptiste Quenot <[EMAIL PROTECTED]> wrote:
> > Hi Upa,
> >
> > We are satisfied with Wicket + Spring + Ibatis, which is basically
> > what you describe, but the SQL statements are externalized in an
> > XML file.
> > --
> > Jean-Baptiste Quenot
> > aka John Banana Qwerty
> > http://caraldi.com/jbq/
--
Download Wicket 1.2.3 now! - http://wicketframework.org
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
