It happens automatically; on the first access of a ASO property on a page, the ASO is retrieved from its storage (session or application). Subsequent accesses are cached by the page (in an instance variable). The instance variable is cleared at the end of the request cycle.
If you are merely changing the properties of the ASO, this works perfectly; thread A will change a property and it is immediatly visible to threads B - Z, regardless of whether they have accessed the ASO property yet or not. If you invoke a setter and change the ASO, there is a window where some threads and pages will have a temporary reference to the old ASO instance (until the end of their respective requests). On 10/24/05, seloha . <[EMAIL PROTECTED]> wrote: > I have an Application Service Object configured in hivemind which has a > scope of application. > > Rarely this object is modified and needs to be re-read. How do I invalidate > the ASO and re-read it to make the change available to all users. > > Thanks inadvance, > > Paul > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Howard M. Lewis Ship Independent J2EE / Open-Source Java Consultant Creator, Jakarta Tapestry Creator, Jakarta HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
