It was my fault, the build was not updating some classes on the war file. 
Sorry to annoy all of you.

On Thu, 5 Jan 2006 15:38:39 -0500, Anne Thomas Manes <[EMAIL PROTECTED]> 
escreveu:
> 
> WSDL?
> 
> On 1/5/06, Claudio Miranda <[EMAIL PROTECTED]> wrote:
> >
> >
> >
> >    Hi all, I did a improvement since my last question. Now the ws client
> > (axis) can send the request with timeouts, thanks.
> >    Now I am facing another issue, I don't know if it is on the server or
> > client side, please take a look.
> >    I know the problem is the server returning a string while the client
> > try to use a Escohida.class, but I don't have (yet) no clue, where the
> > problem is. On the client side, I don't have any xml descriptor file. There
> > is no exception on the server side.
> >    The server is Sun App Server 8, with JAX-RPC. The client is Axis 1.3.
> >
> > ### Exception on client side.
> > Caused by: org.xml.sax.SAXException: Bad types (class java.lang.String ->
> > class claudius.Escolhida)
> >        at org.apache.axis.message.RPCHandler.onStartChild(RPCHandler.java
> > :286)
> >        at org.apache.axis.encoding.DeserializationContext.startElement(
> > DeserializationContext.java:1035)
> >        at org.apache.axis.message.SAX2EventRecorder.replay(
> > SAX2EventRecorder.java:165)
> >        at org.apache.axis.message.MessageElement.publishToHandler(

--
  Claudio Miranda
_______________________________________________________________
  http://www.claudius.com.br/blog              http://www.summa-tech.com
  http://www.soujava.org.br

Reply via email to