Hi Adrian,
I've attached the wsdl in question to the ticket in JIRA. WSDL2Ws still generates
code using CPP_DOC_PROVIDER.
Matt
> Adrian Dick commented on AXISCPP-1002:
> --------------------------------------
>
> Hi,
>
> I was under the impression that for rpc/encoded web services, the
> WSDL2Ws tooling will generate the appropriate code within the
> complex type serializers to produce the correct value for xsi:type.
> If this isn't being done (or at least not correctly), then we should
> be fixing the WSDL2Ws tooling, rather than extending the engine API
> to provide workarounds. Particularly, as doc/literal web services
> don't make use of xsi:type.
>
> Regards,
> Adrian
>
> > Support for xsi:type when serializing complex objects and arrays
> of complex objects.
>
> >
> --------------------------------------------------------------------------------------
> >
> > Key: AXISCPP-1002
> > URL: http://issues.apache.org/jira/browse/AXISCPP-1002
> > Project: Axis-C++
> > Issue Type: New Feature
> > Components: Serialization
> > Affects Versions: 1.6 Beta
> > Environment: Windows XP client (AXIS/C++ version 1.6b ),
> VMware ESX 3.0 server (Axis/Java version 1.2.1)
> > Reporter: Matt Love
> > Attachments: patch
> >
> >
> > Axis/C++ currently doesn't seem to allow me to send the typename
> of a complex object down to the serializer. This is causing
> problems when trying to serialize a 'derived' object, as the server
> cannot identifiy the correct derived type without xsi:type.
>
> --
> This message is automatically generated by JIRA.
> -
> If you think it was sent incorrectly contact one of the administrators:
> http://issues.apache.org/jira/secure/Administrators.jspa
> -
> For more information on JIRA, see: http://www.atlassian.com/software/jira
>
>
