Hi Freeman, Further digging revealed that I was not properly setting the WSDL operation to perform. So I changed the uri for my jbi cxfbc:provider to:
<to uri="jbi:service:http://example.proj/test/MyCxfbcProvider?operation={http://example.proj/test}MyTestMethod"/> That fixed the problem. It is odd that w/o the operation on the uri that Smx was able to find and invoke the correct method, but when the response returned Smx got lost. Another odd thing I noticed was that I couldn't set the operation and the mep at the same time: ...MyCxfbcProvider?mep=in-out&operation={http://example.proj/test}MyTestMethod"/> The schema validator complains: "The reference to entity "operation" must end with the ';' delimiter." I'd be curious to know what the proper syntax is or if what I was trying is even valid. Apparently once I defined the operation it could determine the mep because that operation defines an output message in the WSDL. Thanks, Brendan Freeman Fang wrote: > > Hi, > Any Chance you append a testcase(like SA) which can reproduce your > error? It would be a big help. > Thanks > Freeman > btmahon wrote: >> I am trying to invoke an external web-service using a JBI cxfbc:provider >> from >> a Camel route. The web-service is getting called correctly (it logs the >> incoming request) but I get the following error in ServiceMix (3.3.1.13) >> presumably trying to process the response: >> >> java.lang.NullPointerException >> at >> org.apache.servicemix.cxfbc.CxfBcProviderMessageObserver.onMessage(CxfBcProviderMessageObserver.java:108) >> >> My cxf-bc configuration is as follows: >> <cxfbc:provider >> wsdl="classpath:MyService.wsdl" >> locationURI="http://localhost:8888/myService"; >> service="ms:MyService" >> endpoint="MyServiceImpl" >> useJBIWrapper="false"> >> </cxfbc:provider> >> >> My Camel route is essentially: >> <route> >> .... >> <to >> uri="jbi:service:http://example.proj/myService/MyService?mep=in-out"/> >> <to uri="file:/tmp/MyServiceResponse/"/> >> >> I was able to successfully configure a cxfbc:consumer as a direct proxy >> to >> the cxfbc:provider and that path (no Camel involved) works fine. >> >> Any help would be appreciated. >> >> Thanks, >> Brendan >> >> > > > -- > Freeman Fang > ------------------------ > Open Source SOA: http://fusesource.com > > > -- View this message in context: http://www.nabble.com/NullPointerException-when-calling-cxf-bc-provider-from-camel-tp23157401p23175845.html Sent from the ServiceMix - User mailing list archive at Nabble.com.
