Mailing-List: contact axis-user-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-user@xml.apache.org
Message-ID: <64510FFDEBCAD511B8CB00065B055DE30938F6@galaxy.natsys.fr>
From: =?iso-8859-1?Q?C=E9dric_Chabanois?= <CChabanois@cognicase.fr>
To: "'axis-user@xml.apache.org'" <axis-user@xml.apache.org>
Subject: RE: SAX Exception while using complex types: Bad types
Date: Tue, 26 Nov 2002 14:23:56 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

here is the code that throws this exception :

                  Class xsiClass =3D=20
                          =
context.getTypeMapping().getClassForQName(type);
                  if (null !=3D xsiClass  &&
!JavaUtils.isConvertable(xsiClass, destClass)) {
                      throw new SAXException("Bad types (" +
                                             xsiClass + " -> " + =
destClass +
")"); // FIXME!
                  }

the exception is :
Caused by: org.xml.sax.SAXException: Bad types (class
com.telebahiacelular.movistore.acao.value.AcaoModel -> class
com.telebahiacelular.movistore.acao.value.AcaoModel)


So this code tries to convert AcaoModel to AcaoModel. It should =
work....
JavaUtils.isConvertable uses Class.isAssignableFrom

I don't know why it does not work.

C=E9dric Chabanois

> -----Message d'origine-----
> De : Marcus Brito [mailto:pazu@animegaiden.com.br]
> Envoy=E9 : mardi 26 novembre 2002 14:05
> =C0 : axis-user@xml.apache.org
> Objet : SAX Exception while using complex types: Bad types
>=20
>=20
> Hello again, folks. Here is the second problem I'm having=20
> while trying=20
> to access a Stateless Session Bean as a web service using JBoss and=20
> Axis. I hope your MUA can show this message in the same thread as my=20
> previous message.
>=20
> Here is the problem: after being able to generate the WSDL for the=20
> service (thanks to C=E9dric Chabanois for the helping me), I tried to =

> write a DII client to invoke the service. However, something=20
> goes wrong=20
> again and all I get is an AxisFault. Attached goes:
>=20
> 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.
>=20
> I'm willing to provide any further information. I've seen=20
> that the axis=20
> generate a lot of logging information during the call. I haven't=20
> included it here due it's sheer volume (aronud ~60k for just a single =

> call), but I could provide it if needed.
>=20
> --
> Pazu <pazu@animegaiden.com.br>
>=20