This is an automated email from the ASF dual-hosted git repository.
davsclaus pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel-website.git
The following commit(s) were added to refs/heads/master by this push:
new 5cc0ffd Remove trailing whitespace
5cc0ffd is described below
commit 5cc0ffd95aee055048cfcf989b65c40d17baf395
Author: Claus Ibsen <claus.ib...@gmail.com>
AuthorDate: Thu Jun 18 16:51:41 2020 +0200
Remove trailing whitespace
---
content/blog/2020/06/camel34-whatsnew/index.md | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/content/blog/2020/06/camel34-whatsnew/index.md
b/content/blog/2020/06/camel34-whatsnew/index.md
index 01392e8..7d6f867 100644
--- a/content/blog/2020/06/camel34-whatsnew/index.md
+++ b/content/blog/2020/06/camel34-whatsnew/index.md
@@ -16,9 +16,9 @@ For more details about LTS vs non-LTS releases see this [blog
post](https://came
### So what's in this release?
-This release is mostly about robustness and bug fixes.
+This release is mostly about robustness and bug fixes.
-We have also continued the work to make Camel more modular and lighter.
+We have also continued the work to make Camel more modular and lighter.
This time we removed the dependency on JAXB in the Swagger and OpenAPI modules.
This helps Camel on GraalVM and native compilation as JAXB is a heavy piece of
stack,
allowing GraalVM to eliminate it more easily.
@@ -26,15 +26,15 @@ allowing GraalVM to eliminate it more easily.
We continued to remove usage of reflection in Camel and found a few spots more
where
reflection was in use, when configuring nested options.
-We also added back support for configuring duration values using the shorthand
syntax,
+We also added back support for configuring duration values using the shorthand
syntax,
such as `timeout=30000` can be specified as `timeout=30s`. We had to remove
this in earlier
-versions of Camel 3 due to optimizations. But for Camel 3.4 we found a new
way.
+versions of Camel 3 due to optimizations. But for Camel 3.4 we found a new way.
#### Supervising route controller
The work on the supervising route controller is complete. When Camel starts up
the default route controller
is handling starting the routes safely. The default strategy is that if a
route fails to startup then Camel
-itself will also fail its startup (fail fast).
+itself will also fail its startup (fail fast).
The supervising route controller is a different strategy that allows to
startup routes independent from Camel itself.
This new controller will startup the routes using a background task that can
reschedule routes that
