[JBoss JIRA] (RF-13592) a4j:push doesn't work after rendering
by Igor Bolshakov (JIRA)
[ https://issues.jboss.org/browse/RF-13592?page=com.atlassian.jira.plugin.s... ]
Igor Bolshakov edited comment on RF-13592 at 4/4/14 5:42 AM:
-------------------------------------------------------------
Please, use test application maven project. We don't use portlets anymore. This is only old context parameter we forgot to clean up. Anyway we built sample application and we deployed it under Tomcat Version 8.0.5 and Tomcat Version 7.0.52. Bug is reproduced on both J2EE containers. To test just build WAR and deploy it. Open in browser url http://localhost:8080/sample/pages/push.xhtml. Below is result of "mvn -v" command on my local machine:
{quote}Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19 14:51:28+0100)
Maven home: B:\tools\maven
Java version: 1.7.0_45, vendor: Oracle Corporation
Java home: B:\tools\jdk\jre
Default locale: de_DE, platform encoding: UTF-8
OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"{quote}
was (Author: igor_ab):
Test application project
> a4j:push doesn't work after rendering
> -------------------------------------
>
> Key: RF-13592
> URL: https://issues.jboss.org/browse/RF-13592
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-push/poll
> Affects Versions: 4.3.5
> Environment: JBoss EAP 6.2
> Browser: Chrome 33.0.1750.154 and IE 8.0.7601.17514
> JSF 2.19, Richfaces 4.3.5
> Reporter: Igor Bolshakov
> Assignee: Pavol Pitonak
> Priority: Critical
> Labels: waiting_on_user
> Attachments: a4j.log, localhost.har, push-test.zip, push-test.zip, screenshot.png, web.xml
>
>
> I use {{rendered}} attribute to start/stop a4j:push component in example below. After rendering of a4j:push element the handling of incoming push messages is broken. In my simple example I set alert to notify about recieved message (see attached screenshot).
> View xhtml code:
> {code:xml}<?xml version="1.0" encoding="ISO-8859-1"?>
> <ui:composition xmlns="http://www.w3.org/1999/xhtml"
> xmlns:a4j="http://richfaces.org/a4j"
> xmlns:h="http://java.sun.com/jsf/html"
> xmlns:ui="http://java.sun.com/jsf/facelets">
> <h:form>
> <a4j:outputPanel id="push-panel">
> <a4j:push address="TEST_ADDRESS" ondataavailable="alert('event.rf.data=' + event.rf.data)"
> rendered="#{testBean.enabled}"/>
> </a4j:outputPanel>
> <a4j:commandButton id="startBtn" value="Start Push" action="#{testBean.startPush}" render="push-panel"/>
> <a4j:commandButton id="stopBtn" value="Stop Push" action="#{testBean.stopPush}" render="push-panel"/>
> <a4j:commandButton id="sendMessage" value="Send Message" action="#{testBean.sendMessage}"/>
> </h:form>
> </ui:composition>{code}
> Backing bean class:
> {code}public class TestBean {
> private boolean enabled = false;
> public boolean isEnabled() {
> return enabled;
> }
> public void startPush() {
> enabled = true;
> }
> public void stopPush() {
> enabled = false;
> }
> public void sendMessage() throws MessageException {
> TopicsContext.lookup().publish(new TopicKey("TEST_ADDRESS"), "Hello World");
> }
> }{code}
> Configuration in web.xml (see attachment).
> Scenario:
> 1) Open page
> 2) Click "Start Push" button
> 3) Click "Send Message" button
> 4) Alert "event.rf.data=Hello World" is shown (see attached screenshot)
> 5) Click "Stop Push" button
> 6) Polling is closed (see localhost.har in attachment)
> 7) Click "Start Push" button
> 8) Polling is started (see localhost.har in attachment)
> 9) Click "Send Message" button
> 10) Message is recieved (see localhost.har in attachment)
> 11) No alert, no javascript error
> For more details I saved a4j:log output in a4j.log file.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 3 months
[JBoss JIRA] (RF-13592) a4j:push doesn't work after rendering
by Igor Bolshakov (JIRA)
[ https://issues.jboss.org/browse/RF-13592?page=com.atlassian.jira.plugin.s... ]
Igor Bolshakov updated RF-13592:
--------------------------------
Attachment: push-test.zip
Test application project
> a4j:push doesn't work after rendering
> -------------------------------------
>
> Key: RF-13592
> URL: https://issues.jboss.org/browse/RF-13592
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-push/poll
> Affects Versions: 4.3.5
> Environment: JBoss EAP 6.2
> Browser: Chrome 33.0.1750.154 and IE 8.0.7601.17514
> JSF 2.19, Richfaces 4.3.5
> Reporter: Igor Bolshakov
> Assignee: Pavol Pitonak
> Priority: Critical
> Labels: waiting_on_user
> Attachments: a4j.log, localhost.har, push-test.zip, push-test.zip, screenshot.png, web.xml
>
>
> I use {{rendered}} attribute to start/stop a4j:push component in example below. After rendering of a4j:push element the handling of incoming push messages is broken. In my simple example I set alert to notify about recieved message (see attached screenshot).
> View xhtml code:
> {code:xml}<?xml version="1.0" encoding="ISO-8859-1"?>
> <ui:composition xmlns="http://www.w3.org/1999/xhtml"
> xmlns:a4j="http://richfaces.org/a4j"
> xmlns:h="http://java.sun.com/jsf/html"
> xmlns:ui="http://java.sun.com/jsf/facelets">
> <h:form>
> <a4j:outputPanel id="push-panel">
> <a4j:push address="TEST_ADDRESS" ondataavailable="alert('event.rf.data=' + event.rf.data)"
> rendered="#{testBean.enabled}"/>
> </a4j:outputPanel>
> <a4j:commandButton id="startBtn" value="Start Push" action="#{testBean.startPush}" render="push-panel"/>
> <a4j:commandButton id="stopBtn" value="Stop Push" action="#{testBean.stopPush}" render="push-panel"/>
> <a4j:commandButton id="sendMessage" value="Send Message" action="#{testBean.sendMessage}"/>
> </h:form>
> </ui:composition>{code}
> Backing bean class:
> {code}public class TestBean {
> private boolean enabled = false;
> public boolean isEnabled() {
> return enabled;
> }
> public void startPush() {
> enabled = true;
> }
> public void stopPush() {
> enabled = false;
> }
> public void sendMessage() throws MessageException {
> TopicsContext.lookup().publish(new TopicKey("TEST_ADDRESS"), "Hello World");
> }
> }{code}
> Configuration in web.xml (see attachment).
> Scenario:
> 1) Open page
> 2) Click "Start Push" button
> 3) Click "Send Message" button
> 4) Alert "event.rf.data=Hello World" is shown (see attached screenshot)
> 5) Click "Stop Push" button
> 6) Polling is closed (see localhost.har in attachment)
> 7) Click "Start Push" button
> 8) Polling is started (see localhost.har in attachment)
> 9) Click "Send Message" button
> 10) Message is recieved (see localhost.har in attachment)
> 11) No alert, no javascript error
> For more details I saved a4j:log output in a4j.log file.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 3 months
[JBoss JIRA] (RF-13592) a4j:push doesn't work after rendering
by Igor Bolshakov (JIRA)
[ https://issues.jboss.org/browse/RF-13592?page=com.atlassian.jira.plugin.s... ]
Igor Bolshakov updated RF-13592:
--------------------------------
Attachment: push-test.zip
Sample application project
> a4j:push doesn't work after rendering
> -------------------------------------
>
> Key: RF-13592
> URL: https://issues.jboss.org/browse/RF-13592
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-push/poll
> Affects Versions: 4.3.5
> Environment: JBoss EAP 6.2
> Browser: Chrome 33.0.1750.154 and IE 8.0.7601.17514
> JSF 2.19, Richfaces 4.3.5
> Reporter: Igor Bolshakov
> Assignee: Pavol Pitonak
> Priority: Critical
> Labels: waiting_on_user
> Attachments: a4j.log, localhost.har, push-test.zip, screenshot.png, web.xml
>
>
> I use {{rendered}} attribute to start/stop a4j:push component in example below. After rendering of a4j:push element the handling of incoming push messages is broken. In my simple example I set alert to notify about recieved message (see attached screenshot).
> View xhtml code:
> {code:xml}<?xml version="1.0" encoding="ISO-8859-1"?>
> <ui:composition xmlns="http://www.w3.org/1999/xhtml"
> xmlns:a4j="http://richfaces.org/a4j"
> xmlns:h="http://java.sun.com/jsf/html"
> xmlns:ui="http://java.sun.com/jsf/facelets">
> <h:form>
> <a4j:outputPanel id="push-panel">
> <a4j:push address="TEST_ADDRESS" ondataavailable="alert('event.rf.data=' + event.rf.data)"
> rendered="#{testBean.enabled}"/>
> </a4j:outputPanel>
> <a4j:commandButton id="startBtn" value="Start Push" action="#{testBean.startPush}" render="push-panel"/>
> <a4j:commandButton id="stopBtn" value="Stop Push" action="#{testBean.stopPush}" render="push-panel"/>
> <a4j:commandButton id="sendMessage" value="Send Message" action="#{testBean.sendMessage}"/>
> </h:form>
> </ui:composition>{code}
> Backing bean class:
> {code}public class TestBean {
> private boolean enabled = false;
> public boolean isEnabled() {
> return enabled;
> }
> public void startPush() {
> enabled = true;
> }
> public void stopPush() {
> enabled = false;
> }
> public void sendMessage() throws MessageException {
> TopicsContext.lookup().publish(new TopicKey("TEST_ADDRESS"), "Hello World");
> }
> }{code}
> Configuration in web.xml (see attachment).
> Scenario:
> 1) Open page
> 2) Click "Start Push" button
> 3) Click "Send Message" button
> 4) Alert "event.rf.data=Hello World" is shown (see attached screenshot)
> 5) Click "Stop Push" button
> 6) Polling is closed (see localhost.har in attachment)
> 7) Click "Start Push" button
> 8) Polling is started (see localhost.har in attachment)
> 9) Click "Send Message" button
> 10) Message is recieved (see localhost.har in attachment)
> 11) No alert, no javascript error
> For more details I saved a4j:log output in a4j.log file.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 3 months
[JBoss JIRA] (RF-11427) rich:tab - actionListener
by Pavol Pitonak (JIRA)
[ https://issues.jboss.org/browse/RF-11427?page=com.atlassian.jira.plugin.s... ]
Pavol Pitonak reassigned RF-11427:
----------------------------------
Assignee: Brian Leathem
Thanks [~Trims], it works fine now.
[~bleathem], the is a checkstyle violation on line 580 and it needs to be rebased to lastest master. IMHO we can handle these minor issues, WDYT?
> rich:tab - actionListener
> -------------------------
>
> Key: RF-11427
> URL: https://issues.jboss.org/browse/RF-11427
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-panels-layout-themes
> Affects Versions: 4.0.0.Final, 4.1.0.Milestone2, 4.2.3.CR1
> Environment: RichFaces 4.1.0-SNAPSHOT r.5debbf8981de1839984bdaa38b31f58ed028239d
> Metamer 4.1.0-SNAPSHOT r.22728
> Mojarra 2.1.2-FCS
> Apache Tomcat 7.0.16
> OpenJDK Runtime Environment 1.6.0_22-b22 @ Linux
> Mozilla/5.0 (X11; Linux x86_64; rv:6.0) Gecko/20100101 Firefox/6.0
> RichFaces 4.2.1-SNAPSHOT
> Metamer 4.2.1-SNAPSHOT
> Mojarra 2.1.7-jbossorg-1
> JBoss AS 7.1.1.Final
> Java(TM) SE Runtime Environment 1.6.0_26-b03 @ Linux
> Chrome 18.0.1025.168 @ Linux i686
> Reporter: Jan Papousek
> Assignee: Brian Leathem
> Labels: ci_issue
> Fix For: 5-Tracking
>
>
> It seems that the actionListener attribute doesn't work.
> # deploy Metamer and open http://localhost:8080/metamer/faces/components/richTab/simple.xhtml
> # open tab2
> # open tab1 (action and action listener are invoked)
> # open tab2
> # open tab1 (action and action listener are *NOT* invoked)
> # open tab1 (action and action listener are invoked)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 3 months
[JBoss JIRA] (RF-11427) rich:tab - actionListener
by Valiantsin Shukaila (JIRA)
[ https://issues.jboss.org/browse/RF-11427?page=com.atlassian.jira.plugin.s... ]
Valiantsin Shukaila commented on RF-11427:
------------------------------------------
Just updated the commit. Now action and actionListener is invoked on necessary phase and immediate works fine. Please check.
> rich:tab - actionListener
> -------------------------
>
> Key: RF-11427
> URL: https://issues.jboss.org/browse/RF-11427
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-panels-layout-themes
> Affects Versions: 4.0.0.Final, 4.1.0.Milestone2, 4.2.3.CR1
> Environment: RichFaces 4.1.0-SNAPSHOT r.5debbf8981de1839984bdaa38b31f58ed028239d
> Metamer 4.1.0-SNAPSHOT r.22728
> Mojarra 2.1.2-FCS
> Apache Tomcat 7.0.16
> OpenJDK Runtime Environment 1.6.0_22-b22 @ Linux
> Mozilla/5.0 (X11; Linux x86_64; rv:6.0) Gecko/20100101 Firefox/6.0
> RichFaces 4.2.1-SNAPSHOT
> Metamer 4.2.1-SNAPSHOT
> Mojarra 2.1.7-jbossorg-1
> JBoss AS 7.1.1.Final
> Java(TM) SE Runtime Environment 1.6.0_26-b03 @ Linux
> Chrome 18.0.1025.168 @ Linux i686
> Reporter: Jan Papousek
> Labels: ci_issue
> Fix For: 5-Tracking
>
>
> It seems that the actionListener attribute doesn't work.
> # deploy Metamer and open http://localhost:8080/metamer/faces/components/richTab/simple.xhtml
> # open tab2
> # open tab1 (action and action listener are invoked)
> # open tab2
> # open tab1 (action and action listener are *NOT* invoked)
> # open tab1 (action and action listener are invoked)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 3 months
[JBoss JIRA] (RF-11427) rich:tab - actionListener
by Pavol Pitonak (JIRA)
[ https://issues.jboss.org/browse/RF-11427?page=com.atlassian.jira.plugin.s... ]
Pavol Pitonak commented on RF-11427:
------------------------------------
Hi, all tests for switchable components pass now but action/action listener is not working correctly. Both action and action listener are invoked in fourth phase (update model values) and fifth phase (invoke application) is skipped.
[~bleathem], since we are adding action and action listener to the r:tab, shouldn't we add them also to r:accordionItem and r:togglePanelItem? Are they expected to work in the same way as those in r:panelMenuItem?
> rich:tab - actionListener
> -------------------------
>
> Key: RF-11427
> URL: https://issues.jboss.org/browse/RF-11427
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-panels-layout-themes
> Affects Versions: 4.0.0.Final, 4.1.0.Milestone2, 4.2.3.CR1
> Environment: RichFaces 4.1.0-SNAPSHOT r.5debbf8981de1839984bdaa38b31f58ed028239d
> Metamer 4.1.0-SNAPSHOT r.22728
> Mojarra 2.1.2-FCS
> Apache Tomcat 7.0.16
> OpenJDK Runtime Environment 1.6.0_22-b22 @ Linux
> Mozilla/5.0 (X11; Linux x86_64; rv:6.0) Gecko/20100101 Firefox/6.0
> RichFaces 4.2.1-SNAPSHOT
> Metamer 4.2.1-SNAPSHOT
> Mojarra 2.1.7-jbossorg-1
> JBoss AS 7.1.1.Final
> Java(TM) SE Runtime Environment 1.6.0_26-b03 @ Linux
> Chrome 18.0.1025.168 @ Linux i686
> Reporter: Jan Papousek
> Labels: ci_issue
> Fix For: 5-Tracking
>
>
> It seems that the actionListener attribute doesn't work.
> # deploy Metamer and open http://localhost:8080/metamer/faces/components/richTab/simple.xhtml
> # open tab2
> # open tab1 (action and action listener are invoked)
> # open tab2
> # open tab1 (action and action listener are *NOT* invoked)
> # open tab1 (action and action listener are invoked)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 3 months
[JBoss JIRA] (RF-13595) rich:validator doesn't work when loaded via ajax (re-render)
by Pavol Pitonak (JIRA)
[ https://issues.jboss.org/browse/RF-13595?page=com.atlassian.jira.plugin.s... ]
Pavol Pitonak reassigned RF-13595:
----------------------------------
Assignee: Matej Novotny (was: Pavol Pitonak)
> rich:validator doesn't work when loaded via ajax (re-render)
> ------------------------------------------------------------
>
> Key: RF-13595
> URL: https://issues.jboss.org/browse/RF-13595
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-validators
> Affects Versions: 4.3.5
> Environment: RF 4.3.5
> Mojarra 2.1.27
> Java 7 Update 51 x64
> Tomcat 7.0.52
> Firefox 28.0 + Firebug
> Reporter: Michael B
> Assignee: Matej Novotny
> Attachments: validationTest.zip
>
>
> When loading input components with a rich:validator via ajax (re-render), client side validation bridge breaks due to a missing JS function av_xxxxxxxxx.
> As already described in further detail in a comment to this JIRA here:
> https://issues.jboss.org/browse/RF-12031
> I've created a very basic example project to reproduce the problem for a single input field which becomes visible (re-rendered) when you click on an a4j:commandButton.
> Please note that this is a minimum example only. The problem is also reproducable for other input components besides h:inputText - like for example rich:calendar.
> The workaround described in the referenced JIRA creates other problems in client JS when combined with other components like rich:focus and is also not applicable for other input components besides h:inputText.
> We think the problem is located in the way JS functions are optimized for being re-used as well as in the way they are (not) being added on the client side when a component becomes visible on ajax response re-rendering.
> Please use attached eclipse project to easily reproduce the problem => open Firefox => Firebug console to see the error about the missing JS function av_xxxxxxx ...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 3 months
[JBoss JIRA] (RF-11427) rich:tab - actionListener
by Valiantsin Shukaila (JIRA)
[ https://issues.jboss.org/browse/RF-11427?page=com.atlassian.jira.plugin.s... ]
Valiantsin Shukaila commented on RF-11427:
------------------------------------------
So pull request was updated to fix immediate attribute functionality. Please verify.
> rich:tab - actionListener
> -------------------------
>
> Key: RF-11427
> URL: https://issues.jboss.org/browse/RF-11427
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-panels-layout-themes
> Affects Versions: 4.0.0.Final, 4.1.0.Milestone2, 4.2.3.CR1
> Environment: RichFaces 4.1.0-SNAPSHOT r.5debbf8981de1839984bdaa38b31f58ed028239d
> Metamer 4.1.0-SNAPSHOT r.22728
> Mojarra 2.1.2-FCS
> Apache Tomcat 7.0.16
> OpenJDK Runtime Environment 1.6.0_22-b22 @ Linux
> Mozilla/5.0 (X11; Linux x86_64; rv:6.0) Gecko/20100101 Firefox/6.0
> RichFaces 4.2.1-SNAPSHOT
> Metamer 4.2.1-SNAPSHOT
> Mojarra 2.1.7-jbossorg-1
> JBoss AS 7.1.1.Final
> Java(TM) SE Runtime Environment 1.6.0_26-b03 @ Linux
> Chrome 18.0.1025.168 @ Linux i686
> Reporter: Jan Papousek
> Labels: ci_issue
> Fix For: 5-Tracking
>
>
> It seems that the actionListener attribute doesn't work.
> # deploy Metamer and open http://localhost:8080/metamer/faces/components/richTab/simple.xhtml
> # open tab2
> # open tab1 (action and action listener are invoked)
> # open tab2
> # open tab1 (action and action listener are *NOT* invoked)
> # open tab1 (action and action listener are invoked)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 3 months
[JBoss JIRA] (RF-13514) Support file upload progress tracking in Servlets >= 3.0 environment
by Juraj Húska (JIRA)
[ https://issues.jboss.org/browse/RF-13514?page=com.atlassian.jira.plugin.s... ]
Juraj Húska commented on RF-13514:
----------------------------------
# {{maxFilesQuantity}} - for me it is the other way round, attribute works correctly when adding files with D&D, it does not work when adding files manually. The add button does not disappear nor there is any other restriction to upload more files.
# {{keydown}} - IMHO it should be fired when a user has focus on {{fileUpload}} component and press key (without further releasing). Other key related handlers do not work as well ({{onkeyup}}, {{onkeypress}})
> Support file upload progress tracking in Servlets >= 3.0 environment
> --------------------------------------------------------------------
>
> Key: RF-13514
> URL: https://issues.jboss.org/browse/RF-13514
> Project: RichFaces
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: component-input, core
> Affects Versions: 5.0.0.Alpha3
> Reporter: Lukáš Fryč
> Assignee: Michal Petrov
> Fix For: 4.5.0.Alpha3
>
>
> We currently support two approaches for file upload:
> * Servlets 2.5: own request form data parser [{{MultipartRequestParser}}|https://github.com/richfaces/richfaces/blob/master/framework/src/main/java/org/richfaces/request/MultipartRequestParser.java]
> * Servlets 3.0: leveraging {{HttpServletRequest#getParts()}}
> However as we have discussed RF-13444, we had to finally do a trade-off of limiting support of file progress tracking. I.e. in Servlets 3.0 we have no simple way how to track file upload progress since getParts() returns data for completed request.
> There are several possible outcomes:
> 1) drop server-side file upload progress tracking and leverage XHR2/HTML5 that has built-in ability to track progress
> * imho we are already prepared to switch to XHR2 and client-side progress (possibly leveraging some third-party widget) since [all major browsers support it at least one version back|http://caniuse.com/#feat=xhr2]
> * existing implementation: http://www.script-tutorials.com/pure-html5-file-upload/
> 2) use a {{ServletFilter}} to wrap a request as our {{FileUploadFacesContextFactory}} currently do and so have an earlier access to the request object
> * this principle has a drawback - we have to ensure our filter has high-enough priority so the servlet container won't touch the request body yet
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 3 months