Sajini De Silva created SYNAPSE-914:
---------------------------------------

             Summary: Hierarchical proxy services for synapse
                 Key: SYNAPSE-914
                 URL: https://issues.apache.org/jira/browse/SYNAPSE-914
             Project: Synapse
          Issue Type: Improvement
          Components: Proxy Services
         Environment: synapse
            Reporter: Sajini De Silva
            Priority: Minor


At the moment SYNAPSE supports proxy services that can only be added under 
8280:services/FooProxy etc. Therefore it is very hard to manage the proxy 
services for a large organization when the number of services become large, 
since they have to agree on service name before deploying them. And also 
supporting multiple versions of the same service is not possible without 
changing the service name in the services.xml file.

I have  implemented  the task of supporting hierarchical proxy services in 
SYNAPSE. Now when a proxy service is added other than the name of the proxy 
service, service hierarchy can be inserted. If we deploy a proxy service named 
"foo" with a service hierarchy "a/b/c/" in the 
SYNAPSE_HOME/repository/conf/synapse-config/proxy-services/a/b/c directory, you 
can access that service from 8280:services/a/b/c/foo. 

Here is the configuration for the proxy service named "foo" with a service 
hierarchy "a/b/c/". 

 <proxy name="foo"
          serviceHierarchy="a/b/c/"
          transports="https http"
          startOnLoad="true"
          trace="disable">
      <description/>
      <target>
         <endpoint>
            <address 
uri="http://localhost:9000/services/SimpleStockQuoteService"/>
         </endpoint>
      </target>
   </proxy>

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to