You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Mark Pollack (JIRA)" <ji...@apache.org> on 2008/07/18 23:57:00 UTC
[jira] Created: (AMQNET-96) IConnection interface to support
connection metadata.
IConnection interface to support connection metadata.
-----------------------------------------------------
Key: AMQNET-96
URL: https://issues.apache.org/activemq/browse/AMQNET-96
Project: ActiveMQ .Net
Issue Type: Improvement
Components: ActiveMQ Client
Reporter: Mark Pollack
Assignee: James Strachan
Priority: Trivial
Fix For: 1.0
It would be nice to extend the IConnection interface to include getting metadata, in Java the method. ConnectionMetaData getMetaData() This could even be a simple IDictionary with key value pairs specific to the vendor.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Work stopped: (AMQNET-96) IConnection interface to support
connection metadata.
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQNET-96?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on AMQNET-96 stopped by Timothy Bish.
> IConnection interface to support connection metadata.
> -----------------------------------------------------
>
> Key: AMQNET-96
> URL: https://issues.apache.org/activemq/browse/AMQNET-96
> Project: ActiveMQ .Net
> Issue Type: Improvement
> Components: EMS, MSMQ, NMS
> Reporter: Mark Pollack
> Assignee: Timothy Bish
> Priority: Trivial
> Fix For: 1.2.0
>
>
> It would be nice to extend the IConnection interface to include getting metadata, in Java the method. ConnectionMetaData getMetaData() This could even be a simple IDictionary with key value pairs specific to the vendor.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (AMQNET-96) IConnection interface to support
connection metadata.
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQNET-96?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Bish reassigned AMQNET-96:
----------------------------------
Assignee: Timothy Bish (was: James Strachan)
> IConnection interface to support connection metadata.
> -----------------------------------------------------
>
> Key: AMQNET-96
> URL: https://issues.apache.org/activemq/browse/AMQNET-96
> Project: ActiveMQ .Net
> Issue Type: Improvement
> Components: ActiveMQ
> Reporter: Mark Pollack
> Assignee: Timothy Bish
> Priority: Trivial
> Fix For: 1.2.0
>
>
> It would be nice to extend the IConnection interface to include getting metadata, in Java the method. ConnectionMetaData getMetaData() This could even be a simple IDictionary with key value pairs specific to the vendor.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Work logged: (AMQNET-96) IConnection interface to support
connection metadata.
Posted by "Jim Gomes (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQNET-96?page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#action_36875 ]
Jim Gomes logged work on AMQNET-96:
-----------------------------------
Author: Jim Gomes
Created on: 07/Oct/09 11:08 AM
Start Date: 07/Oct/09 11:07 AM
Worklog Time Spent: 30 minutes
Issue Time Tracking
-------------------
Time Spent: 2 hours, 30 minutes (was: 2 hours)
> IConnection interface to support connection metadata.
> -----------------------------------------------------
>
> Key: AMQNET-96
> URL: https://issues.apache.org/activemq/browse/AMQNET-96
> Project: ActiveMQ .Net
> Issue Type: Improvement
> Components: EMS, MSMQ, NMS
> Reporter: Mark Pollack
> Assignee: Jim Gomes
> Priority: Trivial
> Fix For: 1.2.0
>
> Time Spent: 2 hours, 30 minutes
> Remaining Estimate: 0 minutes
>
> It would be nice to extend the IConnection interface to include getting metadata, in Java the method. ConnectionMetaData getMetaData() This could even be a simple IDictionary with key value pairs specific to the vendor.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (AMQNET-96) IConnection interface to support
connection metadata.
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQNET-96?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Bish updated AMQNET-96:
-------------------------------
Component/s: (was: ActiveMQ)
NMS
MSMQ
EMS
> IConnection interface to support connection metadata.
> -----------------------------------------------------
>
> Key: AMQNET-96
> URL: https://issues.apache.org/activemq/browse/AMQNET-96
> Project: ActiveMQ .Net
> Issue Type: Improvement
> Components: EMS, MSMQ, NMS
> Reporter: Mark Pollack
> Assignee: Timothy Bish
> Priority: Trivial
> Fix For: 1.2.0
>
> Time Spent: 2 hours
> Remaining Estimate: 0 minutes
>
> It would be nice to extend the IConnection interface to include getting metadata, in Java the method. ConnectionMetaData getMetaData() This could even be a simple IDictionary with key value pairs specific to the vendor.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (AMQNET-96) IConnection interface to support
connection metadata.
Posted by "Jim Gomes (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQNET-96?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jim Gomes resolved AMQNET-96.
-----------------------------
Resolution: Fixed
Thanks, Tim. I copied your implementation for ConnectionMetaData to the EMS and MSMQ providers and made appropriate changes for their specific stuff.
> IConnection interface to support connection metadata.
> -----------------------------------------------------
>
> Key: AMQNET-96
> URL: https://issues.apache.org/activemq/browse/AMQNET-96
> Project: ActiveMQ .Net
> Issue Type: Improvement
> Components: EMS, MSMQ, NMS
> Reporter: Mark Pollack
> Assignee: Jim Gomes
> Priority: Trivial
> Fix For: 1.2.0
>
> Time Spent: 2 hours, 30 minutes
> Remaining Estimate: 0 minutes
>
> It would be nice to extend the IConnection interface to include getting metadata, in Java the method. ConnectionMetaData getMetaData() This could even be a simple IDictionary with key value pairs specific to the vendor.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (AMQNET-96) IConnection interface to support
connection metadata.
Posted by "Jim Gomes (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQNET-96?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jim Gomes updated AMQNET-96:
----------------------------
Fix Version/s: 1.1
(was: 1.0)
> IConnection interface to support connection metadata.
> -----------------------------------------------------
>
> Key: AMQNET-96
> URL: https://issues.apache.org/activemq/browse/AMQNET-96
> Project: ActiveMQ .Net
> Issue Type: Improvement
> Components: ActiveMQ Client
> Reporter: Mark Pollack
> Assignee: James Strachan
> Priority: Trivial
> Fix For: 1.1
>
>
> It would be nice to extend the IConnection interface to include getting metadata, in Java the method. ConnectionMetaData getMetaData() This could even be a simple IDictionary with key value pairs specific to the vendor.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Work logged: (AMQNET-96) IConnection interface to support
connection metadata.
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQNET-96?page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#action_36873 ]
Timothy Bish logged work on AMQNET-96:
--------------------------------------
Author: Timothy Bish
Created on: 07/Oct/09 08:18 AM
Start Date: 07/Oct/09 08:17 AM
Worklog Time Spent: 2 hours
Work Description: Added IConnectionMetaData to NMS and an accessor in IConnection
Created an implementation for NMS.ActiveMQ and a unit test.
Issue Time Tracking
-------------------
Time Spent: 2 hours
Remaining Estimate: 0 minutes
> IConnection interface to support connection metadata.
> -----------------------------------------------------
>
> Key: AMQNET-96
> URL: https://issues.apache.org/activemq/browse/AMQNET-96
> Project: ActiveMQ .Net
> Issue Type: Improvement
> Components: EMS, MSMQ, NMS
> Reporter: Mark Pollack
> Assignee: Timothy Bish
> Priority: Trivial
> Fix For: 1.2.0
>
> Time Spent: 2 hours
> Remaining Estimate: 0 minutes
>
> It would be nice to extend the IConnection interface to include getting metadata, in Java the method. ConnectionMetaData getMetaData() This could even be a simple IDictionary with key value pairs specific to the vendor.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Work started: (AMQNET-96) IConnection interface to support
connection metadata.
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQNET-96?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on AMQNET-96 started by Timothy Bish.
> IConnection interface to support connection metadata.
> -----------------------------------------------------
>
> Key: AMQNET-96
> URL: https://issues.apache.org/activemq/browse/AMQNET-96
> Project: ActiveMQ .Net
> Issue Type: Improvement
> Components: ActiveMQ
> Reporter: Mark Pollack
> Assignee: Timothy Bish
> Priority: Trivial
> Fix For: 1.2.0
>
>
> It would be nice to extend the IConnection interface to include getting metadata, in Java the method. ConnectionMetaData getMetaData() This could even be a simple IDictionary with key value pairs specific to the vendor.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (AMQNET-96) IConnection interface to support
connection metadata.
Posted by "Jim Gomes (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQNET-96?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jim Gomes updated AMQNET-96:
----------------------------
Fix Version/s: 1.2
(was: 1.1)
> IConnection interface to support connection metadata.
> -----------------------------------------------------
>
> Key: AMQNET-96
> URL: https://issues.apache.org/activemq/browse/AMQNET-96
> Project: ActiveMQ .Net
> Issue Type: Improvement
> Components: ActiveMQ Client
> Reporter: Mark Pollack
> Assignee: James Strachan
> Priority: Trivial
> Fix For: 1.2
>
>
> It would be nice to extend the IConnection interface to include getting metadata, in Java the method. ConnectionMetaData getMetaData() This could even be a simple IDictionary with key value pairs specific to the vendor.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (AMQNET-96) IConnection interface to support
connection metadata.
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQNET-96?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Bish reassigned AMQNET-96:
----------------------------------
Assignee: Jim Gomes (was: Timothy Bish)
Handing off to you for an EMS and MSMQ impl if you want to add one
> IConnection interface to support connection metadata.
> -----------------------------------------------------
>
> Key: AMQNET-96
> URL: https://issues.apache.org/activemq/browse/AMQNET-96
> Project: ActiveMQ .Net
> Issue Type: Improvement
> Components: EMS, MSMQ, NMS
> Reporter: Mark Pollack
> Assignee: Jim Gomes
> Priority: Trivial
> Fix For: 1.2.0
>
> Time Spent: 2 hours
> Remaining Estimate: 0 minutes
>
> It would be nice to extend the IConnection interface to include getting metadata, in Java the method. ConnectionMetaData getMetaData() This could even be a simple IDictionary with key value pairs specific to the vendor.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.