by =?Utf-8?B?TmljayBIZXBwbGVzdG9u?= <NickHeppleston@[EMAIL PROTECTED]
Jan 18, 2008 at 09:05 AM
Liamo,
I've just checked with a test project and it would appear that this is
expected behaviour of a BizTalk map. When run in Visual Studio (using
'Test
Map', the Xml is output as expected - i.e. your former example), however
run
the same map in the runtime environment and it outputs the latter.
There doesn't appear to be any difference if you use an XmlTransmit or
PassThruTransmit pipeline.
The only suggestion I can therefore offer is to write a custom send
pipeline
component that strips these end tags on known 'problematic' elements.
Nick.
"Liamo" wrote:
> We're currently using a custom xslt file within a BizTalk 2006 (not R2)
map
> to transform a
> message. The xslt works fine, however the output from the map does not
> use self-closing xml tags
>
> e.g. an address element:
>
> <Address Type="somedata" Country="moredata" />
>
> is being outputted as
>
> <Address Type="somedata" Country="moredata></Address>
>
> Although the output is valid xml, our customer is insisting
> upon the former.
>
> The xslt has been tested in XmlSpy and using Xalan and in both cases the
> output is as wanted i.e. using self-closing tags.
>
> Is there a BizTalk or MSXML configuration setting that can be
> changed, or an XSLT setting?
>