[ http://issues.apache.org/jira/browse/TOBAGO-115?page=comments#action_12428844 ] John Allan commented on TOBAGO-115: -----------------------------------
Ok here is the result of all your requested tests... 1) Here is the output on STDERR with AJAX enabled with ReloadTab - this is the only condition where any error is thrown in STDERR Aug 17, 2006 5:47:27 PM org.apache.myfaces.tobago.ajax.api.AjaxPhaseListener beforePhase SEVERE: Ignoring AjaxRequest without valid component tree! 2) Assuming the tests were being run before without an ajax entry in tabago-config, here is the result with ajax disabled (not in config) ReloadTab = broken behavior as per original submission ReloadPage = broken behavior as per original submission 3) Ajax enabled & ReloadTab "Server Error: unable to serve request. Probably a session timeout!" error displayed on webpage. 4) Ajax enabled & ReloadPage broken behavior as per original submission Again all configs work in firefox. > myFaces/Tobago does not work in Internet Explorer on Windows 2000 & 2003 > ------------------------------------------------------------------------ > > Key: TOBAGO-115 > URL: http://issues.apache.org/jira/browse/TOBAGO-115 > Project: MyFaces Tobago > Issue Type: Bug > Affects Versions: 1.0.8 > Environment: Internet Explorer 6 on Windows 2000 Pro, 2000 Server, > 2003 Server > Reporter: John Allan > > The application functions fine within Firefox on Windows XP, Windows 2000 > PRO, Windows 2000 Server, Windows 2003 Server. > The application functions almost correctly exhibits behavior on first click > only within Internet Explorer on Windows XP SP2 > The Application: > Consists of a login screen which verifies against a database and then goes to > a main.jsp page which is composed of 3 tag files. > The main.jsp page has a tabgroup. > Bug: > Login works great, even on problem platforms. > However, once in main.jsp. Clicking on tabs does nothing nor does clicking on > any action buttons. It just refreshes. > I know it sounds like caching behavior, but we have verified cache headers > are outputing correctly and there are no server side caches between the > client and Tomcat running our app. > This has been escalated to Microsoft IE team, as well as their Windows 2000 > team, which has been monitoring the app html communication at length. They > claim the app is simply re-sending the same page and this explains the > behavior. They have verified also that a cache is not involved. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
