You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Timothy Bish (JIRA)" <ji...@apache.org> on 2009/11/19 22:43:52 UTC

[jira] Created: (AMQCPP-269) Update CMS API to include the proper exceptions in the Message interfaces throw declarations

Update CMS API to include the proper exceptions in the Message interfaces throw declarations
--------------------------------------------------------------------------------------------

                 Key: AMQCPP-269
                 URL: https://issues.apache.org/activemq/browse/AMQCPP-269
             Project: ActiveMQ C++ Client
          Issue Type: Improvement
          Components: CMS Impl
            Reporter: Timothy Bish
            Assignee: Timothy Bish


CMS now includes several exception types:

MessageFormatException
MessageEOFException
MessageNotReadableException

etc...

The CMS Message interfaces should be updated to indicate which of these is thrown from the various methods in the Message classes.  The ActiveMQ implementation of the CMS interface will need to be updated as well to actually throw these types.



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


[jira] Updated: (AMQCPP-269) Update CMS API to include the proper exceptions in the Message interfaces throw declarations

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

Timothy Bish updated AMQCPP-269:
--------------------------------

    Affects Version/s: 3.0.1
        Fix Version/s: 3.1

> Update CMS API to include the proper exceptions in the Message interfaces throw declarations
> --------------------------------------------------------------------------------------------
>
>                 Key: AMQCPP-269
>                 URL: https://issues.apache.org/activemq/browse/AMQCPP-269
>             Project: ActiveMQ C++ Client
>          Issue Type: Improvement
>          Components: CMS Impl
>    Affects Versions: 3.0.1
>            Reporter: Timothy Bish
>            Assignee: Timothy Bish
>             Fix For: 3.1
>
>
> CMS now includes several exception types:
> MessageFormatException
> MessageEOFException
> MessageNotReadableException
> etc...
> The CMS Message interfaces should be updated to indicate which of these is thrown from the various methods in the Message classes.  The ActiveMQ implementation of the CMS interface will need to be updated as well to actually throw these types.

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


[jira] Resolved: (AMQCPP-269) Update CMS API to include the proper exceptions in the Message interfaces throw declarations

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

Timothy Bish resolved AMQCPP-269.
---------------------------------

    Resolution: Fixed

Updates in Trunk.

> Update CMS API to include the proper exceptions in the Message interfaces throw declarations
> --------------------------------------------------------------------------------------------
>
>                 Key: AMQCPP-269
>                 URL: https://issues.apache.org/activemq/browse/AMQCPP-269
>             Project: ActiveMQ C++ Client
>          Issue Type: Improvement
>          Components: CMS Impl
>    Affects Versions: 3.0.1
>            Reporter: Timothy Bish
>            Assignee: Timothy Bish
>             Fix For: 3.1
>
>
> CMS now includes several exception types:
> MessageFormatException
> MessageEOFException
> MessageNotReadableException
> etc...
> The CMS Message interfaces should be updated to indicate which of these is thrown from the various methods in the Message classes.  The ActiveMQ implementation of the CMS interface will need to be updated as well to actually throw these types.

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