Hi,
I was looking at the ode extension for HTTP, as I will have to
invoke a REST service from my process in ODE. I am using ODE 1.3.5. I noticed 2
main limitations with the extension:
1. I have a custom header and a query parameter while making a GET REST
service call. Hence I have 2 message parts(one for the query parameter input
and other for the custom header) for the input message that represents this
REST call. When I use urlencoded tag in the wsdl both the header along with the
query parameter are getting encoded in the URL. How can I ensure that header
does not get encoded in the URL?
2. I have REST services which use POST method, but they do take query
parameters and path parameters. These are however ignored by HTTP binding
component. Is there a way to get around this problem?
Awaiting reply. Thanks in advance.
Regards,
Vinay
