On Wed, May 4, 2011 at 3:54 PM, bvahdat <babak.vah...@swissonline.ch> wrote:
> Hi Claus,
>
> Thanks for your reply!
>
> So my same question again: for the sake of avoiding the spring's warning
> mentioned already, would the following change on
> 'org.apache.camel.component.jms.JmsMessageListenerContainer' constructor
> make sense to you:
>
> public JmsMessageListenerContainer(JmsEndpoint endpoint, ErrorHandler
> errorHandler) {
> this.endpoint = endpoint;
> this.setErrorHandler(errorHandler); // set the spring's proprietary
> error handler
> }
>
> Or that you would provide a setter/getter API for ErrorHandler on
> 'org.apache.camel.component.jms.JmsConfiguration' so that we (the camel
> users) could inject an appropriate ErrorHandler implementation from outside.
>
Yeah that would be nice so people can plugin their custom spring error
handler of choice.
Patches is welcome. And having an unit test as well is much better.
Then we love those patches even more :)
> Regards, Babak
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/error-handling-on-Http-POST-from-ActiveMQ-to-PHP-application-tp4347185p4369891.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
--
Claus Ibsen
-----------------
FuseSource
Email: cib...@fusesource.com
Web: http://fusesource.com
CamelOne 2011: http://fusesource.com/camelone2011/
Twitter: davsclaus
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/
