G
Garry Hall
Guest
Interesting. The underlying Xerces parser was upgraded in 11.1, this might explain the behaviour. I am not aware of anything in the client's XML handling that specifically addressed this.
Continue reading...
Continue reading...