You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org> on 2009/07/22 18:47:15 UTC
[jira] Assigned: (QPID-2001) [Logging] Provide mechanism to provide
fixed log messages
[ https://issues.apache.org/jira/browse/QPID-2001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Ritchie reassigned QPID-2001:
------------------------------------
Assignee: Martin Ritchie
> [Logging] Provide mechanism to provide fixed log messages
> ---------------------------------------------------------
>
> Key: QPID-2001
> URL: https://issues.apache.org/jira/browse/QPID-2001
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
> Reporter: Martin Ritchie
> Assignee: Martin Ritchie
>
> Summary:
> As highlighted in the Technical specification:
> http://cwiki.apache.org/confluence/display/qpid/Operational+Logging+-+Status+Update+-+Technical+Specification#OperationalLogging-StatusUpdate-TechnicalSpecification-Howtoprovidefixedlogmessages
> The logging design calls for the ablity to peform something similar to:
> String message = BrokerLogMessages.BRK-1001(version, build);
> Producing:
> BRK-1001 : Startup : Version: 0.6 Build: 794277
> Where the actual LogMessage is parameterized :
> BRK-1001 = Startup : Version {0} Build: {1}
> This has many benefits:
> - it easy to locate where a particular log messasge is sued
> - it makes updating the log messages straight forward.
> - it makes localisation easy
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org