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 "Mark Whitlock (JIRA)" <ax...@ws.apache.org> on 2005/07/13 22:39:09 UTC
[jira] Created: (AXISCPP-743) SoapDeSerializer::getAttribute does not use namespace
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
[jira] Commented: (AXISCPP-743) SoapDeSerializer::getAttribute does not use namespace
Posted by "Mark Whitlock (JIRA)" <ax...@ws.apache.org>.
[ 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
[jira] Commented: (AXISCPP-743) SoapDeSerializer::getAttribute does not use namespace
Posted by "Dushshantha Chandradasa (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXISCPP-743?page=comments#action_12317307 ]
Dushshantha Chandradasa commented on AXISCPP-743:
-------------------------------------------------
It seems to me that SoapDeSerializer::getElement method is also not using the namespace although it recieves it as a parameter.
And at the stub level, we send NULL for parameter.
xsd__int v0 = *(pIWSDZ->getElementAsInt("in0",0));
Mark,
why do we need check for namespace here? Could you please explain the way we should use namespace here.
Dushshantha
> 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