As I see, the "issue" is actually in the xml document itself. The right way of doing it would be to change the xml. The other one is working, but it seems a bit of a quirk. Thanks
–
LukaNov 15 '11 at 15:52

@_Luka: @lwburk is completely right -- it is OK (not a problem) for XML documents or fragments to be in a default namespace.
–
Dimitre NovatchevDec 1 '11 at 23:49

@DimitreNovatchev: I agree that it is ok for the xml documents to be in a default namespace. However, as you've explained the 'MakeRequestResponse' element in my example is neither in a default no-namespace (because it has an xmlns attribute which defines an custom namespace) neither it is in a accessible namespace (because it does not have an prefix associated with the xmlns attribute). From what I've seen on this site, some other xml libraries treat cases like mine as a no-namespace elements, since the definition (xmlns) without a prefix is not correct. Correct me if I'm wrong.
–
LukaDec 2 '11 at 9:20