Milan -
That is a great explanation. When you say "if you have any chance to
modify WSDL file of your web service, you should change it to accept
Base64 encoded signed XML file, instead of XML Document (in the soap
header)", how do we actuall do that ? Please clarify?
Thank you once again for y
Yes, tools like XML Spy often modify XML file, like pretty printing or
replacing every new line
character (ASCII 10) with a pair of new line and carriage return characters
(ASCII 10 and 13).
Such files are still valid XML files (well formed and conformed to its schema),
but signature is
not val
> You need to set preserveWhiteSpace(true) or
> something similar to your XML parser (Xerces, MSXML...)
> and force it not to do pretty printing.
Or, even better, change this line:
getElementsbyTagName.item(0).getFirstChild().getValue()
into:
getElementsbyTagName("MyElement").item(0).getElemen
We are not able to help you, unless you show us small peace of your code and
XML (XSLT). I suppose
that mentioned exception throws XML parser (Xerces)? In that case you might ask
this question in
Xerces mailing list. Btw, have you used setNamespaceAware(true) method?
Best regards,
Milan
--- m
It seems that your document was "changed/modified" a little bit (after
decryption). By modified, I
mean, that it was "pretty printed". This:
some text
was changed into:
some text
Code "getElementsbyTagName.item(0).getFirstChild().getValue()" returns first
node and in your case
it is (nod
