On Thu, May 12, 2011 at 8:03 AM, Chris Richmond
wrote:
> So, what are my options? I have an existing service defined by my service
> interface class which is in use and I am migrating to Camel and is SOAP?
> Can I simply not use Camel to service this service definition?
>
I have created a ticket
Here was my code:
ServiceInterfaceStrategy strategy = new
ServiceInterfaceStrategy(TestService.class, false);
SoapJaxbDataFormat soapDF = new
SoapJaxbDataFormat("com.referentia.cameltest.TestServiceImpl", strategy);
soapDF.setContextPa
So, what are my options? I have an existing service defined by my
service interface class which is in use and I am migrating to Camel and
is SOAP? Can I simply not use Camel to service this service definition?
Thanks,
Chris
On 5/10/2011 6:53 PM, Claus Ibsen wrote:
On Wed, May 11, 2011 at 4:1
On Wed, May 11, 2011 at 4:12 PM, Chris Richmond
wrote:
> I finally successfully got CXF service being served at a Camel consumer
> endpoint, where TestService has the interface annotated method which I can
> call from a .NET soap client no problem:
>
> @WebMethod(operationName="EchoValue")
> @We
Thank you, I discovered exactly what you said and did not use the
dataformat and it starts fine, but now when I try to call my same
initial webmethod(not the new multiparameter method) I get the following.
org.apache.camel.component.bean.AmbiguousMethodCallException: Ambiguous
method invocati
Hi,
You are using camel-cxf and soap dataformat at the same time.
Either of them can do the job for you.
Please check the document of camel-cxf[1] and came-soap[2]
[1]http://camel.apache.org/cxf.html#CXF-HowtoconsumeamessagefromacamelcxfendpointinPOJOdataformat
[2]http://camel.apache.org/soap.h
