XML schema for ESB allows <property> tag to have any XML content,
and it allows for elements using tags <property> as its children to declare
any set of properties.
That makes XML quite flexible, but the ESB editor based on that only cannot
assist customers in setting specific properties. We have only common form
for editing elements described as ANY in dtd/schema.
What is done for presentation of <route-to> and <object-path> is just a small
portion of what ESB editor may be customized into.

It seems that since actions, for instance, are based on Java classes,
the structure of a specific action is well defined by its Java class,
both property names and their types.
It means that each action Java class could contribute to XML schema and specific
forms in ESB editor.
Of course, it may not be reasonable to complicate actual ESB XML schema,
but editor may be based on an extended schema.

So, do you think that ESB editor should recognize some specific objects
(e.g. action based on org.jboss.soa.esb.actions.ContentBasedRouter)
and implement for them more sophisticated set of forms and
context commands than those based on generic schema?