Hi all, I follow-up post to let you know the development of the problem, and a way to circumvent it. The problem is related to JAXB context and the exception occurs when the services are located in the same package, therefore share the same namespace, and are used to share similar objects.
Below are two way of consuming services, taken from CXF website, that lead to different results. The first method is to use dynamic client to consume services, but it results in the exceptions displayed in the previous post (org.apache.cxf.interceptor.Fault: Marshalling Error: org.activiti.engine.impl.webservice.Inc is not known to this context). Basically, jaxb is unable to access the generated classes during the second call. The second method is to use the JAX-WS Proxy that do not throw an exception (is it using jaxb somehow?). Please look at javacode for other details. Then the second consumption that do not trigger execptions (with services located in the same package) So I've partially resolved my problem by using the JAX-WS proxy method instead of the dynamic client generation, but I still don't understand how to create a correct service definition to use the dynamic client. Let me know if you have some ideas on how to create two services that will run in separate administrative domain, sharing the exact same object definition (I mean data types that are shared by the services: same name, namespace, same contract, etc.) and then consume them (in POJO or via activiti ;)) -- View this message in context: http://cxf.547215.n5.nabble.com/Calls-to-multiple-web-service-provider-within-Activiti-fail-with-a-Marshalling-Error-tp5711059p5711346.html Sent from the cxf-issues mailing list archive at Nabble.com.
