gzurowski commented on a change in pull request #399: URL: https://github.com/apache/camel-website/pull/399#discussion_r441787181
########## File path: content/blog/2020/06/camel34-whatsnew/index.md ########## @@ -0,0 +1,95 @@ +--- +title: "Apache Camel 3.4 What's New" +date: 2020-06-19 +authors: [davsclaus] +categories: ["Releases"] +preview: Whats included in the Camel 3.4 LTS release. +--- + +Apache Camel 3.4 is the first LTS (Long Term Support) release of Camel 3. + +This release will be active supported with regular patch releases (important bug and security fixes) for 1-year. + +For more details about LTS vs non-LTS releases see this [blog post](https://camel.apache.org/blog/LTS-Release-Schedule/). + + +### So whats in this release? + +This release is mostly a more robust and bug fix release. + +We have also continued the work to make Camel more modular and lighter. +This time we removed the needed for 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. + +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, +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 wound a new way. + +#### Supervising route controller + +The work on the supervising route controller is complete. When Camel startup 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). + +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 re-scheduled routes that +have failed to startup to retry starting (with backoff). + +We have provided an example using `camel-main` or `camel-spring-boot` which you can find +[here](https://github.com/apache/camel-examples/tree/master/examples/camel-example-main-health) and +[here](https://github.com/apache/camel-spring-boot-examples/tree/master/camel-example-spring-boot-health-checks). + +You can find more details in the [Route Controller](https://camel.apache.org/manual/latest/route-controller.html) documentation. + +#### Health Check + +We have reworked Camel's health-check, to work similar across runtimes, whether its standalone, Spring Boot, +Camel-K, or Quarkus. + +We also introduced the concept of readiness and liveness so a health check can be either one or both. +Each health check can be configured, from `application.properties` the same way, and its all reflection free. + +The previous mentioned examples also comes with health-check so make sure to check those. Review comment: "The _previously_ mentioned..." ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
