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/04/23 09:59:17 UTC

[jira] [Created] (CAMEL-6306) provide a way to introspect a component, find the various parameters available and their types so that tooling can provide forms to let users create & customise endpoints

james strachan created CAMEL-6306:
-------------------------------------

             Summary: provide a way to introspect a component, find the various parameters available and their types so that tooling can provide forms to let users create & customise endpoints
                 Key: CAMEL-6306
                 URL: https://issues.apache.org/jira/browse/CAMEL-6306
             Project: Camel
          Issue Type: New Feature
            Reporter: james strachan
            Assignee: james strachan


>From the current EndpointConfiguration you need a URI or Endpoint to be able to get the configuration object; and there's no way to introspect it to find its properties.

Tools like IDEs or web consoles typically need to start from a blank slate, create a form and let users enter the various properties required to configure and create a new endpoint.

So this issue adds a new ComponentConfiguration API; which is like EndpointConfiguration but can be created on any existing Camel component without any code changes and lets users configure the configuration; then either create a URI string or create an Endpoint directly - or introspect the available properties.

There are 2 implementations; a basic implementation which works with any camel component today and a more advanced implementation which makes use of the @UriEndpoint / @UriParam / @UriParams annotations from CAMEL-6304 to provide better metadata.

The aim is to work with all camel components/endpoints from day 1 but to provide a way for endpoint developers to provide better metadata by using some annotations

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