Polymorphic return values

[6kjfsyg02]

I am trying to return one of two different objects from the same
method, but I can not do it in WSDL or C#.

I have a web service with three methods.

I have been told that one of the methods must return either <Respuesta
....> or <ConfirmacionPe ticion ...> directly under the SOAP Body. Other
methods are already capable of returning just <Respuesta ...> or just
<ConfirmacionPe ticion ...>. What is new is one method being capable of
returning both types.

I have been modifying over one of the previous methods:

[WebMethodAttrib ute( Description = "Blah...")]
[SoapDocumentMet hod( ourMethodNamesp ace, Use = SoapBindingUse. Literal,
ParameterStyle = SoapParameterSt yle.Bare)]
[return: XmlElement( Respuesta.Marca , Namespace =
Respuesta.Espac ioNombres)]
public Respuesta solicitaRespues taAsincrona( ...)

The obvious thing is to substitute the return type by object:

[WebMethodAttrib ute( Description = "Blah...")]
[SoapDocumentMet hod( ourMethodNamesp ace, Use = SoapBindingUse. Literal,
ParameterStyle = SoapParameterSt yle.Bare)]
public object solicitaRespues taAsincrona( ...)

But then the automatic WSDL becomes:

<wsdl:message name="solicitaR espuestaAsincro naSoapOut">
<wsdl:part name="solicitaR espuestaAsincro naResult"
element="tns:so licitaRespuesta AsincronaResult "/>
</wsdl:message>

That is, under <soap:Body> I get a <solicitaRespue staAsincronaRes ult>
element followed by the members of the actual object being returned.
This is not what I want, I want either <Respuesta> or
<ConfirmacionRe spuesta>.

I then tried to have several XML return attributes:

[WebMethodAttrib ute( Description = "Blah...")]
[SoapDocumentMet hod( ourMethodNamesp ace, Use = SoapBindingUse. Literal,
ParameterStyle = SoapParameterSt yle.Bare)
[return:
XmlElement( Respuesta.Marca ,
Namespace = Respuesta.Espac ioNombres),
XmlElement( ConfirmacionPet icion.Marca,
Namespace = ConfirmacionPet icion.EspacioNo mbres)]]
public object solicitaRespues taAsincrona( ...)

but then I get:

System.InvalidO perationExcepti on: You need to add
XmlChoiceIdenti fierAttribute to the 'solicitaRespue staAsincronaRes ult'
member.
I then tried the inverse route of hacking the WSDL. I created a new
type:

<wsdl:types>
....
<!-- Since this does not have a namespace, this breaks the Basic
Profile. -->
<s:schema elementFormDefa ult="qualified" >
<s:complexTyp e name="Respuesta OConfirmacion" >
<s:sequence>
<s:choice minOccurs="0" maxOccurs="1">
<s:element minOccurs="1" maxOccurs="1" name="Respuesta " />
<s:element minOccurs="1" maxOccurs="1"
name="Confirmac ionPeticion" />
</s:choice>
</s:sequence>
</s:complexType>
<!-- Without an explicit element:
// CODEGEN: The operation binding 'solicitaRespue staAsincrona'
from
namespace 'http://www.map.es/scsp/' was ignored.
Specifying a type for use=literal messages is not supported.
Type name='Respuesta OConfirmacion' from targetNamespace =''
cannot be used as top-level any element.-->
<s:element name="Respuesta OConfirmacion"
type="Respuesta OConfirmacion"/>
</s:schema>
</wsdl:types>

and

<wsdl:message name="solicitaR espuestaAsincro naSoapOut">
<wsdl:part name="solicitaR espuestaAsincro naResult"
element="Respue staOConfirmacio n"/>
</wsdl:message>

This type is stubbed as

public partial class RespuestaOConfi rmacion
{
[XmlElement("Con firmacionPetici on", typeof(Confirma cionPeticion))]
[XmlElement("Res puesta", typeof(Respuest a))]
[XmlChoiceIdenti fier("nombreEle mento")]
public object unaRespuestaOUn aConfirmacion;

[System.Xml.Seri alization.XmlIg noreAttribute()]
public RespuestaOConfi rmacionEleccion nombreElemento;
}

[System.Xml.Seri alization.XmlTy peAttribute(Inc ludeInSchema =
false)]
public enum
RespuestaOConfi rmacionEleccion
{
ConfirmacionPet icion,
Respuesta
}
I then tried with:

....
[return:
XmlChoiceIdenti fier(MemberName = "nombreElemento "),
XmlElement( Respuesta.Marca ,
Namespace = Respuesta.Espac ioNombres),
XmlElement( ConfirmacionPet icion.Marca,
Namespace = ConfirmacionPet icion.EspacioNo mbres)]
public RespuestaOConfi rmacion solicitaRespues taAsincrona( ...)

This causes:

System.InvalidO perationExcepti on: There was an error reflecting
'solicitaRespue staAsincronaRes ult'. --->
System.InvalidO perationExcepti on: Missing 'nombreElemento ' member
needed for serialization of choice 'solicitaRespue staAsincronaRes ult'.

in spite of me assigning a value to the nombreElemento field in the
return value.

If I have

[return:
XmlChoiceIdenti fier(MemberName = "nombreElemento "),
XmlElement( Respuesta.Marca ,
Namespace = Respuesta.Espac ioNombres),
XmlElement( ConfirmacionPet icion.Marca,
Namespace = ConfirmacionPet icion.EspacioNo mbres)]
[return: XmlElement("Res puestaOConfirma cion", Namespace = "")]

the return value is serialized as
<RespuestaOConf irmacion>
<Respuesta ...>
....
</RespuestaOConfi rmacion>

That is, the Respuesta or the ConfrimacionPet icion are wrapped with
<RespuestaOConf irmacion> which again is not what I want.
So summarizing, how do you express either in C# or in WSDL that you can
return any of two different elements under <soap:Body>?

Thanks in advance.
--
David Mediavilla

[Yunus Emre ALPÖZEN [MVP]]

My advice u to use a union for multiple return types...

--
HTH

Thanks,
Yunus Emre ALPÖZEN
BSc, MCSD.NET
Microsoft .NET & Security MVP

<6k*******@snea kemail.com> wrote in message
news:11******** **************@ g14g2000cwa.goo glegroups.com.. .

I am trying to return one of two different objects from the same
method, but I can not do it in WSDL or C#.

I have a web service with three methods.

I have been told that one of the methods must return either <Respuesta
...> or <ConfirmacionPe ticion ...> directly under the SOAP Body. Other
methods are already capable of returning just <Respuesta ...> or just
<ConfirmacionPe ticion ...>. What is new is one method being capable of
returning both types.

I have been modifying over one of the previous methods:

[WebMethodAttrib ute( Description = "Blah...")]
[SoapDocumentMet hod( ourMethodNamesp ace, Use = SoapBindingUse. Literal,
ParameterStyle = SoapParameterSt yle.Bare)]
[return: XmlElement( Respuesta.Marca , Namespace =
Respuesta.Espac ioNombres)]
public Respuesta solicitaRespues taAsincrona( ...)

The obvious thing is to substitute the return type by object:

[WebMethodAttrib ute( Description = "Blah...")]
[SoapDocumentMet hod( ourMethodNamesp ace, Use = SoapBindingUse. Literal,
ParameterStyle = SoapParameterSt yle.Bare)]
public object solicitaRespues taAsincrona( ...)

But then the automatic WSDL becomes:

<wsdl:message name="solicitaR espuestaAsincro naSoapOut">
<wsdl:part name="solicitaR espuestaAsincro naResult"
element="tns:so licitaRespuesta AsincronaResult "/>
</wsdl:message>

That is, under <soap:Body> I get a <solicitaRespue staAsincronaRes ult>
element followed by the members of the actual object being returned.
This is not what I want, I want either <Respuesta> or
<ConfirmacionRe spuesta>.

I then tried to have several XML return attributes:

[WebMethodAttrib ute( Description = "Blah...")]
[SoapDocumentMet hod( ourMethodNamesp ace, Use = SoapBindingUse. Literal,
ParameterStyle = SoapParameterSt yle.Bare)
[return:
XmlElement( Respuesta.Marca ,
Namespace = Respuesta.Espac ioNombres),
XmlElement( ConfirmacionPet icion.Marca,
Namespace = ConfirmacionPet icion.EspacioNo mbres)]]
public object solicitaRespues taAsincrona( ...)

but then I get:

System.InvalidO perationExcepti on: You need to add
XmlChoiceIdenti fierAttribute to the 'solicitaRespue staAsincronaRes ult'
member.
I then tried the inverse route of hacking the WSDL. I created a new
type:

<wsdl:types>
...
<!-- Since this does not have a namespace, this breaks the Basic
Profile. -->
<s:schema elementFormDefa ult="qualified" >
<s:complexTyp e name="Respuesta OConfirmacion" >
<s:sequence>
<s:choice minOccurs="0" maxOccurs="1">
<s:element minOccurs="1" maxOccurs="1" name="Respuesta " />
<s:element minOccurs="1" maxOccurs="1"
name="Confirmac ionPeticion" />
</s:choice>
</s:sequence>
</s:complexType>
<!-- Without an explicit element:
// CODEGEN: The operation binding 'solicitaRespue staAsincrona'
from
namespace 'http://www.map.es/scsp/' was ignored.
Specifying a type for use=literal messages is not supported.
Type name='Respuesta OConfirmacion' from targetNamespace =''
cannot be used as top-level any element.-->
<s:element name="Respuesta OConfirmacion"
type="Respuesta OConfirmacion"/>
</s:schema>
</wsdl:types>

and

<wsdl:message name="solicitaR espuestaAsincro naSoapOut">
<wsdl:part name="solicitaR espuestaAsincro naResult"
element="Respue staOConfirmacio n"/>
</wsdl:message>

This type is stubbed as

public partial class RespuestaOConfi rmacion
{
[XmlElement("Con firmacionPetici on", typeof(Confirma cionPeticion))]
[XmlElement("Res puesta", typeof(Respuest a))]
[XmlChoiceIdenti fier("nombreEle mento")]
public object unaRespuestaOUn aConfirmacion;

[System.Xml.Seri alization.XmlIg noreAttribute()]
public RespuestaOConfi rmacionEleccion nombreElemento;
}

[System.Xml.Seri alization.XmlTy peAttribute(Inc ludeInSchema =
false)]
public enum
RespuestaOConfi rmacionEleccion
{
ConfirmacionPet icion,
Respuesta
}
I then tried with:

...
[return:
XmlChoiceIdenti fier(MemberName = "nombreElemento "),
XmlElement( Respuesta.Marca ,
Namespace = Respuesta.Espac ioNombres),
XmlElement( ConfirmacionPet icion.Marca,
Namespace = ConfirmacionPet icion.EspacioNo mbres)]
public RespuestaOConfi rmacion solicitaRespues taAsincrona( ...)

This causes:

System.InvalidO perationExcepti on: There was an error reflecting
'solicitaRespue staAsincronaRes ult'. --->
System.InvalidO perationExcepti on: Missing 'nombreElemento ' member
needed for serialization of choice 'solicitaRespue staAsincronaRes ult'.

in spite of me assigning a value to the nombreElemento field in the
return value.

If I have

[return:
XmlChoiceIdenti fier(MemberName = "nombreElemento "),
XmlElement( Respuesta.Marca ,
Namespace = Respuesta.Espac ioNombres),
XmlElement( ConfirmacionPet icion.Marca,
Namespace = ConfirmacionPet icion.EspacioNo mbres)]
[return: XmlElement("Res puestaOConfirma cion", Namespace = "")]

the return value is serialized as
<RespuestaOConf irmacion>
<Respuesta ...>
...
</RespuestaOConfi rmacion>

That is, the Respuesta or the ConfrimacionPet icion are wrapped with
<RespuestaOConf irmacion> which again is not what I want.
So summarizing, how do you express either in C# or in WSDL that you can
return any of two different elements under <soap:Body>?

Thanks in advance.
--
David Mediavilla

[6kjfsyg02]

Yunus Emre ALPÖZEN [MVP] wrote:

My advice u to use a union for multiple return types...
I appreciate your answer. From my understanding and the message from
the WSDL editor in Visual Studio, union only works with simpleType.
Respuesta and ConfirmacionPet icion are complexType.

I am going to look into abstract types, but I understand that it
requires including an xsi:type in <Respuesta ...> and
<ConfirmacionPe ticion ...>
Yunus Emre ALPÖZEN

<6k*******@snea kemail.com> wrote in message
news:11******** **************@ g14g2000cwa.goo glegroups.com.. .

I am trying to return one of two different objects from the same
method, but I can not do it in WSDL or C#.

I have a web service with three methods.

I have been told that one of the methods must return either <Respuesta
...> or <ConfirmacionPe ticion ...> directly under the SOAP Body. Other
methods are already capable of returning just <Respuesta ...> or just
<ConfirmacionPe ticion ...>. What is new is one method being capable of
returning both types. So summarizing, how do you express either in C# or in WSDL that you can
return any of two different elements under <soap:Body>?

Thanks in advance.
--
David Mediavilla

--
David Mediavilla