minOccurs from VB code - attribute?

[Lucvdv]

In a VB.Net webservice, after adding a data class, members of type String
get a "minOccurs=0" attribute in the generated WSDL.

Is there an attribute you can apply to the definition, or some other way to
turn this into "minOccurs=1"?
For example, in this class:

<WebService(Namespace:=...)> _
public class MyWebService
Inherits System.Web.Services.WebService

<WebMethod()> Public Sub TestFunc(byval t as TestData)
....
End Sub

public class TestData
Public Name as string
end class

end class

the "Name" member of TestData comes out in WSDL as

<s:element minOccurs="0" maxOccurs="1" name="Name" type="s:string" />
I'd like to get minOccurs="1" instead, so clients can understand that the
value isn't optional.

I've tried playing around with the IsNullable attribute through
SystemXml.Serialization.XmlElementAttribute and
System.Xml.Serialization.SoapElement, but it makes no difference.

[Josh Twist]

Hi

If you set the IsNullable to true on the XmlElement attribute (in c#):

[XmlElement(IsNullable=true)]
public string MyString

You will get the desired minOccurs=1 attribute. However, this doesn't
stop clients from
sending nulls strings like this:

<MyString xsi:nil="true">

So you'll also need to manually validate the input and throw an error,
but that's easy enough.

Josh
http://www.thejoyofcode.com/
Lucvdv wrote:

In a VB.Net webservice, after adding a data class, members of type String
get a "minOccurs=0" attribute in the generated WSDL.

Is there an attribute you can apply to the definition, or some other way to
turn this into "minOccurs=1"?
For example, in this class:

<WebService(Namespace:=...)> _
public class MyWebService
Inherits System.Web.Services.WebService

<WebMethod()> Public Sub TestFunc(byval t as TestData)
....
End Sub

public class TestData
Public Name as string
end class

end class

the "Name" member of TestData comes out in WSDL as

<s:element minOccurs="0" maxOccurs="1" name="Name" type="s:string" />
I'd like to get minOccurs="1" instead, so clients can understand that the
value isn't optional.

I've tried playing around with the IsNullable attribute through
SystemXml.Serialization.XmlElementAttribute and
System.Xml.Serialization.SoapElement, but it makes no difference.