Ok, there are at least two bugs that are related to this problem:
1) JDeveloper adds the wrong property when you add a header through the GUI tab "Headers" on an invoke activity. It should be "bpelx:inputHeaderVariable" and NOT "bpelx:headerVariable". (Bug #12541901).
2) Currently in SOA Suite 11g the WS-Addressing headers are overwritten when the SOAP call is made. Enhancement Request #13718140 has been logged asking for this behaviour to be changed in a future release. This is currently being considered by Product Management.
Oracle support suggests that you use OSB to set the headers.
An alternative to using OSB (e.g. in case you don't have OSB installed) is to create a Web Service proxy in JDeveloper and add a message handler to it that adds the appropiate WSA headers to the outbound SOAP call. In that case the message flow would be:
SOA composite (SOA Suite) --> JAX-WS Web Service (incl. message handler that adds WSA headers) --> external Web Service (that requires the WSA headers).
A good place for this information is the Oracle Fusion Middleware Developer's Guide for Oracle Service Bus 11g Release 1 (184.108.40.206.1) on OTN, see: http://docs.oracle.com/cd/E23943_01/dev.1111/e15866/toc.htm
Also see this blog --> http://mazanatti.info/index.php?/archives/43-OSB-11g-synchronous-asynchronous-conversion.html
any clue as to if this limitation is solved ?
We have a business scenario where in first sync call generates a request id and further async responses are sent.
we need to set reply-to in first call on which the callee will revert with async response messsage. but using header variable or normalized message we are not able to make this work ... is this a real limitation of oracle 11g ??