|
Home > Archive > BizTalk Server Orchestration > July 2005 > Attributes missing from output xml file
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 |
Attributes missing from output xml file
|
|
| Chris Kane 2005-07-26, 5:53 pm |
| I have a simple BizTalk 2004 orchestration that receives an InfoPath 2003
document via web services, transforms it to a new message, appends InfoPath
processing instructions to it, and then saves the new message to a file. The
source schema has elements that contain attributes. The transform was
created using BizTalk mapper and it attempts to map the source elements and
attributes to similarly named elements and attributes in the destination
schema. When I test the transform in Visual Studio, the output xml document
contains the elements and attributes as desired. When I submit an InfoPath
document to the orchestration, the output xml document contains the elements
but no attributes. Any ideas? Thanks!
| |
|
| Hi,
Could you supply the schemas, map and sample document instances?
Sincerely
Joerg Fischer
MVP
"Chris Kane" <ChrisKane@discussions.microsoft.com> schrieb im Newsbeitrag
news:4C69768A-0E70-4EC4-BB7C-2367550A2D80@microsoft.com...
>I have a simple BizTalk 2004 orchestration that receives an InfoPath 2003
> document via web services, transforms it to a new message, appends
> InfoPath
> processing instructions to it, and then saves the new message to a file.
> The
> source schema has elements that contain attributes. The transform was
> created using BizTalk mapper and it attempts to map the source elements
> and
> attributes to similarly named elements and attributes in the destination
> schema. When I test the transform in Visual Studio, the output xml
> document
> contains the elements and attributes as desired. When I submit an
> InfoPath
> document to the orchestration, the output xml document contains the
> elements
> but no attributes. Any ideas? Thanks!
| |
| Chris Kane 2005-07-29, 5:55 pm |
| Okay, I think I may be on to something...
I discovered that the source instance submitted by InfoPath is different
than the instance passed to BizTalk by the orchestration's web service. The
attributes in the InfoPath instance are qualified but the instance in BizTalk
shows that they are unqualified. I suspect the orchestration's web service
is doing this.
That being said, I would like confirmation on the following:
I believe the source schema representing the InfoPath document in my
orchestration (an example of this can be found in my last thread) is
expecting the instance to have qualified attributes. Would this explain why
they are not part of the message constructed from the Receive shape?
If this is the case, then what is the best way to make this scenario work?
Thanks!
Chris
"Joerg Fischer" wrote:
> Hi,
>
> Could you supply the schemas, map and sample document instances?
>
> Sincerely
>
> Joerg Fischer
> MVP
>
> "Chris Kane" <ChrisKane@discussions.microsoft.com> schrieb im Newsbeitrag
> news:4C69768A-0E70-4EC4-BB7C-2367550A2D80@microsoft.com...
>
>
>
| |
| Chris Kane 2005-07-29, 5:55 pm |
| I believe I understand the issue and have solved it!
Since my source schema uses all global declarations (I believe InfoPath uses
the "salami slice" schema design pattern) the instance document had to have
qualified elements and attributes. I figured out how to explicitly set these
options in the schema node using the elementFormDefault="qualified" and
attributeFormDefault="qualified" properties. Then, I rebuilt the solution,
re-deployed the assembly, and re-published the web services.
The key was the web service. Now that the schema was right, the
serialization properties required to make the class attributes qualified were
present. Now the web service passes in an instance with qualified attributes!
I am now getting the correct output.
Chris
"Chris Kane" wrote:
> I have a simple BizTalk 2004 orchestration that receives an InfoPath 2003
> document via web services, transforms it to a new message, appends InfoPath
> processing instructions to it, and then saves the new message to a file. The
> source schema has elements that contain attributes. The transform was
> created using BizTalk mapper and it attempts to map the source elements and
> attributes to similarly named elements and attributes in the destination
> schema. When I test the transform in Visual Studio, the output xml document
> contains the elements and attributes as desired. When I submit an InfoPath
> document to the orchestration, the output xml document contains the elements
> but no attributes. Any ideas? Thanks!
|
|
|
|
|