Hi, I guess you just want to create the proxy dynamically, maybe it is based on the request url or content, Am I right?
-- Willem Jiang Red Hat, Inc. Web: http://www.redhat.com Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On March 26, 2015 at 9:27:57 PM, ercan.canlier (ercan.canl...@gmail.com) wrote: > Hi to everybody, > First of all, many thanks for such a great framework that you implemented so > far. > It is extremely powerful and very fast. The documentation is quite in > detail. > I am implementing a web application for our integration tests. > I need to track incoming / outcoming messages to database. > For this, i can handle it via routing to bean and then show at my web page. > I have already read tutorials about cxf proxy, also read some camel's book > but things are not very clear. > I implemented one example, seems i am close to the solution but it is not > finished yet. > From my point of view, if the client sends request to the frontend service > which is proxy here, it should be forwarded to backend real service. > For instance: When user sends request to > http://localhost:8080/real-web-service, it must be forwarded to > http://localhost:8081/backend-web-service, isnt proxy working like that? By > forwarding the request, i must be able to track the messages. > On the other hand, i will publish web services dynamically when the user > load wsdl, how can i proxy them as well? > Should i use jetty at front and match them according to forwarding > properties? But like this, how can i proxy dynamically? > I hope you do understand the scenario and might give me some tips. > Thanks in advance. > Ercan > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Web-Service-Proxy-to-track-incoming-and-outcoming-messages-tp5764824.html > > Sent from the Camel - Users mailing list archive at Nabble.com. >
