[ 
https://issues.apache.org/jira/browse/CAMEL-2989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12984046#action_12984046
 ] 

Christian Schneider commented on CAMEL-2989:
--------------------------------------------

I basically like the idea but we should perhaps do this outside of the 
component project. So perhaps there should be a tooling support project for the 
component that does such a thing.

The reason is that browsing features could make a component much more complex. 
Additionally you will sometimes have to use special APIs to do the browsing 
internally. For example jms is not able to provide the browsing but e.g. for 
tibco ems there is a special proprietary API for browsing the queues. So in 
this case it would make sense to have something like camel-browsing-tibco-ems 
project that delivers the implementation for this jms case.

Additionally to browsing we could also support monitoring and management. For 
example you could want to see how many messages are in a queue or you could 
want to remove a single message. As this is typically production stuff UIs for 
montioring and management will often run in the browser. So we could provide a 
URL to the management console for e.g. a queue.
Something like http://management.myorg.net/<queuename>. So the tooling could 
add this link to the endoint for easy access.

> 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.

Reply via email to