Building a sample to show the problem has been harder than I thought. Because on all bare-bones applications that I tried to build, the URLs end up being different (the counter on the interface seems to be working). What could make my larger application not increment the ?wicket:interface=:<counter>: count? That seems to be the source of my problem. On my application, it's always at 0.
I'm using wicket 1.3.3 (which is the same version as the one I'm testing it with) and, besides a much deeper component tree, the only meaningful thing that is different on my application is that I initialize the SpringComponentInjector (which I don't think should be the issue, but it's good to mention). Thanks, Michel On Thu, Aug 14, 2008 at 10:26 PM, Michel Goldstein < [EMAIL PROTECTED]> wrote: > As I mentioned, I basically used what was in the twiki about JFreeChart > integration. I'll build a simple example of the problem and send it out > sometime tomorrow (USA Pacific time). > > Thanks, > Michel > > > On Thu, Aug 14, 2008 at 7:59 PM, Timo Rantalaiho <[EMAIL PROTECTED]>wrote: > >> On Thu, 14 Aug 2008, Michel Goldstein wrote: >> > Spoke too soon... Unfortunately the problem still seems to be there even >> > after I've added the NonCachingImage. This furthers the confirmation >> that >> > it's not browser caching issue, but a resource "sharing" problem. >> >> From where does the image data come from, and when? >> >> You could show some code, preferably in an easily >> executable quickstart, and maybe someone could help you. >> >> Best wishes, >> Timo >> >> -- >> Timo Rantalaiho >> Reaktor Innovations Oy <URL: http://www.ri.fi/ > >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> >
