I'm wondering if it could make sense to register enpoints in context's
registry having an option so set theirs id;
The aim is to have a common way to identify an endpoint other by uri, so that:
- @Produce(ref = "myEndpontId") would work the same way in any context
- People willing to integrate with camel using a producer template do
not need to know the whole uri, i.e. in vertx-camel-bridge mapping
between a vertx address and an endpoint could be done by id.
I could elaborate it a little bit more if you think it could make sense.