WS-Addressing Headers in WebSphere ESB v6.2

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.

Advertisements

2 Responses to WS-Addressing Headers in WebSphere ESB v6.2

  1. Amir Bahmanyari says:

    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

  2. @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.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: