Re: Adding http(s) compatibility to a component (for discoverable service compatibility)

2024-01-03 Thread Claus Ibsen
Hi Steve Yeah sure we love contributions. When you are done with the work on the dynamic router component then let us know, and we can help find relevant work you may want to help with. That said anyone is welcome to help, and you can find JIRA tickets with outstanding tasks. And also ask on the

Re: Adding http(s) compatibility to a component (for discoverable service compatibility)

2024-01-01 Thread Steve973
Thank you for your insight, Claus! While I am trying to add things that will be as useful as possible to people, I do not always know what would be best for the community. Instead of discovery, I will add some component-specific JMX monitoring and control through the @Managed* annotations. This

Re: Adding http(s) compatibility to a component (for discoverable service compatibility)

2023-12-30 Thread Claus Ibsen
Hi There is this ticket https://issues.apache.org/jira/browse/CAMEL-18546 Its about being able to have a list of hosted services by the current Camel application, that can be exposed for tooling and end users. This is not intended as a distributed service registrt ala Consul or whatever. But a

Re: Adding http(s) compatibility to a component (for discoverable service compatibility)

2023-12-30 Thread Claus Ibsen
Hi A discoverable service? Do you mean some kind of external service registry ala Consul, Kubernetes ? Camel is not everyhing, and if you need a service registry then favour to use those kind of products that does that. Then you can make your component enlist itself into their service registries.