Thanks, Nandana! I tried using the external reference for policies but kept getting a 'policy not found' error. I'll look into it more to see if I'm just missing something stupid.
As for 2, thanks for the reference. Any thoughts on when the next 'official' rampart release will be made since the issue appears to have been resolved after rampart 1.4 was released? Thanks, Bob -----Original Message----- From: Nandana Mihindukulasooriya [mailto:[EMAIL PROTECTED] Sent: Thursday, October 16, 2008 9:59 AM To: [email protected] Subject: Re: Externalize Policy/Rampart Config on server side Hi Bob, 1. Reference an external policy within the services.xml (e.g. policy-ref > similar to module-ref) at the servicegroup and service level. If you use the policy attachment mechanism [1] added lately to Axis2, you must be able to add a policy reference to the service giving an absolute URL of an external policy. But I have never tried it. <service> ... <wsp:PolicyAttachment xmlns:wsp=" http://schemas.xmlsoap.org/ws/2004/09/policy";> <wsp:AppliesTo> <policy-subject identifier="binding:soap11" /> <policy-subject identifier="binding:soap12" /> </wsp:AppliesTo> <wsp:PolicyReference xmlns:wsp=" http://schemas.xmlsoap.org/ws/2004/09/policy"; URI="http://myDomain/mypolicy"/> <wsp:PolicyAttachment/> </service> > 2. A property in the rampart config section within the policy to set a > 'config' callback handler that would be called to retrieve the > rampart/wss4j configuration properties. It would be nice if this > callback request included the service for which the configuration is be > requested. > Rampart has a mechanism to update the RampartConfg using a callback [2] which was added recently. I will write some documentation on how to use it. thanks, nandana [1] - https://wso2.org/library/3786 [2] - http://issues.apache.org/jira/browse/RAMPART-177 -- Nandana Mihindukulasooriya WSO2 inc. http://nandana83.blogspot.com/ http://www.wso2.org
