So, if client A wants to use service X, and the WSDL for service X indicates (by some means) that the input message of any/all operations must be signed using a digital signature, then we have 2 choices:
i) force each application to code in the use of the dig sig client side infrastructure to sign the message and insert the approp. dig sig header
or
ii) have tooling interpret the wsdl for service X and build the appropriate service specific chain for X which decorates the message coming from the application with dig sig information.
It is scenario ii that the pluggable client-side infrastructure was meant to handle.
sgg
++++++++
Steve Graham
[EMAIL PROTECTED]
(919)254-0615 (T/L 444)
Emerging Technologies
++++++++
Glyn Normington/UK/IBM@IBMGB | 
07/03/2002 11:11 AM |  To: [EMAIL PROTECTED] cc: Subject: Re: client-side global chain |
Doug,
A naive question...
>Let's say someone wants to add a client-side handler
>that's service specific.
What might they hope to achieve by doing this? A specific scenario would
help me.
Glyn
