My problem was just the char serialization part. Do you know if by now there are any available?
[]�s Francisco Ar�as Guimar�es eMacDigital (Brasil) Ltda. Email: [EMAIL PROTECTED] Tel. 11-3371-9515 - R. 2065 -----Original Message----- From: Fernandez Martinez, Alejandro [mailto:[EMAIL PROTECTED] Sent: Friday, December 05, 2003 9:10 AM To: '[EMAIL PROTECTED]' Subject: RE: Non-RemoteException serialization Hi Francisco, > -----Mensaje original----- > De: Francisco Areas Guimaraes [mailto:[EMAIL PROTECTED] > Enviado el: jueves 4 de diciembre de 2003 21:02 > Para: [EMAIL PROTECTED] > Asunto: RE: Non-RemoteException serialization > > > Hi, I stumbled upon this problem just now, and instead of creating a > serializer and deserilazer, I switched the variable to int, worked > alright. Since the original message is more than 1 year old, anybody > knows if a Character serializer has been implemented? That is only a partial solution. For example, if the remote side throws an unexpected exception (say, a NullPointerException), it is difficult to see it at all -- you would get an AxisFault just as always, and would have to display or log it to see the problem. Ideally, I would like to be able to differentiate between communication failures, declared exceptions on the remote side and unexpected exceptions. It is hard to tell them apart unless you can get them deserialized via AxisFault.getCause(). Alex.
