41 AM Calle Andersson
wrote:
>
> Unfortunately I currently have limited access to the logs (I'm out of office)
> but I think we only get the following in the log:
>
> WARN [org.apache.camel.component.jpa.JpaConsumer] (Camel
> (camelContext_myContext) thread #26 - jp
JPA consumer logging
Hi
Is it this WARN log you see?
LOG.warn(
"Error processing last message due: {}. Will commit all
previous successful processed message, and ignore this last failure.",
cause.getMessage(), cause);
On Tue, Feb 15, 2022 at 3:28 PM Calle Andersson
Hi,
I recently discovered that the JPA consumer only logs WARN when failing to
populate an entity class (in my specific case, an exception occurred since an
unexpected null couldn’t be mapped to an int).
If I understand it correctly, the JPA consumer uses a LoggingExceptionHandler.
Is there a
There seems to be mixed opinions regarding which of the previously LTS versions
should be available in the documentation pages. Is this a question which will
be discussed further?
Regards,
Calle
ag 28 september 2021 13:58
Till: users@camel.apache.org
Ämne: Re: Camel 3.4 documentation
Hi
You can find component docs in the source code, you can browse on
github for the 3.4.x branch and look in src/main/docs for the
components
On Tue, Sep 28, 2021 at 1:41 PM Calle Andersson
wrote:
>
> H
Hi,
I just noticed the "3.4.x (LTS)" option has been removed from the Camel
Components documentation pages (https://camel.apache.org/components/). Is there
an alternative location where I can find the 3.4.x documentation?
(I currently use Wildfly Camel
(https://github.com/wildfly-extras/wildfl
Hi,
I use Camel 3.4 (I have to use that version) and have a problem when using REST
DSL.
I have the following route:
rest().tag("dummy")
.post()
.route().
.log("### Inside 'first'")
.endRest()
.post("tmp").
.route()
.log("### Inside 'second
Ämne: Re: Passing exchange header into JPA component query
Hi
You can try test this with 3.11.x as there has been a number of
improvements and bug fixes in the endpoint-dsl and whatnot since this
release.
On Tue, Aug 24, 2021 at 6:39 PM Calle Andersson
wrote:
>
> Hi,
>
> I use Camel 3.
Hi,
I use Camel 3.4 and have a question regarding the JPA component.
I have the following query:
SELECT c FROM " + MyEntity.class.getName() + " c WHERE c.dummy = :myParam
I have been trying to get the following configuration to work (using Endpoint
DSL):
.toD(jpa(MyEntity.class.getName()).query
I finally found a solution to my problem. It turned out 'contentTypeHeader'
could be set to 'false' in the following simple way:
restConfiguration().dataFormatProperty("contentTypeHeader", "false")...
Now I am able to return responses with custom Content-Type values.
As a complement to my last answer, one of the reasons I want to set a custom
Content-Type value is because we include versioning in our custom media types
(I skipped this part to simplify my example code in earlier mails). We simply
want to use Content-Type to show the type and version of the da
Hi again,
Is there anyone who can confirm if this behaviour is by design or a bug?
Thanks in advance,
Calle
Från: Calle Andersson
Skickat: fredag 2 juli 2021 16:19
Till: users@camel.apache.org
Ämne: Exchange headers disappears when using JPA component
Hi
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,
I’m migrating some Camel projects from Camel 2.17 to 3.4.
I have a Camel REST DSL based route in which I try to manually set the
”Content-Type” HTTP header of the response. However, no matter what values I
try to set in the route, the only values shown in the responses are either
”appl
Sorry for the spamming. My thoughts are starting to run circles in my mind. :)
Ad 3)
I believe you could ignore the comment regarding CamelHttpRawQuery not beeing
URL encoded since it seems to be handled in HttpHelter.createURI(...). (I saw
the CamelHttpQuery and CamelHttpRawQuery headers beeing
A complement to my last mail.
Ad 3)
After some more investigation I realized that the http-component consumer
doesn't set the CamelHttpRawQuery header (so maybe it isn't a miss in the
documentation after all).
However, the header is still handled by the code I referenced in my last mail
when
Ad 1)
With path parameter I mean {name} in your example (or {id} and {somePathParam}
in the examples from my first mail).
Ad 2)
Does this mean that if I use toD with the http-component, optimization will
always be used no mather how I define the component path (e.g.
toD(http("dummyHost:8181/dum
The most important questions (from my previously mail) which I hope to find an
answer to is:
1. How come the CamelHttpPath header is empty when a Camel REST DSL endpoint
doesn't consists of any path parameters? Is it by design or a bug?
2. In the toD documentation it says that for the optimisat
Hi,
I’m migrating several (around 20-30) Camel REST DSL projects from Camel 2.17 to
3.4. The projects use a similar solution pattern to route incoming calls to
backend systems with a similar URL as the Camel REST endpoints. E.g. when
calling:
http://localhost:8080/services/rest/dummy/lorem/i
Hi,
I was just about to start migrating all our integrations to Camel 3.4 and then
I realized Camel 3.7 was released a couple of days ago. (I want to use Camel
LTS releases only.)
I tried to find out if and when wildfly-camel will support Camel 3.7 but I
can’t find any information about it
21 matches
Mail list logo
