[
https://issues.jboss.org/browse/AS7-4632?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry commented on AS7-4632:
---------------------------------------
Adding this introduces a new contract that all subsystems (including those that are not
part of the AS codebase or even developed under
jboss.org) will have to fulfill. To do it
properly we would have to have core AS expose some sort of API to subsystems to let them
construct loggers by passing in the subsystem name and the "subcategory" name,
and the core would create a logger e.g. "org.jboss.as." + subsystemName +
"." + subcategory. Otherwise we're just hoping subsystems create categories
that follow some naming pattern.
If we can't guarantee that subsystems will respect this contract, we'll only have
a broken feature that will result in bug reports against the logging subsystem, reports
that the logging subsystem devs can't fix.
Also, I think when users like this idea, they probably have a hope that everything
logically associated with the subsystem will be affected. Many of our subsystems have the
bulk of their functionality coming from external libs, and those external libs are not
going to be affected by this, even if the integration layer respects it. So putting
"subsystem=jpa" to TRACE is not going to affect how Hibernate logs. Same for
"subsystem=web" and JBoss Web, etc etc.
All this said, it's a nice dream and one we should keep in mind.
Create ability to turn on logging levels per subsystem
------------------------------------------------------
Key: AS7-4632
URL:
https://issues.jboss.org/browse/AS7-4632
Project: Application Server 7
Issue Type: Feature Request
Components: Logging
Reporter: James Perkins
Assignee: James Perkins
Possibly edit the change-level operation to accept a subsystem name, e.g. jpa, and enable
the specified level for all the JPA categories.
{code}
/subsystem=logging:change-level(level=TRACE,subsystem=jpa)
{code}
More thought needs to go into this though. If the categories are already defined,
changing them could cause confusion.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira