camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Claus Ibsen <>
Subject Re: Component Extensions
Date Fri, 04 Aug 2017 11:35:47 GMT
Hey Luca

Just took a bit of look, especially the first commit about the changes
involving camel-core.

I really like this, great work, its more cleaner and the code is
separated into that component.extension package.


Down the road we should have the some metadata on @Metadata or
something so we can harvest this via the camel apt compiler plugin and
generate in the json metadata file which extensions a component
provides, so tooling can be aware of this. We can then have a list of
known extensions such as the verifier, and metadata etc.

On Fri, Aug 4, 2017 at 11:50 AM, Luca Burgazzoli <> wrote:
> Hello,
> I've recently been working on CAMEL-11550 [1] aimed to introduce the
> concept of "Component Extensions" which are functionalities not directly
> targeting Camel runtime but that can provide some useful stuffs as
> example for tooling.
> You can find the implementation on my camel fork [2] which include:
> - Core API for ComponentExtensions
> - Refactor of the ComponentVerifier to be exposed as extension and
>   deprecation of the old VerifiableComponent
> - Creation of a MetaDataExtension for ServivceNow aimed to retrieve
>   a Json Schema definition for the ServiceNow objects
> - Creation of a maven plugin to generate POJOs for the ServiceNow
>   objects leveraging the MetaDataExtension
> As this new "Component Extension" concept has some minor impacts on
> camel-core I'd like to have your opinion before merging it.
> Regards,
> Luca
> [1]
> [2]
> ---
> Luca Burgazzoli

Claus Ibsen
----------------- @davsclaus
Camel in Action 2:

View raw message