search

kvin024 / ksoap2-android

Automatically exported from code.google.com/p/ksoap2-android
0 stars 0 forks source link

Namespace not added in SoapPrimitive Object #158

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Please refer to Issue 112:   Adding attributes to a simple property; and it 
related fix 
(https://github.com/mosabua/ksoap2-android/commit/f0e23aed58d2b8d0aabc4ae2436a2d
c8c4e036bc)
2. According to the testIssue112() function the expected response is correct 
but the SoapPrimitive object being used also has a namespace attached to it. 
That namespace is not reflected in the response
3.

What is the expected output? What do you see instead?
Expected Output:
 <n0:CostOfRepairs xmlns:n0="MyNameSpace">
   <n0:Power Unit="kW">1500</n0:Power>
 </n0:CostOfRepairs>

Actual Output:
 <n0:CostOfRepairs xmlns:n0="MyNameSpace">
   <Power Unit="kW">1500</Power>
 </n0:CostOfRepairs>

What version of the product are you using? On what operating system?
ksoap2-android-assembly-3.0.0-jar-with-dependencies.jar
Android 

Please provide any additional information below.

Original issue reported on code.google.com by shirazni...@gmail.com on 4 Apr 2013 at 12:21

GoogleCodeExporter commented 9 years ago 
Afaik the nested element uses the same namespace automatically and is therefore 
omitted..

Original comment by mosa...@gmail.com on 7 Apr 2013 at 6:25

GoogleCodeExporter commented 9 years ago 
Hi,

Actually I'm connecting to Exchange Web Services using ksoap2 on Android. 
Unfortunately exchange services expect to include namespace tag in every nested 
element.

Do you have any idea how can I achieve this? Or will this be fixed anytime soon?

Regards,

Shiraz Nisar

Original comment by shirazni...@gmail.com on 9 Apr 2013 at 11:36

GoogleCodeExporter commented 9 years ago 
It will be fixed when someone that needs the fix provides it..

Original comment by mosa...@gmail.com on 9 Apr 2013 at 6:39