Hi
Ah yeah those were an idea to include the full page documentation in
case tooling may be able to use that for something useable.
However the tooling uses all the other bits, so we have just marked
those apis as deprecated.
So we can remove the files from the camel-catalog.
I have created a
"Binding" sounds good to me, too.
On Fri, Aug 20, 2021 at 7:07 PM Claus Ibsen wrote:
> Hi
>
> Yeah one of the hardest problem is naming, and after that renaming as
> a lot of old stuff "expects" the old name.
>
> I am also leading to Binding, as we have other concepts in Camel K
> that are
The level of details for the website build is great. Especially I like that
the log shows 'refname'. I'm always confused to see warns even if I fix up
the main branch.
On Tue, Aug 17, 2021 at 8:27 PM Claus Ibsen wrote:
> Hi
>
> Oh that is great to see more detailed WARN / ERROR as today we get
Hi Onder,
I found the explanation for this behavior. It's caused by
"constant(500)" in the expression:
exchange.getIn().setHeader(Exchange.HTTP_RESPONSE_CODE, constant(500));
The constant expression isn't evaluted to an integer when it is set;
instead it is stored as a ValueBuilder object in
