THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
When used with an InOut MEP, the Exec return the command execution output into the out message. The out message content looks like:
Code Block | ||||
---|---|---|---|---|
| ||||
<output><result> <exitcode>0</exitcode> <output><![CDATA[ total 6729 -rw------- 1 jb jb 1693752 2009-04-09 09:07 f9G0lWzx.tar.part -rw-r--r-- 1 jb jb 8 2009-03-27 18:27 gnome-session-manager srwxr-xr-x 1 jb jb 0 2009-03-26 10:56 gnome-system-monitor.jb.3619273851 drwxr-xr-x 2 jb jb 1024 2009-04-23 08:43 hsperfdata_jb drwxr-xr-x 2 jboss java 1024 2009-04-17 12:46 hsperfdata_jboss drwxr-xr-x 2 weblogic java 1024 2009-04-17 09:40 hsperfdata_weblogic -rw-r--r-- 1 jb jb 870 2009-03-26 10:59 jbi12672.zip -rw-r--r-- 1 jb jb 870 2009-03-26 10:59 jbi12673.zip ]]></output> <error><![CDATA[ ]]></error> </output>result> |
Endpoint
The Exec endpoint can be very simple, waiting for command contained in the in message:
...