HttpMessage.getBody(Map.class) stopped working when migrated from Camel 2 to 3.20.4

Hello, I've used to rely on this function in older Camel, when I was able to deserialize a regular web form POST stream into a generic java.util.Map, I mean, this used to parse the form data (not multipart, just regular) and convert into a Map: Map map = http.getBody(Map.class); This is my

Announcing the Community Over Code 2023 Streaming Track

Hi all, Community Over Code , the ASF conference, will be held in Halifax, Nova Scotia October 7-10, 2023. The call for presentations is open now through July 13, 2023. I am one of the co-chairs for the

Re: Issue in resolving endpoint with property having period

Hi You are using spring and camel manually where you create spring app context and whatnot. Make sure you start spring also, as camel to sync up with spring lifecycle and startup its services such as type converters, properties and whatnot. You can only get better help if you put together a

Re: Issue in resolving endpoint with property having period

Hi, Getting the same issue. Extra information is below for this change Property with key [time] not found, using default value: 5000 Thanks & Regards, Sujeet On Fri, 9 Jun 2023, 15:10 Mikael Koskinen, wrote: > Hi, > > Does the following syntax work: > >

Re: Issue in resolving endpoint with property having period

Hi, Does the following syntax work: from("timer:notification?period={{time:1000}}") pe 9. kesäk. 2023 klo 12.21 Sujeet Singh (sujeetkumarsi...@gmail.com) kirjoitti: > > Hi, > The same issue was reported in stackoverflow 11 months ago. > > java - Using Timer Component with Apache Camel and the

Re: Issue in resolving endpoint with property having period

Hi, The same issue was reported in stackoverflow 11 months ago. java - Using Timer Component with Apache Camel and the period Query Parameter results in error: Error binding property (period=10) with name: period on bean: - Stack Overflow

R: Guaranteed deliveries for spring-rabbitmq producer

Thanks, Ok, I thought it was a general exception handling problem; instead I fell into a bug related to the specific case of missing RabbitMQ exchange. So I'll wait for version 3.21.0 or 4.0 to have the issue fixed. Regards. Marco Cordiner Sytel Reply Via del Giorgione, 59 00147 - Roma -