Data format json-xstream could not be created.' error when deploying Xstream service in JBoss Fuse

Issue

When deploying a service using Xstream for Unmarshall/Marshall task, the following error/exception is thrown:

 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 1) JBAS014612: Operation ("deploy") failed - address: ([("deployment" => "service.jar")]) - failure description: {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"service.jar\".SwitchYardService" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"service.jar\".SwitchYardService: org.switchyard.SwitchYardException: Failed to create route route1 at: >>> Unmarshal[org.apache.camel.model.dataformat.JsonDataFormat@7798b8c1] <<< in route: Route(route1)[[From[switchyard://... because of Data format 'json-xstream' could not be created. Ensure that the data format is valid and the associated Camel component is present on the classpath
    Caused by: org.switchyard.SwitchYardException: Failed to create route route1 at: >>> Unmarshal[org.apache.camel.model.dataformat.JsonDataFormat@7798b8c1] <<< in route: Route(route1)[[From[switchyard://... because of Data format 'json-xstream' could not be created. Ensure that the data format is valid and the associated Camel component is present on the classpath
    Caused by: org.apache.camel.FailedToCreateRouteException: Failed to create route route1 at: >>> Unmarshal[org.apache.camel.model.dataformat.JsonDataFormat@7798b8c1] <<< in route: Route(route1)[[From[switchyard://... because of Data format 'json-xstream' could not be created. Ensure that the data format is valid and the associated Camel component is present on the classpath
    Caused by: java.lang.IllegalArgumentException: Data format 'json-xstream' could not be created. Ensure that the data format is valid and the associated Camel component is present on the classpath"}}
10:44:39,599 ERROR [org.jboss.as.server] (DeploymentScanner-threads - 1) JBAS015870: Deploy of deployment "service.jar" was rolled back with the following failure message