(email resent as plain text)
The current soap web service implementation uses
org.ofbiz.service.engine.SoapSerializer to serialize/deserialize
requests and responses.
This results in an awkward xml structure, e.g.
<map-Map>
<ns2:map-Entry>
<ns2:map-Key>
<ns2:std-String value="partyId"/>
</ns2:map-Key>
<ns2:map-Value>
<ns2:std-String value="1"/>
</ns2:map-Value>
</ns2:map-Entry>
...
There are many options for tidying up the xml, one example is:
<List>
<Map>
<Entry key-class="String" key="partyId"
value-class="String" value="1"/>
<Entry key-class="String" key="partyId"
value-class="String" value="2"/>
</Map>
</List>
Does anyone have any experience or views on how the xml should be structured?
Many thanks,
Chris
>
>
