Hi
Yeah you can find the ranges in
https://github.com/spring-io/start.spring.io/blob/master/start-site/src/main/resources/application.yml
On Mon, Aug 31, 2020 at 9:51 PM Mark Nuttall wrote:
>
> go to start.spring.io/info. It will tell you compatible versions.
>
> On Mon, Aug 31, 2020 at 3:42 PM
Ok, I guess that was a little long. Let's try this:
Given this simple route:
from("seda:experiment")
.toD("http://localhost:8090/sleep?delay=${body}";) // an endpoint that
sleeps for 10*delay seconds
.process("MyProcessor");
How do I asynchronously call "seda:experiment" from another
"If the Spring Boot version is outdated, the UI will request you to make a
choice and select a supported version."
Doesn't work, I'm afraid
/M
‐‐‐ Original Message ‐‐‐
On Monday 31 August 2020 kl. 21:50, Mark Nuttall wrote:
> go to start.spring.io/info. It will tell you compatible ver
Thanks for the reply Zheng.
I'm running very similar code in the TomEE and It doesn't fail on NPE. See
similar behaviour though:
[Thread-0 (ActiveMQ-client] WARN o.a.c.jta.TransactionErrorHandler -
Transaction rollback (0x30730302) redelivered(false) for (MessageId:
ID:9fd77209-ebc6-11ea-955a
go to start.spring.io/info. It will tell you compatible versions.
On Mon, Aug 31, 2020 at 3:42 PM Mikael Andersson Wigander
wrote:
> I have read somewhere on the site the maximum dependency for Spring Boot
> for Camel 2.x but can't find it.
> What's the recommendation?
>
> We have an app heavily
I have read somewhere on the site the maximum dependency for Spring Boot for
Camel 2.x but can't find it.
What's the recommendation?
We have an app heavily dependent on Camel and need to upgrade Spring Boot to
2.2.0.RELEASE due to problems with jUnit5 and 2.1.9.RELEASE using vintage jUnit
tests
Hi Claus - that did the trick. Thanks for your speedy reply! Perhaps the
Javadoc in ConsumerTemplate's receive methods can be amended to reflect
this? I was thrown off initially by the comment there. Happy to make
amendments if worthwhile.
On Mon, Aug 31, 2020 at 11:36 AM Claus Ibsen wrote:
> Hi
Hi
SEDA is built with queueing in mind so those uow works gets handed
over when the exchange is placed on the queue.
direct does not so the route with sftp consumer will done the uow. And
then you do it again with the consumer template.
On Mon, Aug 31, 2020 at 2:44 PM Anthony Wu wrote:
>
> Than
Thanks Claus. Using SEDA seems to work, but it does seem strange that the
exchange is being "done" twice (or something else done two times). The
meaning of this was to test some functionality of an existing route. Should
that existing route be changed to SEDA in that case?
On Mon, Aug 31, 2020 at
There are no cloud formation templates available in the project actually.
Il lun 31 ago 2020, 12:06 senthil kumar sk ha
scritto:
> Hi ,
>
> We required help for camel components deployed in AWS cloud.
> Please share any cloud formation template is available.
>
>
>
> Thanks
> SenthilKumar SK
>
Hi ,
We required help for camel components deployed in AWS cloud.
Please share any cloud formation template is available.
Thanks
SenthilKumar SK
11 matches
Mail list logo
