Hi
I would also add that HTTP servers like Tomcat, Jetty, JBoss etc have an
access log that logs how long time each request takes. And they often have
a API / plugin you can use to have your custom code triggered by the HTTP
server
so you can do any kind of "how long time it takes" you need.
On
Hi
Camel will send back the response at the end of the route in the consumer,
so what you do in that route example will not work.
However if you want to do some kind of custom logging of how long it takes,
then Camel Jetty has send back the response to the client, when the
UnitOfWork is done.
So
I was able to get the repo to run the tests correctly past this
particular issue. All the changes I made to get it to work are in
this commit
https://github.com/lucidguppy/learning-quarkus-camel-testing/commit/3200e96ad46e9579ba4c085e2a8bba4c090f3d8e
What tipped me off was debugging and seeing
Hello,
I am learning how to properly test camel code using test containers
and I am finding difficulty with lateinit items in my test when trying
to inject items created in QuarkusTestResourceLifecycleManager that
are injected into the test. Ultimately - I would like to be able to
set up