Re: IE6 Stops Loading Images
Martin, I think we found a culprit. There are some http 504 errors appearing eventually in the transparent proxy that we set up. I think at this point it is a networking issue. Many thanks for responding. Sincerely, Dawid On Thu, Dec 29, 2011 at 9:33 AM, Dawid Dudzinski wrote: > Wicket 1.4.15 > Images are img tags returned through Wicket's AjaxRequestTarget > object. The app returns new markup that is supposed to get rendered in > browser. > > So far all indications are that the html is generated properly - we > used a transparent proxy between browser and server to inspect > requests and responses. > > We also uncovered an issue with failed HTTP 302 redirects. It is a > possibility that this is causing the problem. > > In the meantime are you aware of any relevant issues that had been > addressed in subsequent Wicket releases? > > Thanks, > Dawid > > > > On Thu, Dec 29, 2011 at 12:23 AM, Martin Grigorov > wrote: >> Which version of Wicket ? >> What kind of request loads the image - Ajax or normal ? >> >> On Thu, Dec 29, 2011 at 4:47 AM, Dawid Dudzinski wrote: >>> Hello, >>> >>> I have an issue that may not be related to Wicket but I'm trying every >>> possible angle to solve my issue quickly and any suggestion would be >>> greatly appreciated. >>> >>> I have an application that for the most part loads only one screen and >>> then swaps out data via Wicket calls. It runs about 10-12 hours a day >>> non-stop and from time to time my users run into a situation where >>> images just stop loading in IE6. The only fix at that point is to >>> clear browser cache and things come back to normal. It may be worth to >>> mention that part of the functionality is an image browser. >>> >>> Image implementation extends the NonCachingImage class but 99% of the >>> time user will works with unique images. >>> >>> Like I wrote above, the application just stops loading images and >>> users have to clear the browser cache to get the app running again. >>> >>> I can't test it with newer browsers - not even newer IE and it only >>> happens after an extended usage. >>> >>> Has anyone run into the same or similar issue? If anyone had to >>> venture a guess it it could be related to Wicket in any way? >>> >>> Thanks in advance, >>> Dawid >>> >>> - >>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >>> For additional commands, e-mail: users-h...@wicket.apache.org >>> >> >> >> >> -- >> Martin Grigorov >> jWeekend >> Training, Consulting, Development >> http://jWeekend.com >> >> - >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> For additional commands, e-mail: users-h...@wicket.apache.org >> - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: IE6 Stops Loading Images
Wicket 1.4.15 Images are img tags returned through Wicket's AjaxRequestTarget object. The app returns new markup that is supposed to get rendered in browser. So far all indications are that the html is generated properly - we used a transparent proxy between browser and server to inspect requests and responses. We also uncovered an issue with failed HTTP 302 redirects. It is a possibility that this is causing the problem. In the meantime are you aware of any relevant issues that had been addressed in subsequent Wicket releases? Thanks, Dawid On Thu, Dec 29, 2011 at 12:23 AM, Martin Grigorov wrote: > Which version of Wicket ? > What kind of request loads the image - Ajax or normal ? > > On Thu, Dec 29, 2011 at 4:47 AM, Dawid Dudzinski wrote: >> Hello, >> >> I have an issue that may not be related to Wicket but I'm trying every >> possible angle to solve my issue quickly and any suggestion would be >> greatly appreciated. >> >> I have an application that for the most part loads only one screen and >> then swaps out data via Wicket calls. It runs about 10-12 hours a day >> non-stop and from time to time my users run into a situation where >> images just stop loading in IE6. The only fix at that point is to >> clear browser cache and things come back to normal. It may be worth to >> mention that part of the functionality is an image browser. >> >> Image implementation extends the NonCachingImage class but 99% of the >> time user will works with unique images. >> >> Like I wrote above, the application just stops loading images and >> users have to clear the browser cache to get the app running again. >> >> I can't test it with newer browsers - not even newer IE and it only >> happens after an extended usage. >> >> Has anyone run into the same or similar issue? If anyone had to >> venture a guess it it could be related to Wicket in any way? >> >> Thanks in advance, >> Dawid >> >> - >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> For additional commands, e-mail: users-h...@wicket.apache.org >> > > > > -- > Martin Grigorov > jWeekend > Training, Consulting, Development > http://jWeekend.com > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
IE6 Stops Loading Images
Hello, I have an issue that may not be related to Wicket but I'm trying every possible angle to solve my issue quickly and any suggestion would be greatly appreciated. I have an application that for the most part loads only one screen and then swaps out data via Wicket calls. It runs about 10-12 hours a day non-stop and from time to time my users run into a situation where images just stop loading in IE6. The only fix at that point is to clear browser cache and things come back to normal. It may be worth to mention that part of the functionality is an image browser. Image implementation extends the NonCachingImage class but 99% of the time user will works with unique images. Like I wrote above, the application just stops loading images and users have to clear the browser cache to get the app running again. I can't test it with newer browsers - not even newer IE and it only happens after an extended usage. Has anyone run into the same or similar issue? If anyone had to venture a guess it it could be related to Wicket in any way? Thanks in advance, Dawid - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Wicket.Ajax.all.processEvaluation
It's fixed now. Someone has checked into version control html with wicket:header section. That section sent to browser incompatible javascript that caused wicket to fail. Thanks, Dave On Wed, Oct 5, 2011 at 4:23 PM, Dawid Dudzinski wrote: > Hello, > > I need a help understanding an error I'm receiving. > > We have a screen divided into 2 pieces. Left side acts almost independently > from the right. Everything works until a call is made and entire right side > swapped out for another content (A call to .replace(Component) is made). > Expected behavior is that left side of the screen will function properly. > > Unfortunately there is an error shown in subject line. Clicking on > components on the left works properly on the server side but Ajax responses > are not processing properly on the browser side. > > What could be the issue? > > Thanks, > Dave >
Wicket.Ajax.all.processEvaluation
Hello, I need a help understanding an error I'm receiving. We have a screen divided into 2 pieces. Left side acts almost independently from the right. Everything works until a call is made and entire right side swapped out for another content (A call to .replace(Component) is made). Expected behavior is that left side of the screen will function properly. Unfortunately there is an error shown in subject line. Clicking on components on the left works properly on the server side but Ajax responses are not processing properly on the browser side. What could be the issue? Thanks, Dave
Tracking Memory Usage
Hello, We are running into memory usage problems in our Wicket application. The team has identified several areas worth of improving. However we were only able to do that by looking at our code and not by profiling the jvm. This brings me to my actual questions: 1. Is there tool or method to determine Wicket's memory usage/session size? 2. Can anyone suggest a tool or a method to profile a jvm? (We use WebSphere AS and RAD IDE - problem is that WAS simply crashes when attempting to run in memory profiling mode) I'm open to all suggestions - if anyone could give some hints I would truly appreciate your help. Thanks, Dave
Dropdowns show through ModalWindow in IE6
Hello, We have an odd problem where one ModalWindow shows dropdowns that are technically below it. (One can actually click on them and modify the values) We knew it was an error in IE6 and JQuery (bgiframe.js is supposed to fix it) but for the most part it never appeared in Wicket. Out of many ModalWindow instances we use only one has this issue. Has anyone experienced this issue? How can we fix it? Was there a post about it on the forum? I searched the archive but could not find one. Thanks, Dave PS. We are working very hard to get get off IE6 but it will take time and the bug needs to be fixed now :-(
Re: PopUp not refreshed while everything else is
FYI. I resorted to passing a raw JQuery to the front end and now it works.
I append JS to target similar to this: "$("#imgtagname").attr("src",
"/path"); Of course imgtagname is dynamically constructed
[getMarkupId()]
However if anyone has solution to my problem or even suggestion I
would welcome any leads.
Thanks,
Dawid
On Mon, Aug 8, 2011 at 11:02 AM, Dawid Dudzinski wrote:
> Hello,
>
> I'm having a strange problem: In a fairly complex application I
> refresh image on main page and need to pop up a dialog
> [org.odlabs.wiquery.ui.dialog.Dialog] with another image.
>
> Main page image updates without issues, dialog opens
> [dialog.open(target);] but the image reference is broken. This is
> really strange because when I reviewed Wicket Ajax Debug i can see the
> proper image reference passed to the front end. There are no errors in
> the debug window.
>
> Could anyone shed some light why I would have such problems?
>
> To add more to this mystery I have Next and Previous button on the
> same pop up and when I click on them I can navigate to the image I'm
> trying to open automatically.
>
> Thanks,
> Dawid
>
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
PopUp not refreshed while everything else is
Hello, I'm having a strange problem: In a fairly complex application I refresh image on main page and need to pop up a dialog [org.odlabs.wiquery.ui.dialog.Dialog] with another image. Main page image updates without issues, dialog opens [dialog.open(target);] but the image reference is broken. This is really strange because when I reviewed Wicket Ajax Debug i can see the proper image reference passed to the front end. There are no errors in the debug window. Could anyone shed some light why I would have such problems? To add more to this mystery I have Next and Previous button on the same pop up and when I click on them I can navigate to the image I'm trying to open automatically. Thanks, Dawid - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
