Well CXF is sending to back just fine. It does indeed, as you suggest, use 
xsi:type. What I am wondering is - is there any way to setup special binding 
rules or other configuration on the server side so that I, as a client, can use 
another way of communicating the type to the server. 

The use case that motivated the question is that some scripting language 
frameworks have a hard time sending xsi types. I am wondering if I can get 
around sending an xsi type by using some alternate method: for example by 
sending some wsdl "element" that happens to be named "type" and for which I 
have set up binding rules on the server-side. 

Does my question make sense?


 


 

-----Original Message-----
From: Benson Margulies <[EMAIL PROTECTED]>
To: [email protected]
Sent: Thu, 1 May 2008 8:38 pm
Subject: Re: Binding to extended wsdl types










What you want is xsi:type. I have no idea how to make JAXB send it, but the
Aegis data binding uses it consistently. Perhaps one of my fellow travellers
can tell how to do it with JAXB.

A quick google seems to suggest that @XmlTypeAdapter might be needed.



 

Reply via email to