> > What about > > <property name="string" (value="literal" | expression="xpath") > > [action=set|remove|cloneAsNode|detachAsNode] [scope=...]/> > > My feeling is that integrating this into the property mediator will > make it too overloaded. We would almost need to include a decision > table into the documentation in order to explain to the user which > combinations of attributes and attribute values are allowed :-) We > should also make sure that we have the option (later) to provide an > XML schema for our configuration language and this schema should > provide a decent level of validation which is not possible with this > degree of overloading. While I was reading the suggestion for the first time, I definitely shared the same concern - both from a user's as well as from a developer's perspective. Anyway I wanted to sleep a bit over it and wait for other reactions. Well, the sleep did not change anything and I'm still thinking this would become unnecessary complex.
> I would definitely prefer a distinct mediator (maybe <extract>?) > implementing clone and detach, as well as the remove operation > suggested below. +1 Regards, Eric
