I
IVE
I submit entire xml of the digitally signed form in one SQL Server database
table column using web service. This xml has international chars inside
(Russian chars). Then I read this column using another web service, save to
file and launch this file. Infopath starts, shows me this form and says me
that digital signature is O.K. If I want to avoide saving to file and use
loadXML() and NewFromSolutionWithData() instead then InfoPath says me that
digital signature is failed. It seems that SQL Server or InfoPath keeps my
xml to 1251 code page and saving to file translates this xml to UNICODE. (If
I see DOM.xml in debug mode before submit there is no encoding attribute in
<?xml ...?>. And I find this attribute in saved form.) Is there any simple
method to translate xml to UNICODE before NewFromSolutionWithData() or
loadXML() (or before submit)?
Ivan Emelin
table column using web service. This xml has international chars inside
(Russian chars). Then I read this column using another web service, save to
file and launch this file. Infopath starts, shows me this form and says me
that digital signature is O.K. If I want to avoide saving to file and use
loadXML() and NewFromSolutionWithData() instead then InfoPath says me that
digital signature is failed. It seems that SQL Server or InfoPath keeps my
xml to 1251 code page and saving to file translates this xml to UNICODE. (If
I see DOM.xml in debug mode before submit there is no encoding attribute in
<?xml ...?>. And I find this attribute in saved form.) Is there any simple
method to translate xml to UNICODE before NewFromSolutionWithData() or
loadXML() (or before submit)?
Ivan Emelin