Affects: Documentation (Ref Guide, User Guide, etc.)
project_key: SOA

Programmer's Guide
Chapter 12 discusses issues regarding custom action development. It should be highlighted that a single action instance is shared between threads during parallel message processing and it has to be taken into consideration.

Moreover earlier in the documentation there is a paragraph - Using a list of method names in a single <action> element has some advantages over the use of successive <action> elements. This is because the action class is instantiated once and methods will be invoked on the same instance of that class. This reduces the overhead and means that "state" information can be kept in the instance objects. - This text is very misleading.

I suggest expanding this chapter into something Like Best practices of custom action development.