[jira] Commented: (TOBAGO-910) tc:upload hangs when entering invalid filename in IE 6
[ https://issues.apache.org/jira/browse/TOBAGO-910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12908662#action_12908662 ] Dennis Hauser commented on TOBAGO-910: -- It's not stupid, it's creativity :-) tc:upload hangs when entering invalid filename in IE 6 -- Key: TOBAGO-910 URL: https://issues.apache.org/jira/browse/TOBAGO-910 Project: MyFaces Tobago Issue Type: Bug Affects Versions: 1.0.28 Environment: Internet Explorer 6 Reporter: Dennis Hauser Assignee: Arvid Hülsebus Priority: Minor Fix For: 1.0.29 How to reproduce: - Enter 'aaa' into the textfield of a tc:upload - Submit the page. -- The browser will display the gray transition pane with the progress indicator forever. It hangs. Probably the execption File 'aaa' is not found is not processed sufficiently in the components Javascript code. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (TOBAGO-910) tc:upload hangs when entering invalid filename in IE 6
[ https://issues.apache.org/jira/browse/TOBAGO-910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12908662#action_12908662 ] Dennis Hauser edited comment on TOBAGO-910 at 9/13/10 4:05 AM: --- It's not stupid, it's creative :-) was (Author: hausden): It's not stupid, it's creativity :-) tc:upload hangs when entering invalid filename in IE 6 -- Key: TOBAGO-910 URL: https://issues.apache.org/jira/browse/TOBAGO-910 Project: MyFaces Tobago Issue Type: Bug Affects Versions: 1.0.28 Environment: Internet Explorer 6 Reporter: Dennis Hauser Assignee: Arvid Hülsebus Priority: Minor Fix For: 1.0.29 How to reproduce: - Enter 'aaa' into the textfield of a tc:upload - Submit the page. -- The browser will display the gray transition pane with the progress indicator forever. It hangs. Probably the execption File 'aaa' is not found is not processed sufficiently in the components Javascript code. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (TOBAGO-910) tc:upload hangs when entering invalid filename in IE 6
[ https://issues.apache.org/jira/browse/TOBAGO-910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12908670#action_12908670 ] Dennis Hauser commented on TOBAGO-910: -- :-) If I had a say in the matter, I'd remove IE6 just as fast as I would remove speed limits and income taxes ... tc:upload hangs when entering invalid filename in IE 6 -- Key: TOBAGO-910 URL: https://issues.apache.org/jira/browse/TOBAGO-910 Project: MyFaces Tobago Issue Type: Bug Affects Versions: 1.0.28 Environment: Internet Explorer 6 Reporter: Dennis Hauser Assignee: Arvid Hülsebus Priority: Minor Fix For: 1.0.29 How to reproduce: - Enter 'aaa' into the textfield of a tc:upload - Submit the page. -- The browser will display the gray transition pane with the progress indicator forever. It hangs. Probably the execption File 'aaa' is not found is not processed sufficiently in the components Javascript code. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TOBAGO-910) tc:upload hangs when entering invalid filename in IE 6
tc:upload hangs when entering invalid filename in IE 6 -- Key: TOBAGO-910 URL: https://issues.apache.org/jira/browse/TOBAGO-910 Project: MyFaces Tobago Issue Type: Bug Affects Versions: 1.0.28 Environment: Internet Explorer 6 Reporter: Dennis Hauser Priority: Minor How to reproduce: - Enter 'aaa' into the textfield of a tc:upload - Submit the page. -- The browser will display the gray transition pane with the progress indicator forever. It hangs. Probably the execption File 'aaa' is not found is not processed sufficiently in the components Javascript code. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (TOBAGO-627) JNDI-Problem on Websphere Application Server
[ https://issues.apache.org/jira/browse/TOBAGO-627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12585470#action_12585470 ] Dennis Hauser commented on TOBAGO-627: -- Hi Bernd, we have applied your Tobago - Patches and successfully tested them on Websphere 6.1.0.13 Thanks! JNDI-Problem on Websphere Application Server Key: TOBAGO-627 URL: https://issues.apache.org/jira/browse/TOBAGO-627 Project: MyFaces Tobago Issue Type: Bug Components: Core Affects Versions: 1.0.15 Environment: Websphere Application Server (at least version 6.1) Reporter: Matthias Wronka Assignee: Bernd Bohmann Fix For: 1.0.16, 1.1.0 In our Logs on WAS we find several outputs like [2/21/08 17:12:16:569 CET] 0022 javaURLContex E NMSV0310E: A JNDI operation on a java: name cannot be completed because the server runtime is not able to associate the operation's thread with any J2EE application component. This condition can occur when the JNDI client using the java: name is not executed on the thread of a server application request. Make sure that a J2EE application does not execute JNDI operations on java: names within static code blocks or in threads created by that J2EE application. Such code does not necessarily run on the thread of a server application request and therefore is not supported by JNDI operations on java: names. Exception stack trace: javax.naming.ConfigurationException [Root exception is javax.naming.NameNotFoundException: Name tobago.ajax.contentType not found in context java:comp/env.] at com.ibm.ws.naming.java.javaURLContextImpl.throwConfigurationExceptionWithDefaultJavaNS(javaURLContextImpl.java:411) at com.ibm.ws.naming.java.javaURLContextImpl.lookup(javaURLContextImpl.java:388) at com.ibm.ws.naming.urlbase.UrlContextImpl.lookup(UrlContextImpl.java:1307) at com.ibm.ws.naming.java.javaURLContextImpl.lookup(javaURLContextImpl.java:353) at org.apache.myfaces.tobago.ajax.api.AjaxResponseRenderer.init(AjaxResponseRenderer.java:74) at org.apache.myfaces.tobago.lifecycle.RenderResponseExecutor.init(RenderResponseExecutor.java:41) at org.apache.myfaces.tobago.lifecycle.TobagoLifecycle.init(TobagoLifecycle.java:65) at org.apache.myfaces.tobago.lifecycle.TobagoLifecycleFactory.init(TobagoLifecycleFactory.java:36) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:67) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:522) at javax.faces.FactoryFinder.getImplGivenPreviousImpl(FactoryFinder.java:547) at javax.faces.FactoryFinder.getImplementationInstance(FactoryFinder.java:432) at javax.faces.FactoryFinder.getFactory(FactoryFinder.java:232) und [2/21/08 17:12:16:665 CET] 0022 javaURLContex E NMSV0310E: A JNDI operation on a java: name cannot be completed because the server runtime is not able to associate the operation's thread with any J2EE application component. This condition can occur when the JNDI client using the java: name is not executed on the thread of a server application request. Make sure that a J2EE application does not execute JNDI operations on java: names within static code blocks or in threads created by that J2EE application. Such code does not necessarily run on the thread of a server application request and therefore is not supported by JNDI operations on java: names. Exception stack trace: javax.naming.ConfigurationException [Root exception is javax.naming.NameNotFoundException: Name uploadRepositoryPath not found in context java:comp/env.] at com.ibm.ws.naming.java.javaURLContextImpl.throwConfigurationExceptionWithDefaultJavaNS(javaURLContextImpl.java:411) at com.ibm.ws.naming.java.javaURLContextImpl.lookup(javaURLContextImpl.java:388) at com.ibm.ws.naming.urlbase.UrlContextImpl.lookup(UrlContextImpl.java:1307) at com.ibm.ws.naming.java.javaURLContextImpl.lookup(javaURLContextImpl.java:353) at org.apache.myfaces.tobago.fileupload.FileUploadFacesContextFactoryImpl.init(FileUploadFacesContextFactoryImpl.java:79) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:67) sowie [2/21/08 17:12:16:695 CET] 0022 javaURLContex E NMSV0310E: A JNDI operation on a java: name cannot be completed because the server runtime is not able to associate the operation's thread with
[jira] Created: (TOBAGO-367) cell spanY attribute results in rendering error
cell spanY attribute results in rendering error --- Key: TOBAGO-367 URL: https://issues.apache.org/jira/browse/TOBAGO-367 Project: MyFaces Tobago Issue Type: Bug Affects Versions: 1.0.10 Reporter: Dennis Hauser Priority: Minor When using spanY attribute of tc:cell to span a cell over several rows, the followig tags are spanned over several rows as well. The example renders a group of radio buttons on the left sie, spanning 2 rows. To its right there should be 2 tc:in, but the first tc:in is spanning over 2 rows as well. tc:box label=Trading Start Time f:facet name=layout tc:gridLayout rows=fixed;fixed;* columns=fixed;fixed;* / %--radiobuttons left, 2-3 ins right --% /f:facet tc:cell spanY=2 tc:selectOneRadio value=#{tradingScheduleController.startTimeType} f:selectItems value=#{tradingScheduleController.timeTypeItems} / /tc:selectOneRadio /tc:cell tc:cell tc:in label=Days before delivery value=1 / /tc:cell tc:cell / tc:cell tc:in label=Time value=15:00 / /tc:cell tc:cell / tc:cell spanX=3 / /tc:box -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TOBAGO-368) tx:in validator attribute is not working
tx:in validator attribute is not working Key: TOBAGO-368 URL: https://issues.apache.org/jira/browse/TOBAGO-368 Project: MyFaces Tobago Issue Type: Improvement Affects Versions: 1.0.10 Reporter: Dennis Hauser tx:in id=eic value=Testlabel=Label validator=CustomValidator/ does not work (CustomValidator.validate is not called on submit) tx:in id=eic value=Testlabel=Label f:validator validatorId=CustomValidator / /tx:in works fine! -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (TOBAGO-368) tx:in validator attribute is not working
[ https://issues.apache.org/jira/browse/TOBAGO-368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491966 ] Dennis Hauser commented on TOBAGO-368: -- My example was more complex than described above, the tx:in although contained native faces validators: tx:in id=eic value=Test label=Label validator=CustomValidator f:validateLength maximum=16/ f:validator validatorId=LengthValidator / f:attribute name=requiredLength value=16 / /tx:in Maybe this validator-combination causes the problem tx:in validator attribute is not working Key: TOBAGO-368 URL: https://issues.apache.org/jira/browse/TOBAGO-368 Project: MyFaces Tobago Issue Type: Improvement Affects Versions: 1.0.10 Reporter: Dennis Hauser tx:in id=eic value=Testlabel=Label validator=CustomValidator/ does not work (CustomValidator.validate is not called on submit) tx:in id=eic value=Testlabel=Label f:validator validatorId=CustomValidator / /tx:in works fine! -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TOBAGO-326) Submit in subform leads to validation of values outside of the subform
Submit in subform leads to validation of values outside of the subform -- Key: TOBAGO-326 URL: https://issues.apache.org/jira/browse/TOBAGO-326 Project: MyFaces Tobago Issue Type: Bug Affects Versions: 1.0.10 Reporter: Dennis Hauser This is an example to reproduce the bug: a tx:selectOneChoice inside a subform submits on every change. All entry fields outside of this subform should be ignored, but instead they are validated as well. tc:tab id=details_contracts label=#{label.adminRefdata_contracts_tabLabel} rendered=#{controller.msAdminUser} f:facet name=layout tc:gridLayout rows=fixed;* columns=710px;* / /f:facet tc:form tc:panel f:facet name=layout tc:gridLayout columns=350px;350px;* rows=fixed;* / /f:facet tc:box label=#{label.adminRefdata_contracts_haltBoxLabel} f:facet name=layout tc:gridLayout columns=fixed;* rows=fixed;* border=0 / /f:facet tc:form -- subform start tx:selectOneChoice value=#{contractHaltController.contractName} label=#{label.adminRefdata_contracts_contract} f:selectItems value=#{contractHaltController.contractItems} / f:facet name=change tc:command action=#{contractHaltController.reloadContract}/ /f:facet /tx:selectOneChoice /tc:form -- subform end tc:cell / tc:selectOneRadio value=#{contractHaltController.contractModType} disabled=#{contractHaltController.contract.inactive || marketHaltController.marketHalt} f:selectItems value=#{contractHaltController.contractModTypeItems} / /tc:selectOneRadio tc:cell / /tc:box tc:box label=#{label.adminRefdata_contracts_boxLabel} f:facet name=layout tc:gridLayout columns=fixed;* rows=fixed;fixed;* border=0 / /f:facet tx:in disabled=#{!contractHaltController.contract.inactive} -- outside of form, but validated as well value=#{contractHaltController.contractTradeFrom} label=#{label.adminRefdata_contracts_startTime} converter=DateConverter / tc:cell / tx:in value=#{contractHaltController.contractTradeUntil} -- outside of form, but validated as well label=#{label.adminRefdata_contracts_endTime} converter=DateConverter / tc:cell / tc:cell spanX=2 / /tc:box tc:cell / tc:cell spanX=3 / /tc:panel tc:cell / tc:panel f:facet name=layout tc:gridLayout columns=*;100px;* rows=fixed;* / /f:facet tc:cell / tc:button label=#{label.adminRefdata_contracts_submitButton} %--tc:attribute name=renderedPartially value=popup-modify-contract /--% popup:confirmationPopup name=popup-modify-contract text=#{label.adminRefdata_contracts_modifyContractPopup_text} onConfirm=contractHaltController.submitContract onCancel=contractHaltController.closeModifyContractPopup / /tc:button
[jira] Created: (TOBAGO-313) Misleading Error Message, if Cookies are deactivated
Misleading Error Message, if Cookies are deactivated Key: TOBAGO-313 URL: https://issues.apache.org/jira/browse/TOBAGO-313 Project: MyFaces Tobago Issue Type: Bug Components: Core Affects Versions: 1.0.9 Reporter: Dennis Hauser Fix For: 1.0.10 If cookies are deactivated in the browser, tobago displays the following error Message: Server Error: Fehler beim Bearbeiten der Anfrage. M�glicherweise ein Session Timeout! I encountered it during ajax reloads of tabs (tabGroup with reloadPage) The error message should at least state something like Please check whether cookies are activated. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (TOBAGO-302) Can't find Overlay after ajax request in IE
[ https://issues.apache.org/jira/browse/TOBAGO-302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476201 ] Dennis Hauser commented on TOBAGO-302: -- I added some logging to tobago.js and tobago-sheet.js that might lead to a better understanding of the difference between firefox and IE. In IE, ajax requests with statis code 304 seem to result in a call of OnFailure. After the first ajax request, IE additionally reports the js-error: 'transport' is undefined. Requests with status code 200 (update of content) seem to work fine in IE as well: Debug-messages of an ajax request in IE: reload sheet with action page:messages Current ActionId = null action= page:messages Execute request! skip update response status 304 Request complete! Queue size : 0 sheet reloaded : skip setup Request completed correctly, timeout: 2 Array.shift(): length 1 ! Request complete! Queue size : 0 The network is down, try to request again --- Debug messages ajax request in Firefox: reload sheet with action page:messages Current ActionId = null action= page:messages Execute request! skip update response status 304 Request complete! Queue size : 0 sheet reloaded : skip setup Request completed correctly, timeout: 2 Changes in .js-files tobago.js: Ajax.Responders.register({ onCreate: function(request) { request['timeoutId'] = window.setTimeout( function() { // If we have hit the timeout and the AJAX request is active, abort it and let the user know if (Tobago.Updater.callInProgress(request.transport)) { request.transport.abort(); Tobago.Transport.requestComplete(); Tobago.Updater.showFailureMessage(); // Run the onFailure method if we set one up when creating the AJAX object if (request.options['onFailure']) { request.options['onFailure'](request.transport, request.json); } } }, Tobago.Updater.UPDATE_TIMEOUT ); }, onComplete: function(request) { LOG.debug('Request completed correctly, timeout: ' + Tobago.Updater.UPDATE_TIMEOUT);-- NEW // Clear the timeout, the request completed ok window.clearTimeout(request['timeoutId']); } }); Tobago.Updater.showFailureMessage = function() { LOG.warn('The network is down, try to request again'); -- NEW //alert('uh oh, it looks like the network is down. Try again shortly'); }; -- tobago-sheet.js: Tobago.Sheet.prototype.onComplete = function(transport) { LOG.debug(sheet reloaded : + transport.responseText.substr(0,20)); -- NEW this.setup(); }; Tobago.Sheet.prototype.onFailure = function() { LOG.debug(sheet not reloaded : + transport.responseText.substr(0,20)); -- NEW Tobago.deleteOverlay(Tobago.element(this.outerDivId)); this.initReload(); }; Can't find Overlay after ajax request in IE --- Key: TOBAGO-302 URL: https://issues.apache.org/jira/browse/TOBAGO-302 Project: MyFaces Tobago Issue Type: Bug Environment: Internet Explorer Reporter: Dennis Hauser Fix For: 1.0.10 After an ajax request without updating any content, the overlay can't be found: FacesContext = [EMAIL PROTECTED] reload sheet with action page:messages -- ajax request (with content update) Current ActionId = null action= page:messages Execute request! update content Request complete! Queue size : 0 reload sheet with action page:messages-- ajax request (update skipped) Current ActionId = null action= page:messages Execute request! skip update response status 304 Request complete! Queue size : 0 skip setup Array.shift(): length 1 ! -- strange error message Request complete! Queue size : 0 -- this line wasn't expected as well, maybe the request is duplicated? Can't find Overlay : page:messages_outer_div-overlay -- strange error message -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TOBAGO-302) Can't find Overlay after ajax request in IE
Can't find Overlay after ajax request in IE --- Key: TOBAGO-302 URL: https://issues.apache.org/jira/browse/TOBAGO-302 Project: MyFaces Tobago Issue Type: Bug Environment: Internet Explorer Reporter: Dennis Hauser Fix For: 1.0.10 After an ajax request without updating any content, the overlay can't be found: FacesContext = [EMAIL PROTECTED] reload sheet with action page:messages-- ajax request (with content update) Current ActionId = null action= page:messages Execute request! update content Request complete! Queue size : 0 reload sheet with action page:messages-- ajax request (update skipped) Current ActionId = null action= page:messages Execute request! skip update response status 304 Request complete! Queue size : 0 skip setup Array.shift(): length 1 ! -- strange error message Request complete! Queue size : 0-- this line wasn't expected as well, maybe the request is duplicated? Can't find Overlay : page:messages_outer_div-overlay -- strange error message -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TOBAGO-303) Ajax reloads stopped when submitting non-JSF request
Ajax reloads stopped when submitting non-JSF request Key: TOBAGO-303 URL: https://issues.apache.org/jira/browse/TOBAGO-303 Project: MyFaces Tobago Issue Type: Bug Reporter: Dennis Hauser Fix For: 1.0.10 After pressing a button with attribute transition=false, ajax reloads quit working: reload sheet with action page:messages -- working ajax request Current ActionId = null action= page:messages Execute request! skip update response status 304 Request complete! Queue size : 0 skip setup reload sheet with action page:messages -- working ajax request Current ActionId = null action= page:messages Execute request! skip update response status 304 Request complete! Queue size : 0 skip setup transition =false Execute request! request removed :function () { if (!this.isSubmit) { this.isSubmit = true; var req = Tobago.Transport.requests.shift(); LOG.debug(request removed : + req.toString()); var oldAction = Tobago.action.value; var oldTarget = Tobago.form.target; Tobago.action.value = actionId; if (target) { Tobago.form.target = target; } Tobago.onSubmit(); Tobago.form.submit(); Tobago.action.value = oldAction; if (target) { Tobago.form.target = oldTarget; } if (target || !transition) { this.isSubmit = false; } Tobago.onBeforeUnload(transition, target); } } -- non JSF submit reload sheet with action page:messages -- stucked ajax request (no log messages follow) the same happens, when you set transition to true but do not provide a faces response, it's not an issue of the transition attribute -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TOBAGO-296) WML client request is not handled correctly, when WML is not supported
WML client request is not handled correctly, when WML is not supported -- Key: TOBAGO-296 URL: https://issues.apache.org/jira/browse/TOBAGO-296 Project: MyFaces Tobago Issue Type: Bug Affects Versions: 1.0.8 Environment: all Reporter: Dennis Hauser Priority: Minor The request of a wml client results in a null pointer exception, because the corresponding renderer does not seem to exist. Exception handling seems to be missing -- stack trace 2007-02-19 14:57:32 WebContainer : 64 ERROR - org.apache.myfaces.tobago.context.ResourceManagerImpl:291 - Path not found, and no fallback. Using empty string. resourceDirs = '[resources, org/apache/myfaces/tobago/renderkit]' contentType = 'wml' theme = 'speyside' browser = 'null' subDir = 'tag' name = 'MenuBarRenderer' suffix = '' key = 'null' 2007-02-19 14:57:32 WebContainer : 64 ERROR - org.apache.myfaces.tobago.context.ResourceManagerImpl:397 - name = 'MenuBarRenderer' clientProperties = 'wml/speyside/null' java.lang.NullPointerException at org.apache.myfaces.tobago.context.ResourceManagerImpl.getRenderer(ResourceManagerImpl.java:392) at org.apache.myfaces.tobago.renderkit.TobagoRenderKit.getRenderer(TobagoRenderKit.java:60) at javax.faces.component.UIComponentBase.getRenderer(UIComponentBase.java:1109) at javax.faces.component.UIComponentBase.getClientId(UIComponentBase.java:272) at javax.faces.webapp.UIComponentTag.doStartTag(UIComponentTag.java:438) at org.apache.myfaces.tobago.taglib.component.TobagoTag.doStartTag(TobagoTag.java:57) at com.ibm._jsp._menubar._jspx_meth_tc_menuBar_0(_menubar.java:381) at com.ibm._jsp._menubar._jspx_meth_f_facet_0(_menubar.java:429) at com.ibm._jsp._menubar._jspService(_menubar.java:75) at com.ibm.ws.jsp.runtime.HttpJspBase.service(HttpJspBase.java:85) at javax.servlet.http.HttpServlet.service(HttpServlet.java:856) at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:966) at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:907) at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:118) at com.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAppFilterChain.java:87) at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:701) at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:646) at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:701) at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:646) at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:475) at com.ibm.ws.wswebcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:463) at com.ibm.wsspi.webcontainer.servlet.GenericServletWrapper.handleRequest(GenericServletWrapper.java:115) at com.ibm.ws.jsp.webcontainerext.AbstractJSPExtensionServletWrapper.handleRequest(AbstractJSPExtensionServletWrapper.java:168) at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.include(WebAppRequestDispatcher.java:606) at org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:1034) at org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:997) at com.ibm._jsp._market._jspx_meth_tc_page_0(_market.java:690) at com.ibm._jsp._market._jspx_meth_f_view_0(_market.java:740) at com.ibm._jsp._market._jspService(_market.java:85) at com.ibm.ws.jsp.runtime.HttpJspBase.service(HttpJspBase.java:85) at javax.servlet.http.HttpServlet.service(HttpServlet.java:856) at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:966) at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:907) at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:118) at com.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAppFilterChain.java:87) at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:701) at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:646) at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:475) at com.ibm.ws.wswebcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:463) at com.ibm.wsspi.webcontainer.servlet.GenericServletWrapper.handleRequest(GenericServletWrapper.java:115) at
[jira] Commented: (TOBAGO-271) Concurrent requests can result in a full freeze
[ https://issues.apache.org/jira/browse/TOBAGO-271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12474499 ] Dennis Hauser commented on TOBAGO-271: -- We've found the original issue causing the problem: URL's in Internet Explorer are limited to 2083 characters (see: http://support.microsoft.com/kb/208427/EN-US/ ) As Tobago is serializing the form for ajax requests into a get request the resulting url can become greater (4000 charcters in our case). I am not sure what IE is doing, simply cutting the request to 2083 chars, not sending anything, etc. However, this has to be handled somehow, either while creating the request on the client or while processing a corrupted request on the server. Concurrent requests can result in a full freeze --- Key: TOBAGO-271 URL: https://issues.apache.org/jira/browse/TOBAGO-271 Project: MyFaces Tobago Issue Type: Bug Affects Versions: 1.0.9 Environment: Internet Explorer (Firefox seems to be ok) Reporter: Dennis Hauser Attachments: screenshot-1.jpg, tobago.js.diff When there is more than one ajax component on a page, the client somtimes freezes. It seems that if there is more than one request in the queue, the system will stop working (no submit possible). The last debug message is Request queued!, which seems to come from the following code in tobago.js: Tobago.Transport = { requests: new Array(), pageSubmited: false, request: function(req, submitPage) { if (submitPage) { this.pageSubmited = true; this.requests.push(req); } else if (!this.pageSubmited) { this.requests.push(req); } else { return; } if (this.requests.length == 1) {--- maybe this is the problem. What about this.requests.length 0 ? LOG.debug(Execute request!); this.requests[0](); } else { LOG.debug(Request queued!); } }, requestComplete: function() { this.requests.shift(); LOG.debug(Request complete! Queue size : + this.requests.length); if (this.requests.length 0) { LOG.debug(Execute request!); this.requests[0](); } } } -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TOBAGO-271) Concurrent requests can result in a full freeze
Concurrent requests can result in a full freeze --- Key: TOBAGO-271 URL: https://issues.apache.org/jira/browse/TOBAGO-271 Project: MyFaces Tobago Issue Type: Bug Affects Versions: 1.0.9 Environment: Internet Explorer (Firefox seems to be ok) Reporter: Dennis Hauser When there is more than one ajax component on a page, the client somtimes freezes. It seems that if there is more than one request in the queue, the system will stop working (no submit possible). The last debug message is Request queued!, which seems to come from the following code in tobago.js: Tobago.Transport = { requests: new Array(), pageSubmited: false, request: function(req, submitPage) { if (submitPage) { this.pageSubmited = true; this.requests.push(req); } else if (!this.pageSubmited) { this.requests.push(req); } else { return; } if (this.requests.length == 1) {--- maybe this is the problem. What about this.requests.length 0 ? LOG.debug(Execute request!); this.requests[0](); } else { LOG.debug(Request queued!); } }, requestComplete: function() { this.requests.shift(); LOG.debug(Request complete! Queue size : + this.requests.length); if (this.requests.length 0) { LOG.debug(Execute request!); this.requests[0](); } } } -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TOBAGO-229) AJAX-reload of scrollable Sheets resets scrollbar to top position
AJAX-reload of scrollable Sheets resets scrollbar to top position - Key: TOBAGO-229 URL: https://issues.apache.org/jira/browse/TOBAGO-229 Project: MyFaces Tobago Issue Type: Bug Reporter: Dennis Hauser A workaround could be to store the scrollbar position before reloading and to set it to the original after the reload is completed ( see attached code fragment exchange-energy-trade_win.js) This does work theoretically, but the marked lines in the second code fragment (tobago-sheet.js) are resetting the sheet completely again. - exchange-energy-trade_win.js function eetReloadOverviewWin() { // neu von hier var dataDiv = Tobago.element(marketPage:overviewSheet_data_div); var scrollTop = dataDiv.scrollTop; var scrollLeft = dataDiv.scrollLeft; // bis hier var options = { insertion: function(receiver, response) { if (response.substring(0, 20) == status code=\304\/) { // no update needed, do nothing receiver.skipUpdate = true; } else if (response.substring(0, 11) == input id=\) { // update content Element.update(receiver, response); // neu von hier var dataDiv2 = Tobago.element(marketPage:overviewSheet_data_div); dataDiv2.scrollTop = scrollTop; dataDiv2.scrollLeft = scrollLeft; // bis hier } else { // unknown response do full page reload LOG.debug(initiating full reload); var mos = Tobago.element(marketPage:overviewSheet); if (mos != null) { Tobago.submitAction(marketPage:overviewSheet); } } if (eetOverviewTimeoutWin) { clearTimeout(eetOverviewTimeoutWin); } eetOverviewTimeoutWin = setTimeout(eetReloadOverviewWin, eetGetConfigWin().overviewSheetReloadTimeout); }, createOverlay: false }; Tobago.reloadComponent(marketPage:overviewSheet, marketPage:overviewSheet, options); } - resources/html/standard/standard/script/tobago-sheet.js Tobago.Sheet.prototype.setup = function() { ... // Problematisches Codefragment, dessen Sinn mir sich nicht erschließt, // dessen Auskommentierung jedoch das Problem löst. :-) // von hier // ToDo: find a better way to fix this problem // IE needs this in case of ajax loading of style classes var outerDiv = Tobago.element(this.outerDivId); outerDiv.className = outerDiv.className; outerDiv.innerHTML = outerDiv.innerHTML; // bis hier ... } - -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (TOBAGO-222) hard-coded component id in Tobago.Updater
hard-coded component id in Tobago.Updater - Key: TOBAGO-222 URL: http://issues.apache.org/jira/browse/TOBAGO-222 Project: MyFaces Tobago Issue Type: Bug Affects Versions: 1.0.8, 1.0.9 Reporter: Dennis Hauser The ajax reload functionality included in Tobago.Updater uses a hard-coded component-id for full page reloads in case it receives an unexpected awnser from the server. See last to else-parts in attached code : Tobago.submitAction(page:overviewSheet); Tobago.Updater = { CODE_SUCCESS: status code=\200\/, CODE_NOT_MODIFIED: status code=\304\/, CODE_RELOAD_REQUIRED: status code=\309\/, UPDATE_TIMEOUT: 5000, // Five seconds options: { method: 'post', asynchronous: true, parameters: '', evalScripts: true, createOverlay: true, onComplete: function(){}, // empty function insertion: function(receiver, response, transport) { //Tobago.deleteOverlay(receiver); //LOG.debug(response = \ + response.substring(0, 30 response.length ? 30 : response.length) + \); //LOG.debug(this.CODE_NOT_MODIFIED = \ + Tobago.Updater.CODE_NOT_MODIFIED + \ ist lang: + Tobago.Updater.CODE_NOT_MODIFIED.length); if (transport.status == 304) { Tobago.deleteOverlay(receiver); LOG.debug(skip update response status 304); } else if (response.substring(0, Tobago.Updater.CODE_NOT_MODIFIED.length) == Tobago.Updater.CODE_NOT_MODIFIED) { // no update needed, do nothing LOG.debug(skip update); receiver.skipUpdate = true; } else if (response.substring(0, Tobago.Updater.CODE_SUCCESS.length) == Tobago.Updater.CODE_SUCCESS) { // update content LOG.debug(update content); Element.update(receiver, response.substring(20)); } else if (response.substring(0, Tobago.Updater.CODE_RELOAD_REQUIRED.length) == Tobago.Updater.CODE_RELOAD_REQUIRED) { // reload complete page LOG.debug(full reload requested); Tobago.submitAction(page:overviewSheet); } else { // unknown response do full page reload LOG.debug(initiating full reload); Tobago.submitAction(page:overviewSheet); } } }, -- 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