Got it, yeah clearly it was I who didn't understand your response. Does CXF have any configuration (other than annotations) to add custom jaxb binding via xmlTypeAdapter? My project auto-generates our valueObjects, along with their jax-ws annotations, which means I would need to add the @XmlTypeAdapter every time we regenerated our value objects.
-----Original Message----- From: Benson Margulies <[EMAIL PROTECTED]> To: [email protected] Sent: Thu, 1 May 2008 8:46 pm Subject: Re: Binding to extended wsdl types Yes, I follow the question, and I suspect that an answer might be hiding in @XmlTypeAdapter. On Thu, May 1, 2008 at 8:44 PM, <[EMAIL PROTECTED]> wrote: > > 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. > > > > > >
