camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From <serv...@paypal.com>
Subject RE: Questions about spring-ws component (KMM79183761V96793L0KM) :ppNA
Date Wed, 20 Feb 2013 21:46:41 GMT
Dear users@camel.apache.org,

Thank you for contacting PayPal Customer Support. My name is Audrey Kate
and I am happy to assist you.

I would suggest for you to contact our account speacialist at this 
number 1-888-883-9770.

It is my pleasure to assist you. Thank you for choosing PayPal.

Sincerely Yours,
Audrey Kate
PayPal Consumer Support
PayPal, an eBay Company





-----------------------------------------  
From:  users@camel.apache.org  
Sent:  Wednesday,  February  ##,  ####  #:##:##  PM  (-##:##)  
To  kana##@paypal.com  
Subject:  Questions  about  spring-ws  component  
  
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  #.#,  and  spring  webservices  
#.#.#.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>#</sch:status>  
             <sch:IPAddress>##.##.##.##</sch:IPAddress>  
          </sch:Action>  
       </sch:DoAction>  
    </soapenv:Body>  
</soapenv:Envelope>  
  
This  request  is  sent  to  http://someserver:####/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=#endp  
ointMapping")  
         .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.######.n#.nabble.com/Questions-about-spring-ws-component-tp#######.html
 
Sent  from  the  Camel  -  Users  mailing  list  archive  at  Nabble.com.  
  

Mime
View raw message