With the implementation of the external binding declaration based on
XPath, I thought "that is cool, I can do my multiple name conflict
customizations (like rename Class to ClassName) in one single step".
However it appears an XPath expression may only resolve to one node:
<bindings node="//xsd:attribute[@name='class']">
<property name="className"/>
</bindings>
Is there a reasons for this, for it would be nice to apply a
transformation on multiple nodes at once. I can see you can have some
precedence problems, but nothing that can't be solved I guess.
--
Mark Brouwer