Bug 957678 - RTGov: ExchangeInterceptor does not work for one-way messages
Summary: RTGov: ExchangeInterceptor does not work for one-way messages
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: JBoss Fuse Service Works 6
Classification: JBoss
Component: RT Governance
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: DR3
: 6.0.0
Assignee: Gary Brown
QA Contact: Jiri Pechanec
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-04-29 08:53 UTC by Jiri Pechanec
Modified: 2013-05-15 04:25 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Known Issue
Doc Text:
Cause: One way invocations not currently supported by runtime governance. Consequence: The one way exchange is not reported to the activity server. Workaround (if any): Use request/response invocations via the SOAP binding. Result: Request/Response invocations originating from a SOAP binding will be reported by the runtime governance infrastructure to the activity server.
Clone Of:
Environment:
Last Closed: 2013-05-15 04:25:53 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Jiri Pechanec 2013-04-29 08:53:20 UTC 
Exchange interceptor is written in the way that it suppose that both IN and OUT phases of exchange are executed. This is not the case for one-way messages.

Under these circumstances the one-way is not recorded/presented.

Try camel-jms-binding to see the behaviour.
Comment 1 Gary Brown 2013-05-09 08:33:47 UTC 
For alpha, only SOAP binding will be supported.

For beta, it is likely that the ExchangeInterceptor (an auditor packaged with the switchyard app) will be replaced by an external event listener that will be able to handle this situation.

Have added some documentation text - feel free to update.
Comment 2 Jiri Pechanec 2013-05-09 08:38:04 UTC 
What if I have one way SOAP binding? Will it work? Would not it be better to limit the text to request/reply SOAP binding?
Comment 3 Gary Brown 2013-05-09 08:43:12 UTC 
Yes, good point - I've updated the text.
Comment 4 Jiri Pechanec 2013-05-15 04:25:53 UTC 
Limitation of alpha
Note You need to log in before you can comment on or make changes to this bug.