From Schema to class to WSDL, element attributes lost in translati

[joewhitehair]

Using a schema, I created classes for my web service using the XSD.exe tool.
With the classes I then wrote a web service function, but the WSDL that is
generated has different minOccurs and maxOccurs values for my elements. I
can seem to figure out why this has changed or how to correct it. I can't
find any way to manually modify the classes for minOccurs or maxOccurs
either. It can happen whether I explicitly set the minOccurs/maxOccurs values
in the original schema or leave them as defaults. Any insight? Code samples
below. Thanks.

schema ---> xsd.exe ---> New class(es) ---> WSDL
'// ***** Original schema sample *****
<xsd:complexTyp e name="MessageHe aderType">
<xsd:sequence >
<xsd:element name="MessageID " type="BLS-DB:MessageIDTyp e"/>
<xsd:element name="Acknowled gement" type="BLS-DB:Acknowledgem entType"
minOccurs="0"/>
</xsd:sequence>
</xsd:complexType >
<xsd:complexTyp e name="MessageID Type">
<xsd:sequence >
<xsd:element name="ID" type="xsd:norma lizedString"/>
<xsd:element name="Timestamp " type="xsd:dateT ime"/>
<xsd:element name="MessageTy pe" type="BLS-DB:MessageNameT ype"/>
<xsd:element name="Sender" type="BLS-DB:ParticipantT ype"/>
</xsd:sequence>
</xsd:complexType >
'//***** Generated Class Sample *****
'<remarks/>
<System.Xml.Ser ialization.XmlT ypeAttribute([Namespace]:="M-TEST")> _
Public Class MessageHeaderTy pe

'<remarks/>
Public MessageID As MessageIDType

'<remarks/>
Public Acknowledgement As Acknowledgement Type
End Class

'<remarks/>
<System.Xml.Ser ialization.XmlT ypeAttribute([Namespace]:="M-TEST")> _
Public Class MessageIDType

'<remarks/>

<System.Xml.Ser ialization.XmlE lementAttribute (DataType:="nor malizedString") > _
Public ID As String

'<remarks/>
Public Timestamp As Date

'<remarks/>
Public MessageType As MessageNameType

'<remarks/>
Public Sender As ParticipantType
End Class
'//***** Generated WSDL Sample *****
<s:complexTyp e name="MessageHe aderType">
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="MessageID "
type="s1:Messag eIDType" />
<s:element minOccurs="0" maxOccurs="1" name="Acknowled gement"
type="s1:Acknow ledgementType" />
</s:sequence>
</s:complexType>
<s:complexTyp e name="MessageID Type">
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="ID"
type="s:normali zedString" />
<s:element minOccurs="1" maxOccurs="1" name="Timestamp "
type="s:dateTim e" />
<s:element minOccurs="1" maxOccurs="1" name="MessageTy pe"
type="s1:Messag eNameType" />
<s:element minOccurs="1" maxOccurs="1" name="Sender"
type="s1:Partic ipantType" />
</s:sequence>
</s:complexType>

[Robert Rae]

Did you have any success finding a solution to this problem? I am trying to
solve the same issue. Thanks.

"joewhiteha ir" wrote:

Using a schema, I created classes for my web service using the XSD.exe tool.
With the classes I then wrote a web service function, but the WSDL that is
generated has different minOccurs and maxOccurs values for my elements. I
can seem to figure out why this has changed or how to correct it. I can't
find any way to manually modify the classes for minOccurs or maxOccurs
either. It can happen whether I explicitly set the minOccurs/maxOccurs values
in the original schema or leave them as defaults. Any insight? Code samples
below. Thanks.

schema ---> xsd.exe ---> New class(es) ---> WSDL
'// ***** Original schema sample *****
<xsd:complexTyp e name="MessageHe aderType">
<xsd:sequence >
<xsd:element name="MessageID " type="BLS-DB:MessageIDTyp e"/>
<xsd:element name="Acknowled gement" type="BLS-DB:Acknowledgem entType"
minOccurs="0"/>
</xsd:sequence>
</xsd:complexType >
<xsd:complexTyp e name="MessageID Type">
<xsd:sequence >
<xsd:element name="ID" type="xsd:norma lizedString"/>
<xsd:element name="Timestamp " type="xsd:dateT ime"/>
<xsd:element name="MessageTy pe" type="BLS-DB:MessageNameT ype"/>
<xsd:element name="Sender" type="BLS-DB:ParticipantT ype"/>
</xsd:sequence>
</xsd:complexType >
'//***** Generated Class Sample *****
'<remarks/>
<System.Xml.Ser ialization.XmlT ypeAttribute([Namespace]:="M-TEST")> _
Public Class MessageHeaderTy pe

'<remarks/>
Public MessageID As MessageIDType

'<remarks/>
Public Acknowledgement As Acknowledgement Type
End Class

'<remarks/>
<System.Xml.Ser ialization.XmlT ypeAttribute([Namespace]:="M-TEST")> _
Public Class MessageIDType

'<remarks/>

<System.Xml.Ser ialization.XmlE lementAttribute (DataType:="nor malizedString") > _
Public ID As String

'<remarks/>
Public Timestamp As Date

'<remarks/>
Public MessageType As MessageNameType

'<remarks/>
Public Sender As ParticipantType
End Class
'//***** Generated WSDL Sample *****
<s:complexTyp e name="MessageHe aderType">
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="MessageID "
type="s1:Messag eIDType" />
<s:element minOccurs="0" maxOccurs="1" name="Acknowled gement"
type="s1:Acknow ledgementType" />
</s:sequence>
</s:complexType>
<s:complexTyp e name="MessageID Type">
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="ID"
type="s:normali zedString" />
<s:element minOccurs="1" maxOccurs="1" name="Timestamp "
type="s:dateTim e" />
<s:element minOccurs="1" maxOccurs="1" name="MessageTy pe"
type="s1:Messag eNameType" />
<s:element minOccurs="1" maxOccurs="1" name="Sender"
type="s1:Partic ipantType" />
</s:sequence>
</s:complexType>

[joewhitehair]

The only solution I found was to modified by hand.
"Robert Rae" wrote:

Did you have any success finding a solution to this problem? I am trying to
solve the same issue. Thanks.

[Dino Chiesa [Microsoft]]

maxOccurs="1" I believe is the default.
So any introduction of that into your generated WSDL does not constitute a
change in meaning.

If you want maxOccurs= (more than 1) then you are talking about an array.

for minOccurs="0", if it is a value type, then you need to include a
property with a name like XxxxSpecified, as per the doc at:
http://msdn.microsoft.com/library/en...ClassTopic.asp

The change of minOccurs="0" in your schema, to minOccurs="1" in the
generated WSDL, comes about because of the "impedance mismatch" between the
..NET type system and the W3C XML Schema type system.
More on that, here:
http://www.25hoursaday.com/weblog/de...ate=2005-02-10
-Dino

"joewhiteha ir" <jo**********@d iscussions.micr osoft.com> wrote in message
news:7A******** *************** ***********@mic rosoft.com...

The only solution I found was to modified by hand.
"Robert Rae" wrote:

Did you have any success finding a solution to this problem? I am trying
to
solve the same issue. Thanks.

>

[Robert Rae]

Dino,

Do you have any suggestions with regard to my post on 3/8 "setting minoccurs
and maxoccurs with attributes"? I am trying to set the maxoccurs value of an
element to a specifc value.

Any help would be greatly appreciated.

"Dino Chiesa [Microsoft]" wrote:

maxOccurs="1" I believe is the default.
So any introduction of that into your generated WSDL does not constitute a
change in meaning.

If you want maxOccurs= (more than 1) then you are talking about an array.

for minOccurs="0", if it is a value type, then you need to include a
property with a name like XxxxSpecified, as per the doc at:
http://msdn.microsoft.com/library/en...ClassTopic.asp

The change of minOccurs="0" in your schema, to minOccurs="1" in the
generated WSDL, comes about because of the "impedance mismatch" between the
..NET type system and the W3C XML Schema type system.
More on that, here:
http://www.25hoursaday.com/weblog/de...ate=2005-02-10
-Dino

"joewhiteha ir" <jo**********@d iscussions.micr osoft.com> wrote in message
news:7A******** *************** ***********@mic rosoft.com...

The only solution I found was to modified by hand.
"Robert Rae" wrote:

Did you have any success finding a solution to this problem? I am trying
to
solve the same issue. Thanks.
>