-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Thilina Gunarathne wrote: > > BTW what's our policy when mapping the transport level errors to the > SOAPFaults.. I mean what we put in to code, reason, details, etc.... > We are trying to come up with a generic javascript error object[1] for > the WSRequest specification. Just curious about how Axis2 handles it > as one of our WSRequest implementations is done on top of Axis2...
I am not aware of any transport error mapping we do inside Axis2. Perhaps we can try to deduce a the fault code and put a minimal message as the reason and that is it. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGgmOjjON2uBzUhh8RAtK8AJ0b84QzXC5EUgjsjkg33eQ7t3NRIACfYof9 dk1vRPleV8zQs9a9MbdL2tU= =3Uu0 -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
