camel-connector component

[davsclaus]

We can create a camel-connector component that supports connector:name?options uris, so it works with the connections that are being created.

Then the route DSL uses those endpoints and they would be easier for citizen developers to understand if they view the source code.

The connector component then reads the json file from the connector to get the default values and what real Camel component to use, and then under the covers builds the actual uri to be used.

A 2nd though could be to let the maven plugin generate the connector as if it was a regular Camel component so the regular tooling would use it as-is. For example the name of the component could be just the connector name, eg the uris are name:path?options. And then it can swizzle/filter the json schema that the existing tooling uses.

This may limit the name to be using A..Z and no spaces etc, as its a regular Camel component name. And no clashes with existing names, eg like jms - file etc.

[davsclaus]

With #15 we now generate a Camel component based on the connector so Camel think its a new component it uses with its existing tooling support.

The implementation in the base class in camel-connector then needs to take the options from the citizen developer and merge together with the hardcoded default values the expert user has set when he/she created the connector.

Those default values are in the camel-connector.json file

And then build a Camel uri of the actual type of component which is the real deal.