Hi Kent,
Thanks for the reply. So, it means it's got to be a global thing? For example, one can't encrypt the out message of an operation while just sign the out message of another operation?
You can actually do this using the following : org.apache.axis2.security.handler.config.InflowConfiguration org.apache.axis2.security.handler.config.OutflowConfiguration I have explained a bit about those at in at the end of my response in this [1] mail. You can use these configurations separately for each operation by setting the parameter into options of the stub or service/operation client just before invoking that operation. Thanks, Ruchith [1] http://marc.theaimsgroup.com/?l=axis-dev&m=114732539613452&w=2 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
