servicemix-exec-service-unit/src/main/resources/archetype-resources/src/main/resources/xbean.xml

<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by Apache ServiceMix Archetype -->
<beans xmlns:exec="http://servicemix.apache.org/exec/1.0"
	xmlns:replaceMe="http://servicemix.apache.org/replaceMe" xmlns="http://www.springframework.org/schema/beans"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="
        http://servicemix.apache.org/exec/1.0 http://servicemix.apache.org/schema/servicemix-exec-@{components.version}.xsd
        http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.0.xsd">

    <!-- 
        The ServiceMix Exec component is used to invoke commands (executables, shell commands, scripts, ...).
        The command can be static (defined in the component endpoint descriptior, the xbean.xml) or
        dynamic (provided in the incoming message, including arguments).
        
        This endpoint provides an abstract WSDL exposed in the endpoint definition.
        
            http://servicemix.apache.org/servicemix-exec.html
    -->

    <!-- BEGIN SNIPPET: exec -->
    <!--
        The exec endpoint is quite simple. It's waiting for command in incoming messages
        and use "date" command as fallback if the incoming message doesn't contain the
        command message part.
        
        Attributes:
            service             : the endpoint service name
            endpoint            : the endpoint name
            interfaceName       : the endpoint interface name
            command             : the fallback command or script
            marshaler           : the marshaler to use to parse the incoming message and construct the exec command
    -->
	<exec:endpoint service="replaceMe:serviceName"
		endpoint="exec" command="date" />
    <!-- END SNIPPET: exec -->

</beans>