You will need a type mapping on both the client and server side for the type.
On the server side, type mappings go in the WSDD file (server-config.wsdd) and are usually part of the service element. They generally get there when the service is deployed. On the client side, type mappings can be in client-config.wsdd, but more likely they are established via calling APIs. For examples, run WSDL2Java -s on the WSDL for your service and check out the code in the *Stub.java and the deploy.wsdd. The Stub code is a bit obscure, but the relevant API is call.registerTypeMapping(). Hope this helps. -- Tom Jordahl Macromedia -----Original Message----- From: Lasker, Kory [mailto:[EMAIL PROTECTED]] Sent: Tuesday, April 16, 2002 4:25 PM To: '[EMAIL PROTECTED]' Subject: beanSerialization I'm having problems trying to unserialize a complexType from my service on the client side, causing me many problems between the role of the client and the deployment descriptor. In the <typeMapping> section of the DD using the default beanSerializer, am I supposed to refer to a class known only by the server-side, client-side, or both? The latter doesn't make any sense to me at all. But, if I use the client-side classes generated from WSDL2Java, I get a "class not found" type exception like this: org.apache.axis.deployment.wsdd.WSDDException: java.lang.ClassNotFoundException: com.lavaclient.Address My WSDD was generated by WSDL2Java as well. <typeMapping xmlns:ns="http://mynamespace.com"; qname="ns:Address" type="java:com.lavaclient.Address" serializer="org.apache.axis.encoding.ser.BeanSerializerFactory" deserializer="org.apache.axis.encoding.ser.BeanDeserializerFactory" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"; /> Any ideas out there? Thanks, Kory Lasker
