- This topic has 3 replies, 1 voice, and was last updated 9 years, 2 months ago by
.
-
Posts
-
-
Hi,
I am having problems with the xml assembler in a custom pipeline.
I am attempting to wrap an xml message with a custom SOAP envelope with the xml assembler. The envelope schema has numerous xmlns declarations and prefix alias that are required to be in the output. I defined this schema as an envelope in the xml assembler and the output does in fact wrap the message in a SOAP header however the envelope only displays the xmlns definition for the envelope schema itself and not the other xmlns declarations explicitly defined in the envelope schema. In addition, all the namespace aliases come accross as ns0, ns1, ns2… in the output as opposed to the aliases defined in the envelope schema.
Does anyone know how to accomplish this? Is there some way to configure the xml assembler to output all of the xmlns declarations as well as utilize the namespace aliases defined in the xml schema for the envelope?
Any input would be greatly appreciated!
Thanks!
-
Firstly the namespace prefixs can be any value you like. When an Xml Parser loads the document it just uses the prefix to determine the namespace an element is in. It will use the prefix to find the namespace definition in the file
Can explain a bit more about the structure of you Soap Header, and what namespace definitions are missing. Could you possibly post a sample?
Also what adapter are you using?
-
HELP! Currently I was just utilizing a custom pipeline with an xml assembler to enclose the message in a SOAP envelope. (no orchestration or adapter) It looks like the SOAP header is my problem. My envelope schema references a header schema. The header schema is flat and does not have a root node which I do not know how to get around. This is the header schema:
<?xml version=”1.0″ encoding=”utf-16″ ?>– <xs:schema xmlns:tns=”http://schemas.xmlsoap.org/ws/2004/03/addressing“ xmlns:b=”http://schemas.microsoft.com/BizTalk/2003“ attributeFormDefault=”unqualified“ elementFormDefault=”qualified“ targetNamespace=”http://schemas.xmlsoap.org/ws/2004/03/addressing“ xmlns:xs=”http://www.w3.org/2001/XMLSchema“><schemaInfo is_envelope=”no“ is_receipt=”no“ schema_type=”document“ xmlns=”http://schemas.microsoft.com/BizTalk/2003“ /></xs:appinfo> </xs:annotation><xs:element name=”To“ type=”xs:string“ /><xs:element fixed=name=”Action“ type=”xs:string“ /></xs:schema>Which results in this? Do not understand why or know how to fix the To & Action nodes not having the ns1 prefix and their values?<?xml version=”1.0″ encoding=”utf-8″ ?><ns1:Address>AddressStr</ns1:Address></ns1:From><ns2:MessageNumber>1234567890</ns2:MessageNumber></ns2:Sequence></ns0:Header> -
-
-
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.