I think you will get better support on the ServiceMix user mailing list for
this kind of question, because it's related to the ServiceMix JBI component.
But good to know you could figured out by yourself.
Best,
Christian
On Sun, Sep 16, 2012 at 2:33 PM, dennisbaerten <den...@baerten-vandebroek.be
> wrote:
> Problem found, both xbean and camelcontext did not have the correct
> servicename from the wsdl.
> I used MediatorService, which actually should be IMediatorService like in
> the wdsl ...
>
> <wsdl:service name="MediatorWS">
> <wsdl:port binding="tns:MediatorWSSoapBinding"
> name="IMediatorService">
>
>
> So the following xbean definition
>
> <cxfbc:provider wsdl="classpath:MediatorService.wsdl"
> locationURI="${uploadMediatorURI}"
> interfaceName="mediator:IMediatorService"
> service="mediator:MediatorWS"
> useJBIWrapper="false" useSOAPEnvelope="false"
> busCfg="http_conduit_config.xml"/>
>
> and camelcontext route
>
> <camel:to
> uri="jbi:endpoint:
> http://www.mycompany.com/xpert/mediator/service/MediatorWS/IMediatorService?mep=in&operation={http://www.mycompany.com/xpert/mediator/service}uploadMediator
> "
> />
>
>
> are working correctly now.
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/javax-jbi-messaging-MessagingException-Could-not-find-route-for-exchange-tp5719417p5719430.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
--
