You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Albert Strasheim (JIRA)" <ji...@apache.org> on 2007/06/06 23:37:33 UTC
[jira] Created: (AMQCPP-124) Provide a ConnectionMetaData interface
in CMS
Provide a ConnectionMetaData interface in CMS
---------------------------------------------
Key: AMQCPP-124
URL: https://issues.apache.org/activemq/browse/AMQCPP-124
Project: ActiveMQ C++ Client
Issue Type: Improvement
Components: CMS Impl
Affects Versions: 2.1
Reporter: Albert Strasheim
Assignee: Nathan Mittler
Priority: Minor
Fix For: 2.1
>From the JMS 1.1 specification:
4.3.7 ConnectionMetaData
A Connection provides a ConnectionMetaData object. This object provides the latest version of JMS supported by the provider as well as the provider's product name and version.
It also provides a list of the JMS defined property names supported by the connection.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (AMQCPP-124) Provide a ConnectionMetaData interface
in CMS
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQCPP-124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Bish updated AMQCPP-124:
--------------------------------
Fix Version/s: 2.2
Assignee: Timothy Bish (was: Nathan Mittler)
> Provide a ConnectionMetaData interface in CMS
> ---------------------------------------------
>
> Key: AMQCPP-124
> URL: https://issues.apache.org/activemq/browse/AMQCPP-124
> Project: ActiveMQ C++ Client
> Issue Type: Improvement
> Components: CMS Impl
> Affects Versions: 2.1
> Reporter: Albert Strasheim
> Assignee: Timothy Bish
> Priority: Trivial
> Fix For: 2.2
>
>
> From the JMS 1.1 specification:
> 4.3.7 ConnectionMetaData
> A Connection provides a ConnectionMetaData object. This object provides the latest version of JMS supported by the provider as well as the provider's product name and version.
> It also provides a list of the JMS defined property names supported by the connection.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQCPP-124) Provide a ConnectionMetaData
interface in CMS
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQCPP-124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39824 ]
Timothy Bish commented on AMQCPP-124:
-------------------------------------
Not sure about the property names, as we don't receive anything from the broker telling us what it supports, we could hard code them, but not sure how useful that would be.
> Provide a ConnectionMetaData interface in CMS
> ---------------------------------------------
>
> Key: AMQCPP-124
> URL: https://issues.apache.org/activemq/browse/AMQCPP-124
> Project: ActiveMQ C++ Client
> Issue Type: Improvement
> Components: CMS Impl
> Affects Versions: 2.1
> Reporter: Albert Strasheim
> Assignee: Timothy Bish
> Priority: Trivial
> Fix For: 2.2
>
>
> From the JMS 1.1 specification:
> 4.3.7 ConnectionMetaData
> A Connection provides a ConnectionMetaData object. This object provides the latest version of JMS supported by the provider as well as the provider's product name and version.
> It also provides a list of the JMS defined property names supported by the connection.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQCPP-124) Provide a ConnectionMetaData
interface in CMS
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQCPP-124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39838 ]
Timothy Bish commented on AMQCPP-124:
-------------------------------------
I'm happy with what's there. One thing still remaining is to link the version info into data provided from the configure script. We don't currently have goo data in Config.h for major and minor version.
> Provide a ConnectionMetaData interface in CMS
> ---------------------------------------------
>
> Key: AMQCPP-124
> URL: https://issues.apache.org/activemq/browse/AMQCPP-124
> Project: ActiveMQ C++ Client
> Issue Type: Improvement
> Components: CMS Impl
> Affects Versions: 2.1
> Reporter: Albert Strasheim
> Assignee: Timothy Bish
> Priority: Trivial
> Fix For: 2.2
>
>
> From the JMS 1.1 specification:
> 4.3.7 ConnectionMetaData
> A Connection provides a ConnectionMetaData object. This object provides the latest version of JMS supported by the provider as well as the provider's product name and version.
> It also provides a list of the JMS defined property names supported by the connection.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQCPP-124) Provide a ConnectionMetaData
interface in CMS
Posted by "Nathan Mittler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQCPP-124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39843 ]
Nathan Mittler commented on AMQCPP-124:
---------------------------------------
I'm fine with that. I'm not quite sure what the motivation was for this particular part of the JMS API anyway. Does anyone else want to chime in? Albert?
> Provide a ConnectionMetaData interface in CMS
> ---------------------------------------------
>
> Key: AMQCPP-124
> URL: https://issues.apache.org/activemq/browse/AMQCPP-124
> Project: ActiveMQ C++ Client
> Issue Type: Improvement
> Components: CMS Impl
> Affects Versions: 2.1
> Reporter: Albert Strasheim
> Assignee: Timothy Bish
> Priority: Trivial
> Fix For: 2.2
>
>
> From the JMS 1.1 specification:
> 4.3.7 ConnectionMetaData
> A Connection provides a ConnectionMetaData object. This object provides the latest version of JMS supported by the provider as well as the provider's product name and version.
> It also provides a list of the JMS defined property names supported by the connection.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (AMQCPP-124) Provide a ConnectionMetaData interface
in CMS
Posted by "Nathan Mittler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQCPP-124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nathan Mittler updated AMQCPP-124:
----------------------------------
Fix Version/s: (was: 2.2)
2.1.1
> Provide a ConnectionMetaData interface in CMS
> ---------------------------------------------
>
> Key: AMQCPP-124
> URL: https://issues.apache.org/activemq/browse/AMQCPP-124
> Project: ActiveMQ C++ Client
> Issue Type: Improvement
> Components: CMS Impl
> Affects Versions: 2.1
> Reporter: Albert Strasheim
> Assignee: Timothy Bish
> Priority: Trivial
> Fix For: 2.1.1
>
>
> From the JMS 1.1 specification:
> 4.3.7 ConnectionMetaData
> A Connection provides a ConnectionMetaData object. This object provides the latest version of JMS supported by the provider as well as the provider's product name and version.
> It also provides a list of the JMS defined property names supported by the connection.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQCPP-124) Provide a ConnectionMetaData
interface in CMS
Posted by "Nathan Mittler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQCPP-124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39839 ]
Nathan Mittler commented on AMQCPP-124:
---------------------------------------
I'm not sure that the Major and Minor versions should come from the client build versions. I was thinking they would just be protocol-specific version info. For example, if a connection is using openwire v2, the major version would be 2. So basically, the connector would hard-code the version info for whatever it supports. Does this make sense?
> Provide a ConnectionMetaData interface in CMS
> ---------------------------------------------
>
> Key: AMQCPP-124
> URL: https://issues.apache.org/activemq/browse/AMQCPP-124
> Project: ActiveMQ C++ Client
> Issue Type: Improvement
> Components: CMS Impl
> Affects Versions: 2.1
> Reporter: Albert Strasheim
> Assignee: Timothy Bish
> Priority: Trivial
> Fix For: 2.2
>
>
> From the JMS 1.1 specification:
> 4.3.7 ConnectionMetaData
> A Connection provides a ConnectionMetaData object. This object provides the latest version of JMS supported by the provider as well as the provider's product name and version.
> It also provides a list of the JMS defined property names supported by the connection.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQCPP-124) Provide a ConnectionMetaData
interface in CMS
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQCPP-124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39840 ]
Timothy Bish commented on AMQCPP-124:
-------------------------------------
Not really. The protocol we use doesn't really have any affect on what version of CMS we are implementing.
> Provide a ConnectionMetaData interface in CMS
> ---------------------------------------------
>
> Key: AMQCPP-124
> URL: https://issues.apache.org/activemq/browse/AMQCPP-124
> Project: ActiveMQ C++ Client
> Issue Type: Improvement
> Components: CMS Impl
> Affects Versions: 2.1
> Reporter: Albert Strasheim
> Assignee: Timothy Bish
> Priority: Trivial
> Fix For: 2.2
>
>
> From the JMS 1.1 specification:
> 4.3.7 ConnectionMetaData
> A Connection provides a ConnectionMetaData object. This object provides the latest version of JMS supported by the provider as well as the provider's product name and version.
> It also provides a list of the JMS defined property names supported by the connection.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQCPP-124) Provide a ConnectionMetaData
interface in CMS
Posted by "Nathan Mittler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQCPP-124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39841 ]
Nathan Mittler commented on AMQCPP-124:
---------------------------------------
Ah - I was referring to Provider Major and Minor versions - you're referring to JMS Major and Minor versions.
I would say we can leave out the CMS Major and Minor versions altogether ... doesn't really add any benefit. Rather, we could just stick with provider version information to get info about the particular connector.
> Provide a ConnectionMetaData interface in CMS
> ---------------------------------------------
>
> Key: AMQCPP-124
> URL: https://issues.apache.org/activemq/browse/AMQCPP-124
> Project: ActiveMQ C++ Client
> Issue Type: Improvement
> Components: CMS Impl
> Affects Versions: 2.1
> Reporter: Albert Strasheim
> Assignee: Timothy Bish
> Priority: Trivial
> Fix For: 2.2
>
>
> From the JMS 1.1 specification:
> 4.3.7 ConnectionMetaData
> A Connection provides a ConnectionMetaData object. This object provides the latest version of JMS supported by the provider as well as the provider's product name and version.
> It also provides a list of the JMS defined property names supported by the connection.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQCPP-124) Provide a ConnectionMetaData
interface in CMS
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQCPP-124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39842 ]
Timothy Bish commented on AMQCPP-124:
-------------------------------------
Well in that case then returning some number that tells the user about an openwire or stomp protocol version doesn't really make much sense either, what is a user going to do with that, we don't expect users to know about the intimate details of the protocol, nor is there any real info available to them about the differences between versions. Stomp doesn't even have a version.
So then I think this issue just vanished in a puff of logic.
> Provide a ConnectionMetaData interface in CMS
> ---------------------------------------------
>
> Key: AMQCPP-124
> URL: https://issues.apache.org/activemq/browse/AMQCPP-124
> Project: ActiveMQ C++ Client
> Issue Type: Improvement
> Components: CMS Impl
> Affects Versions: 2.1
> Reporter: Albert Strasheim
> Assignee: Timothy Bish
> Priority: Trivial
> Fix For: 2.2
>
>
> From the JMS 1.1 specification:
> 4.3.7 ConnectionMetaData
> A Connection provides a ConnectionMetaData object. This object provides the latest version of JMS supported by the provider as well as the provider's product name and version.
> It also provides a list of the JMS defined property names supported by the connection.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (AMQCPP-124) Provide a ConnectionMetaData interface
in CMS
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQCPP-124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Bish closed AMQCPP-124.
-------------------------------
Resolution: Fixed
Will not implement.
> Provide a ConnectionMetaData interface in CMS
> ---------------------------------------------
>
> Key: AMQCPP-124
> URL: https://issues.apache.org/activemq/browse/AMQCPP-124
> Project: ActiveMQ C++ Client
> Issue Type: Improvement
> Components: CMS Impl
> Affects Versions: 2.1
> Reporter: Albert Strasheim
> Assignee: Timothy Bish
> Priority: Trivial
> Fix For: 2.2
>
>
> From the JMS 1.1 specification:
> 4.3.7 ConnectionMetaData
> A Connection provides a ConnectionMetaData object. This object provides the latest version of JMS supported by the provider as well as the provider's product name and version.
> It also provides a list of the JMS defined property names supported by the connection.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQCPP-124) Provide a ConnectionMetaData
interface in CMS
Posted by "Nathan Mittler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQCPP-124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39837 ]
Nathan Mittler commented on AMQCPP-124:
---------------------------------------
Agreed. Let's leave the properties out. What you have in trunk for ConnectionMetaData looks fine to me.
> Provide a ConnectionMetaData interface in CMS
> ---------------------------------------------
>
> Key: AMQCPP-124
> URL: https://issues.apache.org/activemq/browse/AMQCPP-124
> Project: ActiveMQ C++ Client
> Issue Type: Improvement
> Components: CMS Impl
> Affects Versions: 2.1
> Reporter: Albert Strasheim
> Assignee: Timothy Bish
> Priority: Trivial
> Fix For: 2.2
>
>
> From the JMS 1.1 specification:
> 4.3.7 ConnectionMetaData
> A Connection provides a ConnectionMetaData object. This object provides the latest version of JMS supported by the provider as well as the provider's product name and version.
> It also provides a list of the JMS defined property names supported by the connection.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (AMQCPP-124) Provide a ConnectionMetaData interface
in CMS
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQCPP-124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Bish updated AMQCPP-124:
--------------------------------
Priority: Trivial (was: Minor)
Fix Version/s: (was: 2.1)
> Provide a ConnectionMetaData interface in CMS
> ---------------------------------------------
>
> Key: AMQCPP-124
> URL: https://issues.apache.org/activemq/browse/AMQCPP-124
> Project: ActiveMQ C++ Client
> Issue Type: Improvement
> Components: CMS Impl
> Affects Versions: 2.1
> Reporter: Albert Strasheim
> Assignee: Nathan Mittler
> Priority: Trivial
>
> From the JMS 1.1 specification:
> 4.3.7 ConnectionMetaData
> A Connection provides a ConnectionMetaData object. This object provides the latest version of JMS supported by the provider as well as the provider's product name and version.
> It also provides a list of the JMS defined property names supported by the connection.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.