axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Anne Thomas Manes <>
Subject Re: deserializer not found
Date Tue, 05 Jul 2005 18:21:01 GMT
Have you defined a client config file and specified the deserializer
using either a <typeMapping> or <beanMapping> definition?


On 7/4/05, Patrick Quinn <> wrote:
> Hi 
> I'm still stuck with my deserializer problem: 
> org.xml.sax.SAXException: Deserializing parameter 'ProvidentResponse': 
> could not find de
> serializer for type
> {http://ProvidentConnector.ProvidentResponseToOrch}ProvidentResponse
> Does anyone know of a resource where I can find out more about the
> intricacies of serializing/deserializing within a SOAP and/or Axis context? 
> I am writing a java client app to communicate with a BizTalk web service, so
> all I really want to do is make sure that I am doing the right thing on the
> client side (although if I could get a working Axis test service simulator
> that would be good too ...) 
> Pat =00This e-mail and any attachments may be confidential and/or legally
> privileged. If you have received this e-mail and you are not a named
> addressee, please inform Evolving Systems TIS at and then
> delete the e-mail from your system. If you are not a named addressee you
> must not use, disclose, distribute, copy, print or rely on this e-mail. To
> ensure regulatory compliance and for the protection of our clients and
> business, Evolving Systems may monitor and read e-mails sent to and from its
> servers. Although Evolving Systems routinely screens for viruses, addressees
> should scan this e-mail and any attachments for viruses. Evolving Systems
> makes no representation or warranty as to the absence of viruses in this
> e-mail or any attachments.
> Registered Office: One Angel Square, Torrents Street, London. EC1V 1PL.
> Registered number 2325854

View raw message