RE: Registering the serializer/deserializer!

[John Pirie]

Sudhir,   This seems to me to be an acceptable way to register the (de)serializers on the client, though I had used one of the other variations of registerTypeMapping.   Are you specifying the type mapping in the wsdd file on the server?  Something like:           <beanMapping qname="ns1:TAnyWhoInfo"                      xmlns:ns1="http://tempuri.org"                      languageSpecificType="java:my.package.TAnyWhoInfo" /> From what I have read recently, it seems as though this element will be scoped; so if you place it within a service, it will be so scoped.   You could also opt to use <typeMapping>, for which <beanMapping> is a shorthand.   John Michael Pirie   -----Original Message----- From: Sudhir [mailto:[EMAIL PROTECTED]] Sent: Wednesday, June 12, 2002 6:23 PM To: [EMAIL PROTECTED] Subject: Registering the serializer/deserializer! Is this the right way to register a serializer and a deserializer?   Class beansf = org.apache.axis.encoding.ser.BeanSerializerFactory.class; Class beandf = org.apache.axis.encoding.ser.BeanDeserializerFactory.class; Service  service = new Service(); call = (Call) service.createCall(); javax.xml.rpc.namespace.QName qName; qName = new javax.xml.rpc.namespace.QName("http://tempuri.org/", "TAnyWhoInfo"); call.registerTypeMapping(TAnyWhoInfo.class, qName, beansf, beandf, false);   But I am gettint the following exception. org.xml.sax.SAXException: Bad types (null -> class TAnyWhoInfo)         at org.apache.axis.message.RPCHandler.onStartChild(RPCHandle r.java:205)         at org.apache.axis.encoding.DeserializationContextImpl.start Element(DeserializationContextImpl.java:831)         at org.apache.axis.message.SAX2EventRecorder.replay(SAX2Even   What could be the reason?   The trouble with the world is that the stupid are cocksure and the intelligent are full of doubt. Integrity without knowledge is weak and useless, and knowledge without integrity is dangerous and dreadful. This communication is intended only for the use of the individual or entity to whom/which it is addressed, and information contained in this communication is privileged and confidential. If the receiver of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender of this email (so that we may correct our internal records) and delete this communication without making a copy of it. Thank you.