Thilo, Please flesh out a concrete proposal in the wiki and open a JIRA. We'd really appreciate some diff's against the current SVN Head as well.
thanks, dims On 1/24/07, Thilo Frotscher <[EMAIL PROTECTED]> wrote:
Hi, I just encountered the problem that there is no way in Axis2 to define a service-based or operation-based configuration for Rampart on the client side. Consider a situation where you want to develop a client application that needs to communicate with multiple services or multiple operations, and these have different security requirements. In such a case you'll have to create a set of axis2.xml files, load all of them into multiple configuration contexts, and then juggle these contexts before and after sending messages. This is very inconvenient. Therefore I'd like to propose an extension of the client-side configuration, so that service-based and operation-based configuration is possible for clients. This was possible with Axis 1. Also, I think it's quite confusing for beginners that the same axis2.xml file is used for client app as well as for the Axis2 web application (as for example in the code samples). Parameters that only apply to the server side should either be grouped and clearly marked, or there should be two different axis2.xml files: one for the client side and one for the server side (as in Axis 1). I do recognize though, that many parameters are needed on both sides, as client applications can also start listeners an act as servers etc. and services can send messages (i.e. be clients). Thanks, Thilo --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
