Skip to content

Conversation

rastislavpapp
Copy link
Collaborator

@rastislavpapp rastislavpapp commented Aug 31, 2025

like so:

image

pointing to org.apache.camel.component.file.GenericFileEndpoint#setAppendChars

I'm not quite sure how to determine which class the query parameter is actually located in, and whether I can determine this programmatically, so I went with the most primitive approach - take the component class name (e.g. DirectComponent), replace Component with Endpoint, or Configuration, and try to find appropriate setter there. If there's a better way, or if there's more possible places to look in, I'll gladly change the logic.

…tters in camel classes (*Endpoint, *Configuration)
@rastislavpapp rastislavpapp force-pushed the endpoint_parameter_refs branch from 53597fc to dbcbc2f Compare August 31, 2025 21:06
@davsclaus
Copy link
Collaborator

what is the purpose of this ? The tooling should not directly use any configurer classes. The information about which options a camel component / endpoint supports is already defined in json files from camel-catalog, or from 3rd party components inside their JARs as json files.

@rastislavpapp
Copy link
Collaborator Author

It's so that you can click on a parameter name in an endpoin uri and it'll take you to the actual setter in the appropriate class, like in the example above.
As a user I find myself looking for this kind of information all the time, to look in the javadoc, or actually see where the parameter is used and for what.

@davsclaus
Copy link
Collaborator

Ah okay, yeah that makes it quicker to dive into the camel source code

@rastislavpapp rastislavpapp merged commit 07a7824 into camel-tooling:main Sep 1, 2025
3 checks passed
@rastislavpapp rastislavpapp deleted the endpoint_parameter_refs branch September 1, 2025 14:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants