AW: [ANNOUNCEMENT] Apache Camel 3.0.0 Released

Hi guys, I'm looking forward into working with the new version. Congratulations and respect for your hard work! But I do have some questions: * When will there be a "Camel in Action 3" book from Claus? * Since the migration is quite a task with all the changes, how long is there

AW: pollEnrich with header property from previous exchange

Hi, is it possible for you to determine the topic/hostname and so on outside the camelcontext for example in a static method? That way you could provide camel with the complete url and thus you don't have to use an exchange header. regards daniel Von: Imran

AW: Fwd: Camel always sending MQRFH2 headers to target WebsphereMQ queue

Hi for the encoding do you mean this? .setHeader("JMS_IBM_Character_Set", constant("UTF-8")) You could also use the mq-jms-spring-boot-starter: https://github.com/ibm-messaging/mq-jms-spring Maybe that's better for you. Kind regards, Daniel Von:

AW: BridgeErrorHandler on JMS Endpoint does not work as expected

Hi Claus, thanks a lot. I will try the workaround with the MapJmsMessage as soon as I have time. Best regards, Daniel Novak Von: Claus Ibsen Gesendet: Freitag, 18. Oktober 2019 13:36:02 An: users@camel.apache.org Betreff: Re: BridgeErrorHandler on JMS

AW: BridgeErrorHandler on JMS Endpoint does not work as expected

Hi Claus, this poison message mechanism is yet not configured but I will configure it and then this poisonous message will be treated like you said. That way every other possible poisonous situation will also work and the communication will be more stable so I like the poison message

AW: BridgeErrorHandler on JMS Endpoint does not work as expected

Hi Claus, thanks a lot for the input. I tried the convertBodyTo method but it seems that this method uses the same API which causes the root problem, so that didn't help. But because of your idea I tried a custom made processor public void process(Exchange exchange) throws Exception {

AW: BridgeErrorHandler on JMS Endpoint does not work as expected

Hi Claus, I think the problem with the JMS Consumer is a bug in Camel. As described in CiA2 as soon as I am in the route the configured errorHandler and onException definition should be triggered as soon as an exception occurs. My route is the following: public void configure() {

AW: BridgeErrorHandler on JMS Endpoint does not work as expected

Hi Raymond, I think I had the same problem with the FTP-Producer and I resolved it using an onCompletionExceptionHandler. which I configured for the endpoint. onCompletionExceptionHandler=#myAdapterExceptionHandler Best regards, Daniel Novak Von: Claus

AW: BridgeErrorHandler on JMS Endpoint does not work as expected

No. I think it's 11.4.8 Bridging the consumer with Camel’s error handler But unfortunately it doesn't help me with my case. regards Daniel Von: ski n Gesendet: Mittwoch, 16. Oktober 2019 16:16:52 An: users@camel.apache.org Betreff: Re: BridgeErrorHandler on

AW: BridgeErrorHandler on JMS Endpoint does not work as expected

Hi guys, thanks for the answers. In the meantime I tried with Camel 2.24.2 and the JMS-Component but the problem is still the same. Next I will with the sjms2 component. I think that in the JMS-Component the EndpointMessageListener could do more with the exception as just setting it into

AW: BridgeErrorHandler on JMS Endpoint does not work as expected

That's good to know because I also have other Camel Routes which use SFTP as consuming endpoint. I will check their behaviour too. Regards, Daniel Von: ski n Gesendet: Mittwoch, 16. Oktober 2019 10:51:48 An: users@camel.apache.org Betreff: Re:

BridgeErrorHandler on JMS Endpoint does not work as expected

Hi guys, I tried to use the bridgeErrorHandler flag on my JMS Endpoint but sadly it does not work. Because there is a lot of code which I have to share with you to make you understand my problem I created a stackoverflow question as it is way easier to read and to respond on comments there.

AW: Changing the Default Header Filter Strategy

Hi, if you don't want to configure every endpoint and can't use the defaultFilterStrategy I assume the best way would be to use your own component/endpoint which is a subclass of the camel-endpoint you currently use and which does what you want. You can write the component by yourself and

AW: How to get a Camel for commercial use

Hi there, here is a list of vendors providing commercial support for camel: https://camel.apache.org/manual/latest/commercial-camel-offerings.html Best regards, Daniel Novak Von: 이성규 Gesendet: Mittwoch, 18. September 2019 04:52:31 An: users@camel.apache.org

Definition of subscriptionname in Camel JMS-Endpoint does not work as expected

Dear Camel guys and girls, I have a question regarding the property "subscriptionName" which can be specified for a JMS-Consumer. First, here is my project setup: * Camel 2.24.1 * Spring-Boot: 2.1.0.RELEASE I create a simple standalone JAR which just should consume from defined