Although using the java bindings here is valid and works with java based scripting languages, I'd initially thought of binding to script variables as a more natural/universal way of implementing bindings for this component type. Perhaps we can do both using <binding> (bind to script variables) and <java-binding>/<interface-binding> (bind to java interface?

On a separate note perhaps we can extend the binding concept to allow bindings to use expressions (using new expression evaluator) and other components and not just endpoints. This relates somewhat to the composite component issue.

Sounds interesting. By all means write something up. I agree there should be different types of <binding> but my goal here was to match current capabilities, since this isn't a major feature point right now.

Agreed, good idea. Only concern was that we are using "<binding>" element for this java-specific case and therefore won't be able to use this element for more generic/universal script component bindings (to script variables instead of java interface maybe) in the future. A solution would leave what you added as is and just change the element name to "java-binding".

Should probably write up the idea to extend bindings in the composite component issue, or create a new issue for it, i'll do that at some point.

We should be as clear as possible naming them, and maybe only use the <binding> element if there is a clear default binding type for a given component type.