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
From
http://www.jboss.org/community/wiki/LoggingStandards:
# INFO - Use the INFO level priority for service life-cycle events and
other crucial related information.
The most common user error on AS 5 is having your dependencies not
sorted out. So people will see that stuff being deployed, but not being
started. That's why EJB3s not only show deployment, but also the start
conditions at INFO level, it'll remain to be so.
Carlo
- 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.
- DML