You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@axis.apache.org by "Samisa Abeysinghe (JIRA)" <ax...@ws.apache.org> on 2005/02/02 04:17:38 UTC

[jira] Updated: (AXISCPP-347) XML specification for naming elements and attributes are not followed by IHeaderBlock and IAttribute APIs

     [ http://issues.apache.org/jira/browse/AXISCPP-347?page=history ]

Samisa Abeysinghe updated AXISCPP-347:
--------------------------------------

    Component: SOAP

> XML specification for naming elements and attributes are not followed by IHeaderBlock and IAttribute APIs
> ---------------------------------------------------------------------------------------------------------
>
>          Key: AXISCPP-347
>          URL: http://issues.apache.org/jira/browse/AXISCPP-347
>      Project: Axis-C++
>         Type: Bug
>   Components: SOAP
>     Reporter: James Jose

>
> Hai
>   I am James working in IBM - I am in a group which is working to provide full FV test coverage for the public APIs in the Axis C++ client engine.
> XML specification for naming elements and attributes are not followed by IHeaderBlock and IAttribute APIs
> -------------------------------------------------------------
> The APIs are not checking for invalid element,attribute and namespace names. ie it allows to generate SOAP message with 
> invalid element name,attribute name,namespace prefix. 
> According to XML specification the allowed characters in an 
> xml name are -
>     Letters,Number character,underscore,colon,hyphen and period
>     Name may not start with the strings xml,XML,Xml, or any other
>     string that would match any variation of these three characters
>     (eg xMl,XMl...)
> Also the characters like '<', '&' cannot appear 
> in xml values(element,attribute,namespace URI).
> For Eg.
>  createImmediateChild(ELEMENT_NODE,"name<","xml","http://axis.com",NULL) will generate an element in the SOAP message. Also the resultant SOAP message will be non-compliant to WSI basic profile.
> Also other APIs like
> createNamespaceDecl()
> createChild()
> createImmediateChild()
> createAttribute()
> setUri()
> setPrefix()  are  not following the XML standards in naming.

-- 
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
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira