Mailing-List: contact axis-c-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache AXIS C Developers List" <axis-c-dev@ws.apache.org>
Message-ID: <209529899.1122912636123.JavaMail.jira@ajax.apache.org>
Date: Mon, 1 Aug 2005 18:10:36 +0200 (CEST)
From: "Mark Whitlock (JIRA)" <axis-c-dev@ws.apache.org>
To: axis-c-dev@ws.apache.org
Subject: [jira] Commented: (AXISCPP-743) SoapDeSerializer::getAttribute does
 not use namespace
In-Reply-To: <1305085727.1121287149512.JavaMail.jira@ajax.apache.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

    [ http://issues.apache.org/jira/browse/AXISCPP-743?page=comments#action_12317347 ] 

Mark Whitlock commented on AXISCPP-743:
---------------------------------------

Hi Dushshantha,
I guess the way of recreating the problem is to write a test that has 2 elements with the same name but different namespaces, and two attributes with the same name but different namespaces. Then I imagine this code would fail since it would (incorrectly) be unable to distinguish between them. Discussing this with Adrian, this seems a valid test. Another related test would be to have an attribute and an element with the same name but different namespaces. I haven't reproduced this problem - I just noticed what seems like a bug and raised the JIRA to capture the problem.
Mark

> SoapDeSerializer::getAttribute does not use namespace
> -----------------------------------------------------
>
>          Key: AXISCPP-743
>          URL: http://issues.apache.org/jira/browse/AXISCPP-743
>      Project: Axis-C++
>         Type: Bug
>   Components: Client - Deserialization
>     Reporter: Mark Whitlock

>
> While looking through the code I noticed that SoapDeSerializer::getAttribute does not use the namespace that it passed. This looks like a bug to me. I imagine I could recreate the problem by deserializing two attributes which have the same name but different namespaces. If this is not a bug, then namespace should not be passed to SoapDeSerializer::getAttribute. I have not checked whether there are other methods with similar bugs.

-- 
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
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira