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/15 00:56:32 UTC

[jira] Created: (AMQCPP-129) Implement QueueBrowser

Implement QueueBrowser
----------------------

                 Key: AMQCPP-129
                 URL: https://issues.apache.org/activemq/browse/AMQCPP-129
             Project: ActiveMQ C++ Client
          Issue Type: New Feature
            Reporter: Albert Strasheim
            Assignee: Nathan Mittler
            Priority: Minor
             Fix For: 2.2


>From the JMS 1.1 spec:

5.9 QueueBrowser

A client uses a QueueBrowser to look at messages on a queue without removing
them. A QueueBrowser can be created from a Session or a QueueSession.

The browse methods return a java.util.Enumeration that is used to scan the
queue's messages. It may be an enumeration of the entire content of a queue,
or it may contain only the messages matching a message selector.

Messages may be arriving and expiring while the scan is done. JMS does not
require the content of an enumeration to be a static snapshot of queue content.
Whether these changes are visible or not depends on the JMS provider.

I think I might tackle this in a few weeks' time.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (AMQCPP-129) Implement QueueBrowser

Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/AMQCPP-129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Timothy Bish updated AMQCPP-129:
--------------------------------

    Fix Version/s:     (was: 3.0)
                   3.1

> Implement QueueBrowser
> ----------------------
>
>                 Key: AMQCPP-129
>                 URL: https://issues.apache.org/activemq/browse/AMQCPP-129
>             Project: ActiveMQ C++ Client
>          Issue Type: New Feature
>            Reporter: Albert Strasheim
>            Assignee: Timothy Bish
>            Priority: Minor
>             Fix For: 3.1
>
>
> From the JMS 1.1 spec:
> 5.9 QueueBrowser
> A client uses a QueueBrowser to look at messages on a queue without removing
> them. A QueueBrowser can be created from a Session or a QueueSession.
> The browse methods return a java.util.Enumeration that is used to scan the
> queue's messages. It may be an enumeration of the entire content of a queue,
> or it may contain only the messages matching a message selector.
> Messages may be arriving and expiring while the scan is done. JMS does not
> require the content of an enumeration to be a static snapshot of queue content.
> Whether these changes are visible or not depends on the JMS provider.
> I think I might tackle this in a few weeks' time.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Resolved: (AMQCPP-129) Implement QueueBrowser

Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/AMQCPP-129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Timothy Bish resolved AMQCPP-129.
---------------------------------

    Resolution: Fixed

Fixed in trunk.  Updated QueueBrowser interface in CMS to properly implement this feature.

> Implement QueueBrowser
> ----------------------
>
>                 Key: AMQCPP-129
>                 URL: https://issues.apache.org/activemq/browse/AMQCPP-129
>             Project: ActiveMQ C++ Client
>          Issue Type: New Feature
>            Reporter: Albert Strasheim
>            Assignee: Timothy Bish
>            Priority: Minor
>             Fix For: 3.2.0
>
>
> From the JMS 1.1 spec:
> 5.9 QueueBrowser
> A client uses a QueueBrowser to look at messages on a queue without removing
> them. A QueueBrowser can be created from a Session or a QueueSession.
> The browse methods return a java.util.Enumeration that is used to scan the
> queue's messages. It may be an enumeration of the entire content of a queue,
> or it may contain only the messages matching a message selector.
> Messages may be arriving and expiring while the scan is done. JMS does not
> require the content of an enumeration to be a static snapshot of queue content.
> Whether these changes are visible or not depends on the JMS provider.
> I think I might tackle this in a few weeks' time.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (AMQCPP-129) Implement QueueBrowser

Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/AMQCPP-129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Timothy Bish updated AMQCPP-129:
--------------------------------

    Fix Version/s:     (was: 3.1)
                   3.2.0

> Implement QueueBrowser
> ----------------------
>
>                 Key: AMQCPP-129
>                 URL: https://issues.apache.org/activemq/browse/AMQCPP-129
>             Project: ActiveMQ C++ Client
>          Issue Type: New Feature
>            Reporter: Albert Strasheim
>            Assignee: Timothy Bish
>            Priority: Minor
>             Fix For: 3.2.0
>
>
> From the JMS 1.1 spec:
> 5.9 QueueBrowser
> A client uses a QueueBrowser to look at messages on a queue without removing
> them. A QueueBrowser can be created from a Session or a QueueSession.
> The browse methods return a java.util.Enumeration that is used to scan the
> queue's messages. It may be an enumeration of the entire content of a queue,
> or it may contain only the messages matching a message selector.
> Messages may be arriving and expiring while the scan is done. JMS does not
> require the content of an enumeration to be a static snapshot of queue content.
> Whether these changes are visible or not depends on the JMS provider.
> I think I might tackle this in a few weeks' time.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (AMQCPP-129) Implement QueueBrowser

Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/AMQCPP-129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Timothy Bish updated AMQCPP-129:
--------------------------------

    Fix Version/s:     (was: 2.3)
                   2.4.0

> Implement QueueBrowser
> ----------------------
>
>                 Key: AMQCPP-129
>                 URL: https://issues.apache.org/activemq/browse/AMQCPP-129
>             Project: ActiveMQ C++ Client
>          Issue Type: New Feature
>            Reporter: Albert Strasheim
>            Assignee: Timothy Bish
>            Priority: Minor
>             Fix For: 2.4.0
>
>
> From the JMS 1.1 spec:
> 5.9 QueueBrowser
> A client uses a QueueBrowser to look at messages on a queue without removing
> them. A QueueBrowser can be created from a Session or a QueueSession.
> The browse methods return a java.util.Enumeration that is used to scan the
> queue's messages. It may be an enumeration of the entire content of a queue,
> or it may contain only the messages matching a message selector.
> Messages may be arriving and expiring while the scan is done. JMS does not
> require the content of an enumeration to be a static snapshot of queue content.
> Whether these changes are visible or not depends on the JMS provider.
> I think I might tackle this in a few weeks' time.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Assigned: (AMQCPP-129) Implement QueueBrowser

Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/AMQCPP-129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Timothy Bish reassigned AMQCPP-129:
-----------------------------------

    Assignee: Timothy Bish  (was: Nathan Mittler)

> Implement QueueBrowser
> ----------------------
>
>                 Key: AMQCPP-129
>                 URL: https://issues.apache.org/activemq/browse/AMQCPP-129
>             Project: ActiveMQ C++ Client
>          Issue Type: New Feature
>            Reporter: Albert Strasheim
>            Assignee: Timothy Bish
>            Priority: Minor
>             Fix For: 2.3
>
>
> From the JMS 1.1 spec:
> 5.9 QueueBrowser
> A client uses a QueueBrowser to look at messages on a queue without removing
> them. A QueueBrowser can be created from a Session or a QueueSession.
> The browse methods return a java.util.Enumeration that is used to scan the
> queue's messages. It may be an enumeration of the entire content of a queue,
> or it may contain only the messages matching a message selector.
> Messages may be arriving and expiring while the scan is done. JMS does not
> require the content of an enumeration to be a static snapshot of queue content.
> Whether these changes are visible or not depends on the JMS provider.
> I think I might tackle this in a few weeks' time.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (AMQCPP-129) Implement QueueBrowser

Posted by "Nathan Mittler (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/AMQCPP-129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nathan Mittler updated AMQCPP-129:
----------------------------------

    Fix Version/s:     (was: 2.2)
                   2.3

> Implement QueueBrowser
> ----------------------
>
>                 Key: AMQCPP-129
>                 URL: https://issues.apache.org/activemq/browse/AMQCPP-129
>             Project: ActiveMQ C++ Client
>          Issue Type: New Feature
>            Reporter: Albert Strasheim
>            Assignee: Nathan Mittler
>            Priority: Minor
>             Fix For: 2.3
>
>
> From the JMS 1.1 spec:
> 5.9 QueueBrowser
> A client uses a QueueBrowser to look at messages on a queue without removing
> them. A QueueBrowser can be created from a Session or a QueueSession.
> The browse methods return a java.util.Enumeration that is used to scan the
> queue's messages. It may be an enumeration of the entire content of a queue,
> or it may contain only the messages matching a message selector.
> Messages may be arriving and expiring while the scan is done. JMS does not
> require the content of an enumeration to be a static snapshot of queue content.
> Whether these changes are visible or not depends on the JMS provider.
> I think I might tackle this in a few weeks' time.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.