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