Nice work Srinath !!! :-) Sure... we can work on integrating this with axis2 so it will support the other cases as well... Especially I'd like if we can get all the interop scenarios working with policy (expressed in the wsdl) as well. In doing so, please note that right now we cannot extract all information required using (E.g. alias of the encr user) ws-sec policy but lets try and see how far we get... and we can use the usual configuration mechanism to provide those missing config information.
IMHO this is an axis2 change in terms of communicating the sec policy into the security module/handlers and we will be able to use it even when we integrate the updated wss4j stuff once we are done with the sec policy integration into the core of wss4j. Thanks, Ruchith On 3/8/06, Srinath Perera <[EMAIL PROTECTED]> wrote: > Hi All; > > Right now, In my local machine I have a security policy client side > working for Security signature. The code to use it look like this. > > AxisServiceBuilder asb = new AxisServiceBuilder(); > AxisService service = asb.getAxisService(wsdlDefinition); > > WSDLBasedPolicyProcessor policyProcessor = new > > WSDLBasedPolicyProcessor(configContext); > policyProcessor.configureServicePolices(service); > ServiceClient serviceClient = new ServiceClient(configContext,service); > serviceCleint .......//use it > > There are few local changes I should check in and once I do it I > believe we can make this work for Axis2 in general easily. Ruchith > shall we setup a sample and test this for general case. Do you have > time to work with me couple of hours on this? > > Thanks > Srinath > > -- > ============================ > Srinath Perera: > http://www.cs.indiana.edu/~hperera/ > http://www.bloglines.com/blog/hemapani >
