Hi Okay so we have first set of pojo beans in the camel-catalog for almost all of the out-of-the-box: - aggregation strategy - aggregation repository - idempotent repository
Some of these beans would need a bit more tooling friendly configuration, and this is something we can work on the next couple of releases. We can also use this when we find other beans that you may want to use with Camel such as RoutePolicy beans. And then markup those as well for inclusion in the catalog. To do that you add @Metadata(label = "bean") on the class (search in code for existing and see how its done) On Thu, Mar 14, 2024 at 10:09 PM Claus Ibsen <claus.ib...@gmail.com> wrote: > Hi > > https://issues.apache.org/jira/browse/CAMEL-17641 > > For some camel EIPs and components you can use aggregation strategy, > idempotent repository and other kind of beans that Camel provides a API for. > > To configure and use these beans then you often would need to find a doc > snippet that has an example. And maybe also dive into the source code. > > So I started to mark up these beans that we have in all the components, > and then to include metadata about these in camel-catalog. > > This allows us to put these in the docs, and make better tooling that can > tap into the catalog to know what comes from ASF Camel. > > The PR is a first prototype with some beans marked up from core, and > camel-zipfile. > https://github.com/apache/camel/pull/13491 > > But there are potentially 30-50 more beans we need to find and markup, and > also make sure they are pojo configure friendly with getter/setters. > > > > -- > Claus Ibsen > ----------------- > @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2 > -- Claus Ibsen ----------------- @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
