This depends on being resolved
I have refactored the way that the merge components are written so that it should be much easier for people to generate their own merge 'processors' for custom XML files that may not exist out of the box.
A merge strategy can be created, which is responsible for working out how to merge two XML nodes. There is an implementation of the two most common merges - Preserve and Overwrite.
Additionally there is NodeMergeStrategy - used for combining XML Documents together which can fetch values from the left and right documents via XPath; and a 'ChooseByName' merge strategy - this is so that, for example, the default behaviour may be to overwrite the values, but for specific nodes, you want to override this behaviour (for example, to merge applicationContext settings in resin-web.xml).