Boy, do I feel dumb! I'm pretty new to axis but I
felt like I was starting to have a good understanding
of it - at least up until now that is.
I'm trying to view raw SOAP messages as they leave and
are returned to my client. I'm able to call a test
service through a local Axis server with the
SOAPMonitor, but now I'm calling a remote (non-Axis)
server. I've tried using Call.setClientHandlers,
using the HandlerRegistry, digging through the list
archives, reading the apis, screaming, kicking,
banging my head against the wall - now I'm reduced to
whining on the mailing list.
Using the setClientHandlers route creates an
exception. Here are snippets of my client code:
Service service = new Service();
Call call = (Call)service.createCall();
....
QName movement = new
QName("urn:PackTrackConsumer","Movement");
call.registerTypeMapping(Movements.class,movement,...
The code works fine here. However, once I add the
call to setClientHandlers, I get a IOException that
there isn't a serializer for the Movements class. I
have seen this mentioned in the mailing list archives,
but have not been able to find a solution. I'm not
using WSDL2Java stubs since I don't have a WSDL file
to work from.
While going through the archives, I stumbled upon the
concept of using the HandlerRegistry. I'm not able to
get this to work because I don't understand what QName
to use in order to get the HandlerChain from the
service's HandlerRegistry (do I need to provide a WSDL
file to make this work)?
Anyway, I've quickly realized that I don't grok this
SOAP/Axis stuff as well as I thought. Any assistance
in getting the setClientHandlers to work without
stomping on my my type mappings, or in helping me
figure out how to successfully extract the
HandlerChain, would be most appreciated!
Thanks in advance,
Todd
todd_run at yahoo dot com
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
