You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Sorin Suciu (JIRA)" <qp...@incubator.apache.org> on 2010/08/26 15:29:53 UTC
[jira] Created: (QPID-2824) Use toLogString rather than toString on
LogSubject(s) and add a new GenericActor for logging 0-10 op log messages
Use toLogString rather than toString on LogSubject(s) and add a new GenericActor for logging 0-10 op log messages
-----------------------------------------------------------------------------------------------------------------
Key: QPID-2824
URL: https://issues.apache.org/jira/browse/QPID-2824
Project: Qpid
Issue Type: Improvement
Components: Java Broker
Affects Versions: 0.7
Reporter: Sorin Suciu
Priority: Minor
Fix For: 0.7
Currently the LogSubject and the subsequent implementation classes are using toString method to provide the log subject - I think it is better to use toLogString so the LogSubject interface can be implemented by other object without impacting the generic toString method which could be use for some other purposes. Also having a GenericActor could be useful for non-specialized cases where the LogSubject does not need complex constructs.
--
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
[jira] Closed: (QPID-2824) Use toLogString rather than toString on
LogSubject(s)
Posted by "Sorin Suciu (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-2824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sorin Suciu closed QPID-2824.
-----------------------------
> Use toLogString rather than toString on LogSubject(s)
> -----------------------------------------------------
>
> Key: QPID-2824
> URL: https://issues.apache.org/jira/browse/QPID-2824
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
> Affects Versions: 0.7
> Reporter: Sorin Suciu
> Assignee: Robbie Gemmell
> Priority: Minor
> Fix For: 0.7
>
> Attachments: qpid-2824.patch
>
>
> Currently the LogSubject and the subsequent implementation classes are using toString method to provide the log subject - I think it is better to use toLogString so the LogSubject interface can be implemented by other object without impacting the generic toString method which could be use for some other purposes.
--
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
[jira] Updated: (QPID-2824) Use toLogString rather than toString on
LogSubject(s) and add a new GenericActor for logging 0-10 op log messages
Posted by "Sorin Suciu (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-2824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sorin Suciu updated QPID-2824:
------------------------------
Attachment: (was: qpid-2824.patch)
> Use toLogString rather than toString on LogSubject(s) and add a new GenericActor for logging 0-10 op log messages
> -----------------------------------------------------------------------------------------------------------------
>
> Key: QPID-2824
> URL: https://issues.apache.org/jira/browse/QPID-2824
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
> Affects Versions: 0.7
> Reporter: Sorin Suciu
> Priority: Minor
> Fix For: 0.7
>
> Attachments: qpid-2824.patch
>
>
> Currently the LogSubject and the subsequent implementation classes are using toString method to provide the log subject - I think it is better to use toLogString so the LogSubject interface can be implemented by other object without impacting the generic toString method which could be use for some other purposes. Also having a GenericActor could be useful for non-specialized cases where the LogSubject does not need complex constructs.
--
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
[jira] Updated: (QPID-2824) Use toLogString rather than toString on
LogSubject(s) and add a new GenericActor for logging 0-10 op log messages
Posted by "Sorin Suciu (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-2824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sorin Suciu updated QPID-2824:
------------------------------
Attachment: qpid-2824_1.patch
This is for the test suite - AbstractTestMessages is modified to use toLogString rather than toString.
> Use toLogString rather than toString on LogSubject(s) and add a new GenericActor for logging 0-10 op log messages
> -----------------------------------------------------------------------------------------------------------------
>
> Key: QPID-2824
> URL: https://issues.apache.org/jira/browse/QPID-2824
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
> Affects Versions: 0.7
> Reporter: Sorin Suciu
> Priority: Minor
> Fix For: 0.7
>
> Attachments: qpid-2824.patch, qpid-2824_1.patch
>
>
> Currently the LogSubject and the subsequent implementation classes are using toString method to provide the log subject - I think it is better to use toLogString so the LogSubject interface can be implemented by other object without impacting the generic toString method which could be use for some other purposes. Also having a GenericActor could be useful for non-specialized cases where the LogSubject does not need complex constructs.
--
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
[jira] Updated: (QPID-2824) Use toLogString rather than toString on
LogSubject(s) and add a new GenericActor for logging 0-10 op log messages
Posted by "Sorin Suciu (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-2824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sorin Suciu updated QPID-2824:
------------------------------
Attachment: (was: qpid-2824_1.patch)
> Use toLogString rather than toString on LogSubject(s) and add a new GenericActor for logging 0-10 op log messages
> -----------------------------------------------------------------------------------------------------------------
>
> Key: QPID-2824
> URL: https://issues.apache.org/jira/browse/QPID-2824
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
> Affects Versions: 0.7
> Reporter: Sorin Suciu
> Priority: Minor
> Fix For: 0.7
>
> Attachments: qpid-2824.patch
>
>
> Currently the LogSubject and the subsequent implementation classes are using toString method to provide the log subject - I think it is better to use toLogString so the LogSubject interface can be implemented by other object without impacting the generic toString method which could be use for some other purposes. Also having a GenericActor could be useful for non-specialized cases where the LogSubject does not need complex constructs.
--
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
[jira] Updated: (QPID-2824) Use toLogString rather than toString on
LogSubject(s)
Posted by "Robbie Gemmell (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-2824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robbie Gemmell updated QPID-2824:
---------------------------------
Summary: Use toLogString rather than toString on LogSubject(s) (was: Use toLogString rather than toString on LogSubject(s) and add a new GenericActor for logging 0-10 op log messages)
Assignee: Robbie Gemmell
Description: Currently the LogSubject and the subsequent implementation classes are using toString method to provide the log subject - I think it is better to use toLogString so the LogSubject interface can be implemented by other object without impacting the generic toString method which could be use for some other purposes. (was: Currently the LogSubject and the subsequent implementation classes are using toString method to provide the log subject - I think it is better to use toLogString so the LogSubject interface can be implemented by other object without impacting the generic toString method which could be use for some other purposes. Also having a GenericActor could be useful for non-specialized cases where the LogSubject does not need complex constructs. )
> Use toLogString rather than toString on LogSubject(s)
> -----------------------------------------------------
>
> Key: QPID-2824
> URL: https://issues.apache.org/jira/browse/QPID-2824
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
> Affects Versions: 0.7
> Reporter: Sorin Suciu
> Assignee: Robbie Gemmell
> Priority: Minor
> Fix For: 0.7
>
> Attachments: qpid-2824.patch
>
>
> Currently the LogSubject and the subsequent implementation classes are using toString method to provide the log subject - I think it is better to use toLogString so the LogSubject interface can be implemented by other object without impacting the generic toString method which could be use for some other purposes.
--
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
[jira] Updated: (QPID-2824) Use toLogString rather than toString on
LogSubject(s) and add a new GenericActor for logging 0-10 op log messages
Posted by "Sorin Suciu (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-2824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sorin Suciu updated QPID-2824:
------------------------------
Attachment: qpid-2824.patch
> Use toLogString rather than toString on LogSubject(s) and add a new GenericActor for logging 0-10 op log messages
> -----------------------------------------------------------------------------------------------------------------
>
> Key: QPID-2824
> URL: https://issues.apache.org/jira/browse/QPID-2824
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
> Affects Versions: 0.7
> Reporter: Sorin Suciu
> Priority: Minor
> Fix For: 0.7
>
> Attachments: qpid-2824.patch
>
>
> Currently the LogSubject and the subsequent implementation classes are using toString method to provide the log subject - I think it is better to use toLogString so the LogSubject interface can be implemented by other object without impacting the generic toString method which could be use for some other purposes. Also having a GenericActor could be useful for non-specialized cases where the LogSubject does not need complex constructs.
--
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
[jira] Updated: (QPID-2824) Use toLogString rather than toString on
LogSubject(s) and add a new GenericActor for logging 0-10 op log messages
Posted by "Sorin Suciu (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-2824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sorin Suciu updated QPID-2824:
------------------------------
Attachment: qpid-2824.patch
Patch combining the previous 2 patches and fixing tests.
> Use toLogString rather than toString on LogSubject(s) and add a new GenericActor for logging 0-10 op log messages
> -----------------------------------------------------------------------------------------------------------------
>
> Key: QPID-2824
> URL: https://issues.apache.org/jira/browse/QPID-2824
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
> Affects Versions: 0.7
> Reporter: Sorin Suciu
> Priority: Minor
> Fix For: 0.7
>
> Attachments: qpid-2824.patch, qpid-2824.patch, qpid-2824_1.patch
>
>
> Currently the LogSubject and the subsequent implementation classes are using toString method to provide the log subject - I think it is better to use toLogString so the LogSubject interface can be implemented by other object without impacting the generic toString method which could be use for some other purposes. Also having a GenericActor could be useful for non-specialized cases where the LogSubject does not need complex constructs.
--
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
[jira] Resolved: (QPID-2824) Use toLogString rather than toString
on LogSubject(s)
Posted by "Robbie Gemmell (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-2824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robbie Gemmell resolved QPID-2824.
----------------------------------
Resolution: Fixed
Patch applied.
> Use toLogString rather than toString on LogSubject(s)
> -----------------------------------------------------
>
> Key: QPID-2824
> URL: https://issues.apache.org/jira/browse/QPID-2824
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
> Affects Versions: 0.7
> Reporter: Sorin Suciu
> Assignee: Robbie Gemmell
> Priority: Minor
> Fix For: 0.7
>
> Attachments: qpid-2824.patch
>
>
> Currently the LogSubject and the subsequent implementation classes are using toString method to provide the log subject - I think it is better to use toLogString so the LogSubject interface can be implemented by other object without impacting the generic toString method which could be use for some other purposes.
--
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
[jira] Updated: (QPID-2824) Use toLogString rather than toString on
LogSubject(s) and add a new GenericActor for logging 0-10 op log messages
Posted by "Sorin Suciu (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-2824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sorin Suciu updated QPID-2824:
------------------------------
Attachment: qpid-2824.patch
> Use toLogString rather than toString on LogSubject(s) and add a new GenericActor for logging 0-10 op log messages
> -----------------------------------------------------------------------------------------------------------------
>
> Key: QPID-2824
> URL: https://issues.apache.org/jira/browse/QPID-2824
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
> Affects Versions: 0.7
> Reporter: Sorin Suciu
> Priority: Minor
> Fix For: 0.7
>
> Attachments: qpid-2824.patch
>
>
> Currently the LogSubject and the subsequent implementation classes are using toString method to provide the log subject - I think it is better to use toLogString so the LogSubject interface can be implemented by other object without impacting the generic toString method which could be use for some other purposes. Also having a GenericActor could be useful for non-specialized cases where the LogSubject does not need complex constructs.
--
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
[jira] Updated: (QPID-2824) Use toLogString rather than toString on
LogSubject(s) and add a new GenericActor for logging 0-10 op log messages
Posted by "Sorin Suciu (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-2824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sorin Suciu updated QPID-2824:
------------------------------
Attachment: (was: qpid-2824.patch)
> Use toLogString rather than toString on LogSubject(s) and add a new GenericActor for logging 0-10 op log messages
> -----------------------------------------------------------------------------------------------------------------
>
> Key: QPID-2824
> URL: https://issues.apache.org/jira/browse/QPID-2824
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
> Affects Versions: 0.7
> Reporter: Sorin Suciu
> Priority: Minor
> Fix For: 0.7
>
>
> Currently the LogSubject and the subsequent implementation classes are using toString method to provide the log subject - I think it is better to use toLogString so the LogSubject interface can be implemented by other object without impacting the generic toString method which could be use for some other purposes. Also having a GenericActor could be useful for non-specialized cases where the LogSubject does not need complex constructs.
--
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