Re: AW: AW: AW: AW: deserialization error: unexpected XML reader state. expected: END but found: START:

Lorenzi, Michael wrote:

>There is the same problem when I use wsif/axis1.2.
>
>"it seems that your service does not handle well input  <ns1:String_1 
>...> - try to get <String_1 ...> sent and i think it may work (based on 
>what is in the WSDL at "
>
>That's correct! I tried it the old way with SOAP and it generated a correct message without the "ns1".
>
>How can I tell WSIF to use the SOAP-Provider instead of the AXIS?
>  
>
either regenerate JAR file to change metadata to select SOAP provider or 
override it in your code:

import 
org.apache.wsif.providers.soap.apachesoap.WSIFDynamicProvider_ApacheSOAP;


        
WSIFPluggableProviders.overrideDefaultProvider("http://schemas.xmlsoap.org/wsdl/soap/", 
new
WSIFDynamicProvider_ApacheSOAP());

and for AXIS

import 
org.apache.wsif.providers.soap.apacheaxis.WSIFDynamicProvider_ApacheAxis;

        
WSIFPluggableProviders.overrideDefaultProvider("http://schemas.xmlsoap.org/wsdl/soap/", 
new WSIFDynamicProvider_ApacheAxis());

alek

>
>Thank you
>Michael
>
>
>-----Ursprüngliche Nachricht-----
>Von: Aleksander Slominski [mailto:[email protected]]
>Gesendet: Sa 04.06.2005 13:27
>An: [email protected]
>Betreff: Re: AW: AW: AW: deserialization error: unexpected XML reader state. expected: END but found: START:
> 
>Lorenzi, Michael wrote:
>
>  
>
>>Thank you! I really got it to work. Here are the messages which are exchanged:
>> 
>>
>>    
>>
>it seems that your service does not handle well input  <ns1:String_1 
>...> - try to get <String_1 ...> sent and i think it may work (based on 
>what is in the WSDL at 
>http://metis.di.uoa.gr:8888/schedule/web-service?WSDL and what i 
>remember about soap rpc/encoding binding style) - it seems you are using 
>AXIS 1.0 - did you try running test with new WSIF/AXIS 1.2 ?
>
>alek
>
>  
>
>>OUTGOING MESSAGE:
>>
>>POST /schedule/web-service HTTP/1.0
>>Content-Type: text/xml; charset=utf-8
>>Accept: application/soap+xml, application/dime, multipart/related, text/*
>>User-Agent: Axis/1.0
>>Host: metis.di.uoa.gr:8080
>>Cache-Control: no-cache
>>Pragma: no-cache
>>SOAPAction: ""
>>Content-Length: 496
>>
>><?xml version="1.0" encoding="UTF-8"?>
>><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
>><soapenv:Body>
>> <ns1:updateScheduleDB soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns1="http://schedule/wsdl/Schedule">
>>  <ns1:String_1 xsi:type="xsd:string">Michael Lorenzi</ns1:String_1>
>> </ns1:updateScheduleDB>
>></soapenv:Body>
>></soapenv:Envelope>
>>
>>
>>INCOMING MESSAGE:
>>
>>HTTP/1.1 500 Internal Server Error
>>X-Powered-By: Servlet/2.4
>>SOAPAction: ""
>>Content-Type: text/xml; charset="utf-8"
>>Date: Sat, 04 Jun 2005 07:58:50 GMT
>>Server: Sun-Java-System/JWSDP-1.3
>>Connection: close
>>
>><?xml version="1.0" encoding="UTF-8"?>
>>
>><env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:enc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns0="http://schedule/types/Schedule" env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><env:Body><env:Fault><faultcode>env:Client</faultcode><faultstring>JAXRPC.TIE.01: caught exception while handling request: deserialization error: unexpected XML reader state. expected: END but found: START: {http://schedule/wsdl/Schedule}String_1</faultstring></env:Fault></env:Body></env:Envelope>
>>
>>
>>
>>
>>
>>
>>-----Ursprüngliche Nachricht-----
>>Von: Aleksander Slominski [mailto:[email protected]]
>>Gesendet: Sa 04.06.2005 09:40
>>An: [email protected]
>>Betreff: Re: AW: AW: deserialization error: unexpected XML reader state. expected: END but found: START:
>>
>>Lorenzi, Michael wrote:
>>
>> 
>>
>>    
>>
>>>"then have WSIF client to talk to your host/listenPort instead of 
>>>targetHost/targetPort"
>>>
>>>and how do I tell WSIF to talk to a special host/port?
>>>
>>>
>>>   
>>>
>>>      
>>>
>>change your WSDL service port soap:address location URL to point to 
>>"http://your host:listenPort/schedule/web-service" (modify WSDL returned 
>>by http://metis.di.uoa.gr:8888/schedule/web-service?WSDL) and use it in 
>>your WSIF client (if you need more help you need to post actual source 
>>code and how to run it to reproduce your problem ...)
>>
>>HTH,
>>
>>alek
>>
>> 
>>
>>    
>>
>>>-----Ursprüngliche Nachricht-----
>>>Von: Aleksander Slominski [mailto:[email protected]]
>>>Gesendet: Fr 03.06.2005 21:57
>>>An: [email protected]
>>>Betreff: Re: AW: deserialization error: unexpected XML reader state. expected: END but found: START:
>>>
>>>Lorenzi, Michael wrote:
>>>
>>>
>>>
>>>   
>>>
>>>      
>>>
>>>>What "Listen Port" and "Port" numbers do I have to set for the two services stated before? I don't see any message in the tcpmon.
>>>>
>>>>
>>>>  
>>>>
>>>>     
>>>>
>>>>        
>>>>
>>>for java org.apache.axis.utils.tcpmon [listenPort targetHost targetPort]
>>>set listenPort to some value you like (that client will use) and 
>>>targetHost/targetPort to location of your service.
>>>
>>>then have WSIF client to talk to your host/listenPort instead of 
>>>targetHost/targetPort
>>>
>>>alek
>>>
>>>
>>>
>>>   
>>>
>>>      
>>>
>>>>Sorry for the easy question, but I don't find the solution.
>>>>
>>>>
>>>>-----Ursprüngliche Nachricht-----
>>>>Von: Aleksander Slominski [mailto:[email protected]]
>>>>Gesendet: Fr 03.06.2005 19:23
>>>>An: [email protected]
>>>>Betreff: Re: deserialization error: unexpected XML reader state. expected: END but found: START:
>>>>
>>>>Lorenzi, Michael wrote:
>>>>
>>>>
>>>>
>>>>  
>>>>
>>>>     
>>>>
>>>>        
>>>>
>>>>>Hi all,
>>>>>
>>>>>when I want to invoke the Operation "updateScheduleDB" of the WSDL "http://metis.di.uoa.gr:8888/schedule/web-service?WSDL" or the Operation "isPatientInsured" of the WSDL "http://metis.di.uoa.gr:8888/insurancecompany/web-service?WSDL"
>>>>>
>>>>>I get a strange error:
>>>>>
>>>>>EXIT  WSIFDefaultMessage.getObjectPart(JAXRPC.TIE.01: caught exception while handling request: deserialization error: unexpected XML reader state. expected: END but found: START: {http://schedule/wsdl/Schedule}String_1)
>>>>>
>>>>>
>>>>>I use the last release of WSIF, 2.0. Can anyone tell me why and help me?
>>>>>
>>>>>
>>>>> 
>>>>>
>>>>>    
>>>>>
>>>>>       
>>>>>
>>>>>          
>>>>>
>>>>please use TCPMon to see what is XML on the wire - it is hard to say 
>>>>what happens unless you see what is going on the wire with SOAP/HTTP.
>>>>
>>>>alek
>>>>
>>>>
>>>>
>>>>  
>>>>
>>>>     
>>>>
>>>>        
>>>>
>>>   
>>>
>>>      
>>>
>> 
>>
>>    
>>
>
>
>  
>


-- 
The best way to predict the future is to invent it - Alan Kay