[
https://issues.apache.org/jira/browse/CAMEL-21426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18014607#comment-18014607
]
Radovan Netuka edited comment on CAMEL-21426 at 8/19/25 1:21 PM:
-----------------------------------------------------------------
[~davsclaus] I've noticed there are a lot of examples in
[https://github.com/apache/camel-kamelets-examples]. There were some
discussions before on aggregating examples together. Do you support this idea?
Currently, there are lot of similar examples, each for just one kind of
feature. My idea is to aggregate examples that have something in common
together.
There could be 3 examples showing basic route features (one in each DSL - i.e.
Java, XML and Yaml). For each component, there could be one example (only if
the topic is not too complex, otherwise there'd be several to keep things
simple).
Each example could be tagged to keep track what it explains. Like #xml, #beans,
#jms would say this example shows routes in XML, featuring beans and JMS
component. We could use these tags in the docs somehow to make it easier for
users to navigate to a topic they are interested in.
Just thinking out loud. Would love to hear your opinion.
was (Author: rnetuka):
[~davsclaus] I've noticed there are a lot of examples in
[https://github.com/apache/camel-kamelets-examples]. There were some
discussions before on aggregating examples together. Do you support this idea?
Currently, there are lot of similar examples, each for just one kind of
feature. My idea is to aggregate several examples that have something in common
together and tag them somehow.
For example *app-routes-beans* could be merged with any component example
because it just shows (very valuable) feature on how to define a bean in XML
DSL, but nothing more. Also, there are several possibilities on how to do
something. Routes could be defined in Java DSL, XML DSL, Yaml etc. With this
approach, we would be able to cover almost every DSL feature by distributing
them to component examples. We could add tags, like #xml_routes, #beans, #jms
to each example for further search on what each examples contains.
Just thinking out loud. Would love to hear your opinion.
> camel-jbang-examples
> --------------------
>
> Key: CAMEL-21426
> URL: https://issues.apache.org/jira/browse/CAMEL-21426
> Project: Camel
> Issue Type: New Feature
> Components: camel-jbang, examples
> Reporter: Claus Ibsen
> Assignee: Radovan Netuka
> Priority: Major
> Fix For: 4.x
>
>
> We have a lot of mixed stuff at
> [https://github.com/apache/camel-kamelets-examples]
> We should create a new camel-jbang-examples folder with a smaller set of
> examples that are better documented and aimed for users new to Camel or
> quickly want to try and see Camel in action.
> We should generate a table of content (like we do for the other examples
> repo) that has a summary and category so users can better find what they are
> looking for.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
