You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@synapse.apache.org by "John Bouck (JIRA)" <ji...@apache.org> on 2008/03/07 21:53:48 UTC
[jira] Created: (SYNAPSE-249) Configurable URL's for proxy services
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
Fix For: 1.2
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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Resolved: (SYNAPSE-249) Configurable URL's for proxy
services
Posted by "Ruwan Linton (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ruwan Linton resolved SYNAPSE-249.
----------------------------------
Resolution: Fixed
Fix Version/s: (was: 1.3)
NIGHTLY
Fixed on the svn trunk
> 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: NIGHTLY
>
>
> 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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Updated: (SYNAPSE-249) Configurable URL's for proxy services
Posted by "Asankha C. Perera (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Asankha C. Perera updated SYNAPSE-249:
--------------------------------------
Priority: Minor (was: Major)
Assignee: Asankha C. Perera
A nice to have feature to be incorporated into 1.2 if time permits
> 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: Asankha C. Perera
> Priority: Minor
> Fix For: 1.2
>
>
> 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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Commented: (SYNAPSE-249) Configurable URL's for proxy
services
Posted by "Ruwan Linton (JIRA)" <ji...@apache.org>.
[ 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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Commented: (SYNAPSE-249) Configurable URL's for proxy
services
Posted by "Ruwan Linton (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12609760#action_12609760 ]
Ruwan Linton commented on SYNAPSE-249:
--------------------------------------
Now you can configure the proxy service URL to be customized using the service level parameters.
* you can specify a the URI on which this service is being exposed on as a service parameter with name "ServiceURI"
* While this service is exposed on the virtual ServiceURI it also serves on the actual URL of the service but WSDL will show the virtual URL that has been specified in the parameter
* This parameter has to specify the service path for example if you specify the following,
<parameter name="ServicecURI">version/2008/07/02/MyService</parameter>
the full service URL would be;
http://localhost:8280/version/2008/07/02/MyService
> 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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Updated: (SYNAPSE-249) Configurable URL's for proxy services
Posted by "Ruwan Linton (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ruwan Linton updated SYNAPSE-249:
---------------------------------
Fix Version/s: (was: 1.2)
1.3
Is there any urgent requirement for this issue. If not I would like to postpone this to the next release
> 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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Assigned: (SYNAPSE-249) Configurable URL's for proxy
services
Posted by "Ruwan Linton (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ruwan Linton reassigned SYNAPSE-249:
------------------------------------
Assignee: Ruwan Linton (was: Asankha C. Perera)
> 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.2
>
>
> 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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org