Hi, How did you start the camel route? Did you have chance to go through this page[1] and this example[2]?
[1]http://camel.apache.org/spring-web-services.html#SpringWebServices-Exposingwebservices [2]http://camel.apache.org/spring-ws-example.html -- Willem Jiang Red Hat, Inc. FuseSource is now part of Red Hat Web: http://www.fusesource.com | http://www.redhat.com Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/) (English) http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese) Twitter: willemjiang Weibo: 姜宁willem On Thursday, February 21, 2013 at 5:33 AM, NCSWolfpak wrote: > Hello, > > I'm currently experimenting with camel and I'm trying to create a route that > will take the payload of a spring-ws SOAP request and route it to an > activemq topic. I believe I have Camel configured correctly since it has > been routing between other endpoint types without problems, and ActiveMQ > seems to be configured correctly since I have been able to route other > messages to the queues/topics. My guess is I've misconfigured the route > builder for the spring-ws component or misunderstood its usage. For > reference I'm using Camel 2.10.3, Spring 3.1, and spring webservices > 2.1.2.RELEASE. Camel and ActiveMQ are running embedded with the Spring > context. > > Currently, I have Spring-ws configured to have a request called DoAction on > my server ‘someserver.’ The request appears as below: > > <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" > xmlns:sch="http://company.com/actions/schemas"> > <soapenv:Header/> > <soapenv:Body> > <sch:DoAction> > <sch:Action> > <sch:status>1</sch:status> > <sch:IPAddress>10.12.13.14</sch:IPAddress> > </sch:Action> > </sch:DoAction> > </soapenv:Body> > </soapenv:Envelope> > > This request is sent to http://someserver:9090/webapp/action/ > > Using SoapUI, the requests seem to be handled in Spring without any issues. > > In my routebuilder (extending SpringRouteBuilder, overriding configure()), I > currently have the following configured: > > from("spring-ws:uri:http://localhost/webapp/action?endpointMapping=#endpointMapping") > .convertBodyTo(String.class).to("activemq:topic:someTopic"); > > I have tried several other mapping types and addresses ranging from > specifying the specific host, specific host and port, wildcards, etc but in > all cases it doesn’t seem that the SOAP requests submitted and processed are > making their way through camel. I’ve even tried creating a beforeProcess > breakpoint, but those aren’t being triggered at all when the SOAP requests > are submitted. I don’t suppose there are any ideas on how we should be > configuring the mapping-type/address combination (or maybe anything else) in > order to route the DoAction requests? Thanks in advance for any help with > this. > > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Questions-about-spring-ws-component-tp5727906.html > Sent from the Camel - Users mailing list archive at Nabble.com > (http://Nabble.com).