I think I've discovered why this is; Google has a number of cached
references to components that I have deprecated from my app; so say
Google is storing a reference to $ DirectLink$9, but that is no longer
there, then the page is throwing an exception. I suppose there is not
much I can do about this.
I seem to recall a post where somebody had a way of flushing the
client-side cache? Or was I making that up?
Dan
Daniel M Garland wrote:
Hi all,
Sometimes in my logs for my live tapestry app I see exceptions like
[EMAIL PROTECTED] does not contain a component
$DirectLink$8sp=S7.
which is weird, since the template quite clearly contains this component
and I see $DirectLink$8sp=S7 when I hover the mouse over the link in my
browser. But sometimes I get
[EMAIL PROTECTED] does not contain a component .
Which isn't really helpful at all. It seems to happen on a variety of
components, not just these two examples. And I can't reproduce the
behaviour myself its only in my logs.
Any ideas what could cause this erratic behaviour?
--
Dan Garland
------------------------
[EMAIL PROTECTED]
mob: +44 (0) 7979 770053
icq: 120963437
aim: dmgarland1767
______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
