Demonstrating the ability to load endpoint definitions dynamically from the remote registry.
This example introduces dynamic endpoints, where the definition of the endpoint is stored in the registry. To follow this example execute the stock quote client as 'ant stockquote..' and see that the message is routed to the SimpleStockQuoteService on the default Axis2 instance on HTTP port 9000.
Repeat the above command immediately again, and notice that the endpoint is cached and reused by Synapse - similarly to sample 8.
Now edit the repository/conf/sample/resources/endpoint/dynamic_endpt_1.xml file and update the address to 'http://localhost:9001/services/SimpleStockQuoteService'. After the cached value expires, the Registry loads the new definition of the endpoint, and then the messages are routed to the second sample Axis2 server on HTTP port 9001.