Reload is also very useful on the single node when using file based service registry definition. For example, I use JSON-based service registry definition and when I change the config in that file (externalized from web context) - reload reloads that file def. into in-memory representation and viola - the updated service definition is available without needing to restart the web container.
This is a lightweight and convenient alternative for persisting service definitions to more bulky RDBMS approach. Cheers, Dmitriy. Sent from my iPhone On Mar 1, 2012, at 7:08, Pavlos Drandakis <[email protected]> wrote: > Hello all, > > The comment in applicationContext.xml says that this job is needed for a > clustered CAS environment, so... is it safe/right to remove/disable the > relevant beans from applicationContext.xml in a non clustered CAS environment? > > Thanks, in advance, > Pavlos > > -- > You are currently subscribed to [email protected] as: > [email protected] > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-user -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
