webMethods B2B and DOM parser

Hi there,

I wanted to know is that whether or not webMethods has overrode any of DOM API or its implementation? As I see all those API in client.jar. Specifically, if I use xerces.jar standalone, that is, using it outside webMethods B2B, I noticed that an element will only have one TEXT_NODE as child, say you have an element e1 with value 123@quot456, the value will be stored in a child TEXT_NODE. However, if I run my application within webMethods B2B, I found that the value is split into three parts, 123, ", 456, and are stored in three child TEXT_NODE. This suggested to me that webMethods has done something specifically on the implementation of DOM API.

Thanks much.