RE: deserializing error

2005-06-27 Thread Patrick Quinn
2005 19:55 An: axis-user@ws.apache.org Betreff: RE: deserializing error Just bouncing this one, as the question was fairly generic: The server-config.wsdd file I notice does not have the bean mapping described by Mark. Should I add

RE: deserializing error

2005-06-27 Thread Patrick Quinn
_ Von: Patrick Quinn [mailto:[EMAIL PROTECTED] Gesendet: Sonntag, 26. Juni 2005 19:55 An: axis-user@ws.apache.org Betreff: RE: deserializing error Just bouncing this one, as the question was fairly generic: The server

RE: deserializing error

2005-06-26 Thread Patrick Quinn
-user@ws.apache.org Cc: Subject: RE: deserializing error Hi Guys Thanks for your responses, really appreciated. Yes, the code segment exists as follows: qName = new javax.xml.namespace.QName

RE: deserializing error

2005-06-25 Thread Patrick Quinn
@ws.apache.org Cc: Subject: RE: deserializing error Hi Patrick, you have a generated stub class. look at your stub class if this code segement exists qName = new javax.xml.namespace.QName(urn:[yourpacckagename

Re: deserializing error

2005-06-24 Thread mmalinos
Try this... QName qn = new QName(somenamespace,somequalifiedname); call.registerTypeMapping(yourbean.class, qn, new BeanSerializerFactory(yourbean.class, qn), new BeanDeserializerFactory(yourbean.class,

RE: deserializing error

2005-06-24 Thread Patrick Quinn
16:43 To: axis-user@ws.apache.org Subject: Re: deserializing error Try this... QName qn = new QName(somenamespace,somequalifiedname); call.registerTypeMapping(yourbean.class, qn, new BeanSerializerFactory(yourbean.class, qn

RE: deserializing error

2005-06-24 Thread Ferruh Zamangör
PROTECTED] An: axis-user@ws.apache.org Betreff: RE: deserializing error Datum: Fri, 24 Jun 2005 17:00:32 +0100 Thanks for the tip. The registerTypeMapping call is already made in the stub, as part of createCall(): synchronized (this) { if (firstCall