You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Will Norris (JIRA)" <de...@tapestry.apache.org> on 2008/01/04 22:02:35 UTC
[jira] Created: (TAPESTRY-2018) Use SLF4J Markers on Tapestry log
messages
Use SLF4J Markers on Tapestry log messages
------------------------------------------
Key: TAPESTRY-2018
URL: https://issues.apache.org/jira/browse/TAPESTRY-2018
Project: Tapestry
Issue Type: Improvement
Reporter: Will Norris
Logging messages generated by Tapestry for pages and components use the same logger name as the Logger that is injected into the object for users to use. This means that it is not possible to differentiate between Tapestry-generated messages and user-generated messages for the purpose of configuring different logging.
SLF4J supports the use Markers to enrich log statements... essentially metadata. If Tapestry were to use Markers for all framework generated messages, it would be simple to identity them within one's logging configuration. For example...
> logger.debug("Finished class transformation: " + transformation);
would become...
> logger.debug(MarkerFactory.getMarker("tapestry-core"), "Finished class transformation: " + transformation);
or something similar. I know for sure that Logback supports Markers... not sure about others.
Mailing List Discussion: http://thread.gmane.org/gmane.comp.java.tapestry.user/56791
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Updated: (TAPESTRY-2018) Use SLF4J Markers on Tapestry log
messages
Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-2018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship updated TAPESTRY-2018:
-------------------------------------------
Affects Version/s: 5.0
> Use SLF4J Markers on Tapestry log messages
> ------------------------------------------
>
> Key: TAPESTRY-2018
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2018
> Project: Tapestry
> Issue Type: Improvement
> Affects Versions: 5.0
> Reporter: Will Norris
>
> Logging messages generated by Tapestry for pages and components use the same logger name as the Logger that is injected into the object for users to use. This means that it is not possible to differentiate between Tapestry-generated messages and user-generated messages for the purpose of configuring different logging.
> SLF4J supports the use Markers to enrich log statements... essentially metadata. If Tapestry were to use Markers for all framework generated messages, it would be simple to identity them within one's logging configuration. For example...
> > logger.debug("Finished class transformation: " + transformation);
> would become...
> > logger.debug(MarkerFactory.getMarker("tapestry-core"), "Finished class transformation: " + transformation);
> or something similar. I know for sure that Logback supports Markers... not sure about others.
> Mailing List Discussion: http://thread.gmane.org/gmane.comp.java.tapestry.user/56791
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Closed: (TAPESTRY-2018) Use SLF4J Markers on Tapestry log
messages
Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-2018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship closed TAPESTRY-2018.
------------------------------------------
Resolution: Duplicate
Assignee: Howard M. Lewis Ship
TAPESTRY-2474
> Use SLF4J Markers on Tapestry log messages
> ------------------------------------------
>
> Key: TAPESTRY-2018
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2018
> Project: Tapestry
> Issue Type: Improvement
> Affects Versions: 5.0
> Reporter: Will Norris
> Assignee: Howard M. Lewis Ship
>
> Logging messages generated by Tapestry for pages and components use the same logger name as the Logger that is injected into the object for users to use. This means that it is not possible to differentiate between Tapestry-generated messages and user-generated messages for the purpose of configuring different logging.
> SLF4J supports the use Markers to enrich log statements... essentially metadata. If Tapestry were to use Markers for all framework generated messages, it would be simple to identity them within one's logging configuration. For example...
> > logger.debug("Finished class transformation: " + transformation);
> would become...
> > logger.debug(MarkerFactory.getMarker("tapestry-core"), "Finished class transformation: " + transformation);
> or something similar. I know for sure that Logback supports Markers... not sure about others.
> Mailing List Discussion: http://thread.gmane.org/gmane.comp.java.tapestry.user/56791
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org