synapse-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ruwan Linton (JIRA)" <>
Subject [jira] Commented: (SYNAPSE-412) REST Invocation Issue with Proxy Services
Date Mon, 04 Aug 2008 09:21:44 GMT


Ruwan Linton commented on SYNAPSE-412:

I have applied the patch and committed the code. Good work Saliya, with a one minor comment,
do not do additional formatting in the javadoc to make it look aligned in the code which will
result in messy java docs.

> REST Invocation Issue with Proxy Services
> -----------------------------------------
>                 Key: SYNAPSE-412
>                 URL:
>             Project: Synapse
>          Issue Type: Bug
>          Components: Transports
>            Reporter: Saliya Ekanayake
>            Priority: Minor
>             Fix For: NIGHTLY
>         Attachments: 20080729_fix.patch
> A proxy service in Synapse (say, myproxy) can be accessed via an HTTP GET call. This,
however, requires the user to type in the operation name after the proxy name (e.g. http://localhost:8280/services/myproxy/mediate).
If given the proxy name only it'll show the information on the service. This approach incurs
errors when the actual request we want to send to the back end doesn't require a method name.
> Consider an example where a user wants to get a file hosted in the back end server via
a proxy service in Synapse. If he/she creates a simple proxy service as in sample 150 to do
this, the actual URI send to the back end consists of the resource name followed by the method
name (if no WSDL is given this method name will be "mediate"). This will not serve the user
with his/her resource, instead will return an error.
> We can overcome this issue by letting a user invoke a proxy service by its name (or a
method name followed by the name if necessary). The information on the service is shown only
if the user types the "?info" parameter after the service name. So with this fix the information
on our sample proxy service can be retrieved by entering http://localhost:8280/services/myproxy?info
into the browser. The service can be accessed by entering http://localhost:8280/services/myproxy
into the browser.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message