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.
Any ideas would be greatly appreciated. Thanks, Michel On Thu, Aug 14, 2008 at 1:18 PM, Michel Goldstein < [EMAIL PROTECTED]> wrote: > I read a different thread that is going on right now about preventing image > caching by using a NonCachingImage instead Image and seeing that it adds a > random reference to the image, I thought it might help on my problem too. > And, as far as I can tell, it actually did solve my problem too. > > Should the wiki be changed to use NonCachingImage or is it supposed to work > with Image? I feel like it should, but I probably don't know the internals > Wicket enough to make this call. Maybe my code was still missing something > else. > > Thanks, > Michel > > > On Thu, Aug 14, 2008 at 12:01 PM, Michel Goldstein < > [EMAIL PROTECTED]> wrote: > >> Q: are all the urls really exactly the same? >> >> Yes, they are exactly the same >> >> Q: is your pagesettings.automaticmultiwindowsupport enabled? >> >> Interesting. I didn't know of such setting. But I did change it in the >> application, adding: >> >> getPageSettings().setAutomaticMultiWindowSupport(true); >> >> but I'm still seeing the same behavior and the same URLs. >> >> Michel >> >> >> On Thu, Aug 14, 2008 at 11:15 AM, Igor Vaynberg <[EMAIL PROTECTED]>wrote: >> >>> are all the urls really exactly the same? >>> >>> is your pagesettings.automaticmultiwindowsupport enabled? >>> >>> -igor >>> >>> On Thu, Aug 14, 2008 at 10:30 AM, Michel Goldstein >>> <[EMAIL PROTECTED]> wrote: >>> > Hi, >>> > >>> > I have an application that generates different reports based on what >>> the >>> > user selects. The report generation page is the same, but the reports >>> vary. >>> > Part of the reports contain a DynamicImageResource (JFreeChart chart). >>> > Everything works great when a user is looking at a report at a time. >>> But >>> > when multiple browser windows are open at the same time for the same >>> user, >>> > each containing a different report, diagrams seem to get shared between >>> > reports, or sometimes are missing from some of them (broken resource). >>> > >>> > Looking at the generated URL, it looks like the problem must be with >>> > something more fundamental in the way I'm structuring my page, because >>> the >>> > image URL seems to be fixed to the component tree: >>> > >>> > <img >>> src="../../../../?wicket:interface=:0:label_content:summaryPanelContainer:0:summaryPanel:processedHistory::IResourceListener::" >>> > wicket:id="processedHistory"/> >>> > >>> > >>> > Which will always be the same between reports, so it's expected that >>> they >>> > will show the same image (if I understand the rest of the architecture >>> > correctly). Is there something I'm missing here? To create the image, I >>> > followed what is in the wiki: >>> > >>> > http://cwiki.apache.org/WICKET/jfreechart-and-wicket-example.html >>> > >>> > Is there something missing there? Do I have to wrap my images on some >>> > container that will ensure that its path will be unique for each >>> report? Or >>> > actually, is there a way to do that? >>> > >>> > As a more general Wicket architecture question, are resources >>> > session-specific, or are concurrent users also potentially sharing the >>> > resource too? I wasn't able to verify this correctly on my side because >>> > synchronizing different is harder than just ctrl-clicking on multiple >>> report >>> > links on a same browser. >>> > >>> > Thanks and I apologize if this was already discussed before. I wasn't >>> able >>> > to find any references to it. >>> > >>> > Michel >>> > >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [EMAIL PROTECTED] >>> For additional commands, e-mail: [EMAIL PROTECTED] >>> >>> >> >
