Hello,
On the server side, Rampart configuration is done in service.xml. In this file, you can specify the behavior of Rampart either for the entire service or for a specific operation, depending on where in the file you insert the configuration. I wonder how an operation-based configuration of Rampart can be done on the client side. For example, I want that my client application uses different Rampart configurations for service operation A and B. The only options for client configuration I know are the following: 1) Insert parameters in axis2.xml of the client's repository. -> This however means that the configuration is global, i.e. for all services and all operations. Is there a way to configure a different Rampart behavior for a particular service or operation in the client's axis2.xml file? 2) Load specific configuration using ConfigurationContextFactory -> This way I can load a different configuration per Stub or ServiceClient, i.e. per service, but again I can't configure Rampart based on operations, just for the entire service. 3) Use code to configure Rampart on client-side (classes OutflowConfiguration, InflowConfiguration) -> same problem like with 2) The only solution I could think of is to load my ServiceClient with a different set of options, depending on the operation I will invoke next. This doesn't sound very appealing to me. Is there another way? Any hints are very welcome. Thanks, Thilo --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
