|
Home > Archive > BizTalk Server Applications Integration > May 2005 > Generated schema and RowType response
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Generated schema and RowType response
|
|
|
| In the SDK for BTS 2004, the SQL Adapter sample has a generated XSD called
AgentResponse.xsd that returns a row from "SP_Get_Agent_and_Interest". No
matter what I do, I cannot replicate the structure of the response message.
I keep coming up with Success/anytype as my return value. Can anyone explain
EXACTLY how this rowType response was generated? Alternatively, does it
require manipulation of the generated XSD in a text editor or the like after
generation?
Thanks.
--
John
| |
| WenJun Zhang[msft] 2005-05-09, 7:47 am |
| Hi John,
This should be a common mistake. Before generating the SQL service
schema in VS.net, you should add xmldata clause at the end of your
stored procedure, and remove it after the auto generation. Please
Refer to the following sample:
Using the SQL Adapter with a Stored Procedure in an Orchestration
http://msdn.microsoft.com/library/d...ary/en-us/opera
tions/htm/ebiz_prog_adapt_tbdk.asp
Thanks.
Best regards,
WenJun Zhang
Microsoft Online Partner Support
This posting is provided "AS IS" with no warranties, and confers no
rights.
| |
|
| Thanks WenJun. I actually tried this - and it did not work. I am using a
parameterized input sproc.
Further experimentation has led me to conclude that, with a parameterized
sproc, I actually don't need ANY FOR XML statement of any kind in the sproc.
I still am able to get the request/response XSD. The response is SUCCESS,
AnyType. What I am now doing is actually nesting the request part of the XSD
in the XSD of the sproc for the parent table as a child record, and just
discarding the response part. Seems to be working well, and emulates a
behavior of the 2002 version that I had sorely missed. In fact, it is easier
to set up than the 2002 version, as the XSDs can be autogenerated, and you
don't have to sit there in Mapper and configure a ton of name/value pair
attributes.
JT
""WenJun Zhang[msft]"" wrote:
> Hi John,
>
> This should be a common mistake. Before generating the SQL service
> schema in VS.net, you should add xmldata clause at the end of your
> stored procedure, and remove it after the auto generation. Please
> Refer to the following sample:
>
> Using the SQL Adapter with a Stored Procedure in an Orchestration
> http://msdn.microsoft.com/library/d...ary/en-us/opera
> tions/htm/ebiz_prog_adapt_tbdk.asp
>
> Thanks.
>
> Best regards,
>
> WenJun Zhang
> Microsoft Online Partner Support
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
>
|
|
|
|
|