Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Looks like I'm limited by the framework and the way in which the handlers work. I think at this stage, my only option is to go to a lower level. I did take a look at using tubes but the same behaviour exhibited itself so it looks as though any attempt to work with the XML of the request fails. As such, I'm going to have to abandon handlers for the time being and investigate at a lower level whether I can make use of <a href="http://jax-ws.java.net/nonav/jax-ws-20-fcs/arch/com/sun/xml/ws/api/pipe/Codec.html" rel="nofollow">codecs</a> to do what I'm after. An MTOM implementation sounds like it may do what I'm after at the byte level:</p> <p><a href="http://jax-ws.java.net/nonav/jax-ws-20-fcs/arch/com/sun/xml/ws/encoding/MtomCodec.html" rel="nofollow">http://jax-ws.java.net/nonav/jax-ws-20-fcs/arch/com/sun/xml/ws/encoding/MtomCodec.html</a></p> <p>I imagined this would be a lot less complex to get working but will update with my progress on the codec front.</p> <p>@David: Thanks for your help on the handler front but looks as though there is no solution at that level.</p> <p><strong>Update 1</strong></p> <p>Came up with an alternate solution that works for my purposes. </p> <ol> <li>I sign the necessary parts of the SOAP message using my SOAPHandler.</li> <li>Wrote a new SOAPHandler that then takes resultant message and manually extracts the incorrectly inlined binary content.</li> <li>I then create an <code>AttachmentPart</code> and inject the content from Step 2 into that. It takes Base64 encoded text too which is handy. That <code>AttachmentPart</code> then has a reference UUID assigned to it for <code>Content-Id</code>.</li> <li><p>I then create a new element in place of the Base64 content in the SOAP body that reference the UUID, along the lines of the following:</p> <pre><code>&lt;xop:Include xmlns:xop="http://www.w3.org/2004/08/xop/include" href="cid:UUID!!!"&gt;&lt;/xop:Include&gt; </code></pre></li> </ol> <p>Will probably write a blog post on this as it's been a bit of an epic journey to this point. It was not the best solution but it was certainly easier than going down the tubes/codec path.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload