You can leverage camel-jetty or camel-servlet to receive the request, and then route the message to the script endpoint like this. <from uri="jetty://localhost:8080/myservice"/> <to uri="script:xxx"/> …
-- 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 Wednesday, December 12, 2012 at 11:39 PM, neilac333 wrote: > To answer your question, the trigger will be a web request to a certain URL. > The web endpoint will receive the request and then fire off the Python > script. The script could then either return a string for the directory name > where the output file has been generated or the full path of the file > itself. This should then serve as the message body for the next endpoint to > do stuff with the file. > > Given this, how would the Spring DSL configuration look? > > Thanks. > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Python-Script-Producing-a-File-tp5723933p5723957.html > Sent from the Camel - Users mailing list archive at Nabble.com > (http://Nabble.com).
