Camel Properties

[ghost]

It would be good if there was intellisense for properties, would also be good if I tried to use a property that doesn't exist it would highlight the error. Would also be good if I used a property in a 'to' that I could ctrl+click it and I would be taken to the route that implements the 'from'

[AlanFoster]

Hey @matthewwilson,

Thanks for the feedback. Currently property placeholder references are only provided within blueprint beans.

There are currently two raised issues which have similar requirements to your request

• Add support for property-placeholders in {{propertyName}} notation #2 Add support for property-placeholders in {{propertyName}} notation
• Add support for uri/component language #16 Add support for uri/component language

Fulfiing the criteria for these issues and closing them is challenging due to the property interpolation within the URI language. This makes lexing/parsing a lot more involved than the other places you can use a property-placeholder value, for instance inside blueprint beans.

In the best case scenario the language is easy to lex/parse

<to uri="direct:start" />

If the user ctrl+clicks direct they can be taken to the org.apache.camel.component.direct.DirectComponent class, and if they ctrl+click start they can be taken to the target camel route.

However when property-interpolation is involved, it becomes a lot harder. Firstly there is the issue of deciding what reference contributions should be used. For instance consider the following XML

<to uri="direct:{{prop<caret>}}" />

When providing references to the current caret position, what should the plugin resolve to? The property placeholder itself, or the route it may point to? We can infer the user probably wants to have a configuration for a route name, but the user may actually want a reference to the property-placeholder itself. In this example it is still easy to allow reference contribution for the direct component.

Another more complex scenario may be the following;

<cm:property-placeholder name="component" value="direct" />
<cm:property-placeholder name="name" value="start" />
<cm:property-placeholder name="endpoint" value="${component}:${name}" />
...
<to uri="{{endpoint<caret>}}" />

What should the plugin provide a reference to now? From the parsing of the URI attribute it is simply a placeholder reference, which is easy to parse. However if we traverse the properties we can see that the end result may be a camel URI definition. But how do we now handle this?

Potentially a gutter icon could be added to access all of the different possible references of the final resolved interpolated string, but I imagine this wouldn't be a great user experience or intuitive - as no other plugin currently does this.

If there's a good way to deal with these scenarios this is definitely something i'd like to add :)