[
https://issues.apache.org/jira/browse/CAMEL-2989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12984036#action_12984036
]
Claus Ibsen commented on CAMEL-2989:
------------------------------------
Ben the idea is much more complicated :)
James want the component to discover the _possibilities_. For example a file
component, should traverse the file system and report back.
The idea is to assist tooling so you can smart complete or the likes.
So if you have a file structure
/myapp/order
/myapp/order/foo
/myapp/order/bar
And the endpoint was {{file:/myapp/order}}
Then it would return back a list of
{code}
file:/myapp/order/foo
file:/myapp/order/bar
{code}
We may omit the existing endpoint prefix and return, if that makes more sense.
{code}
foo
bar
{code}
> 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.
