[ 
https://issues.apache.org/jira/browse/SYNAPSE-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12609756#action_12609756
 ] 

Ruwan Linton commented on SYNAPSE-249:
--------------------------------------

Rather than the proposed syntax, I would like to introduce sort of a more 
generic configuration for this. This feature is being implemented on the nhttp 
transport level and hence it would be interesting to axis2 as well.

So I will be adding this configuration point as a service parameter.

> Configurable URL's for proxy services 
> --------------------------------------
>
>                 Key: SYNAPSE-249
>                 URL: https://issues.apache.org/jira/browse/SYNAPSE-249
>             Project: Synapse
>          Issue Type: Improvement
>    Affects Versions: 1.1
>         Environment: all
>            Reporter: John Bouck
>            Assignee: Ruwan Linton
>            Priority: Minor
>             Fix For: 1.3
>
>
> Allow exact url's to be specified for proxy services.  This can allow for url 
> versioning schemes for services like:
> http://synserv/soap/2007-10-10/MyService -> version 1 of the service
> http://synserv/soap/2008-01-10/MyService  -> version 2 of the service
> http://synserv/soap/2008-03-05/MyService -> version 3 of the service
> some possible examples of how the configuration file could look:
> <proxy name="blah">
>   <url="http://server.com/myurl/2008-09-09/service";>
>   ...
> </proxy>
> <proxy name="2008-09-09/service">
>   ...
> </proxy>
> Don't forget that synapse can be deployed behind a proxy server and that 
> there may be a servername defined in the axis configuration.  Also generated 
> WSDL's for the proxy service must also pick up the service URL.

-- 
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to