Hello.  In my component, I have a control channel component that services a
few types of administrative messages that configure the component in
certain ways.  I would like to experiment with making the control component
endpoint a discoverable service, so I would like to try to clarify some
things before I start.

First, I assume that I will need to create another component-endpoint pair
that uses HTTP.  That seems really obvious, but I wanted to make sure that
I am not missing something.  It certainly would not be the first time that
has happened!

Next, is the Undertow component the best example for me to learn how I
should approach it?  I should only need basic http/https functionality to
accept the request information.  If possible, I would like to be able to
reuse the logic that my non-http control channel already implements.  If
there is another component that provides an http endpoint as (mostly) an
additional access point, I would be interested in seeing that.  The
undertow component is pretty substantial, and I do not know if it would be
worth that additional complexity and code to integrate with component
discovery.

Lastly, what else should I be aware of?  The "Service Registry" page in the
Camel online manual does not seem to be directed toward
developers, other than the idea of implementing DiscoverableService.  If I
end up doing all of this with my component, would it be helpful to add a
more detailed section to the manual to help others get started with
implementation?

Thanks,
Steve

Reply via email to