I am not sure , but,
I had a similar problem where axis tried to deserialize an exception A to
an exception B class,which end with same fault as you encounter.The
reason was that the QName of
the exceptions on the wsdd was shared , when I change it and gave each
exception a different QN
The whole stack trace should not bather you (unless from networking
point of view) ,the calling code should parse the axis xml response and
throw the exception just as you wish , so that you can display a simple
string to the caller. This is right if you are using WSDL2Java to
generate classes for
I am using Axis on the Server side and Axis
Call (through WSIF) on the
Client side :
I have a very declared exception on my WebService
,which
do appear on the wsdl , BUT , when this
exception is
throw on the server side ,on the client side it's
considere as an Undeclaredthrowable
fromValue(Integer
value)
public String toString()
what is wrong ?
Thanks
Ofer Baranes
server side! ,
both root cause exceptions are in the signature of the
invoked
service.
What could that be ? why does Axis client and server are not sync ?
(by root cause I mean AxisFault ‘detail’ field)
Thanks
Ofer baranes
seen code of others, which used a DynamicProxy
to
obtain a client stub instead of using WSDL2Java to do so.
I was amazed that
such a way is absent from the user guide or its demo.
I believe most
users will preferred using the DynamicProxy
way.
Best Regards and Thanks
Ofer Baranes
