Using WSS4J/Axis2 API, Part 2, Sending WS-Signed and Encrypted Message Transmission Optimization Mechanism (MTOM)/XML-binary Optimized Packaging (XOP) Attachments to a Axis2/Rampart Web service
From the developerWorks archives
Date archived: May 14, 2019 | First published: June 29, 2010
Continuing from part 1 of this article series, which showed how to use WSS4J and AXIS2 API to send WS-Signed and WS-Encrypted SOAP messages. This final article in the series will focus on how to send Message Transmission Optimization Mechanism (MTOM)/XML-binary Optimized Packaging (XOP) enabled WS-Signed /WS-Encrypted SOAP messages using WSS4J/AXIS2 API.
This content is no longer being updated or maintained. The full article is provided "as is" in a PDF file. Given the rapid evolution of technology, some content, steps, or illustrations may have changed.