On Tuesday, February 14, 2012 4:29:06 PM Jason Pell wrote: > Hi, > > It does not seem to work for much other than SERVICE. I have not > tested all combinations so far, but so far all I have managed to have > working is SERVICE. > > I am now trying to associate Policy with one operation, while another > operation has no ws-security requirements at all. I have tried > BINDING_OPERATION, PORT_TYPE_OPERATION, neither of which work. > > Am certainly looking forward to your analysis. If you could point me > in the right direction of the code I would need to look at as I am > interested to understand this area of cxf as well
Honestly, not quite sure where to look yet. The fact that the policy is properly exposed in the WSDL (via the ?wsdl url) shows that the policy is loaded fine and attached into the service model. The runtime SHOULD be using that just fine as it should be exactly the same as if the policy was loaded from a real WSDL. Thus, I'm not sure what would cause it yet. Probably will need to dig through the effective policy calculation stuff for both the wsdl first and non-wsdl cases to see where the policies are coming from and see what may be different. No idea yet. Again, very strange to see the policies in the wsdl, but no have them take affect. :-( -- Daniel Kulp [email protected] - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com
