Soap RPC call inside soapUi

[Guest]

Hi there

I’m new here, and of course what made me register was a problem…
Already searched somethings, nothing that i found helped, so i’m posting this thread…
So, using soapUi 1.7 to call a BC service, with a record reference input and output…

The input is something like

[html]
<Abc_in>
0
1
2
3
4
5
</Abc_in>
[/html]
the output I expected was something like:

[html]<Abc_out>
<Abc_out>
0
2


171
171
171
171
171
171
171
171


171
171
171
171
171
171
171
171
171
171
171
171
171
171
171




</Abc_out>
</Abc_out>
[/html]
but i’m getting this:

[html]<Abc_out xsi:type=“webM:Abc_out” id=“id1”>
<Abc_out xsi:type=“Abc_out” id=“id2”>
1
3



171
171
171
171
171
171
171
171



171
171
171
171
171
171
171
171
171
171
171
171
171
171
171






</Abc_out>
</Abc_out>[/html]
the question is: how the hell do i get rid of the attributes

xsi:type="...." id="..." 

and the

"xsi:type="SOAP-ENC:Array" SOAP-ENC:arrayType="webM:sellArrayItem[...]" id="..." "

and

<item xsi:type="webM:VendaArrayItem" id="...">

tags?

sorry if the post it not ok in style and stuff…

Thanks everyone…

Christian

[wMusers.Com1 (wMusers.Com)]

Try setting watt.server.SOAP.userMultiReference to “false” in the IS extended settings.

See Appendix C in teh SOAP Developer’s Guide 7.1.1 PDF.

watt.server.SOAP.useMultiReference

Specifies how the message coder is to encode parameters that point to the same underlying data object in the pipeline. Set to true or false. Default is true. For example, if two output parameters cDate and oDate point to the same underlying data in the pipeline, the message coder encodes the parameters like this if watt.server.SOAP.useMultiReference is true:

<cDate id="id1">03/15/2000</cDate> 
<amt id="id2">300</amt>
<oDate href="#id1"></oDate>
<acct id=id4>cash</acct>

Note: The oDate parameter is encoded as a reference

And like this if watt.server.SOAP.useMultiReference is false:

<cDate>03/15/2000</cDate> 
<amt>300</amt>
<oDate>03/15/2000</oDate>
<acct>cash</acct>

Note: The oDate parameter is encoded as an independent element

Note: This parameter affects only the way in which multi‐referenced parameters are encoded. It does not affect the way in which they are decoded. The message coder always recognizes and decodes multi‐referenced elements regardless of how

[Guest]

Hi mcarlson, thanks for your reply.

this attribute shoud be set inside the BC startup right?
I tried that but did not work…

I was reading the guide you mencioned and there is said that “And encodes them like this if watt.server.SOAP.useMultiReference=false [FONT=TimesNewRoman][SIZE=3]or is not set at
all”

but anyway you gave me a new thing to look for.

any other ideia would be appreciated!

thanks again!

Christian

[/size][/font]

[Guest]

[SIZE=2]Hey mcarlson!
that actually worked, i was putting the property in the wrong place!
but that only removed the id attribute, but the xsi:type attribute and the array stuff atil already there…

anyone knows where can i find the list of properties that can be set?

thaks!

Christian!
[/size]