> I would have assumed that the default services > manager call the reload after a service is added, updated, or deleted.
I don't think that will fix the problem. The node that made the change is self-consistent. It's the _other_ CAS nodes that have stale data and need to call reload(). > I will file a JIRA issue for this as this is something that should be > addressed in some form or fashion. Thanks for taking the initiative to file a Jira issue for this; it clearly needs to be addressed. I can't think of any straightforward solution other than a Quartz job that calls reload() on the ServicesManager bean periodically. That way the other nodes will eventually refresh and get updated. Ideally there'd be some sort of message-driven notification to other nodes, but that seems a lot more complex. M -- 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
