.net - WCF service and interoperability -

i have following wcf service believe can improved. need able support windows , non-windows clients using soap1.1 , soap1.2.

my concerns input parameter initdata on api initdatarequest , return parameter of getdata. currently, have development policy parameters constrained xml-formatted strings , client , server responsible serializing/deserializing in respective environments.

[servicecontract] public interface iatomdatainterfacewcf {     [operationcontract]     guid opensession(atomsessiontype sessiontype);      [operationcontract]     void closesession(guid sessionid);      [operationcontract]     int initdatarequest(guid sessionid, string initdata);      [operationcontract]     string getdata(guid sessionid, int count); } 

using soapui soap request initdatarequest shows following element parameter 'initdata'.

<tem:initdata>?</tem:initdata> 

this bothered our ibm websphere developers expected else. suggested, without guidance, use xsd describe api hence providing more structure these parameters, have not been able head around how use it.

any ideas?

thanks in advance.

there nothing inherently non-interoperable service contract. not sure why think there room improvement unless contact not support business reason built address.

you can expose service on soap 1.1 , 1.2 defining endpoint each of basichttpbinding , wshttpbinding respectively.

i don't know mean this:

we have development policy parameters constrained xml-formatted strings

soap xml standard; non-xml content must formatted or end bad xml. not development policy technical constraint.

i don't understand problem soapui setting string value initdata question mark. concerned in way not valid string? realise soapui puts "?" there , can change whatever want right?

finally, if consumers of service saying need xsd host wsdl endpoint , can go endpoint , download xsd there.