tadayosi commented on PR #3901: URL: https://github.com/apache/camel-k/pull/3901#issuecomment-1354299231
> What about uri that for some other reason does not resolve to a component that we know. We also support jitpack dependencies and custom Maven repositories that might ship libraries with custom components that are not known to the Catalog. All these will raise the error here or am I missing something? I think it's a good question, and I raised the same at https://github.com/apache/camel-k/issues/3449#issuecomment-1226854358. In Camel, users can even change the scheme name for the existing components. https://camel.apache.org/manual/component.html#_programmatically At that time, I took that Camel K doesn't allow such use cases like extending with their own components or simply renaming the components. We assume every valid component should be present in the Camel Quarkus and Catalog. Can you think of any other cases where throwing an error at this state might cause issues? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@camel.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
