Home Page › Forums › BizTalk 2004 – BizTalk 2010 › publishing a schema as web service
- This topic has 0 replies, 1 voice, and was last updated 9 years, 1 month ago by
community-content.
-
AuthorPosts
-
-
January 10, 2008 at 12:04 PM #18762
I’m having a problem when publishing a schema as web service. The web service published by BizTalk is expecting just a single data (the root element) without other elements of the schema. So, what should be done to publish a web service showing all elements of the schema.
the schema is like this,
<?xml version=”1.0″ encoding=”utf-16″ ?>
– <xschema xmlns:ns0=”http://AA.BBB.BizTalk.PPBW.PropertySchema.PropertySchema” xmlns:b=”http://schemas.microsoft.com/BizTalk/2003” xmlns=”http://PPURLGet” attributeFormDefault=”unqualified” elementFormDefault=”qualified” targetNamespace=”http://PPURLGet” version=”1.0″ xmlns:xs=”http://www.w3.org/2001/XMLSchema“>
– <xs:annotation>
– <xs:appinfo>
<msbtssqlqlScript value=”exec [usp_Get_PP_URLs]” xmlns:msbtssql=”http://schemas.microsoft.com/BizTalk/2003” />
– <imports xmlns=”http://schemas.microsoft.com/BizTalk/2003“>
<namespace prefix=”ns0″ uri=”http://AA.BBB.BizTalk.PPBW.PropertySchema.PropertySchema” location=”.\propertyschema.xsd” />
</imports>
</xs:appinfo>
</xs:annotation>
– <xs:element name=”PPURLRequest”>
– <xs:annotation>
– <xs:appinfo>
– <properties xmlns=”http://schemas.microsoft.com/BizTalk/2003“>
<property name=”ns0:Id” xpath=”/*[local-name()=’PPURLRequest’ and namespace-uri()=’http://PPURLGet’%5D/*%5Blocal-name()=’tbl_PP_Trigger’ and namespace-uri()=’http://PPURLGet’%5D/*%5Blocal-name()=’Id’ and namespace-uri()=’http://PPURLGet’%5D” />
<property name=”ns0:MessageType” xpath=”/*[local-name()=’PPURLRequest’ and namespace-uri()=’http://PPURLGet’%5D/*%5Blocal-name()=’tbl_PP_Trigger’ and namespace-uri()=’http://PPURLGet’%5D/*%5Blocal-name()=’MessageType’ and namespace-uri()=’http://PPURLGet’%5D” />
</properties>
</xs:appinfo>
</xs:annotation>
– <xs:complexType>
– <xsequence>
<xs:element xmlns:q1=”http://PPURLGet” minOccurs=”0″ maxOccurs=”1″ name=”tbl_PP_Trigger” type=”q1:tbl_PP_TriggerType” />
</xsequence>
</xs:complexType>
</xs:element>
– <xs:complexType name=”tbl_PP_TriggerType”>
– <xs:choice minOccurs=”0″ maxOccurs=”1″>
<xs:element xmlns:q2=”http://PPURLGet” name=”Id” type=”q2:IdType” />
<xs:element xmlns:q3=”http://PPURLGet” name=”PlantDataSource” type=”q3lantDataSourceType” />
<xs:element xmlns:q4=”http://PPURLGet” name=”PP_Adapter_URL” type=”q4P_Adapter_URLType” />
<xs:element xmlns:q5=”http://PPURLGet” name=”DestinationSystem” type=”q5estinationSystemType” />
<xs:element xmlns:q6=”http://PPURLGet” name=”MessageType” type=”q6:MessageTypeType” />
<xs:element xmlns:q7=”http://PPURLGet” name=”ItemIDSeparator” type=”q7:ItemIDSeparatorType” />
<xs:element xmlns:q8=”http://PPURLGet” name=”FromDateTime” type=”q8:FromDateTimeType” />
<xs:element xmlns:q9=”http://PPURLGet” name=”ToDateTime” type=”q9:ToDateTimeType” />
<xs:element xmlns:q10=”http://PPURLGet” name=”AggrResampleUOMID” type=”q10:AggrResampleUOMIDType” />
<xs:element xmlns:q11=”http://PPURLGet” name=”AggrResampleInterval” type=”q11:AggrResampleIntervalType” />
<xs:element xmlns:q12=”http://PPURLGet” name=”AggrAggregate” type=”q12:AggrAggregateType” />
<xs:element xmlns:q13=”http://PPURLGet” name=”RawNumValues” type=”q13:RawNumValuesType” />
<xs:element xmlns:q14=”http://PPURLGet” name=”RawBounds” type=”q14:RawBoundsType” />
<xs:element xmlns:q15=”http://PPURLGet” name=”Sent” type=”q15entType” />
<xs:element xmlns:q16=”http://PPURLGet” name=”SentDate” type=”q16entDateType” />
</xs:choice>
</xs:complexType>
– <xs:complexType name=”IdType”>
– <xsimpleContent>
<xs:extension base=”xs:int” />
</xsimpleContent>
</xs:complexType>
– <xs:complexType name=”PlantDataSourceType”>
– <xsimpleContent>
<xs:extension base=”xstring” />
</xsimpleContent>
</xs:complexType>
– <xs:complexType name=”PP_Adapter_URLType”>
– <xsimpleContent>
<xs:extension base=”xstring” />
</xsimpleContent>
</xs:complexType>
– <xs:complexType name=”DestinationSystemType”>
– <xsimpleContent>
<xs:extension base=”xstring” />
</xsimpleContent>
</xs:complexType>
– <xs:complexType name=”MessageTypeType”>
– <xsimpleContent>
<xs:extension base=”xstring” />
</xsimpleContent>
</xs:complexType>
– <xs:complexType name=”ItemIDSeparatorType”>
– <xsimpleContent>
<xs:extension base=”xstring” />
</xsimpleContent>
</xs:complexType>
– <xs:complexType name=”FromDateTimeType”>
– <xsimpleContent>
<xs:extension base=”xstring” />
</xsimpleContent>
</xs:complexType>
– <xs:complexType name=”ToDateTimeType”>
– <xsimpleContent>
<xs:extension base=”xstring” />
</xsimpleContent>
</xs:complexType>
– <xs:complexType name=”AggrResampleUOMIDType”>
– <xsimpleContent>
<xs:extension base=”xstring” />
</xsimpleContent>
</xs:complexType>
– <xs:complexType name=”AggrResampleIntervalType”>
– <xsimpleContent>
<xs:extension base=”xstring” />
</xsimpleContent>
</xs:complexType>
– <xs:complexType name=”AggrAggregateType”>
– <xsimpleContent>
<xs:extension base=”xstring” />
</xsimpleContent>
</xs:complexType>
– <xs:complexType name=”RawNumValuesType”>
– <xsimpleContent>
<xs:extension base=”xstring” />
</xsimpleContent>
</xs:complexType>
– <xs:complexType name=”RawBoundsType”>
– <xsimpleContent>
<xs:extension base=”xstring” />
</xsimpleContent>
</xs:complexType>
– <xs:complexType name=”SentType”>
– <xsimpleContent>
<xs:extension base=”xstring” />
</xsimpleContent>
</xs:complexType>
– <xs:complexType name=”SentDateType”>
– <xsimpleContent>
<xs:extension base=”xstring” />
</xsimpleContent>
</xs:complexType>
</xschema>thank you,
Teddy
-
-
AuthorPosts
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.