[RESULT] [VOTE] Release Apache Camel Kamelets 4.4.1
Hello all, The vote passes with the following result: 7 +1 binding votes: Andrea Cosentino, Claus Ibsen, Babak Vahdat, Jean-Baptiste Onofrè, Zineb Bendhiba, Pasquale Congiusti and Otavio Rodolfo Piske 2 +1 non-binding votes: Claudio Miranda and Gaelle Fournier Thanks to all the voters. I'll go ahead with the process.
Re: [VOTE] Release Apache Camel Kamelets 4.4.1
Thanks all, The vote passes. I'll go ahead. Il giorno lun 25 mar 2024 alle ore 17:30 Otavio Rodolfo Piske < angusyo...@gmail.com> ha scritto: > +1 (binding) > > Thanks! > > On Mon, Mar 25, 2024 at 12:22 PM Pasquale Congiusti < > pasquale.congiu...@gmail.com> wrote: > > > +1 (binding) > > > > Thanks! > > > > Pasquale. > > > > On Fri, Mar 22, 2024 at 7:05 AM Andrea Cosentino > > wrote: > > > > > Hello all, > > > > > > This is a vote for releasing camel-kamelets 4.4.1 > > > > > > This is the second release of camel-kamelets supporting LTS Camel 4.4.x > > and > > > it contains alignment to 4.4.1 and some fixes. > > > > > > Kamelets release files: > > > https://dist.apache.org/repos/dist/dev/camel/camel-kamelets/4.4.1 > > > Kamelets staging repository: > > > https://repository.apache.org/content/repositories/orgapachecamel-1687 > > > Kamelets Tag: > > > https://github.com/apache/camel-kamelets/releases/tag/v4.4.1 > > > > > > Please cast your vote. > > > > > > [ ] +1 Release camel-kamelets 4.4.1 > > > [ ] -1 Veto the release (provide specific comments) > > > > > > The vote is open for at least 72 hours. > > > > > > Here's my +1. > > > > > > Thanks, > > > Andrea Cosentino > > > > > > > > -- > Otavio R. Piske > http://orpiske.net >
Svar: Re: Svar: Re: Issue with unit or work and toV endpoint when Excetion thrown
Sorry cry wolf
My bad
/M
Den 26 mars 2024 kl 10:46, Mikael Andersson Wigander
<[mikael.andersson.wigan...@pm.me.INVALID](mailto:Den 26 mars 2024 kl 10:46,
Mikael Andersson Wigander < skrev:
> Hi and thanks for the fix.
>
> However there are some additional issues.
>
> The rest dsl is not returning the correct status code.
>
> I have reverted back to a normal flow using .to().
>
> Not sure if it’s related.
>
> But I’m not capable to return the correct http status code. The error message
> is returned but with 200 OK.
>
> /M
>
> Den 23 mars 2024 kl 09:27, Claus Ibsen <[claus.ib...@gmail.com](mailto:Den 23
> mars 2024 kl 09:27, Claus Ibsen < skrev:
>
>> Hi
>>
>> Thanks for the sample project. This is the http response I see now after a
>> code-fix
>>
>> ~/workspace ❯ curl -i -X POST http://localhost:8080/test
>>
>> 8s
>> HTTP/1.1 500
>> Content-Type: application/json
>> Transfer-Encoding: chunked
>> Date: Sat, 23 Mar 2024 08:02:31 GMT
>> Connection: close
>>
>> {
>> "status" : 1000,
>> "message" : "ERROR message = Unspecific Error(Error occurred)"
>> }%
>>
>> On Sat, Mar 23, 2024 at 9:15 AM Claus Ibsen wrote:
>>
>>> Hi
>>>
>>> https://issues.apache.org/jira/browse/CAMEL-20607
>>>
>>> On Thu, Mar 21, 2024 at 1:03 PM Mikael Andersson Wigander
>>> wrote:
>>>
Hi
As simple as I get do it…
https://github.com/hakuseki/demo-Camel-UoW
/M
On Thursday, March 21st, 2024 at 11:09, Claus Ibsen <
claus.ib...@gmail.com> wrote:
> Hi
>
> Yeah if you keep it plain camel and not fancy spring boot stuff
>
> On Thu, Mar 21, 2024 at 11:06 AM Mikael Andersson Wigander
> mikael.andersson.wigan...@pm.me.invalid wrote:
>
> > Spring boot OK?
> >
> >
> > /M
> >
> > Den 21 mars 2024 kl 10:51, Claus Ibsen <[claus.ib...@gmail.com
](mailto:Den
> > 21 mars 2024 kl 10:51, Claus Ibsen < skrev:
> >
> > > Hi
> > >
> > > Can you make something that is pure camel (not quarkus) that will
help
> > >
> > > On Thu, Mar 21, 2024 at 7:56 AM Mikael Andersson Wigander
> > > mikael.andersson.wigan...@pm.me.invalid wrote:
> > >
> > > > Here's a repo to use
> > > >
> > > > https://github.com/hakuseki/code-with-quarkus
> > > >
> > > > /M
> > > >
> > > > On Wednesday, March 20th, 2024 at 22:17, Claus Ibsen <
> > > > claus.ib...@gmail.com> wrote:
> > > >
> > > > > Hi
> > > > >
> > > > > Are you able to put together a smaller and simpler example with
just
> > > > > routes
> > > > > (no rest-dsl) that can let us quicker take a look and better
> > > > > understand
> > > > > what is happening?
> > > > >
> > > > > On Mon, Mar 18, 2024 at 10:04 AM Mikael Andersson Wigander
> > > > > mikael.andersson.wigan...@pm.me.invalid wrote:
> > > > >
> > > > > > Hi
> > > > > >
> > > > > > I have experienced a weird behavior in Camel 4.4.0 in Quarkus
where
> > > > > > the
> > > > > > Exception handling is not executing as expected when using a
toV().
> > > > > >
> > > > > > In my code sample below everything starts with a rest call.
> > > > > > If this rest call finish without errors then the original
message
> > > > > > should
> > > > > > be returned.
> > > > > > If an error is thrown, then an error message should be
returned.
> > > > > >
> > > > > > But if I call an endpoint using the .toV(), the error is
processed
> > > > > > as
> > > > > > expected BUT NOT returned. It seems like something is messing
with
> > > > > > the
> > > > > > unit
> > > > > > of work or whatever…
> > > > > >
> > > > > > from(direct("start"))
> > > > > > .setBody(constant(List.of("A", "B")))
> > > > > > .to(direct("line"));
> > > > > >
> > > > > > // .toV(direct("line").getUri(), "mySend", "myReceive");
> > > > > >
> > > > > > By commenting out the .to() and removing the comment on
.toV() the
> > > > > > problem
> > > > > > occurs.
> > > > > >
> > > > > > This is a simulation so the incoming rest post payload is NOT
> > > > > > returned
> > > > > > (just POST a JSON), however the body of the "start" endpoint
should
> > > > > > be
> > > > > > returned if everything work, but an error message should be
returned
> > > > > > if an
> > > > > > error is thrown.
> > > > > > This is not happening if the .toV() is used. Then the body of
the
> > > > > > "start"
> > > > > > endpoint is returned.
> > > > > >
> > > > > > Might this be a bug or have I messed something up?
> > > > > >
> > > > > > I really like the Variables now, to send to an endpoint and be
> > > > > > certain
> > > > > > the
> > > > > > original body is untouched
Svar: Re: Svar: Re: Issue with unit or work and toV endpoint when Excetion thrown
Hi and thanks for the fix.
However there are some additional issues.
The rest dsl is not returning the correct status code.
I have reverted back to a normal flow using .to().
Not sure if it’s related.
But I’m not capable to return the correct http status code. The error message
is returned but with 200 OK.
/M
Den 23 mars 2024 kl 09:27, Claus Ibsen <[claus.ib...@gmail.com](mailto:Den 23
mars 2024 kl 09:27, Claus Ibsen < skrev:
> Hi
>
> Thanks for the sample project. This is the http response I see now after a
> code-fix
>
> ~/workspace ❯ curl -i -X POST http://localhost:8080/test
>
> 8s
> HTTP/1.1 500
> Content-Type: application/json
> Transfer-Encoding: chunked
> Date: Sat, 23 Mar 2024 08:02:31 GMT
> Connection: close
>
> {
> "status" : 1000,
> "message" : "ERROR message = Unspecific Error(Error occurred)"
> }%
>
> On Sat, Mar 23, 2024 at 9:15 AM Claus Ibsen wrote:
>
>> Hi
>>
>> https://issues.apache.org/jira/browse/CAMEL-20607
>>
>> On Thu, Mar 21, 2024 at 1:03 PM Mikael Andersson Wigander
>> wrote:
>>
>>>
>>> Hi
>>>
>>> As simple as I get do it…
>>>
>>> https://github.com/hakuseki/demo-Camel-UoW
>>>
>>>
>>>
>>> /M
>>>
>>>
>>> On Thursday, March 21st, 2024 at 11:09, Claus Ibsen <
>>> claus.ib...@gmail.com> wrote:
>>>
>>> > Hi
>>> >
>>> > Yeah if you keep it plain camel and not fancy spring boot stuff
>>> >
>>> > On Thu, Mar 21, 2024 at 11:06 AM Mikael Andersson Wigander
>>> > mikael.andersson.wigan...@pm.me.invalid wrote:
>>> >
>>> > > Spring boot OK?
>>> > >
>>> > >
>>> > > /M
>>> > >
>>> > > Den 21 mars 2024 kl 10:51, Claus Ibsen <[claus.ib...@gmail.com
>>> ](mailto:Den
>>> > > 21 mars 2024 kl 10:51, Claus Ibsen < skrev:
>>> > >
>>> > > > Hi
>>> > > >
>>> > > > Can you make something that is pure camel (not quarkus) that will
>>> help
>>> > > >
>>> > > > On Thu, Mar 21, 2024 at 7:56 AM Mikael Andersson Wigander
>>> > > > mikael.andersson.wigan...@pm.me.invalid wrote:
>>> > > >
>>> > > > > Here's a repo to use
>>> > > > >
>>> > > > > https://github.com/hakuseki/code-with-quarkus
>>> > > > >
>>> > > > > /M
>>> > > > >
>>> > > > > On Wednesday, March 20th, 2024 at 22:17, Claus Ibsen <
>>> > > > > claus.ib...@gmail.com> wrote:
>>> > > > >
>>> > > > > > Hi
>>> > > > > >
>>> > > > > > Are you able to put together a smaller and simpler example with
>>> just
>>> > > > > > routes
>>> > > > > > (no rest-dsl) that can let us quicker take a look and better
>>> > > > > > understand
>>> > > > > > what is happening?
>>> > > > > >
>>> > > > > > On Mon, Mar 18, 2024 at 10:04 AM Mikael Andersson Wigander
>>> > > > > > mikael.andersson.wigan...@pm.me.invalid wrote:
>>> > > > > >
>>> > > > > > > Hi
>>> > > > > > >
>>> > > > > > > I have experienced a weird behavior in Camel 4.4.0 in Quarkus
>>> where
>>> > > > > > > the
>>> > > > > > > Exception handling is not executing as expected when using a
>>> toV().
>>> > > > > > >
>>> > > > > > > In my code sample below everything starts with a rest call.
>>> > > > > > > If this rest call finish without errors then the original
>>> message
>>> > > > > > > should
>>> > > > > > > be returned.
>>> > > > > > > If an error is thrown, then an error message should be
>>> returned.
>>> > > > > > >
>>> > > > > > > But if I call an endpoint using the .toV(), the error is
>>> processed
>>> > > > > > > as
>>> > > > > > > expected BUT NOT returned. It seems like something is messing
>>> with
>>> > > > > > > the
>>> > > > > > > unit
>>> > > > > > > of work or whatever…
>>> > > > > > >
>>> > > > > > > from(direct("start"))
>>> > > > > > > .setBody(constant(List.of("A", "B")))
>>> > > > > > > .to(direct("line"));
>>> > > > > > >
>>> > > > > > > // .toV(direct("line").getUri(), "mySend", "myReceive");
>>> > > > > > >
>>> > > > > > > By commenting out the .to() and removing the comment on
>>> .toV() the
>>> > > > > > > problem
>>> > > > > > > occurs.
>>> > > > > > >
>>> > > > > > > This is a simulation so the incoming rest post payload is NOT
>>> > > > > > > returned
>>> > > > > > > (just POST a JSON), however the body of the "start" endpoint
>>> should
>>> > > > > > > be
>>> > > > > > > returned if everything work, but an error message should be
>>> returned
>>> > > > > > > if an
>>> > > > > > > error is thrown.
>>> > > > > > > This is not happening if the .toV() is used. Then the body of
>>> the
>>> > > > > > > "start"
>>> > > > > > > endpoint is returned.
>>> > > > > > >
>>> > > > > > > Might this be a bug or have I messed something up?
>>> > > > > > >
>>> > > > > > > I really like the Variables now, to send to an endpoint and be
>>> > > > > > > certain
>>> > > > > > > the
>>> > > > > > > original body is untouched without the hazzle of
>>> storing/restoring
>>> > > > > > > logic…
>>> > > > > > >
>>> > > > > > > /M
>>> > > > > > >
>>> > > > > > > *public class *TestRouter *extends *EndpointRouteBuilder {
>>> > > > > > > @Override
>>> > > > > > > *public void *configure() *throws Exception {
>>> > > > > > > onException(IllegalAccessException.class)
>>> > > > > > >
