[
https://issues.apache.org/jira/browse/CAMEL-2989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12984283#action_12984283
]
Ben O'Day commented on CAMEL-2989:
----------------------------------
Alright, thanks for the clarification. Sounds like this would require
component specific implementations, but perhaps an interface could be added to
the core to provide a framework for this. Overall, this starts to overlap with
enhancing the management/monitoring of runtime routes/endpoints/exchanges, etc.
I've used JMX for specific requirements for this in the past (AMQ queue mgmt,
route start/stop/stats, etc)...but a more general framework for this would be
nice. I'll think about this a bit...
> provider an API to query available endpoints on a component
> -----------------------------------------------------------
>
> Key: CAMEL-2989
> URL: https://issues.apache.org/jira/browse/CAMEL-2989
> Project: Camel
> Issue Type: New Feature
> Components: camel-core
> Affects Versions: 2.4.0
> Reporter: james strachan
> Fix For: 3.0.0
>
>
> many components like file, activemq, nmr, jbi, database all are capable of
> browsing the available endpoints that a user could use from, say, a command
> line tool or from camel-web.
> So we should add a browse API that lets you query a component for available
> endpoints.
> Maybe allow things to be browsed in a tree kind of way - maybe with a text
> search type thing (for completion boxes etc)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
