Bug 778629

Summary: Programmers_Guide.pdf StaticWiretap description is confusing
Product: [JBoss] JBoss Enterprise SOA Platform 5 Reporter: Burr Sutter <burr.sutter>
Component: DocumentationAssignee: Kevin Conner <kevin.conner>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 5.0   
Target Milestone: ---   
Target Release: 5.0.0 GA, 5.0.0 ER2   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-1105
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: SOA-1105 Environment:
Last Closed: 2010-01-05 15:20:38 UTC Type: Feature Request
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Burr Sutter 2008-12-23 19:10:42 UTC
++ This bug is a clone of bug 778628 ++

Date of First Response: 2010-01-05 10:20:38
project_key: SOA

This section:
StaticWiretap
Static message wiretapping action. The StaticWiretap differs from the StaticRouter in that the
StaticWiretap "listens in" on the action chain and allows the message to continue in the chain to
subsequent actions, while the StaticRouter action only pushes the message to destinations that are
defined in its route-to chain.
-------------
I believe StaticWiretap differs from StaticRouter in that the wiretap allows the actions below it to be executed while the router terminates the action chain at the point it is used.  The router should therefore be the last action in the chain.

Review org.jboss.soa.esb.actions.StaticRouter (extends StaticWiretap):
    public Message process(Message message) throws ActionProcessingException
    {
        super.process(message) ;
        return null ;
    }

Where return null terminates the action chain.

Comment 1 Jeff Yu 2009-01-20 07:07:52 UTC
Link: Added: This issue depends JBESB-2298