to solve this problem I have 1. a client that reads the wsdl and policies and sends the message to the server. This is the normal way to work with wsdls with policies. 2. for the server side because of the bug mentioned that no Signature is created as an action, we use the programatic approach where we manually specify in the endpoints action that the server needs a UsernameToken, Timestamp and Signature and we provide as wsdl location a wsdl without policies.
Then it works. But it would be nice that the server side also could interpret the policies written in the wsdl. Is there anyone that made the server side work with thatose policies written in the wsdl or are you also following this hibrid approach. thanks Ovidio -- View this message in context: http://cxf.547215.n5.nabble.com/EndorsingSupportingTokens-and-SignedSupportingTokens-throing-a-Nullpointer-exception-tp4689470p4692695.html Sent from the cxf-dev mailing list archive at Nabble.com.
