Inconsistent handling of faults in ActionProcessingPipeline for oneway services ------------------------------------------------------------------------------- Key: JBESB-3616 URL: https://issues.jboss.org/browse/JBESB-3616 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.9 Reporter: Kevin Conner There is a consistency problem when handling faults within the ActionProcessingPipeline. The processing of faults for a oneway invocation currently checks the FaultTo in the call header and, if not present, does not return a fault. Unfortunately this creates an inconsistency with the fault behaviour of a request/response service which checks FaultTo and then falls back to ReplyTo/From. This inconsistency is a problem if you choose to split a request/response service into two or more chained services, as faults which occur in the oneway services will not be returned to the consumer as intended. The fault behaviour should be changed so that the oneway processing is the same as the request/response processing, i.e. DefaultFaultTo.getFaultTo should ignore the oneway flag and attend to query the ReplyTo/From EPRs. I suspect I introduced this issue. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira