The
client stubs generated by Axis are great for creating the basic SOAP message,
but what if you want to add other new features, such as encryption or digital
signatures as specified by WS-Security? Adding handlers to the client-side
handler chain allows these additional features to be added to the outgoing
message without having to change the originally generated stubs. Sample code in
the IBM web services toolkit, which is built on top of Axis, uses client-side
handlers for just this sort of thing. .
Dan
Weston
-----Original Message-----
From: Volkmann, Mark [mailto:[EMAIL PROTECTED]
Sent: Friday, March 07, 2003 11:15 AM
To: '[EMAIL PROTECTED]'
Subject: AxisClient uses?What are some examples of why one would want to use an Axis engine on the client-side. I'm referring to the class AxisClient and the whole handler framework it supports. It makes perfect sense to me why I'd want this on the server-side supported by AxisServer. I just don't get what AxisClient buys me.
***********************************************************************************
WARNING: All e-mail sent to and from this address will be received or
otherwise recorded by the A.G. Edwards corporate e-mail system and is
subject to archival, monitoring or review by, and/or disclosure to,
someone other than the recipient.
************************************************************************************
