axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dennis Reil" <>
Subject Re: can't find deserializer problem
Date Sat, 11 May 2002 16:46:40 GMT
Finally I found a way to get it work. You have to take the service-object and
create a call. Then just create a mapping for the custom data type. Then do the
method-calls as normal. I inserted the following lines after the instantiation of the
Call call = (Call) service.createCall();
            QName collectionqn = new QName(DLM_NS,"collection");
            call.registerTypeMapping(Collection.class, collectionqn, new BeanSerializerFactory(Collection.class,
                new BeanDeserializerFactory(Collection.class,collectionqn));

    Dennis Reil

----- Original Message ----- 
  From: Jabali Putrevu 
  Sent: Saturday, May 11, 2002 6:05 PM
  Subject: Re: can't find deserializer problem

  Could you resolve this problem?  I'm getting the similar exception when I run my cilent
    ----- Original Message ----- 
    From: Dennis Reil 
    Sent: Friday, May 10, 2002 8:35 AM
    Subject: Re: can't find deserializer problem

    Ok, I'll attach the wsdl, I used to create the proxy classes.
      ----- Original Message ----- 
      From: Glen Daniels 
      To: '' 
      Sent: Friday, May 10, 2002 3:33 PM
      Subject: RE: can't find deserializer problem

      Could you send along the WSDL?
        -----Original Message-----
        From: Dennis Reil []
        Sent: Friday, May 10, 2002 5:57 AM
        To: AXIS-User-List
        Subject: can't find deserializer problem

        I wrote a wsdl-document describing a service, which uses schemas to describe
        custom data types. 
        I generated the stub, ... with the wsdl2java-tool. Then I implemented and deployed
        the service. 
        The Client uses the WSLocator-Class. With tcpmon I can see, that the requests and

        responses are working fine, but the client throws an exception. It says, it can't
        a deserializer for the collection-type. Do I have to specify additional parameters
        the client to work correctly ? The service itself seems to have no problem with the
        custom type.
        Any ideas ? The exception and the client code can be seen below.

            Dennis Reil

        org.xml.sax.SAXException: Deserializing parameter 'collection':  could not find deserializer
for type
         at org.apache.axis.message.RPCHandler.onStartChild(
         at org.apache.axis.encoding.DeserializationContextImpl.startElement(
         at org.apache.axis.message.SAX2EventRecorder.replay(
         at org.apache.axis.message.MessageElement.publishToHandler(
         at org.apache.axis.message.RPCElement.deserialize(
         at org.apache.axis.message.RPCElement.getParams(
         at org.apache.axis.client.Call.invoke(
         at org.apache.axis.client.Call.invoke(
         at org.apache.axis.client.Call.invoke(
         at RechercheDienst.RechercheDienstBindingStub.searchByXPathQuery(
         at RechercheDienst.Test.main(


        package RechercheDienst;

        import com.dnsalias.eVerlageWS.Searchrequest;

        public class Test {

         public static void main(String[] args) {
                    RechercheDienstWS service = new RechercheDienstWSLocator();
                    RechercheDienstInterface port = service.getRechercheDienstPort();
                  catch (Exception e){
                    System.out.println("DEBUG: Fehler");

View raw message