Re: Namespaces in Envelope + Payload -setup

Let me be a bit more exact on what the actual problem was after all. The 
first version could not find the element with the following Xpath reference:
/envelope:Envelope/envelope:PayloadEnvelope/Payload/MsgID

The application attempting to make the reference is using Xerces C++ 2.7.0 
and Xalan C++ 1.10.0

After declaring the default and payload: -namespaces on "top level", the 
element became visible to the system.

So basically I was expecting that one of the versions is not conforming to 
standards since it's not working with Xpath, although it validates nicely. 
Would not be the first time that Spy does something unexpected...

_________________________________________

Antti Sissonen [Antti_Sissonen@hotmail.com]

_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today it's FREE! 
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/