[ 
https://issues.apache.org/jira/browse/AXIS2C-787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Lazarski resolved AXIS2C-787.
------------------------------------
    Fix Version/s: 2.0.0
                       (was: 1.7.0)
       Resolution: Fixed

    QName equality is defined by {namespace_uri}localpart only - prefixes
    are just namespace aliases. Including prefix in axutil_qname_to_string()
    caused hash lookups to fail when the same QName used different prefixes.
    
    Before: "localpart|namespace_uri|prefix"
    After:  "localpart|namespace_uri"
    
    This fixes axiom_element_get_attribute() failing for attributes with
    different prefixes but the same namespace URI.
    


> axutil_qname_to_string serialize with the prefix.
> -------------------------------------------------
>
>                 Key: AXIS2C-787
>                 URL: https://issues.apache.org/jira/browse/AXIS2C-787
>             Project: Axis2-C
>          Issue Type: Bug
>          Components: util
>    Affects Versions: 1.2.0
>         Environment: Linux Ubuntu, But this is a bug in every platform
>            Reporter: Dimuthu Gamage
>            Priority: Major
>             Fix For: 2.0.0
>
>
> Currently the axutil_qname_to_serialize function serialize the qname with the 
> prefix.
> "localpart|namespace_uri|prefix"
> This cause problems in comparing qnames, 
> I.e. although axutil_qname_equals has get rid of this using different 
> approaches (just not comparing prefixes), In other places like axiom this 
> serialized strings kept in the hashes. (e.g. attribute hash in the element). 
> This leads axiom_element_get_attribute not to work on occasions where the 
> prefix of the given qname is different. This is a problem for 
> interoperability. 
> I think these bugs can be fixed if we remove the prefix in the serialized 
> string generated from axutil_qname_to_string



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to