Thanks for the answer,
The REST service is always called with the HTTP "Accept" header set as one of
the custom media types ("application/my.dummy.mediatype+xml" or
"application/my.dummy.mediatype+json"). The REST DSL based route uses the value
of that HTTP header to populate the "Accept" heade
Hi,
In Camel 3.4, the exchange headers disappears when using the JPA component
(example using Endpoint DSL):
.to(jpa(DummyEntity.class.getName()).persistenceUnit("dummyPU").query("SELECT c
FROM " + DummyEntity.class.getName() + " c"))
I believe the headers dissappears since the exchange pa
Hi
This would be the first time I hear about this.
Do you have only one active Camel application (node) that runs this
route with the FTP consumer?
If you can reproduce this on a test environment, then you are also
welcome to try with Camel 3.11.0 release.
On Thu, Jul 1, 2021 at 5:12 PM Carsten
Hi
Are you sure you want to set the Content-Type: Accept
I think this is wrong.
The content type is what the structure of the message body is, such as
xml, plain text, json, etc.
However there is a HTTP Accept header that a client can use to tell
the server what content-type the client can accep
Hi
Can you put together a sample project that demonstrates this and put
either on github somewhere, or create a JIRA ticket and attach as .zip
file.
Then we can take a look at it
On Fri, Jul 2, 2021 at 9:06 AM Klug Andreas (CI/XDM1)
wrote:
>
> Hello everyone,
>
> I'm using Camel 3.11 with Spring
Hello everyone,
I'm using Camel 3.11 with Spring Boot 2.5.1, having a route template configured
in Java DSL approximately like this:
routeTemplate()
...
from("quartz://)
...
.circuitBreaker().resilience4jConfiguration(...)
.process(ExceptionHandlers::patchMDC)
...
.split()..header(..
