Red Hat Bugzilla – Bug 779374
NullAction shipped with the SOA-P
Last modified: 2011-04-08 16:09:09 EDT
Date of First Response: 2010-01-04 10:49:59
Two different customers have for testing/performance purposes have produced create their own NullAction, I have even produced one while messing around. We should include a NullAction as part of the standard set of Actions.
There are two options for this at present
- don't declare any "actions" element on the service and you have a service which returns the incoming message as a response
- use the EchoRouter as your null action. The EchoRouter does log at INFO though (not sure why) so this would need to be disabled if testing performance.
To disable the logging it would be necessary to change jboss-log4j.xml and add the following
The first suggestion is not applicable as there is an explicit check in the pipeline preventing a 'naked' pipeline from being configured.
Link: Added: This issue related JBIDE-5637
This was triaged for SOA 5.1.0. It is not in 5.1.0