From: Harbhanu <har...@hu...> - 2007-05-16 03:28:08
|
selectXPath(ap,L"/ns1:Envelope/ns1:Header/*[@ns1:mustUnderstand]") Evaluation of this(in evalXpath) .returns an empty set..r u also getting an empty set..?? _____ From: Jimmy Zhang [mailto:cra...@co...] Sent: Wednesday, May 16, 2007 11:14 AM To: Harbhanu Cc: vtd...@li... Subject: Re: soap.c and soap2.xml Well, yes, you have to call setDoc with the actuall content length... when "r", VC replaces /r/n with /n so the file appears shorter... What expression? Is it declareXPathNameSpace(ap,L"ns1",Lhttp://www.w3.org/2003/05/soap-envelope);? I tried it and it worked for me... ----- Original Message ----- From: Harbhanu <mailto:har...@hu...> To: 'Jimmy Zhang' <mailto:cra...@co...> Cc: vtd...@li... Sent: Tuesday, May 15, 2007 7:22 PM Subject: RE: soap.c and soap2.xml Yes.. now the exception is not there..after using any of the suggested solutions . ("rb' for binary mode) What was the problem??? Was it regarding the legth mismatch between the actual length a the length passed.. Now, the evaluation is not correct.it works for the root selection..but when I execute the original expression . the result is empty... Any clues?? Thanks for the prompt replies..expecting the similar level of activity n promptness in this mailing list!! Regards, Harbhanu _____ From: Jimmy Zhang [mailto:cra...@co...] Sent: Tuesday, May 15, 2007 3:58 PM To: Harbhanu Cc: vtd...@li... Subject: Re: soap.c and soap2.xml I think you should use __int64, to fix the parse exception there are two ways, one is to fopen() the XML doc using the "ro" instead of "r," this is to treat the XML as binary data... the other way is to assign i (an int) the return value of fread(), so instead of "fread(...)," do "i=fread(...)." Either one should fix the problem... ----- Original Message ----- From: Harbhanu <mailto:har...@hu...> To: 'Jimmy Zhang' <mailto:cra...@co...> Cc: vtd...@li... Sent: Monday, May 14, 2007 11:13 PM Subject: RE: soap.c and soap2.xml Hi, Currently I am using Vtd-XML version 2.0. I want to use it on windows..VC-6. Even i think the problem must be pertaining to change of Long...but don't know the exact source. When I use Long typedef as long... Line Number: 14 Offset: 6 parse exception e ==> Parse exception in parse() Ending tag error: Start/ending tag mismatch When I use Long typedef as __int64.. Line Number: 47 Offset: 1 parse exception e ==> Parse exception in parse() Other Error: XML not terminated properly Did u do any change for long long in your code ??.. In my case it will result in compilation errors.... Please try after doing this change in your code.are you also getting similar problem or there is some configuration related issue. Regards, Harbhanu _____ From: Jimmy Zhang [mailto:cra...@co...] Sent: Tuesday, May 15, 2007 12:13 PM To: har...@hu... Cc: vtd...@li... Subject: soap.c and soap2.xml I tried the same code today and could not duplicate this issue. I am using VC 2003... but that should not matter... What version of VTD-XML are you using? Changing Long to long will not work because a long is 32 bit, a Long is 64-bit... can you make file on Linux? ======================================== Hi, I am trying to use the C version of VTD-XML. I tried executing the test program given (the SOAP example)... <http://vtd-xml.sourceforge.net/codeSample/cs4.html> http://vtd-xml.sourceforge.net/codeSample/cs4.html [using soap.c soap2.xml] But i am getting this error.... Line Number: 14 Offset: 6 parse exception e ==> Parse exception in parse() Ending tag error: Start/ending tag mismatch I am using VC 6 on Win2k... When i tried compilig the project... i got this error error C2632: 'long' followed by 'long' is illegal So.. i modified the typedef for Long to have only long... Apart from this i didn't any other change .... Any clue about the problem.... How should i solve the compilation error And if the change is correct... then what else can be the problem... In case someone has a working example ... please share it... Thanks !! Regards |