Comment #2 on issue 2556 by [email protected]: Simple library to create XML/XCAP Diff documents
http://code.google.com/p/mobicents/issues/detail?id=2556
Bartosz, second pass over api and dom impl committed, please review. Unit tests are included, and complete javadocs.
If it looks good to you please work on the document patch component builder op that compares 2 versions of the doc, what I have in my mind is to dive node by node into the tree recursively, and then on return each node passes null or patching instructions (if it is different) to parent. Now it may happen that such model could generate too many patching instructions, some for small changes, thus introducing maybe more patching instrcutions xml then actual xml updated, so what we could do to avoid that is, if parent gets more than one child node different, then instead of children patching instructions the parent would create another one and return back a single patching instruction for the whole parent, makes sense?
