Greetings,
I'm trying to configure an interceptable web services proxy using Camel
1.4.0. My initial thought was to attempt to create a simple HTTP proxy:
...
from("jetty:http://localhost:8080/services/myService";)
.to("http://otherhost:80/Service1.asmx";);
...
The hope was that this would also expose features like using ?wsdl in a
browser, for example. What seems to happen instead is that query parameters
are stripped from the incoming GET request, and the request type is
converted into a POST.
I have several .Net web services running in another application that I'm
trying to provide a transparent front end for. Rather than manually code
(or generate) separate implementations for each WS, I'd rather pass the
requests through in a manner that permits interception in later
implementations. Is there a better way to do this? What am I doing wrong?
Regards,
Michael Murphree
--
View this message in context:
http://www.nabble.com/Proxying-web-services-tp19498936s22882p19498936.html
Sent from the Camel - Users mailing list archive at Nabble.com.
