[
https://issues.apache.org/jira/browse/AXISCPP-1002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12628780#action_12628780
]
nadir amra commented on AXISCPP-1002:
-------------------------------------
The current implementation for xsd:any element is to map it to the following
c++ structure:
The current implement for xsd:any element is to map it to following c++ class:
class STORAGE_CLASS_INFO AnyType
{
public:
AnyType();
~AnyType();
/**
* _array Contains an array of xml encoded strings.
*/
XML_String* _array;
/**
* _size Contains how many xml strings are there in _array
*/
int _size;
};
I have no clue why this was done. We always return one string when
deserializing, as what I expect. Can anyone clarify this for me?
To support the type xsd:anyType, i am leaning torwards defining the following:
typedef AxisChar * xsd__anyType;
This seems reasonable to me - returning the root element and its subnodes as a
string during deserialization and expecting a valid xml string when serializing
(basically using the string as-is).
Any problems with this?
> Support for xsd:anyType
> -----------------------
>
> Key: AXISCPP-1002
> URL: https://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, vimsdk.zip
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
