Re: Question mark before <root> node?

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance


BizTalkVirtuoso wrote:

I'm trying to determine if the question mark is inserted in component
or in the orchestration. Also it may be a good idea to remove the map
and just trim the values
in the component.

Ben McFarlin
Microsoft BizTalk Server Consultant
www.biztalkvirtuoso.com

Well, I'm fairly certain that it's happening in the orchestration. If I
remove the map, the returned xml document has the xml declaration in
place of the question mark.
I originally was not using a map, and was trying to trim the values
with the Trim() function in my C# code. However, if the TI component
returned an empty string, the AppendChild in my C# code would append a
string of the length of the field to the Xml document.
The reason this is a problem is that the calling application is written
in Powerbuilder, and the response Xml string is imported into a
datawindow. For some reason, the import fails on strings of spaces in
field values, and shifts the data.
I have found a workaround by just stripping the question mark from the
returned xml string in my Powerbuilder code. I don't like that
solution, I'd still like to know what's going on with the question
mark.. and why writing the message to the Event log clears it up?
Anyway, thank you for all of your help with this!

.

Relevant Pages