After investigating the Axis2 problems with one-way signing and encryption further I found that they were due to misconfiguration in my code. I've requested a correction to the discussion of Axis2 in the article, and have also sent in replacement code showing that Axis2 correctly handles the one-way cases I tested (at least, once the policy namespace is changed to the submission version). With the corrected code, Axis2 actually does the best of the stacks in handling this type of situation!
I wanted to make sure the correction got into this thread, too, in case others find it through searches in the future. - Dennis On 11/03/2010 12:54 PM, Dennis Sosnoski wrote: > Hi Thomas, > > I haven't had any luck with one-way security policies using Axis2, > though I didn't try this particular combination. You might find my > latest Java Web Services article on devWorks of interest: > http://www.ibm.com/developerworks/java/library/j-jws18/index.html This > one covers WS-Policy in some detail, and includes my tests with some > one-way policies. Your case is simpler than the ones I used, so you > might find that CXF or Metro would work for what you want. > > You could also try attaching the policies directly to the actual Axis2 > message object in your client code (rather than including them in the > WSDL for client code generation), and see if that works. > > - Dennis > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
