+1

Il gio 4 lug 2019, 06:48 Claus Ibsen <claus.ib...@gmail.com> ha scritto:

> Hi
>
> I think we should close down on the last bits and get milestone 4
> released and in the hands to the community.
>
> We had a number of significant improvements and features such as:
>
> 1) Endpoint DSL
> Type safe fluent builder for configuring endpoints in Java
>
> 2) Camel Main
> Standalone Camel for microservices
> Needed for Camel K and Camel Quarkus as the way to bootstrap Camel
>
> 3) camel-core-engine
> Tiny set of dependencies (only include absolutely what you need)
> Needed by Camel K and Camel Quarkus to have smaller set of JARs on
> classpath
>
> 4) components depend on camel-support
> Further reduced the dependency directly on camel-core for all set of
> components. To ensure we use camel-api/camel-support for components
> only.
>
> 5) lazy start producer
> You can configure in the endpoint that the producer should lazy start
> (eg on 1st message) you can use this to allow Camel to startup even if
> the producer would fail on startup - but now that failure is deferred
> to 1st message which you can then use Camels route error handler to
> deal with etc
>
> 6) SPI for Reactive Engine
> So we can plugin a different engine such as Camel Quarkus can benefit
> from using its reactive engine.
>
> 7) DSL more extensive
> The reifiers and DSL model is more extensive/expandable. For example a
> new yaml dsl flow is developed at Camel K that required some of these
> changes.
>
> 8) Properties component / placeholder
> We can now easier extend this and also plugin to more 3rd parties such
> as Eclipse MicroProfile Config (which is also needed by Camel Quarkus)
>
> 9) Usual stuff
> Like bug fixes and whatnot.
>
>
> I am currently working on getting the property component and
> placeholder refactored so it works better and can easier to integrated
> with other configuration libraries. Also it would allow us to
> differentiate between read-only placeholders that can be loaded at
> once, and others that are on-demand (eg to lookup in a database,
> hashicorp vault etc.)
>
> Also the CI build server is now 100% passing for the last couple of days.
>
> So lets see if we can get the last bits done by end of tomorrow or end
> of next week, and get a RC cut.
>
> And we also need a M4 for both Camel K and Camel Quarkus to upgrade and
> use.
>
> Any thoughts?
>
>
>
>
>
>
>
>
>
>
>
> --
> Claus Ibsen
> -----------------
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>

Reply via email to