Hi! Axis 1.x has a type mapping registry which I believe is also used by WSIF in which you can register serializer/deserializer pairs for Object to an XML Qualified name. So when you are preparing to make a call you just put Java Objects into an Array and do a Call.invoke() and Axis used the type map to figure out how to serialize/deserialize the object into XML for the SOAP message. Similarly, with WSIF you put a Java object into the Part list for an invoke, and the type registry is used to dynamically determine how to convert the Object into XML. Axis 2 does not take Java Objects in its new ServiceClient methods.
Paul Fremantle thought that the type mapping could be added to the adb dynamic binding portion of Axis2 though. If you have been able to convert WSIF over to Axis2 then perhaps I missed something. I am not very familiar with Axis2. -Doug. -----Original Message----- From: Sanjiva Weerawarana [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 21, 2006 1:11 PM To: wsif-dev@ws.apache.org Subject: RE: Axis 2.0 and WSIF On Wed, 2006-06-21 at 13:51 -0400, Jackson, Douglas wrote: > Hi Hasalaka, > It is my understanding that Axis 2 does not do dynamic data binding. What do you mean by "dynamic data binding"? I can't understand what Axis1 does for data binding that Axis2 doesn't .. nor WSIF. Thanks, Sanjiva. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
