Yes I'm extending Image. I'll try NonCachingImage, though it didn't seem
like client-side caching was the problem. You never know with those
pesky browsers.


Igor Vaynberg wrote:
> use NonCachingImage instead of Image
> -Igor
> On 7/21/06, *Eelco Hillenius* <[EMAIL PROTECTED]
> <mailto:[EMAIL PROTECTED]>> wrote:
>     Do you use an Image component?
>     Eelco
>     On 7/21/06, Nathan Hamblen < [EMAIL PROTECTED]
>     <mailto:[EMAIL PROTECTED]>> wrote:
>     > Has anyone tried ajax-updating an Image whose resource is a
>     > DynamicImageResource? I'm finding that, even though the resource
>     > contents have changed, the same URL is generated to access it and the
>     > original image is returned if I request that URL.
>     >
>     > Nathan

Take Surveys. Earn Cash. Influence the Future of IT
Join's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
Wicket-user mailing list

Reply via email to