You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@activemq.apache.org by "Hiram Chirino (JIRA)" <ji...@apache.org> on 2006/06/12 22:02:51 UTC

[jira] Updated: (AMQ-751) Extend ExceptionListener mechanism by creating a custom AMQ exception which would provide more detail about the exception

     [ https://issues.apache.org/activemq/browse/AMQ-751?page=all ]

Hiram Chirino updated AMQ-751:
------------------------------

    Fix Version: 4.1
       Priority: Minor  (was: Major)

Sounds like a good idea.  Lets try to get it in for 4.1

> Extend ExceptionListener mechanism by creating a custom AMQ exception which would provide more detail about the exception
> -------------------------------------------------------------------------------------------------------------------------
>
>          Key: AMQ-751
>          URL: https://issues.apache.org/activemq/browse/AMQ-751
>      Project: ActiveMQ
>         Type: Improvement

>   Components: JMS client, Broker
>     Reporter: Massive Boisson
>     Priority: Minor
>      Fix For: 4.1

>
>
> To quote James:
> "I wonder if we could add a neater non-JMS extension to ActiveMQ to make it easier to be notified asynchronously of which Message objects could not be sent? I guess we could just use the ExceptionListener and use a custom type of Exception which contained the Message object?"
> I think this would greatly increase the usefulness of async sends.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira