Hi Claudi
"A Dynamic Proxy may be defined by specifying a proxy with the key as its
definition. As the remote registry entry changes, the proxy will dynamically
be updated accordingly."
I tried to do a dynamic proxy, but I didn't find the correct syntax. Maybe
it isn't supported for now?
Yes, you are right. This line should be removed from the document as we
currently do not support the specification of a key for proxy services
similarly to dynamic endpoints or sequences.
2. I tried the full registry based configuration (example 11), but the cache
isn't reloaded after the cachableDuration value timeout. Is it a bug?
No, this is working correctly as expected. The configuration in sample
11 is as follows:
<!-- a full registry based configuration -->
<definitions xmlns="http://ws.apache.org/ns/synapse";>
<registry provider="org.apache.synapse.registry.url.SimpleURLRegistry">
<parameter
name="root">file:./repository/conf/sample/resources/</parameter>
<parameter name="cachableDuration">15000</parameter>
</registry>
</definitions>
and illustrates that you could start a cluster of Synapse instances
pointing to the same registry alone, without creating multiple (local)
configuration files. (i.e. to load the exact same configuration - use
the registry itself to hold the overall synapse.xml) Note that you are
just specifying the root of the registry, and synapse looks for the
[key] "synapse.xml" and loads the configuration contained therein. Now
the synapse.xml actually loaded by the above contains:
<definitions xmlns="http://ws.apache.org/ns/synapse";>
<log level="custom">
<property name="message" value="This is a dynamic ESB configuration"/>
</log>
<send/>
</definitions>
which is *not* a dynamic configuration - itself. Hence once the
instance/s starts up, each message will simply print the log message
"This is a dynamic ESB configuration" even through you edit the file
later. What you could now try is to introduce dynamism into this
configuration as well. e.g. Use the configuration from sample # 9
<!-- introduction dynamic sequences -->
<definitions xmlns="http://ws.apache.org/ns/synapse";>
<registry provider="org.apache.synapse.registry.url.SimpleURLRegistry">
<parameter
name="root">file:./repository/conf/sample/resources/</parameter>
<parameter name="cachableDuration">15000</parameter>
</registry>
<sequence key="sequence/dynamic_seq_1.xml"/>
</definitions>
Now you've got a dynamic configuration that has fully been loaded off
the registry. If you edit the sequence specified in dynamic_seq_1.xml,
you will notice the changes taking effect after cache expiry.
This is one of the more advanced examples you will find in Synapse, and
you need to understand the registry and dynamic reloading of
configuration and resources. However, it is also one of the unique
abilities of Synapse - which I have not seen offered by any other ESB.
let me know if you need any further help in this regard
asankha
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
