[
https://issues.jboss.org/browse/RTGOV-566?page=com.atlassian.jira.plugin....
]
Michael Clay commented on RTGOV-566:
------------------------------------
another use case for this
This one is required because for e.g. SOAP messages originating from a SCA binding for
which there is no possibility to configure a custom ContextMapper
to retrieve/extract (SOAP header) exchange properties which need to be simply passed
through to some referenced service (Reference).
Consider the following example application with one service with a soap and a sca binding
and an implementation which simple forwards (proxies) the soap request to some referenced
service (i.e. Reference in sy/sca terms). This referenced service is configured with a
custom contextmapper which has the same configuration like the one on the incoming soap
binding to tunnel/forward all SOAP header properties.
[resubmit] RemoteMessage#context is empty
-----------------------------------------
Key: RTGOV-566
URL:
https://issues.jboss.org/browse/RTGOV-566
Project: RTGov (Run Time Governance)
Issue Type: Bug
Components: User Interface
Reporter: Michael Clay
Assignee: Gary Brown
Fix For: 2.0.0.Final
because RemoteMessage#context is empty/not used there is no way to pass
properties required for the implementation of the resubmitted/retried service invocation
(e.g. SOAPHeader are stored as message properties)
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)