You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Marcus Brito <pa...@animegaiden.com.br> on 2002/11/26 14:05:17 UTC
SAX Exception while using complex types: Bad types
Hello again, folks. Here is the second problem I'm having while trying
to access a Stateless Session Bean as a web service using JBoss and
Axis. I hope your MUA can show this message in the same thread as my
previous message.
Here is the problem: after being able to generate the WSDL for the
service (thanks to Cédric Chabanois for the helping me), I tried to
write a DII client to invoke the service. However, something goes wrong
again and all I get is an AxisFault. Attached goes:
1) The full stack trace;
2) The WSDL (generated by axis using ?wsdl) for the service;
3) The Service interface (an EJB remote interface);
4) The DII client source code.
I'm willing to provide any further information. I've seen that the axis
generate a lot of logging information during the call. I haven't
included it here due it's sheer volume (aronud ~60k for just a single
call), but I could provide it if needed.
--
Pazu <pa...@animegaiden.com.br>
Same types considered incompatibles
Posted by Marcus Brito <pa...@animegaiden.com.br>.
Here we go, once again. I've messed a lot since my last error, and my
previous error disappeared. However, I've got a new one, still related
to some type strangeness. Axis seems to consider a type as incompatible
with itself.
This is what happens when I try to access the service:
faultString: Tried to invoke method public abstract
com.telebahiacelular.movistore.acao.value.AcaoPKModel
com.telebahiacelular.movistore.acao.interfaces.Acao.inserir(com.telebahiacelular.movistore.acao.value.AcaoModel)
throws javax.ejb.CreateException,java.rmi.RemoteException with arguments
com.telebahiacelular.movistore.acao.value.AcaoModel. The arguments do
not match the signature.
The service is actually a Stateless Session Bean deployed on JBoss. See
previous messages from this same thread.
Attached goes:
1) The SOAP request and response, as captured by tcpmon
2) The complete fault stack trace
3) The service WSDD descriptor
4) The service interface
5) The client source code
Environment: JBoss 3.2.0beta2 + Apache Axis 2002-11-26 interim drop.
--
Pazu <pa...@animegaiden.com.br>