Two issues here - one that the load message is probably logged at too high a level. Mike, Ryan, WDYT? Then, there is the issue that we get a message printed to STDERR (which is really ugly) and is due to JBoss not having a bridge from JDK logging to log4j - there was some work from some other JBoss guys recently IIRC - I'll try to track it down. On 16/02/2008, Christian Bauer <christian.bauer(a)gmail.com&gt; wrote: > We should probably do the same: > > http://jira.icefaces.org/browse/ICE-2072 > > Our seamframework.org production log is full of them because every > notification e-mail rendering logs them. I remember reporting this to > Facelets a year or so ago but can't find the issue anymore. > _______________________________________________ > seam-dev mailing list > seam-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/seam-dev > -- Pete Muir http://in.relation.to/Bloggers/Pete http://labs.jboss.com/jbossseam

Pete Muir wrote: > Two issues here - one that the load message is probably logged at too > high a level. Mike, Ryan, WDYT? > Sorry for the delay. I'm fine with lowering the logging level for those messages. Please log an issue so we don't forget.

> Then, there is the issue that we get a message printed to STDERR > (which is really ugly) and is due to JBoss not having a bridge from > JDK logging to log4j - there was some work from some other JBoss guys > recently IIRC - I'll try to track it down. > > On 16/02/2008, Christian Bauer <christian.bauer(a)gmail.com&gt; wrote: > >> We should probably do the same: >> >> http://jira.icefaces.org/browse/ICE-2072 >> >> Our seamframework.org production log is full of them because every >> notification e-mail rendering logs them. I remember reporting this to >> Facelets a year or so ago but can't find the issue anymore. >> _______________________________________________ >> seam-dev mailing list >> seam-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/seam-dev >> >> > > >