Message-ID: <1610047030.7791.1418875849163.JavaMail.firstname.lastname@example.org> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_7790_1764259937.1418875849163" ------=_Part_7790_1764259937.1418875849163 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
You can see the WS-Addressing support in the javadoc<= /a>. The most common use case is when implementing a server side handler wi= shing to process the current WS-Addressing context.=20
Here's some example code to show you how to do thisAn error occurre= d: cvs.activesoap.codehaus.org. The system administrator has been notified.= =20
Things are similar on the client side - you need to create the MessageExchang= e instance first, then configure the WS-Addressing context on it before= performing the client invocation.An error occurred: cvs.activesoap.co= dehaus.org. The system administrator has been notified.