Pass polymorphic type as argument in SoapUI when using ServiceKnownType in WCF Service

Question

I have a WCF Service; this service has an operation that receives an argument of type Request. This is only the base type, and when calling the operation we actually send a value of type Request_V1 (which inherts from Request), that has the complete implementation of the request I want to send.

When trying to test the service using soapUI, I'm able to create the complex type of type Request_V1 (adding the proper namespace) but for some reason, the service is receiving the value as if it were of Request type.

Reading about ServiceKnowType, I found out here that I need to specify somehow explicitly in the client this inheritance relationship, but I haven't found any info regarding how to do it on soapUI

Has anybody experienced and solved the same issue?

Thanks

did you ever figure this out? If yes, can you please explain the possible solution. I am having a similar issue — Punit Vora, Nov 01 '13 at 22:32

score 2 · Answer 1 · answered Apr 15 '16 at 19:16

2

You also have to specify the type in the SOAP message. For example

<Request i:type="d:RequestV1">

...

where i is defined as XML-Instance namespace

answered Apr 15 '16 at 19:16

josagyemang

503
5
9

zendu · Answer 2 · 2016-07-12T20:46:07.070

1

On service side, you need to typecast to specific derived type.

operation (Request request){
    if(!(request is Request_V1)){
        throw Excetion("Unknown type!");
    }

    var request_v1 = Request as Request_V1;

    // use request_v1
}

On SOAP UI side, specify type as below:

<soapenv:Body xmlns:i="http://www.w3.org/2001/XMLSchema-instance">
  <ns1:OperationName>
     <ns1:request i:type="ns2:Request_V1">

Make sure you have defined ns1 and ns2 before referring to them.

edited Jul 12 '16 at 20:46

answered Sep 30 '14 at 15:54

zendu

1,108
1
14
36

That is already set, the problem is (was) how to make the proper envelope in SoapUI – pollirrata Sep 30 '14 at 18:45

score 0 · Answer 3 · edited May 23 '17 at 12:19

0

You don't specify the inheritance in the client, rather in the service. SOAPUI shouldn't have a problem with that. Check you have the correct declarations on your data contracts. This might help - Deserialize Abstract Class.

edited May 23 '17 at 12:19

Community

1
1

answered Mar 26 '13 at 22:52

stephenl

3,119
4
22
22

All the needed `KnownType` attributes have been already added to the DataContract, but for some reason is not working :( – pollirrata Mar 26 '13 at 23:03

Pass polymorphic type as argument in SoapUI when using ServiceKnownType in WCF Service

3 Answers3