I solved this issue in Java by handling tags that do not exist in the XML doc in a more robust manner. Not the cleanest solution; but it works now. The difference in escape processing didn't cause any problems...
- Character escaping issues in xalan-1 to xalan-2 migration kroberts
- kroberts
