[
https://jira.jboss.org/jira/browse/JBAOP-623?page=com.atlassian.jira.plug...
]
Jason T. Greene commented on JBAOP-623:
---------------------------------------
This doesn't really solve the problem, because the second that an AOP logger is used,
which is when an AOP class is loaded, all projects will begin logging to the console. The
only thing that should ever install a logger plugin is the actual application/container.
Doing this in the aop command line tools or ant tasks would be fine, but it should not be
done in the actual framework code. I would recommend just moving that logger install code
to tasks/commands.
SystemOutLoggerPlugin dumps trace level to the console for ALL
projects that log
--------------------------------------------------------------------------------
Key: JBAOP-623
URL:
https://jira.jboss.org/jira/browse/JBAOP-623
Project: JBoss AOP
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 2.0.0.CR15
Reporter: Jason T. Greene
Assignee: Stale Pedersen
Fix For: 2.0.0.GA
If aop is used by a project, and logging is intended to be muted (null plugin is used),
AOP installs a logger that dumps everything (not just AOP messages) at all levels to the
console. This is because the init method is static and affects everything that uses the
jboss Logger class. It would be much friendlier to other projects if the AOPLogger
implemented this behavior instead of installing a global plugin. Also, it would be nice if
the console output from it could be disabled via some property.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira