axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Whitlock (JIRA)" <axis-c-...@ws.apache.org>
Subject [jira] Created: (AXISCPP-255) Bad XSDTYPE's
Date Wed, 10 Nov 2004 15:12:23 GMT
Bad XSDTYPE's
-------------

         Key: AXISCPP-255
         URL: http://nagoya.apache.org/jira/browse/AXISCPP-255
     Project: Axis-C++
        Type: Bug
  Components: Basic Architecture  
    Versions: 1.3 Final    
    Reporter: Mark Whitlock
    Priority: Minor


TypeMapping.hpp has in it...

typedef enum XSDTYPETag 
{ XSD_UNKNOWN=1, XSD_INT, XSD_FLOAT, XSD_STRING, XSD_LONG, XSD_SHORT, \
                XSD_BYTE, XSD_UNSIGNEDLONG, \
                XSD_BOOLEAN, XSD_UNSIGNEDINT, XSD_UNSIGNEDSHORT, \
                XSD_UNSIGNEDBYTE, \
                XSD_DOUBLE, XSD_DECIMAL, XSD_DURATION, \
                XSD_DATETIME, XSD_TIME, XSD_DATE, \
                XSD_YEARMONTH, XSD_YEAR, XSD_MONTHDAY, XSD_DAY, \
                XSD_MONTH, XSD_HEXBINARY, \
                XSD_BASE64BINARY, XSD_ANYURI, XSD_QNAME, XSD_NCNAME, XSD_NOTATION, \
                XSD_INTEGER, \
                XSD_ARRAY, USER_TYPE, ACCESSOR, XSD_NMTOKEN, XSD_ANY
} XSDTYPE;

Some of these XSD types look invalid. ACCESSOR is not mentioned anywhere in the code. Also
XSD_YEARMONTH and XSD_NCNAME probably will not work since there are switch statements in (for
instance) Param.cpp with cases for most of these xsd types - but there is no case for XSD_YEARMONTH,
ACCESSOR and XSD_NCNAME. So the code would drop into the default: return AXIS_FAIL. I'm not
sure whether XSD_YEARMONTH, ACCESSOR and XSD_NCNAME should be valid or not or whether there
are other xsd types in the list which are invalid or untested. I am particularly concerned
about this since TypeMapping.hpp is external.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


Mime
View raw message