axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "nadir amra (JIRA)" <axis-c-...@ws.apache.org>
Subject [jira] Issue Comment Edited: (AXISCPP-1002) Support for xsd:anyType
Date Thu, 04 Sep 2008 18:19:44 GMT

    [ https://issues.apache.org/jira/browse/AXISCPP-1002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12628419#action_12628419
] 

nadiramra edited comment on AXISCPP-1002 at 9/4/08 11:18 AM:
--------------------------------------------------------------

Just adding a little bit of information regarding differences between any and xsd:anyType:
=====================
xsd:anyType is a type, like xsd:integer (though xsd:anyType is special in that it can act
as a simple or complex type, and it places essentially no restrictions on the tree that it
validates. 
A sample use would be:

        <xsd:element name="e" type="xsd:anyType"/>

This would mean that elements named <e> can have any content, any 
attributes, etc.

xs:any is a wildcard, usable as a term in a content model.  For example:

        <xsd:complexType name="T">
        <xsd:sequence>
                <xsd:element ref="A"/>
            <xsd:any />
                <xsd:element ref="C"/>
        </xsd:sequence>
        </xsd:complexType>
 
Elements of type T must have content <A/><???/><C/>, where <???> can
be any named element. 
==============================
A good article to read: http://www.ibm.com/developerworks/xml/library/ws-tip-xsdcaution.html
==============================
My thinking is to implement anyType using the support we have for any.

      was (Author: nadiramra):
    Just adding a little bit of information regarding differences between any and xsd:anyType:
=====================
xsd:anyType is a type, like xsd:integer (though xsd:anyType is special in that it can act
as a simple or complex type, and it places essentially no restrictions on the tree that it
validates. 
A sample use would be:

        <xsd:element name="e" type="xsd:anyType"/>

This would mean that elements named <e> can have any content, any 
attributes, etc.

xs:any is a wildcard, usable as a term in a content model.  For example:

        <xsd:complexType name="T">
        <xsd:sequence>
                <xsd:element ref="A"/>
            <xsd:any />
                <xsd:element ref="C"/>
        </xsd:sequence>
        </xsd:complexType>
 
Elements of type T must have content <A/><???/><C/>, where <???> can
be any named element. 
==============================
My thinking is to implement anyType using the support we have for any.
  
> 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: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org


Mime
View raw message