Extend ExceptionListener mechanism by creating a custom AMQ exception which would provide more detail about the exception

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.