Perfect. Thank you! Tom.
> On Jan 27, 2016, at 9:24 AM, Dmitriy Kopylenko <[email protected]> wrote: > > Once the services are loaded into memory from the existing resource (file, > URI), the responsibility for “watching” this resource lies in the separate > component (a Spring managed bean bound to a periodic scheduled task). If > during its "watch loop” iteration the resource becomes unavailable, the > exception is caught and simply logged. The rest of the system is un-affected. ... -- You received this message because you are subscribed to the Google Groups "CAS Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. Visit this group at https://groups.google.com/a/apereo.org/group/cas-user/.
