On 15 Apr 2009, at 16:53, Jason T. Greene wrote:
David M. Lloyd wrote:
> On 04/15/2009 05:48 AM, Jaikiran Pai wrote:
>> Looks good :)
>>
>> On a related note, I guess we could do something about the INFO
>> level logs that flood the console when the admin-console is being
>> deployed and accessed? Looking at what is being logged, it doesn't
>> look like they should be logged at INFO level:
> The rules are:
> - One-time, terse messages can be at INFO
> - Per-deployment/lifecycle stuff can be no higher than DEBUG
> - Per-request stuff can be no higher than TRACE
> AFAICT, Seam is not "above the law" here. So why are we talking
> about yet more exceptions in the logging config? How about the
> SEAM guys fix the problem?
> I hope you guys are aware that we have a reputation for having
> absurdly spammy log files - especially Seam apps.
Agreed. Someone should file a SEAM Jira on this, and we can filter
them in the meantime.
https://jira.jboss.org/jira/browse/JBSEAM-2232 - any specific or
general comments welcome :-)
(Unfortunately I sent everything from the wrong email address earlier
so it was bouncing, hence the one sided conversation).
--
Jason T. Greene
JBoss, a division of Red Hat
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
--
Pete Muir
http://www.seamframework.org
http://in.relation.to/Bloggers/Pete