Musers, The current implementation of persistence doesn't retain some of the semantics of the original "startup-count". One use case that isn't well served is the case where a ServiceGroup is desired at startup, but the contents of the service group are always added dynamically. At present, persistence is a function of the router definition, and there's no opt-out (or opt-in, we can debate which is more appropriate) ability at the resource definition level.
What does everyone think of making persistence override-able at the resource definition level? Cheers, Joel The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
