xmlns issue when using SQLStreamProvider

Oct 5, 2012 at 6:10 PM

I'm using Scheduled Task Adapter 4.0 to get data from SQL Server (SQL 2008 R2) stored procedure.  Data is returned by stored proc like this:

<Item xmlns:ns1="http://myurl" id="001" desc="blah" />
<Item xmlns:ns1="http://myurl" id="002" desc="blahblah" />

Once that message is processed by the BizTalk receive location using scheduler it looks like this:
<Items xmlns="http://myurl">

   <Item xmlns:ns1="http://myurl" id="001" desc="blah" xmlns=""/>
   <Item xmlns:ns1="http://myurl" id="002" desc="blahblah" xmlns=""/>


The extra xmlns="" cause BizTalk mapper to consider the xml invalid

I'm sure it's the matter of specifying correct parameters either on SQLStreamProvider task or on XMLReceive pipeline of that receive location, but haven't been able to figure out what those are.
Any help much appreciated!

Nov 7, 2012 at 9:22 AM


I will try to see what is causing this behaviour and as soon as possible and I'll let you know.

Thanks for your comment.

Nov 12, 2013 at 4:20 AM

This issue seems to be haunting us as well. We have a custom pipeline which reads the incoming file and replaces xlmns="" with empty characters. But, we want to know if there is any alternative for this.

Please let us know if you have found any solution for it.

Thanks in advance.


Nov 12, 2013 at 4:48 PM
Yes, we seem to have found a resolution:
Let's say data returned by the stored procedure is represented by schema mySchema.xsd. We changed formdefault attribute on that schema to "unqualified", like so:

<xs:element maxOccurs="unbounded" form="unqualified" name="mySchema">