Nandana. Thanks. Yes, I was thinking of something along the same lines. There should be a way to associate a common policy with more than one service without having to duplicate it across the services to which it applies. This way we can do some central policy management. The policy can reside possibly locally (Axis2 repo) or even remotely (some http/ftp location?) - so Axis2 can retrieve and load it during deployment time. I'll drop a mail to the Axis2 Dev list sometime soon. Thanks again, Murali
----- Original Message ---- From: Nandana Mihindukulasooriya <[EMAIL PROTECTED]> To: rampart-dev@ws.apache.org Sent: Tuesday, December 4, 2007 3:49:17 AM Subject: Re: Associating security policies with Axis2 services Hi, I have a design question. Currently each Axis2 service has its ws-security > policy associated with it via the services.xml deployment file. So there > is a 1-to-1 mapping between the service and the policy. But, is there a way > to create one security policy and associate with 2 or more services without > including it with the service? You mean, like having a specific place in the AXIS2 repository and dropping all common policies there and just specifying the policy ID ( or something unique ) in the services.xml. I think this will be a good idea. But I think this has to be done in AXIS2. In the deployment time, the policy has to be loaded and attached to the service. So this has to happen in the AXIS2 deployment. So I think, it is good idea to drop a mail to AXIS2 DEV list about your proposal. Regards, Nandana > Get easy, one-click access to your favorites. > Make Yahoo! your homepage. > http://www.yahoo.com/r/hs > ____________________________________________________________________________________ Looking for last minute shopping deals? Find them fast with Yahoo! Search. http://tools.search.yahoo.com/newsearch/category.php?category=shopping
