Mailing-List: contact users-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@cocoon.apache.org
Received-SPF: pass (hermes.apache.org: local policy)
Message-ID: <41ABFD7F.9080905@soociety.com>
Date: Tue, 30 Nov 2004 12:56:31 +0800
From: pguillard <pguillard@soociety.com>
User-Agent: Mozilla Thunderbird 0.8 (X11/20040913)
MIME-Version: 1.0
To: users cocoon <users@cocoon.apache.org>
Subject: Invalidate cachingURI coplet cache 
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hi all,

Question1:
I know it's possible to invalidate the cachingURI coplet cache 
"manually" from within flow, xsp or action but don't know how, here is 
where i am in flow:
function reset_cache() {
        var cidmanager = 
Packages.org.apache.cocoon.portal.profile.impl.CopletInstanceDataManager();
        var mycoplet = new 
Packages.org.apache.cocoon.portal.coplet.adapter.impl.CachingURICopletAdapter();
        var cid = cidmanager.getCopletInstanceData("test-1")
        mycoplet.setCacheInvalid(cid);        
}   
Question2: Is this strategy correct ?
- I plan to use this to invalidate cachingURI coplet cache after a form 
has been submitted, then the user going back to this portal-tab will see 
the coplet refreshed with the form again
- Some users may update things that will change the content of other 
coplets (not concerning their profile and without having to login 
again), i assume i should also invalidate the cache for that coplets / 
that users in order to view these coplets updated.

Regards,
Phil

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org