R2D2 wrote:
Hello Alek,
hi R2D2?!
I am using WSIF 2.0 and the Axis jars which are
packaged with it only. It is Axis 1.0.
if possible try and use the latest WSIF/AXIS and wee what happens:
http://cvs.apache.org/dist/wsif-2.0/nightly/
Is there someway in which I can use the
BeanDeserializer
check this thread and try to use mapType
http://www.mail-archive.com/[email protected]/msg00459.html
instead of the SimpleSerializer ?
i think you can access AXIS Call object through casting WSIFPort to
WSIFPort_ApacheAxis (check mailing list archives - for example
http://article.gmane.org/gmane.comp.apache.webservices.wsif.user/150
http://article.gmane.org/gmane.comp.apache.webservices.wsif.user/6)
and that should allow you to overwrite serializers - also you could try
client side deployment descriptor
BTW, the logs actually show the xml message coming
back successfully :
i would need to see the actual XML/HTTP message on the wire to say
something useful - probably there is some small mismatch in its
structure triggering the problem - use TCPMon and check what *exactly*
is XML on the wire ...
The entire response XMLis available between these 2
blocks ie, between END1 and START2
i could not see any XML in your email ...
best,
alek
--
The best way to predict the future is to invent it - Alan Kay
