Hi,
I had sometimes the same problem and again today. So the problem could be, that the namespace uri in the DeploymentDescriptor file in the Serializer Mapping section <isd:map encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"; xmlns:x ="<namespace uri>" qname="x:<name>" and in the client class, when you initialize the serializer object org.apache.soap.encoding.soapenc.BeanSerializer catSer = new org.apache.soap.encoding.soapenc.BeanSerializer(); smr.mapTypes( WebServiceConstants.NS_URI_SOAP_ENC, new QName(<NAMESPACEURI>, "<name>"), some.class, catSer, catSer); must be the same. and also the given name. For me it helped, maybe it is nearly the same problem in your app. cya de.we. On 28.11.2001 11:57:54 "Xiao Juguang" wrote: > Hi, all. > How are you today? I am almost crashed when I tried to fix the problem > below. > > Here is my problem. > > I create serializer and deserializer for one of my class, Exon. I write > mapping code in deployment descriptor and deploy it. I can see the result of > deployment via web admin pages of Apache SOAP. > When I tried to run client code, I met the fault : > > Fault Code = SOAP-ENV:Server > Fault String = java.lang.IllegalArgumentException: No Serializer found to > serialize a "Exon", using encoding style http://schemas. > xmlsoap.org/soap/encoding/ > > I tried to find the potential causes: > > 1) location of my Exon and its ser/deserializer.-- I think tomcat can find > them because I placed them in tomcat/classes > > 2) Typo in deployment descriptor -- I checked time. > > > What is other cause reason to lead to such problem? Please help. > > Thanks > > Juguang > ____________________________________________ SinnerSchrader Deutschland GmbH Communication & Technology mailto:[EMAIL PROTECTED] http://www.sinnerschrader.com fon +49.(0) 40.39 88 55-0 fax +49.(0) 40.39 88 55-55 gasstrasse 8-16 | 22761 hamburg | germany ____________________________________________
