You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "james strachan (JIRA)" <ji...@apache.org> on 2013/05/24 11:16:20 UTC

[jira] [Created] (CAMEL-6391) provide an endpoint path completion API so that we can complete endpoint paths (e.g. directory names, queue names, database table names) inside Karaf commands, IDEs or web consoles

james strachan created CAMEL-6391:
-------------------------------------

             Summary: provide an endpoint path completion API so that we can complete endpoint paths (e.g. directory names, queue names, database table names) inside Karaf commands, IDEs or web consoles
                 Key: CAMEL-6391
                 URL: https://issues.apache.org/jira/browse/CAMEL-6391
             Project: Camel
          Issue Type: New Feature
            Reporter: james strachan
            Assignee: james strachan


We've got the ComponentConfiguration API which is pretty cool for figuring out what parameters are available on an endpoint; but there's no help for completing the main name/path text of an endpoint. Most endpoints have a main 'path' string once you take away things like user/host/port or whatever parameters there are. 

e.g. name of queue / name of database table / directory/path for file/ftp/scp, name of hadoop file or whatever.

Rather like the Completer APIs in Karaf commands, it'd be nice if we had a little API so Component implementors can implement a simple method in EndpointCompleter to expose completions for UIs/tools/shell.s 

Think of it as like bash completion but for endpoint names/paths.

e.g. imagine a command where you want to create or send to an endpoint; picking the component name, you then need to be able to pick which queue/directory/table to use.

This patch adds a simple API to the ComponentConfiguration API and to the MBean

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira