WS-Addressing Headers in WebSphere ESB v6.2
February 5, 2009 2 Comments
I wrote previously about how WS-Addressing headers could be accessed in a WebSphere ESB mediation flow, by writing a JAX-RPC handler to intercept them and insert them into a custom SOAP header.
However, in WebSphere ESB 6.2, this is much easier – these headers will now automatically appear as part of the ServiceMessageObject at /headers/WSAHeader. They are effectively read-only; any changes that you make will not affect outgoing messages.
SOA Tips 'n' Tricks 
IBM should give 6.1’ers an iFix for this issue.
WS-Addressing and WS-Security cannt be empty in a client’s incoming BO message. I really hope they give us a fix soon or we are facing major surgery in our design.
Thanks
AB
@Amir,
I understand your concerns, but this blog is not an official IBM support mechanism. If you are looking for an iFix from IBM, it’s important that you open a PMR (your IBM client team can help you if needed) to request that.
Thanks,
Andrew.