From jira-events at lists.jboss.org Thu Mar 1 03:49:40 2012 From: jira-events at lists.jboss.org (Juraj Huska (JIRA)) Date: Thu, 1 Mar 2012 03:49:40 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12003) Including h:head breaks f:ajax events of commandButton In-Reply-To: <135907437.40978.1330081357692.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1055117762.56320.1330591780521.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12672460#comment-12672460 ] Juraj Huska commented on RF-12003: ---------------------------------- I was able to reproduce it. The code with this example can be found [here|https://github.com/jhuska/richfaces-sanbox/tree/RF-12003]. The behavior is the same as described above. When the h:head tag is removed than the expected behavior works. However, the look and feel of command button changes to plain HTML(please see the screenshot). > Including h:head breaks f:ajax events of commandButton > ------------------------------------------------------ > > Key: RF-12003 > URL: https://issues.jboss.org/browse/RF-12003 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: base functionality > Affects Versions: 4.1.0.Final, 4.2.0.CR1 > Environment: JBoss 7.0.2 Final, JBoss 7.1.0 Final, RichFaces 4.2.0 Final, 4.1.0 Final, Chrome and Safari > Reporter: Joern Ohmen > Assignee: Juraj Huska > Priority: Critical > Labels: Header, JSF2.0, RichFaces4 > Attachments: brokenRFHheadAdded.png > > > If I add h:head-Tag to my page, the ajax events of the h:commandButton are not working. The example should show up a panel with a click on a button, but nothing happens. The example is working when h:head is removed. I use a ConversationScoped Bean. > {code} > > > xmlns:h="http://java.sun.com/jsf/html" > xmlns:f="http://java.sun.com/jsf/core" > xmlns:ui="http://java.sun.com/jsf/facelets" > xmlns:fn="http://java.sun.com/jsp/jstl/functions" > xmlns:a4j="http://richfaces.org/a4j" > xmlns:rich="http://richfaces.org/rich"> > > Test > > > listener="#{testController.beginConversation}" /> > > > > > action="#{testController.changeRenderInputPanel}"> > > > rendered="#{testController.renderInputPanel}"> > > > > > > > > {code} > {code} > import java.io.Serializable; > import javax.enterprise.context.Conversation; > import javax.enterprise.context.ConversationScoped; > import javax.inject.Inject; > import javax.inject.Named; > import org.apache.commons.logging.Log; > @Named > @ConversationScoped > public class TestController implements Serializable{ > private static final long serialVersionUID = 1L; > > @Inject > private Conversation conversation; > > private String newCommentAuthor; > > private boolean renderInputPanel = true; > > @Inject > private Log logger; > > public boolean isRenderInputPanel() { > return renderInputPanel; > } > public void setRenderInputPanel(boolean renderInputPanel) { > this.renderInputPanel = renderInputPanel; > } > > public void changeRenderInputPanel() { > this.setRenderInputPanel(!isRenderInputPanel()); > logger.info("render panel: " + renderInputPanel); > } > public String getNewCommentAuthor() { > return newCommentAuthor; > } > public void setNewCommentAuthor(String newCommentAuthor) { > this.newCommentAuthor = newCommentAuthor; > } > public void beginConversation() { > if (conversation.isTransient()) { > conversation.setTimeout(120000); > conversation.begin(); > } > } > public void endConversation() { > if (!conversation.isTransient()) { > conversation.end(); > return; > } > } > } > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 1 03:49:41 2012 From: jira-events at lists.jboss.org (Juraj Huska (JIRA)) Date: Thu, 1 Mar 2012 03:49:41 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12003) Including h:head breaks f:ajax events of commandButton In-Reply-To: <135907437.40978.1330081357692.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <284472895.56324.1330591781236.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj Huska updated RF-12003: ----------------------------- Attachment: brokenRFHheadAdded.png > Including h:head breaks f:ajax events of commandButton > ------------------------------------------------------ > > Key: RF-12003 > URL: https://issues.jboss.org/browse/RF-12003 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: base functionality > Affects Versions: 4.1.0.Final, 4.2.0.CR1 > Environment: JBoss 7.0.2 Final, JBoss 7.1.0 Final, RichFaces 4.2.0 Final, 4.1.0 Final, Chrome and Safari > Reporter: Joern Ohmen > Assignee: Juraj Huska > Priority: Critical > Labels: Header, JSF2.0, RichFaces4 > Attachments: brokenRFHheadAdded.png > > > If I add h:head-Tag to my page, the ajax events of the h:commandButton are not working. The example should show up a panel with a click on a button, but nothing happens. The example is working when h:head is removed. I use a ConversationScoped Bean. > {code} > > > xmlns:h="http://java.sun.com/jsf/html" > xmlns:f="http://java.sun.com/jsf/core" > xmlns:ui="http://java.sun.com/jsf/facelets" > xmlns:fn="http://java.sun.com/jsp/jstl/functions" > xmlns:a4j="http://richfaces.org/a4j" > xmlns:rich="http://richfaces.org/rich"> > > Test > > > listener="#{testController.beginConversation}" /> > > > > > action="#{testController.changeRenderInputPanel}"> > > > rendered="#{testController.renderInputPanel}"> > > > > > > > > {code} > {code} > import java.io.Serializable; > import javax.enterprise.context.Conversation; > import javax.enterprise.context.ConversationScoped; > import javax.inject.Inject; > import javax.inject.Named; > import org.apache.commons.logging.Log; > @Named > @ConversationScoped > public class TestController implements Serializable{ > private static final long serialVersionUID = 1L; > > @Inject > private Conversation conversation; > > private String newCommentAuthor; > > private boolean renderInputPanel = true; > > @Inject > private Log logger; > > public boolean isRenderInputPanel() { > return renderInputPanel; > } > public void setRenderInputPanel(boolean renderInputPanel) { > this.renderInputPanel = renderInputPanel; > } > > public void changeRenderInputPanel() { > this.setRenderInputPanel(!isRenderInputPanel()); > logger.info("render panel: " + renderInputPanel); > } > public String getNewCommentAuthor() { > return newCommentAuthor; > } > public void setNewCommentAuthor(String newCommentAuthor) { > this.newCommentAuthor = newCommentAuthor; > } > public void beginConversation() { > if (conversation.isTransient()) { > conversation.setTimeout(120000); > conversation.begin(); > } > } > public void endConversation() { > if (!conversation.isTransient()) { > conversation.end(); > return; > } > } > } > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 1 03:55:37 2012 From: jira-events at lists.jboss.org (Juraj Huska (JIRA)) Date: Thu, 1 Mar 2012 03:55:37 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12003) Including h:head breaks f:ajax events of commandButton In-Reply-To: <135907437.40978.1330081357692.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <659965063.56339.1330592137335.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12672463#comment-12672463 ] Juraj Huska commented on RF-12003: ---------------------------------- I have removed richfaces dependencies (as there is not RichFaces component used in the example), and the behavior is the same. So IMHO it is not caused by RichFaces but JSF mojarra. I can file an issue there, if you agree ? > Including h:head breaks f:ajax events of commandButton > ------------------------------------------------------ > > Key: RF-12003 > URL: https://issues.jboss.org/browse/RF-12003 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: base functionality > Affects Versions: 4.1.0.Final, 4.2.0.CR1 > Environment: JBoss 7.0.2 Final, JBoss 7.1.0 Final, RichFaces 4.2.0 Final, 4.1.0 Final, Chrome and Safari > Reporter: Joern Ohmen > Assignee: Juraj Huska > Priority: Critical > Labels: Header, JSF2.0, RichFaces4 > Attachments: brokenRFHheadAdded.png > > > If I add h:head-Tag to my page, the ajax events of the h:commandButton are not working. The example should show up a panel with a click on a button, but nothing happens. The example is working when h:head is removed. I use a ConversationScoped Bean. > {code} > > > xmlns:h="http://java.sun.com/jsf/html" > xmlns:f="http://java.sun.com/jsf/core" > xmlns:ui="http://java.sun.com/jsf/facelets" > xmlns:fn="http://java.sun.com/jsp/jstl/functions" > xmlns:a4j="http://richfaces.org/a4j" > xmlns:rich="http://richfaces.org/rich"> > > Test > > > listener="#{testController.beginConversation}" /> > > > > > action="#{testController.changeRenderInputPanel}"> > > > rendered="#{testController.renderInputPanel}"> > > > > > > > > {code} > {code} > import java.io.Serializable; > import javax.enterprise.context.Conversation; > import javax.enterprise.context.ConversationScoped; > import javax.inject.Inject; > import javax.inject.Named; > import org.apache.commons.logging.Log; > @Named > @ConversationScoped > public class TestController implements Serializable{ > private static final long serialVersionUID = 1L; > > @Inject > private Conversation conversation; > > private String newCommentAuthor; > > private boolean renderInputPanel = true; > > @Inject > private Log logger; > > public boolean isRenderInputPanel() { > return renderInputPanel; > } > public void setRenderInputPanel(boolean renderInputPanel) { > this.renderInputPanel = renderInputPanel; > } > > public void changeRenderInputPanel() { > this.setRenderInputPanel(!isRenderInputPanel()); > logger.info("render panel: " + renderInputPanel); > } > public String getNewCommentAuthor() { > return newCommentAuthor; > } > public void setNewCommentAuthor(String newCommentAuthor) { > this.newCommentAuthor = newCommentAuthor; > } > public void beginConversation() { > if (conversation.isTransient()) { > conversation.setTimeout(120000); > conversation.begin(); > } > } > public void endConversation() { > if (!conversation.isTransient()) { > conversation.end(); > return; > } > } > } > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 1 05:03:38 2012 From: jira-events at lists.jboss.org (Balaji Thangamani (JIRA)) Date: Thu, 1 Mar 2012 05:03:38 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11988) rich:fileUpload doesn't seem to work on GlassFish In-Reply-To: <1031298844.7144.1329428856250.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <69763603.56646.1330596218803.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12672506#comment-12672506 ] Balaji Thangamani commented on RF-11988: ---------------------------------------- This issue has nothinf to do with glassfish. The issue is the MyFaces version. rich:fileUpload works smoothly with Mojarra RI(atleast with the latest version). I checked with version MyFaces 2.0.2 it did not work. But when upgraded to Latest MyFaces release (2.0.12) it worked. I tested this in Tomcat and Glassfish and rich:upload works smoothly. > rich:fileUpload doesn't seem to work on GlassFish > ------------------------------------------------- > > Key: RF-11988 > URL: https://issues.jboss.org/browse/RF-11988 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.2.0.CR1 > Environment: Mac OS X, Firefox 10, Chrome 17, GlassFish 3.1.2, GlassFish 4.0 > Reporter: Jason Lee > Fix For: 4.3-Tracking > > Attachments: rfupload.log, rfupload.tar.gz > > > While it renders fine, POSTs initiated from rich:fileUpload error out. I have tested this using both Firefox 10+ and Chrome 17+ against GlassFish 3.1.2 and GlassFish 4.0. I will attach both the log file and a sample application that should demonstrate the issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 1 05:05:37 2012 From: jira-events at lists.jboss.org (Balaji Thangamani (JIRA)) Date: Thu, 1 Mar 2012 05:05:37 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11988) rich:fileUpload doesn't seem to work on GlassFish In-Reply-To: <1031298844.7144.1329428856250.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1473385016.56655.1330596337233.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12672506#comment-12672506 ] Balaji Thangamani edited comment on RF-11988 at 3/1/12 5:05 AM: ---------------------------------------------------------------- This issue has nothinf to do with glassfish. The issue is the MyFaces version. rich:fileUpload works smoothly with Mojarra RI(atleast with the latest version). I checked with version MyFaces 2.0.2 it did not work. But when upgraded to Latest MyFaces release (2.0.12) it worked. I tested this in Tomcat and Glassfish and rich:upload works smoothly with MyFaces 2.0.12 atleast. I have not tried with JSF 2.1 implementations. was (Author: balaji.thangamani): This issue has nothinf to do with glassfish. The issue is the MyFaces version. rich:fileUpload works smoothly with Mojarra RI(atleast with the latest version). I checked with version MyFaces 2.0.2 it did not work. But when upgraded to Latest MyFaces release (2.0.12) it worked. I tested this in Tomcat and Glassfish and rich:upload works smoothly. > rich:fileUpload doesn't seem to work on GlassFish > ------------------------------------------------- > > Key: RF-11988 > URL: https://issues.jboss.org/browse/RF-11988 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.2.0.CR1 > Environment: Mac OS X, Firefox 10, Chrome 17, GlassFish 3.1.2, GlassFish 4.0 > Reporter: Jason Lee > Fix For: 4.3-Tracking > > Attachments: rfupload.log, rfupload.tar.gz > > > While it renders fine, POSTs initiated from rich:fileUpload error out. I have tested this using both Firefox 10+ and Chrome 17+ against GlassFish 3.1.2 and GlassFish 4.0. I will attach both the log file and a sample application that should demonstrate the issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 1 05:10:50 2012 From: jira-events at lists.jboss.org (Juraj Huska (JIRA)) Date: Thu, 1 Mar 2012 05:10:50 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12003) Including h:head breaks f:ajax events of commandButton In-Reply-To: <135907437.40978.1330081357692.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <239801596.56696.1330596650757.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12672463#comment-12672463 ] Juraj Huska edited comment on RF-12003 at 3/1/12 5:09 AM: ---------------------------------------------------------- I have removed richfaces dependencies (as there is not any RichFaces component used in the example), and the behavior is the same. So IMHO it is not caused by RichFaces but JSF mojarra instead. I can file an issue there, if you agree ? was (Author: jhuska): I have removed richfaces dependencies (as there is not RichFaces component used in the example), and the behavior is the same. So IMHO it is not caused by RichFaces but JSF mojarra. I can file an issue there, if you agree ? > Including h:head breaks f:ajax events of commandButton > ------------------------------------------------------ > > Key: RF-12003 > URL: https://issues.jboss.org/browse/RF-12003 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: base functionality > Affects Versions: 4.1.0.Final, 4.2.0.CR1 > Environment: JBoss 7.0.2 Final, JBoss 7.1.0 Final, RichFaces 4.2.0 Final, 4.1.0 Final, Chrome and Safari > Reporter: Joern Ohmen > Assignee: Juraj Huska > Priority: Critical > Labels: Header, JSF2.0, RichFaces4 > Attachments: brokenRFHheadAdded.png > > > If I add h:head-Tag to my page, the ajax events of the h:commandButton are not working. The example should show up a panel with a click on a button, but nothing happens. The example is working when h:head is removed. I use a ConversationScoped Bean. > {code} > > > xmlns:h="http://java.sun.com/jsf/html" > xmlns:f="http://java.sun.com/jsf/core" > xmlns:ui="http://java.sun.com/jsf/facelets" > xmlns:fn="http://java.sun.com/jsp/jstl/functions" > xmlns:a4j="http://richfaces.org/a4j" > xmlns:rich="http://richfaces.org/rich"> > > Test > > > listener="#{testController.beginConversation}" /> > > > > > action="#{testController.changeRenderInputPanel}"> > > > rendered="#{testController.renderInputPanel}"> > > > > > > > > {code} > {code} > import java.io.Serializable; > import javax.enterprise.context.Conversation; > import javax.enterprise.context.ConversationScoped; > import javax.inject.Inject; > import javax.inject.Named; > import org.apache.commons.logging.Log; > @Named > @ConversationScoped > public class TestController implements Serializable{ > private static final long serialVersionUID = 1L; > > @Inject > private Conversation conversation; > > private String newCommentAuthor; > > private boolean renderInputPanel = true; > > @Inject > private Log logger; > > public boolean isRenderInputPanel() { > return renderInputPanel; > } > public void setRenderInputPanel(boolean renderInputPanel) { > this.renderInputPanel = renderInputPanel; > } > > public void changeRenderInputPanel() { > this.setRenderInputPanel(!isRenderInputPanel()); > logger.info("render panel: " + renderInputPanel); > } > public String getNewCommentAuthor() { > return newCommentAuthor; > } > public void setNewCommentAuthor(String newCommentAuthor) { > this.newCommentAuthor = newCommentAuthor; > } > public void beginConversation() { > if (conversation.isTransient()) { > conversation.setTimeout(120000); > conversation.begin(); > } > } > public void endConversation() { > if (!conversation.isTransient()) { > conversation.end(); > return; > } > } > } > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 1 05:10:51 2012 From: jira-events at lists.jboss.org (Juraj Huska (JIRA)) Date: Thu, 1 Mar 2012 05:10:51 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12003) Including h:head breaks f:ajax events of commandButton In-Reply-To: <135907437.40978.1330081357692.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1677632868.56700.1330596651584.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj Huska reassigned RF-12003: -------------------------------- Assignee: (was: Juraj Huska) > Including h:head breaks f:ajax events of commandButton > ------------------------------------------------------ > > Key: RF-12003 > URL: https://issues.jboss.org/browse/RF-12003 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: base functionality > Affects Versions: 4.1.0.Final, 4.2.0.CR1 > Environment: JBoss 7.0.2 Final, JBoss 7.1.0 Final, RichFaces 4.2.0 Final, 4.1.0 Final, Chrome and Safari > Reporter: Joern Ohmen > Priority: Critical > Labels: Header, JSF2.0, RichFaces4 > Attachments: brokenRFHheadAdded.png > > > If I add h:head-Tag to my page, the ajax events of the h:commandButton are not working. The example should show up a panel with a click on a button, but nothing happens. The example is working when h:head is removed. I use a ConversationScoped Bean. > {code} > > > xmlns:h="http://java.sun.com/jsf/html" > xmlns:f="http://java.sun.com/jsf/core" > xmlns:ui="http://java.sun.com/jsf/facelets" > xmlns:fn="http://java.sun.com/jsp/jstl/functions" > xmlns:a4j="http://richfaces.org/a4j" > xmlns:rich="http://richfaces.org/rich"> > > Test > > > listener="#{testController.beginConversation}" /> > > > > > action="#{testController.changeRenderInputPanel}"> > > > rendered="#{testController.renderInputPanel}"> > > > > > > > > {code} > {code} > import java.io.Serializable; > import javax.enterprise.context.Conversation; > import javax.enterprise.context.ConversationScoped; > import javax.inject.Inject; > import javax.inject.Named; > import org.apache.commons.logging.Log; > @Named > @ConversationScoped > public class TestController implements Serializable{ > private static final long serialVersionUID = 1L; > > @Inject > private Conversation conversation; > > private String newCommentAuthor; > > private boolean renderInputPanel = true; > > @Inject > private Log logger; > > public boolean isRenderInputPanel() { > return renderInputPanel; > } > public void setRenderInputPanel(boolean renderInputPanel) { > this.renderInputPanel = renderInputPanel; > } > > public void changeRenderInputPanel() { > this.setRenderInputPanel(!isRenderInputPanel()); > logger.info("render panel: " + renderInputPanel); > } > public String getNewCommentAuthor() { > return newCommentAuthor; > } > public void setNewCommentAuthor(String newCommentAuthor) { > this.newCommentAuthor = newCommentAuthor; > } > public void beginConversation() { > if (conversation.isTransient()) { > conversation.setTimeout(120000); > conversation.begin(); > } > } > public void endConversation() { > if (!conversation.isTransient()) { > conversation.end(); > return; > } > } > } > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 1 07:20:36 2012 From: jira-events at lists.jboss.org (Joern Ohmen (JIRA)) Date: Thu, 1 Mar 2012 07:20:36 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12003) Including h:head breaks f:ajax events of commandButton In-Reply-To: <135907437.40978.1330081357692.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1415618735.57240.1330604436550.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12672584#comment-12672584 ] Joern Ohmen commented on RF-12003: ---------------------------------- I think you are right, sorry I didn't test it without RichFaces. > Including h:head breaks f:ajax events of commandButton > ------------------------------------------------------ > > Key: RF-12003 > URL: https://issues.jboss.org/browse/RF-12003 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: base functionality > Affects Versions: 4.1.0.Final, 4.2.0.CR1 > Environment: JBoss 7.0.2 Final, JBoss 7.1.0 Final, RichFaces 4.2.0 Final, 4.1.0 Final, Chrome and Safari > Reporter: Joern Ohmen > Priority: Critical > Labels: Header, JSF2.0, RichFaces4 > Attachments: brokenRFHheadAdded.png > > > If I add h:head-Tag to my page, the ajax events of the h:commandButton are not working. The example should show up a panel with a click on a button, but nothing happens. The example is working when h:head is removed. I use a ConversationScoped Bean. > {code} > > > xmlns:h="http://java.sun.com/jsf/html" > xmlns:f="http://java.sun.com/jsf/core" > xmlns:ui="http://java.sun.com/jsf/facelets" > xmlns:fn="http://java.sun.com/jsp/jstl/functions" > xmlns:a4j="http://richfaces.org/a4j" > xmlns:rich="http://richfaces.org/rich"> > > Test > > > listener="#{testController.beginConversation}" /> > > > > > action="#{testController.changeRenderInputPanel}"> > > > rendered="#{testController.renderInputPanel}"> > > > > > > > > {code} > {code} > import java.io.Serializable; > import javax.enterprise.context.Conversation; > import javax.enterprise.context.ConversationScoped; > import javax.inject.Inject; > import javax.inject.Named; > import org.apache.commons.logging.Log; > @Named > @ConversationScoped > public class TestController implements Serializable{ > private static final long serialVersionUID = 1L; > > @Inject > private Conversation conversation; > > private String newCommentAuthor; > > private boolean renderInputPanel = true; > > @Inject > private Log logger; > > public boolean isRenderInputPanel() { > return renderInputPanel; > } > public void setRenderInputPanel(boolean renderInputPanel) { > this.renderInputPanel = renderInputPanel; > } > > public void changeRenderInputPanel() { > this.setRenderInputPanel(!isRenderInputPanel()); > logger.info("render panel: " + renderInputPanel); > } > public String getNewCommentAuthor() { > return newCommentAuthor; > } > public void setNewCommentAuthor(String newCommentAuthor) { > this.newCommentAuthor = newCommentAuthor; > } > public void beginConversation() { > if (conversation.isTransient()) { > conversation.setTimeout(120000); > conversation.begin(); > } > } > public void endConversation() { > if (!conversation.isTransient()) { > conversation.end(); > return; > } > } > } > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 1 11:33:39 2012 From: jira-events at lists.jboss.org (Jason Lee (JIRA)) Date: Thu, 1 Mar 2012 11:33:39 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11988) rich:fileUpload doesn't seem to work on GlassFish In-Reply-To: <1031298844.7144.1329428856250.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1067849341.58845.1330619619651.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12672806#comment-12672806 ] Jason Lee commented on RF-11988: -------------------------------- GlassFish does not use MyFaces. It uses Mojarra. > rich:fileUpload doesn't seem to work on GlassFish > ------------------------------------------------- > > Key: RF-11988 > URL: https://issues.jboss.org/browse/RF-11988 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.2.0.CR1 > Environment: Mac OS X, Firefox 10, Chrome 17, GlassFish 3.1.2, GlassFish 4.0 > Reporter: Jason Lee > Fix For: 4.3-Tracking > > Attachments: rfupload.log, rfupload.tar.gz > > > While it renders fine, POSTs initiated from rich:fileUpload error out. I have tested this using both Firefox 10+ and Chrome 17+ against GlassFish 3.1.2 and GlassFish 4.0. I will attach both the log file and a sample application that should demonstrate the issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 1 16:07:36 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Thu, 1 Mar 2012 16:07:36 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11635) rich:calendar missing attribute title In-Reply-To: <466623820.48577.1320229605292.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <314395588.60174.1330636056755.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12672930#comment-12672930 ] Brian Leathem commented on RF-11635: ------------------------------------ This should be a trivial matter of adding a title @Attribute, and passing the attribute through in the render to the input component. > rich:calendar missing attribute title > ------------------------------------- > > Key: RF-11635 > URL: https://issues.jboss.org/browse/RF-11635 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.1.0.Milestone3 > Reporter: Rene O > Priority: Minor > Fix For: 4.3-Tracking > > > The rich:calendar component has no title-attribute. > Example: > shows no tooltip. > shows the tooltip 'some text' -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 1 16:50:39 2012 From: jira-events at lists.jboss.org (Vairavan Laxman (JIRA)) Date: Thu, 1 Mar 2012 16:50:39 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-10758) Input fields in popupPanel loose focus In-Reply-To: <285449601.26426.1300194531841.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1424859652.60231.1330638639032.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-10758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12672938#comment-12672938 ] Vairavan Laxman commented on RF-10758: -------------------------------------- Even I'm facing the same issue on both Firefox and Internet Explorer. Any fix for this would be great! > Input fields in popupPanel loose focus > -------------------------------------- > > Key: RF-10758 > URL: https://issues.jboss.org/browse/RF-10758 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.0.0.CR1 > Environment: Tomcat 7.0.8, MyFaces 2.0.4, RichFaces 4.0.0-SNAPSHOT, Firefox 3.6.15, InternetExplorer 8 > Reporter: Marc-Christian Schroeer > Fix For: 4.Future > > > When opening a popupPanel with inputText-components, pressing the tab key to switch between input fields results in the address input field getting the focus. tabindex-attributes do not help this issue. This issue does not exist with Google Chrome browsers. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 2 00:07:38 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Fri, 2 Mar 2012 00:07:38 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-10758) Input fields in popupPanel loose focus In-Reply-To: <285449601.26426.1300194531841.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1256284190.61310.1330664858030.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-10758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-10758: ------------------------------- Fix Version/s: 4.3.0.Milestone1 (was: 4.Future) Forum Reference: http://community.jboss.org/message/593845#593845 (was: http://community.jboss.org/message/593845#593845) > Input fields in popupPanel loose focus > -------------------------------------- > > Key: RF-10758 > URL: https://issues.jboss.org/browse/RF-10758 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.0.0.CR1 > Environment: Tomcat 7.0.8, MyFaces 2.0.4, RichFaces 4.0.0-SNAPSHOT, Firefox 3.6.15, InternetExplorer 8 > Reporter: Marc-Christian Schroeer > Fix For: 4.3.0.Milestone1 > > > When opening a popupPanel with inputText-components, pressing the tab key to switch between input fields results in the address input field getting the focus. tabindex-attributes do not help this issue. This issue does not exist with Google Chrome browsers. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 2 02:41:36 2012 From: jira-events at lists.jboss.org (Marek Novotny (JIRA)) Date: Fri, 2 Mar 2012 02:41:36 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12020) Reduce number of absolute opened files Message-ID: <756676139.61444.1330674096251.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Marek Novotny created RF-12020: ---------------------------------- Summary: Reduce number of absolute opened files Key: RF-12020 URL: https://issues.jboss.org/browse/RF-12020 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: cdk Affects Versions: 4.2.0.Final Environment: linux Reporter: Marek Novotny While RF Components is compiled, it normally over goes under limit for maximum open files. I did some change which helped a little, but there will be probably bigger effect if the logic is re-factored to not open all files at the same time in generator/src/main/java/org/richfaces/cdk/templatecompiler/RendererClassGenerator.java of render method. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 2 02:43:36 2012 From: jira-events at lists.jboss.org (Marek Novotny (JIRA)) Date: Fri, 2 Mar 2012 02:43:36 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12020) Reduce number of absolute opened files In-Reply-To: <756676139.61444.1330674096251.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <507708856.61447.1330674216163.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marek Novotny updated RF-12020: ------------------------------- Attachment: cdk-generator.patch Patch for closing files in finally block to be sure not to let open files. > Reduce number of absolute opened files > -------------------------------------- > > Key: RF-12020 > URL: https://issues.jboss.org/browse/RF-12020 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: cdk > Affects Versions: 4.2.0.Final > Environment: linux > Reporter: Marek Novotny > Attachments: cdk-generator.patch > > > While RF Components is compiled, it normally over goes under limit for maximum open files. > I did some change which helped a little, but there will be probably bigger effect if the logic is re-factored to not open all files at the same time in generator/src/main/java/org/richfaces/cdk/templatecompiler/RendererClassGenerator.java of render method. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 2 02:49:36 2012 From: jira-events at lists.jboss.org (Marek Novotny (JIRA)) Date: Fri, 2 Mar 2012 02:49:36 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12021) Compilation of Input UI component logs 2 errors about faces-config.xml Message-ID: <518462150.61467.1330674576214.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Marek Novotny created RF-12021: ---------------------------------- Summary: Compilation of Input UI component logs 2 errors about faces-config.xml Key: RF-12021 URL: https://issues.jboss.org/browse/RF-12021 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-input Affects Versions: 4.2.0.Final Reporter: Marek Novotny Compilation of RF UI Components specifically Input UI has got 2 errors in log - related to bad faces-config.xml on line number 29 and 240. The following is snippet of log: {noformat} [INFO] ------------------------------------------------------------------------ [INFO] Building RichFaces UI Components: Input UI 4.2.0.Final [INFO] ------------------------------------------------------------------------ [INFO] [INFO] --- maven-enforcer-plugin:1.0-redhat-1:enforce (enforce-java-version) @ richfaces-ui-input-ui --- [INFO] The requirePluginVersions rule is currently not compatible with Maven3. [INFO] [INFO] --- maven-enforcer-plugin:1.0-redhat-1:enforce (enforce-maven-version) @ richfaces-ui-input-ui --- [INFO] The requirePluginVersions rule is currently not compatible with Maven3. [INFO] [INFO] --- maven-cdk-plugin:4.2.0.Final-redhat-1:generate (cdk-generate-sources) @ richfaces-ui-input-ui --- [Error] faces-config.xml:29:71: cvc-complex-type.2.4.a: Invalid content was found starting with element 'xi:include'. One of '{"http://java.sun.com/xml/ns/javaee":property, "http://java.sun.com/xml/ns/javaee":component-extension}' is expected. [Error] faces-config.xml:240:71: cvc-complex-type.2.4.a: Invalid content was found starting with element 'xi:include'. One of '{"http://java.sun.com/xml/ns/javaee":property, "http://java.sun.com/xml/ns/javaee":component-extension}' is expected. {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 2 09:45:37 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Fri, 2 Mar 2012 09:45:37 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11882) a4j jsFunction cannot transform java class to json in the getData method call In-Reply-To: <1733561605.53594.1326459021528.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <575814952.63417.1330699537012.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-11882. -------------------------------- Assignee: Brian Leathem Resolution: Incomplete Description > a4j jsFunction cannot transform java class to json in the getData method call > ----------------------------------------------------------------------------- > > Key: RF-11882 > URL: https://issues.jboss.org/browse/RF-11882 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.1.0.Final > Reporter: Dirk Dollar > Assignee: Brian Leathem > Priority: Minor > Labels: waiting_on_user > > I get a > FATAL: > {code} > ...javax.faces.FacesException: Error in conversion Java Object to JavaScript > at org.ajax4jsf.javascript.ScriptUtils.appendScript(ScriptUtils.java:194) [:4.1.0.Final] > at org.ajax4jsf.javascript.ScriptUtils.appendScript(ScriptUtils.java:123) [:4.1.0.Final] > .... > Caused by: java.lang.IllegalAccessException: Class org.ajax4jsf.javascript.PropertyUtils can not access a member of class java.util.HashMap$Entry with modifiers "public final" > {code} > Which wasn't there in richfaces 3.3.3 > The code snippet: > {code} > class MyBean{ > public String actionMethod(){ > ....do something which creates a Map data, now I want to sort it before I return it: > private List> sortDataIntoList(Map data) { > List> sortedList = new ArrayList>(data.entrySet()); > Collections.sort(sortedList, new Comparator>() { > public int compare(Entry f1, Entry f2) { > return f1.getValue().compareTo(f2.getValue()); > } > }); > if(sortedList.size()>max) > return sortedList.subList(0, max); > return sortedList; > } > ...and return it from... > public static MyInnerClass{ > List> data > public MyInnerClass(List> data){ > this.data=data > } > public List> getData(){ > return data;} > } > } > {code} > results in the mentioned error > A possible workaround is to use one's own implementation of a key value object e.g. something like > http://stackoverflow.com/questions/521171/a-java-collection-of-value-pairs-tuples -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 2 09:47:37 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Fri, 2 Mar 2012 09:47:37 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11966) Radiobuttons not visible in firefox but visible in IE In-Reply-To: <179375426.30615.1328707969055.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <360401397.63452.1330699657868.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-11966: ------------------------------- Fix Version/s: 3.Future Labels: (was: waiting_on_user) Use of the a4j:support tag indicates this is an RF 3 issue. > Radiobuttons not visible in firefox but visible in IE > ----------------------------------------------------- > > Key: RF-11966 > URL: https://issues.jboss.org/browse/RF-11966 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Roopa Shenoy > Priority: Blocker > Fix For: 3.Future > > > Hi , > We are facing certain issues regarding rendering radio buttons in firefox. > It works fine in IE but doesnot work in Firefox > Please find the below block of code. > In the code shown below,there are two panels for displaying radio buttons. > Last piece of code which displays commandlink is visible ,but the radiobuttons which needs to be shown on pageload is not visible. > When we click on commandlink , the flag showMoreValues turns true and only on click of this link the radiobuttons in second part of the code is visible. > Can you please help me out regarding this issue? > {code} > > > > > > > valueChangeListener="#{subscriptionCard.productChanged}" > value="#{subscriptionCard.selectedProductCode}"> > reRender="convertingForm,privateParamCard,businessParamCard,errorDetailsSubs,facilitiesCard,numberSelectCard,npPanel,paymentFormCard"/> > > > > > > > > items="#{subscriptionCard.showMoreValues}"> > > valueChangeListener="#{subscriptionCard.productChanged}" > value="#{subscriptionCard.selectedProductCode}"> > reRender="convertingForm,privateParamCard,businessParamCard,errorDetailsSubs,facilitiesCard,numberSelectCard,npPanel,paymentFormCard"/> > itemValue="#{privateAllProducts.value}"/> > > > > > > > > action="#{subscriptionCard.retrieveMoreValuess}" > reRender="moreValues" > value="#{msgs.subscriptioncard_link_more_Values}"> > > > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 2 10:23:36 2012 From: jira-events at lists.jboss.org (Chris Ligon (JIRA)) Date: Fri, 2 Mar 2012 10:23:36 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-7921) DropDownMenu: wrong vertical positioning of popup list on scrolling in Firefox In-Reply-To: <1149049456.1253702269266.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com> Message-ID: <50231828.63648.1330701816704.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-7921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12673223#comment-12673223 ] Chris Ligon commented on RF-7921: --------------------------------- I had a drop down menu in a rich:dataTable and it worked fine (no offset). But, when I put the rich:dataTable inside of a rich:tab this offset issue presented itself. Mano, could you explain a little bit about what this piece of code is doing? Why are you doing the layer.replace part? It seems that maybe you are escaping the :, but why is that? This workaround works to some extent. The problem is that for another dropdown menu (with sub-menus) outside of the rich:dataTable this script causes errors. Basically, the menu does not drop down, it's not visible at all. And, after removing the mouse from over the menu item, I see just below the menu item, "/:/g/:/g". Is there a way to limit the scope of this script so that it just works on the dropdown menus that need it? > DropDownMenu: wrong vertical positioning of popup list on scrolling in Firefox > ------------------------------------------------------------------------------ > > Key: RF-7921 > URL: https://issues.jboss.org/browse/RF-7921 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-menu > Affects Versions: 3.3.1, 3.3.2.CR1 > Environment: winXP, hibernate 3.2.4.sp1, seam 2.1.0.SP1, firefox 3.5.3 > Reporter: rofl rofl > Priority: Minor > Labels: drop_down_menu, firefox, position > Fix For: 3.Future > > Attachments: cannot_reproduce.jpg, ddmenu_pos_noScrolling.JPG, ddmenu_pos_withScrolling.JPG > > > The popup list of the drop down menu is wrongly positioned when one scrolls the page. It is shown too far below it's anchor point (i.e. it is not directly connected to it's anchor point) - the offset changes on scrolling (i.e. the more one scrools down, the farer below it is shown) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 2 11:00:38 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 2 Mar 2012 11:00:38 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-8287) CDK Make build incremental In-Reply-To: <1018283144.1264201219651.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com> Message-ID: <1995453384.63786.1330704038258.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-8287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated RF-8287: --------------------------- Attachment: IMAG0064.jpg > CDK Make build incremental > -------------------------- > > Key: RF-8287 > URL: https://issues.jboss.org/browse/RF-8287 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: cdk > Reporter: Alexander Smirnov > Assignee: Luk?? Fry? > Fix For: 4.3-Tracking > > Attachments: AptBuilder-profile.png, CDKProcessorImpl-profile.png, FreeMarker-usage.png, IMAG0064.jpg > > > To speed-up development builds, CDK should record "last modified" time of source files in the model. Generated file should be written only if target does not exist or its modification time is less then recorded for source files. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Sat Mar 3 06:31:38 2012 From: jira-events at lists.jboss.org (Frank Cornelis (JIRA)) Date: Sat, 3 Mar 2012 06:31:38 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11382) Datatable and ExtendedDatatable evaluate value attribute even if rendered=false In-Reply-To: <1693354179.35301.1315563986219.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <804248965.64904.1330774298829.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12673362#comment-12673362 ] Frank Cornelis commented on RF-11382: ------------------------------------- This is a very annoying bug. If you have RBAC enabled on the bean that is being called, the application explodes. When rendered evaluated to false, the dataTable should not call the bean as it might not have enough permissions in this case. > Datatable and ExtendedDatatable evaluate value attribute even if rendered=false > ------------------------------------------------------------------------------- > > Key: RF-11382 > URL: https://issues.jboss.org/browse/RF-11382 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.0.0.Final, 4.1.0.Milestone2 > Environment: Fedora 15, Glassfish 3.1.1, CDI (Weld) > Reporter: Frederick K?mpfer > Assignee: Brian Leathem > Labels: lazy-loaded > Fix For: 4.3-Tracking > > > In Richfaces 4 both datatable and extendedDatatable evaluate the value attribute even when rendered is set to false, even though it is not necessary. This makes it hard to achieve performance by trimming parts of the view tree. The built-in h:dataTable behaves correctly in that case. > To reproduce simply try this snipplet: > {code:xml} > > > > > {code} > Side note: The reason I'm posting this is, that i want to embed a rich:dataTable in a ajax loaded rich:togglePanelItem which is loaded on demand. Probably fixing the "render" problem will also make the dataTable lazy-loadable when switching to the corresponding togglePanelItem. > I hope this is no duplicate, I only found RichFaces 3 issues mentioning this problem. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 5 12:45:37 2012 From: jira-events at lists.jboss.org (Virage Group (JIRA)) Date: Mon, 5 Mar 2012 12:45:37 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-8176) Upgrade Prototype to version 1.6.1 In-Reply-To: <1734615056.1259759489663.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com> Message-ID: <1951188654.67865.1330969537873.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-8176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12673702#comment-12673702 ] Virage Group commented on RF-8176: ---------------------------------- Hi, We ran into the prototype/hanging IE bug https://community.jboss.org/message/560209 https://community.jboss.org/message/553262 and http://blog.swwomm.com/2010/04/1-item-remaining-problem-in-ie.html It seems that prototype 1.6.1 solves that bug. as "org.richfaces.ExcludeScripts" parameter seems not be available in 3.3.3 and patching the framework.pack.js file seems not easy, is there any chance to see a bug fix release of richfaces with Prototype version 1.6.1 ? Perhaps is there any workaround ? (Of course, we are looking to upgrade to RF 4 but it won't be done in a short term and the "hanging ie" bug is upsetting the users) > Upgrade Prototype to version 1.6.1 > ---------------------------------- > > Key: RF-8176 > URL: https://issues.jboss.org/browse/RF-8176 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: third-party > Affects Versions: 3.3.2.SR1 > Reporter: Francois Botha > Priority: Minor > Fix For: 3.Future > > > I know you guys had performance issues with Prototype 1.6.0.2, but maybe the latest version (1.6.1 at time of writing) fixes those issues. > I have a specific interest in version 1.6.1 because I'd like to use Growler for Prototype. Unfortunately Prototype 1.6.0.x has a bug which makes it useless on IE. 1.6.1 solves that bug. Bug logged at https://prototype.lighthouseapp.com/projects/8886/tickets/529-element-constructor-doesnt-add-classname-in-ie8 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 5 18:17:36 2012 From: jira-events at lists.jboss.org (Evan Toliopoulos (JIRA)) Date: Mon, 5 Mar 2012 18:17:36 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11585) mediaOutput doesn't work in CDI @ConversationScoped In-Reply-To: <1543595142.24553.1319547285289.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <769148453.68682.1330989456343.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12673800#comment-12673800 ] Evan Toliopoulos commented on RF-11585: --------------------------------------- This problem also exists with @ViewScoped (JSF scope) beans. > mediaOutput doesn't work in CDI @ConversationScoped > --------------------------------------------------- > > Key: RF-11585 > URL: https://issues.jboss.org/browse/RF-11585 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component > Affects Versions: 4.0.0.Final > Environment: NetBeans7.0.1 + GlassFish 3.1.1 + CDI 1.1 + JSF2.1 + RichFaces4.0.0-Final. > Reporter: Edilmar Alves > Priority: Critical > Fix For: 4.3-Tracking > > Original Estimate: 4 weeks > Remaining Estimate: 4 weeks > > When using a controller with @ConversationScoped (CDI scope), the following exception arises: GRAVE: org.jboss.weld.context.ContextNotActiveException: WELD-001303 No active contexts for scope type javax.enterprise.context.ConversationScoped -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 5 18:21:36 2012 From: jira-events at lists.jboss.org (Evan Toliopoulos (JIRA)) Date: Mon, 5 Mar 2012 18:21:36 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11585) mediaOutput doesn't work in CDI @ConversationScoped In-Reply-To: <1543595142.24553.1319547285289.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <192032280.68697.1330989696410.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12673800#comment-12673800 ] Evan Toliopoulos edited comment on RF-11585 at 3/5/12 6:20 PM: --------------------------------------------------------------- This problem also exists with @ViewScoped (JSF scope) beans. [JBoss 6.1/JEE6, JSF 2.0, Seam 3.1.0, RichFaces 4.1.0] was (Author: evantoliopoulos): This problem also exists with @ViewScoped (JSF scope) beans. > mediaOutput doesn't work in CDI @ConversationScoped > --------------------------------------------------- > > Key: RF-11585 > URL: https://issues.jboss.org/browse/RF-11585 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component > Affects Versions: 4.0.0.Final > Environment: NetBeans7.0.1 + GlassFish 3.1.1 + CDI 1.1 + JSF2.1 + RichFaces4.0.0-Final. > Reporter: Edilmar Alves > Priority: Critical > Fix For: 4.3-Tracking > > Original Estimate: 4 weeks > Remaining Estimate: 4 weeks > > When using a controller with @ConversationScoped (CDI scope), the following exception arises: GRAVE: org.jboss.weld.context.ContextNotActiveException: WELD-001303 No active contexts for scope type javax.enterprise.context.ConversationScoped -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 5 19:23:36 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 5 Mar 2012 19:23:36 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11985) rich:dataTable with MyFaces 2.x.x - Target Unreachable, identifier 'client' resolved to null In-Reply-To: <119852735.5474.1329403117984.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <132264452.68814.1330993416274.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12673815#comment-12673815 ] Brian Leathem commented on RF-11985: ------------------------------------ Jean ANDRE, The attached java files here are not compilable; they reference classes that have not been provided. There are 4 facelet files included, and 3 java files - is all this complexity required to reproduce this issue? Have you tried reproducing it with simpler conditions? As it stand now, I have to disect the code samples you provided to discern your intent, and build a simple example that reproduces the issue. Providing an EAR bundle is only goes so far, as one is not easily able to make and observe changes to the framework, nor the provided code. I've written a wiki article that highlights some important aspects to keep in mind when submitting an issue report: https://community.jboss.org/wiki/SubmittingEffectiveIssueReports Please review the article, and consider any work you put into helping us isolate the issue as your "contribution" to the open-source process. Keep in mind that we are as interested in coming to a resolution with this issue as you are, but with many individuals reporting bugs in many different areas, we have to focus our attention on resolving issues that will have the biggest impact to our user-base. > rich:dataTable with MyFaces 2.x.x - Target Unreachable, identifier 'client' resolved to null > -------------------------------------------------------------------------------------------- > > Key: RF-11985 > URL: https://issues.jboss.org/browse/RF-11985 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.2.0.CR1 > Environment: MyFaces 2.0.x and 2.1.6 - RichFaces 4.2.0 CR1 - WAS 8.0.0.1 - Spring 3.0.6 - Hibernate Validator 4.2.0 Final > Reporter: Jean ANDRE > Priority: Critical > Labels: myfaces, waiting_on_user > Attachments: index.xhtml, listClient.xhtml, ResultClientController.java, searchClient.xhtml, SearchClientController.java, tabsClient.xhtml, TabsClientController.java > > > We made a test under MyFaces implementation of JSF 2.0 and actually we got an error with the dataTable. At the first call of the web page, the dataTable performs well but once the dataTable is redisplayed, the dataTable is unable to reach an existing variable declared by the attribute var (ex.var="client"). > We made also the test by using the h:dataTable, the standard JSF tag and it is working perfectly - As you know we also use Mojarra as JSF implementation and it's working too. Then the problem seems to come from with rich:dataTable. Nothing very special here in using the tag. > {code} > > > > > > >   > > rendered="#{resultClientController.isDejaVu(client.id)}" > alt="#{msg['common.dejaVu.alt']}" > title="#{msg['common.dejaVu.tooltip']}" /> > > {code} > {code} > javax.faces.FacesException: javax.el.PropertyNotFoundException: /pages/client/listClient.xhtml at line 78 and column 51 rendered="#{resultClientController.isDejaVu(client.id)}": Target Unreachable, identifier 'client' resolved to null > at org.apache.myfaces.shared_impl.context.ExceptionHandlerImpl.wrap(ExceptionHandlerImpl.java:241) > at org.apache.myfaces.shared_impl.context.ExceptionHandlerImpl.handle(ExceptionHandlerImpl.java:156) > at org.apache.myfaces.lifecycle.LifecycleImpl.executePhase(LifecycleImpl.java:191) > at org.apache.myfaces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118) > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:189) > at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1147) > at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:722) > at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:449) > at com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest(ServletWrapperImpl.java:178) > at com.ibm.ws.webcontainer.filter.WebAppFilterChain.invokeTarget(WebAppFilterChain.java:125) > at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:92) > at com.intact.crm.web.filter.LoginFilter.doFilter(LoginFilter.java:56) > at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:192) > at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:89) > at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:919) > at com.ibm.ws.webcontainer.filter.WebAppFilterManager.invokeFilters(WebAppFilterManager.java:1016) > at com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleRequest(CacheServletWrapper.java:87) > at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:886) > at com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContainer.java:1655) > at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:195) > at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:452) > at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewRequest(HttpInboundLink.java:511) > at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.processRequest(HttpInboundLink.java:305) > at com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpICLReadCallback.java:83) > at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:165) > at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217) > at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161) > at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:138) > at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:204) > at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:775) > at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905) > at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1650) > Caused by: javax.el.PropertyNotFoundException: /pages/client/listClient.xhtml at line 78 and column 51 rendered="#{resultClientController.isDejaVu(client.id)}": Target Unreachable, identifier 'client' resolved to null > at org.apache.myfaces.view.facelets.el.TagValueExpression.getValue(TagValueExpression.java:89) > at javax.faces.component._DeltaStateHelper.eval(_DeltaStateHelper.java:260) > at javax.faces.component.UIComponentBase.isRendered(UIComponentBase.java:1007) > at javax.faces.component.UIComponent.isVisitable(UIComponent.java:289) > at javax.faces.component.UIComponent.visitTree(UIComponent.java:767) > at javax.faces.component.UIComponentBase.visitTree(UIComponentBase.java:991) > at javax.faces.component.UIComponent.visitTree(UIComponent.java:793) > at javax.faces.component.UIComponentBase.visitTree(UIComponentBase.java:991) > at org.richfaces.component.UIDataAdaptor.visitComponents(UIDataAdaptor.java:1259) > at org.richfaces.component.UIDataAdaptor.visitDataChildren(UIDataAdaptor.java:1286) > at org.richfaces.component.UIDataTableBase.visitDataChildren(UIDataTableBase.java:359) > at org.richfaces.component.UIDataAdaptor.visitTree(UIDataAdaptor.java:1360) > at javax.faces.component.UIComponent.visitTree(UIComponent.java:793) > at javax.faces.component.UIComponentBase.visitTree(UIComponentBase.java:991) > at javax.faces.component.UINamingContainer.visitTree(UINamingContainer.java:169) > at javax.faces.component.UIComponent.visitTree(UIComponent.java:793) > at javax.faces.component.UIComponentBase.visitTree(UIComponentBase.java:991) > at org.richfaces.component.AbstractTogglePanel.visitTree(AbstractTogglePanel.java:719) > at javax.faces.component.UIForm.visitTree(UIForm.java:269) > at javax.faces.component.UIComponent.visitTree(UIComponent.java:793) > at javax.faces.component.UIComponentBase.visitTree(UIComponentBase.java:991) > at javax.faces.component.UIComponent.visitTree(UIComponent.java:793) > at javax.faces.component.UIComponentBase.visitTree(UIComponentBase.java:991) > at org.apache.myfaces.view.facelets.tag.ui.DebugPhaseListener._doTreeVisit(DebugPhaseListener.java:310) > at org.apache.myfaces.view.facelets.tag.ui.DebugPhaseListener.afterPhase(DebugPhaseListener.java:286) > at org.apache.myfaces.lifecycle.PhaseListenerManager.informPhaseListenersAfter(PhaseListenerManager.java:111) > at org.apache.myfaces.lifecycle.LifecycleImpl.executePhase(LifecycleImpl.java:185) > ... 29 more > {code} > Please, not that the application is a single page application, everything appends inside a single page. Dynamic include is used to achieve this goal (see index.xhtml) - Tab is also dynamic except for the search. See screen shot. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 6 07:37:37 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?J=C3=A1n_Jamrich_=28JIRA=29?=) Date: Tue, 6 Mar 2012 07:37:37 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11970) Ajax event create exception on form submission when defined on dataTable inside that form In-Reply-To: <1907532891.33570.1328789028473.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1209297530.69886.1331037457195.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] J?n Jamrich reassigned RF-11970: -------------------------------- Assignee: (was: J?n Jamrich) Add problem simulation into Metamer. It still appears in RF 4.2.0-SNAPSHOT. For more info see following commit: https://github.com/richfaces/qa/commit/d50647d277a47ba1833cfda75d5a8e2053233694 (metamer/application/src/main/webapp/components/richDataTable/rf-11970.xhtml) > Ajax event create exception on form submission when defined on dataTable inside that form > ----------------------------------------------------------------------------------------- > > Key: RF-11970 > URL: https://issues.jboss.org/browse/RF-11970 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.1.0.Final > Environment: All > Reporter: shimon lifshitz > > I defined ajax support event="rowclick" on rich:dataTable. This table is defined inside a form. When I tried to submit the form (h:command). I got an exception: > {code} > Caused by: java.lang.NullPointerException > at org.richfaces.renderkit.DataTableRenderer.doDecode(DataTableRenderer.java:111) > at org.richfaces.renderkit.RendererBase.decode(RendererBase.java:80) > at javax.faces.component.UIComponentBase.decode(UIComponentBase.java:787) > {code} > Problem can be easily fixed by addind check for null in relevent line: > {code} > if (!behaviorEvent.startsWith(ROW)) { ---> > if (behaviorEvent == null ||!behaviorEvent.startsWith(ROW)) > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 6 07:43:39 2012 From: jira-events at lists.jboss.org (Jean ANDRE (JIRA)) Date: Tue, 6 Mar 2012 07:43:39 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11985) rich:dataTable with MyFaces 2.x.x - Target Unreachable, identifier 'client' resolved to null In-Reply-To: <119852735.5474.1329403117984.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1292865319.69903.1331037819604.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12673937#comment-12673937 ] Jean ANDRE commented on RF-11985: --------------------------------- Hello Brian, Well, agree with your request - We understand your needs. For this bug, we have cancelled the migration to MyFaces/CDI because under WAS we are not able to upgrade to the latest version of 2.1.6. We learnt that WAS 8 is using MyFaces 2.0.2.... We got also some other problems as explained below: After we changed the code to use the c:if and the subView (see forum: https://community.jboss.org/message/721147), the modifications made to the code does not allow the application to perform well under MyFaces. We got some error messages about duplicate Ids even if the application does not have any duplicate Ids and even if the application is running perfectly under Mojarra. Another problem we found is about the id syntax. Under RAD/MyFaces, having an id like #{tab.id}-blabla is not correct but with Mojarra, it is. We absolutely need to have a calculated Id as we create dynamically some tabs and as we include several occurrences of the same physical fragment. Actually, the status is: under Mojorra, the application performs well. Under MyFaces 2.0.2 the application is not compatible. (sounds strange...) If time permit, we will try to test the application under another application server with the latest implementation of MyFaces and with the latest implementation of CDI (OWB). I will return back to you if we got some interesting results for you. Sincerely - Jean. > rich:dataTable with MyFaces 2.x.x - Target Unreachable, identifier 'client' resolved to null > -------------------------------------------------------------------------------------------- > > Key: RF-11985 > URL: https://issues.jboss.org/browse/RF-11985 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.2.0.CR1 > Environment: MyFaces 2.0.x and 2.1.6 - RichFaces 4.2.0 CR1 - WAS 8.0.0.1 - Spring 3.0.6 - Hibernate Validator 4.2.0 Final > Reporter: Jean ANDRE > Priority: Critical > Labels: myfaces, waiting_on_user > Attachments: index.xhtml, listClient.xhtml, ResultClientController.java, searchClient.xhtml, SearchClientController.java, tabsClient.xhtml, TabsClientController.java > > > We made a test under MyFaces implementation of JSF 2.0 and actually we got an error with the dataTable. At the first call of the web page, the dataTable performs well but once the dataTable is redisplayed, the dataTable is unable to reach an existing variable declared by the attribute var (ex.var="client"). > We made also the test by using the h:dataTable, the standard JSF tag and it is working perfectly - As you know we also use Mojarra as JSF implementation and it's working too. Then the problem seems to come from with rich:dataTable. Nothing very special here in using the tag. > {code} > > > > > > >   > > rendered="#{resultClientController.isDejaVu(client.id)}" > alt="#{msg['common.dejaVu.alt']}" > title="#{msg['common.dejaVu.tooltip']}" /> > > {code} > {code} > javax.faces.FacesException: javax.el.PropertyNotFoundException: /pages/client/listClient.xhtml at line 78 and column 51 rendered="#{resultClientController.isDejaVu(client.id)}": Target Unreachable, identifier 'client' resolved to null > at org.apache.myfaces.shared_impl.context.ExceptionHandlerImpl.wrap(ExceptionHandlerImpl.java:241) > at org.apache.myfaces.shared_impl.context.ExceptionHandlerImpl.handle(ExceptionHandlerImpl.java:156) > at org.apache.myfaces.lifecycle.LifecycleImpl.executePhase(LifecycleImpl.java:191) > at org.apache.myfaces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118) > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:189) > at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1147) > at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:722) > at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:449) > at com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest(ServletWrapperImpl.java:178) > at com.ibm.ws.webcontainer.filter.WebAppFilterChain.invokeTarget(WebAppFilterChain.java:125) > at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:92) > at com.intact.crm.web.filter.LoginFilter.doFilter(LoginFilter.java:56) > at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:192) > at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:89) > at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:919) > at com.ibm.ws.webcontainer.filter.WebAppFilterManager.invokeFilters(WebAppFilterManager.java:1016) > at com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleRequest(CacheServletWrapper.java:87) > at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:886) > at com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContainer.java:1655) > at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:195) > at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:452) > at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewRequest(HttpInboundLink.java:511) > at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.processRequest(HttpInboundLink.java:305) > at com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpICLReadCallback.java:83) > at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:165) > at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217) > at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161) > at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:138) > at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:204) > at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:775) > at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905) > at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1650) > Caused by: javax.el.PropertyNotFoundException: /pages/client/listClient.xhtml at line 78 and column 51 rendered="#{resultClientController.isDejaVu(client.id)}": Target Unreachable, identifier 'client' resolved to null > at org.apache.myfaces.view.facelets.el.TagValueExpression.getValue(TagValueExpression.java:89) > at javax.faces.component._DeltaStateHelper.eval(_DeltaStateHelper.java:260) > at javax.faces.component.UIComponentBase.isRendered(UIComponentBase.java:1007) > at javax.faces.component.UIComponent.isVisitable(UIComponent.java:289) > at javax.faces.component.UIComponent.visitTree(UIComponent.java:767) > at javax.faces.component.UIComponentBase.visitTree(UIComponentBase.java:991) > at javax.faces.component.UIComponent.visitTree(UIComponent.java:793) > at javax.faces.component.UIComponentBase.visitTree(UIComponentBase.java:991) > at org.richfaces.component.UIDataAdaptor.visitComponents(UIDataAdaptor.java:1259) > at org.richfaces.component.UIDataAdaptor.visitDataChildren(UIDataAdaptor.java:1286) > at org.richfaces.component.UIDataTableBase.visitDataChildren(UIDataTableBase.java:359) > at org.richfaces.component.UIDataAdaptor.visitTree(UIDataAdaptor.java:1360) > at javax.faces.component.UIComponent.visitTree(UIComponent.java:793) > at javax.faces.component.UIComponentBase.visitTree(UIComponentBase.java:991) > at javax.faces.component.UINamingContainer.visitTree(UINamingContainer.java:169) > at javax.faces.component.UIComponent.visitTree(UIComponent.java:793) > at javax.faces.component.UIComponentBase.visitTree(UIComponentBase.java:991) > at org.richfaces.component.AbstractTogglePanel.visitTree(AbstractTogglePanel.java:719) > at javax.faces.component.UIForm.visitTree(UIForm.java:269) > at javax.faces.component.UIComponent.visitTree(UIComponent.java:793) > at javax.faces.component.UIComponentBase.visitTree(UIComponentBase.java:991) > at javax.faces.component.UIComponent.visitTree(UIComponent.java:793) > at javax.faces.component.UIComponentBase.visitTree(UIComponentBase.java:991) > at org.apache.myfaces.view.facelets.tag.ui.DebugPhaseListener._doTreeVisit(DebugPhaseListener.java:310) > at org.apache.myfaces.view.facelets.tag.ui.DebugPhaseListener.afterPhase(DebugPhaseListener.java:286) > at org.apache.myfaces.lifecycle.PhaseListenerManager.informPhaseListenersAfter(PhaseListenerManager.java:111) > at org.apache.myfaces.lifecycle.LifecycleImpl.executePhase(LifecycleImpl.java:185) > ... 29 more > {code} > Please, not that the application is a single page application, everything appends inside a single page. Dynamic include is used to achieve this goal (see index.xhtml) - Tab is also dynamic except for the search. See screen shot. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 6 10:21:37 2012 From: jira-events at lists.jboss.org (Juraj Huska (JIRA)) Date: Tue, 6 Mar 2012 10:21:37 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12022) showcase - UAgentInfo is not serialized Message-ID: <1295764103.70688.1331047297172.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Juraj Huska created RF-12022: -------------------------------- Summary: showcase - UAgentInfo is not serialized Key: RF-12022 URL: https://issues.jboss.org/browse/RF-12022 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: showcase Affects Versions: 4.2.0.Final Environment: -showcase, -Tomcat 6,7, -arquillian tests Reporter: Juraj Huska Priority: Trivial When running functional tests for showcase with Arquillian on Tomcat 6 or 7, I am encountering following exception during showcase undeploying process: {code} WARNING: Cannot serialize session attribute userAgent for session E4F43AA62674D093726971AC8361F9F8 java.io.NotSerializableException: org.richfaces.demo.ui.UAgentInfo at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1164) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1518) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1483) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1400) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1158) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:330) at org.apache.catalina.session.StandardSession.writeObject(StandardSession.java:1585) at org.apache.catalina.session.StandardSession.writeObjectData(StandardSession.java:1015) at org.apache.catalina.session.StandardManager.doUnload(StandardManager.java:528) at org.apache.catalina.session.StandardManager.unload(StandardManager.java:469) at org.apache.catalina.session.StandardManager.stop(StandardManager.java:678) at org.apache.catalina.core.StandardContext.stop(StandardContext.java:4882) at org.apache.catalina.manager.ManagerServlet.undeploy(ManagerServlet.java:1390) at org.apache.catalina.manager.ManagerServlet.doGet(ManagerServlet.java:382) at javax.servlet.http.HttpServlet.service(HttpServlet.java:617) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:563) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:859) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:602) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489) at java.lang.Thread.run(Thread.java:662) {code} UAgentInfo is used by UserAgentProcessor(session scoped bean) and therefore IMHO should be serialized. When I made it serialize-able, the exception disappeared. I did not notice any broken functionality by this exception, and same for the fixed one showcase, only cleaner test output. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 6 10:45:42 2012 From: jira-events at lists.jboss.org (Bertrand P (JIRA)) Date: Tue, 6 Mar 2012 10:45:42 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12023) comboBox in dataTable Message-ID: <1186358326.70819.1331048742987.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Bertrand P created RF-12023: ------------------------------- Summary: comboBox in dataTable Key: RF-12023 URL: https://issues.jboss.org/browse/RF-12023 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-selects, component-tables Affects Versions: 4.1.0.Final Environment: All Reporter: Bertrand P When a is in a of a , the row is selected when comboBox is selected. A workaround is: , but that doesn't work when the arrow is clicked. Because the arrow is generated in an independent span: -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 6 12:17:39 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Tue, 6 Mar 2012 12:17:39 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11992) cache bug in portlet In-Reply-To: <162483894.26432.1329646296148.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <780022530.71206.1331054259177.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12674079#comment-12674079 ] Brian Leathem commented on RF-11992: ------------------------------------ Comments from Ken Finnigan in IRC: {quote} (07:05:42 AM) kenfinnigan: bleathem: if the code snippet in the JIRA is accurate, in terms of what RF *does* set in headers (07:06:19 AM) kenfinnigan: then I would say it makes sense to set the blank Pragma to prevent any browsers from ignoring the Cache Control settings (07:06:38 AM) kenfinnigan: as it appears HTTP 1.0 uses Pragma, whereas 1.1 uses Cache Control (07:06:52 AM) kenfinnigan: so it could be that the portal servers only understand 1.0 of HTTP (07:07:51 AM) kenfinnigan: though not sure about that last stmt, as that would imply EAP 5 doesn't understand HTTP 1.1 (07:07:54 AM) kenfinnigan: which I know is not the case (07:08:06 AM) kenfinnigan: either way, probably makes sense for RF to set it {quote} > cache bug in portlet > -------------------- > > Key: RF-11992 > URL: https://issues.jboss.org/browse/RF-11992 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 3.3.3.Final, 4.2.0.CR1 > Environment: jboss portal 2.7.2; Gatein portal > Reporter: Ivan Ravin > Priority: Minor > Fix For: 4.3.0.Milestone1 > > > On Jboss and Gatein portal richfaces cant be cached when user is logged in. > Bug is found for richfaces 3.3.3 but i think can be reproduced for 4.x because org.richfaces.resource.AbstractCacheableResource has similar code. > The steps for reproduce bug are: > download portlet bridge 2.2 archive > deploy richFacesPortlet.war from portlet bridge archive (i used jboss portal 2.7.2 bundle and GateIn-3.1.0-FINAL-jbossas) > look at network activity (i did with firefox + firebug, the same result on any other browser). Just open page with richfaces portlet. > When user is not logged in, all richfaces resources are caching well, and this is headers returned by server: > |Cache-Control |max-age=86400| > |Content-Type |text/javascript| > |Date |Thu, 26 Jan 2012 17:57:39 GMT| > |Expires |27 Jan 2012 17:57:39 GMT| > |Last-Modified |26 Jan 2012 17:42:17 GMT| > |Server |Apache-Coyote/1.1| > |X-Powered-By |Servlet 2.4; JBoss-4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200807181417)/JBossWeb-2.0| > But when user is logged in all richfaces stuff come from network every time (more than 1.3 mb). > This is headers returned by portal 2.7.2 when user logged in: > |Cache-Control |{color:red}no-cache,{color} max-age=86400| > |Content-Type |text/javascript| > |Date |Thu, 26 Jan 2012 18:26:49 GMT| > |Expires |{color:red}Thu, 01 Jan 1970 03:00:00 MSK,{color} 27 Jan 2012 18:26:49 GMT| > |Last-Modified |26 Jan 2012 18:05:56 GMT| > |{color:red}Pragma{color} |{color:red}No-cache{color}| > |Server |Apache-Coyote/1.1| > |Transfer-Encoding |chunked| > |X-Powered-By |Servlet 2.4; JBoss-4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200807181417)/JBossWeb-2.0| > The same problem with GateIn-3.1.0-FINAL-jbossas bundle, but now only one wrong header: > |Cache-Control |max-age=86400| > |Content-Type |text/javascript;charset=UTF-8| > |Date |Sat, 28 Jan 2012 08:54:14 GMT| > |Expires |29 Jan 2012 08:54:14 GMT| > |Last-Modified |28 Jan 2012 08:51:11 GMT| > |{color:red}Pragma{color} |{color:red}No-cache{color}| > |Server |Apache-Coyote/1.1| > |Transfer-Encoding |chunked| > |X-Powered-By |Servlet 2.5; JBoss-5.0/JBossWeb-2.1| > This header (Pragma) appears only when user is logged in, and again, all richfaces resources come through network. > I did some debug and found that richfaces create good headers, but there is some code in portal which put wrong values into real response before richfaces. I cant find this code in portal sources, so maybe it is JBoss AS problem, or third party component. > In Gatein portal problem was partially resolved: it overwrites 2 wrong headers with values provided by richfaces, but "pragma" header is absent in richfaces response, and this way in secured portlets richfaces generate too much unnesessary traffic. > To solve problem for GateIn there is enough to provide empty Pragma header; To solve problem for JBoss Portal its required to fix resource headers processing in portal code, like it done in gatein. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 6 12:17:40 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Tue, 6 Mar 2012 12:17:40 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11992) cache bug in portlet In-Reply-To: <162483894.26432.1329646296148.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1461297369.71211.1331054260375.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-11992: ------------------------------- Fix Version/s: 4.3.0.Milestone1 Forum Reference: https://community.jboss.org/thread/178136?tstart=150 (was: https://community.jboss.org/thread/178136?tstart=150) > cache bug in portlet > -------------------- > > Key: RF-11992 > URL: https://issues.jboss.org/browse/RF-11992 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 3.3.3.Final, 4.2.0.CR1 > Environment: jboss portal 2.7.2; Gatein portal > Reporter: Ivan Ravin > Priority: Minor > Fix For: 4.3.0.Milestone1 > > > On Jboss and Gatein portal richfaces cant be cached when user is logged in. > Bug is found for richfaces 3.3.3 but i think can be reproduced for 4.x because org.richfaces.resource.AbstractCacheableResource has similar code. > The steps for reproduce bug are: > download portlet bridge 2.2 archive > deploy richFacesPortlet.war from portlet bridge archive (i used jboss portal 2.7.2 bundle and GateIn-3.1.0-FINAL-jbossas) > look at network activity (i did with firefox + firebug, the same result on any other browser). Just open page with richfaces portlet. > When user is not logged in, all richfaces resources are caching well, and this is headers returned by server: > |Cache-Control |max-age=86400| > |Content-Type |text/javascript| > |Date |Thu, 26 Jan 2012 17:57:39 GMT| > |Expires |27 Jan 2012 17:57:39 GMT| > |Last-Modified |26 Jan 2012 17:42:17 GMT| > |Server |Apache-Coyote/1.1| > |X-Powered-By |Servlet 2.4; JBoss-4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200807181417)/JBossWeb-2.0| > But when user is logged in all richfaces stuff come from network every time (more than 1.3 mb). > This is headers returned by portal 2.7.2 when user logged in: > |Cache-Control |{color:red}no-cache,{color} max-age=86400| > |Content-Type |text/javascript| > |Date |Thu, 26 Jan 2012 18:26:49 GMT| > |Expires |{color:red}Thu, 01 Jan 1970 03:00:00 MSK,{color} 27 Jan 2012 18:26:49 GMT| > |Last-Modified |26 Jan 2012 18:05:56 GMT| > |{color:red}Pragma{color} |{color:red}No-cache{color}| > |Server |Apache-Coyote/1.1| > |Transfer-Encoding |chunked| > |X-Powered-By |Servlet 2.4; JBoss-4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200807181417)/JBossWeb-2.0| > The same problem with GateIn-3.1.0-FINAL-jbossas bundle, but now only one wrong header: > |Cache-Control |max-age=86400| > |Content-Type |text/javascript;charset=UTF-8| > |Date |Sat, 28 Jan 2012 08:54:14 GMT| > |Expires |29 Jan 2012 08:54:14 GMT| > |Last-Modified |28 Jan 2012 08:51:11 GMT| > |{color:red}Pragma{color} |{color:red}No-cache{color}| > |Server |Apache-Coyote/1.1| > |Transfer-Encoding |chunked| > |X-Powered-By |Servlet 2.5; JBoss-5.0/JBossWeb-2.1| > This header (Pragma) appears only when user is logged in, and again, all richfaces resources come through network. > I did some debug and found that richfaces create good headers, but there is some code in portal which put wrong values into real response before richfaces. I cant find this code in portal sources, so maybe it is JBoss AS problem, or third party component. > In Gatein portal problem was partially resolved: it overwrites 2 wrong headers with values provided by richfaces, but "pragma" header is absent in richfaces response, and this way in secured portlets richfaces generate too much unnesessary traffic. > To solve problem for GateIn there is enough to provide empty Pragma header; To solve problem for JBoss Portal its required to fix resource headers processing in portal code, like it done in gatein. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 6 12:23:36 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Tue, 6 Mar 2012 12:23:36 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11985) rich:dataTable with MyFaces 2.x.x - Target Unreachable, identifier 'client' resolved to null In-Reply-To: <119852735.5474.1329403117984.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <105709060.71226.1331054616255.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-11985: ------------------------------- Fix Version/s: 4.Future > rich:dataTable with MyFaces 2.x.x - Target Unreachable, identifier 'client' resolved to null > -------------------------------------------------------------------------------------------- > > Key: RF-11985 > URL: https://issues.jboss.org/browse/RF-11985 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.2.0.CR1 > Environment: MyFaces 2.0.x and 2.1.6 - RichFaces 4.2.0 CR1 - WAS 8.0.0.1 - Spring 3.0.6 - Hibernate Validator 4.2.0 Final > Reporter: Jean ANDRE > Priority: Critical > Labels: myfaces, waiting_on_user > Fix For: 4.Future > > Attachments: index.xhtml, listClient.xhtml, ResultClientController.java, searchClient.xhtml, SearchClientController.java, tabsClient.xhtml, TabsClientController.java > > > We made a test under MyFaces implementation of JSF 2.0 and actually we got an error with the dataTable. At the first call of the web page, the dataTable performs well but once the dataTable is redisplayed, the dataTable is unable to reach an existing variable declared by the attribute var (ex.var="client"). > We made also the test by using the h:dataTable, the standard JSF tag and it is working perfectly - As you know we also use Mojarra as JSF implementation and it's working too. Then the problem seems to come from with rich:dataTable. Nothing very special here in using the tag. > {code} > > > > > > >   > > rendered="#{resultClientController.isDejaVu(client.id)}" > alt="#{msg['common.dejaVu.alt']}" > title="#{msg['common.dejaVu.tooltip']}" /> > > {code} > {code} > javax.faces.FacesException: javax.el.PropertyNotFoundException: /pages/client/listClient.xhtml at line 78 and column 51 rendered="#{resultClientController.isDejaVu(client.id)}": Target Unreachable, identifier 'client' resolved to null > at org.apache.myfaces.shared_impl.context.ExceptionHandlerImpl.wrap(ExceptionHandlerImpl.java:241) > at org.apache.myfaces.shared_impl.context.ExceptionHandlerImpl.handle(ExceptionHandlerImpl.java:156) > at org.apache.myfaces.lifecycle.LifecycleImpl.executePhase(LifecycleImpl.java:191) > at org.apache.myfaces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118) > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:189) > at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1147) > at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:722) > at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:449) > at com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest(ServletWrapperImpl.java:178) > at com.ibm.ws.webcontainer.filter.WebAppFilterChain.invokeTarget(WebAppFilterChain.java:125) > at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:92) > at com.intact.crm.web.filter.LoginFilter.doFilter(LoginFilter.java:56) > at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:192) > at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:89) > at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:919) > at com.ibm.ws.webcontainer.filter.WebAppFilterManager.invokeFilters(WebAppFilterManager.java:1016) > at com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleRequest(CacheServletWrapper.java:87) > at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:886) > at com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContainer.java:1655) > at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:195) > at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:452) > at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewRequest(HttpInboundLink.java:511) > at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.processRequest(HttpInboundLink.java:305) > at com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpICLReadCallback.java:83) > at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:165) > at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217) > at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161) > at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:138) > at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:204) > at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:775) > at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905) > at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1650) > Caused by: javax.el.PropertyNotFoundException: /pages/client/listClient.xhtml at line 78 and column 51 rendered="#{resultClientController.isDejaVu(client.id)}": Target Unreachable, identifier 'client' resolved to null > at org.apache.myfaces.view.facelets.el.TagValueExpression.getValue(TagValueExpression.java:89) > at javax.faces.component._DeltaStateHelper.eval(_DeltaStateHelper.java:260) > at javax.faces.component.UIComponentBase.isRendered(UIComponentBase.java:1007) > at javax.faces.component.UIComponent.isVisitable(UIComponent.java:289) > at javax.faces.component.UIComponent.visitTree(UIComponent.java:767) > at javax.faces.component.UIComponentBase.visitTree(UIComponentBase.java:991) > at javax.faces.component.UIComponent.visitTree(UIComponent.java:793) > at javax.faces.component.UIComponentBase.visitTree(UIComponentBase.java:991) > at org.richfaces.component.UIDataAdaptor.visitComponents(UIDataAdaptor.java:1259) > at org.richfaces.component.UIDataAdaptor.visitDataChildren(UIDataAdaptor.java:1286) > at org.richfaces.component.UIDataTableBase.visitDataChildren(UIDataTableBase.java:359) > at org.richfaces.component.UIDataAdaptor.visitTree(UIDataAdaptor.java:1360) > at javax.faces.component.UIComponent.visitTree(UIComponent.java:793) > at javax.faces.component.UIComponentBase.visitTree(UIComponentBase.java:991) > at javax.faces.component.UINamingContainer.visitTree(UINamingContainer.java:169) > at javax.faces.component.UIComponent.visitTree(UIComponent.java:793) > at javax.faces.component.UIComponentBase.visitTree(UIComponentBase.java:991) > at org.richfaces.component.AbstractTogglePanel.visitTree(AbstractTogglePanel.java:719) > at javax.faces.component.UIForm.visitTree(UIForm.java:269) > at javax.faces.component.UIComponent.visitTree(UIComponent.java:793) > at javax.faces.component.UIComponentBase.visitTree(UIComponentBase.java:991) > at javax.faces.component.UIComponent.visitTree(UIComponent.java:793) > at javax.faces.component.UIComponentBase.visitTree(UIComponentBase.java:991) > at org.apache.myfaces.view.facelets.tag.ui.DebugPhaseListener._doTreeVisit(DebugPhaseListener.java:310) > at org.apache.myfaces.view.facelets.tag.ui.DebugPhaseListener.afterPhase(DebugPhaseListener.java:286) > at org.apache.myfaces.lifecycle.PhaseListenerManager.informPhaseListenersAfter(PhaseListenerManager.java:111) > at org.apache.myfaces.lifecycle.LifecycleImpl.executePhase(LifecycleImpl.java:185) > ... 29 more > {code} > Please, not that the application is a single page application, everything appends inside a single page. Dynamic include is used to achieve this goal (see index.xhtml) - Tab is also dynamic except for the search. See screen shot. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 6 12:47:40 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Tue, 6 Mar 2012 12:47:40 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11884) Multiple Errors with IE8/9 In-Reply-To: <1562607854.56099.1326530722497.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <983438734.71285.1331056060059.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-11884: ------------------------------- Fix Version/s: 4.2.1.CR1 > Multiple Errors with IE8/9 > -------------------------- > > Key: RF-11884 > URL: https://issues.jboss.org/browse/RF-11884 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes, component-tables, component-tree > Environment: Windows 7 64, Tomcat 7.0.23, Mojarra 2.1.3, IE8/9 (all errors), Chrome 16.09 (one problem), PrimesFaces 2.2.1 (ChartGraphics only, problems still persist when PF is removed) > Reporter: Friedhelm Kuehn > Priority: Critical > Fix For: 4.2.1.CR1 > > Attachments: ProgramVariable_Table.xhtml, Richfaces_4.1_Problems.pdf, Richfaces_4.1_Problems_Konfiguration.pdf, Test.war > > > Problem 1: Shaded TabbedPane Tabs, not changing color when tabbing. Big spacing area below tabs (height about 20 px, should be 2px). > Problem 2: Content of not-popped-up Popup-Panel is not visible, but an area is claimed on screen. > Problem 3: with icon: Icon is surrounded by dark border > Problem 4: No Horzontal-Scroller in ExtendDatatable (with Chrome also). > Problem 5: Use of IconCollapsed/..Expanded creates double Icons in TreeNode > Problem 6: Javascript Error in ExtendedDataTable.js > Biggest Problem: We have to deliver our application in a few weeks. Support for IE8/9 is hard customer requirement. > I have a made a documentation for each problem, but don't find a way to attach a PDF to this issue - ?? > Please help ! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 6 13:26:37 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Tue, 6 Mar 2012 13:26:37 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11801) ClientValidatorImpl ClassCastException in restoreState (StateHolderSaver not an Object[]) In-Reply-To: <1599733089.80179.1323286480699.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <2093836170.71356.1331058397594.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-11801: ------------------------------- Labels: waiting_on_user (was: ) For details on how to submit an effective code sample, refer to the guide: https://community.jboss.org/wiki/SubmittingEffectiveIssueReports > ClientValidatorImpl ClassCastException in restoreState (StateHolderSaver not an Object[]) > ----------------------------------------------------------------------------------------- > > Key: RF-11801 > URL: https://issues.jboss.org/browse/RF-11801 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-validators > Affects Versions: 4.1.0.CR1 > Reporter: Giovanni Pelosi > Assignee: Jan Papousek > Labels: waiting_on_user > Attachments: abDataTemplate.xhtml, dataform.xhtml, input.xhtml > > > when i do an ajax submit on a form with inputs fields (h:inputText) > (defined in a composite component), i got this exception: > ClassCastException > in org.richfaces.component.behavior.ClientValidatorImpl.restoreState at line 357 > {code} > @Override > public void restoreState(FacesContext context, Object state) { > if (context == null) { > throw new NullPointerException(); > } > if (state != null) { > ==> Object[] values = (Object[]) state; > super.restoreState(context, values[0]); > if (values.length != 1) { > groups = (Class[]) values[1]; > // If we saved state last time, save state again next time. > clearInitialState(); > } > } > } > {code} > because state is an instance of javax.faces.component.StateHolderSaver > RF 4.1CR1 > MOJARRA 2.1.3 > JBoss 7.0.2 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 6 13:30:37 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Tue, 6 Mar 2012 13:30:37 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11950) rich:findComponent does not retrieve the component for multiply-nested, dynamically generated tab components In-Reply-To: <25533681.21797.1328288808791.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <82987916.71370.1331058637955.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-11950: ------------------------------- Summary: rich:findComponent does not retrieve the component for multiply-nested, dynamically generated tab components (was: rich:findComponent does not retrieve the component ) Fix Version/s: 4.Future Assignee: (was: J?n Jamrich) > rich:findComponent does not retrieve the component for multiply-nested, dynamically generated tab components > ------------------------------------------------------------------------------------------------------------ > > Key: RF-11950 > URL: https://issues.jboss.org/browse/RF-11950 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: base functionality > Affects Versions: 4.1.0.Final > Environment: Websphere 8 - RAD 8 - JSF Mojorra 2.1.4 - Spring 3.0.6 Final - Firefox 10.0 - Windows 7 (6.1 sp1) > Reporter: Jean ANDRE > Fix For: 4.Future > > Attachments: index.xhtml, index.xhtml, listClient.xhtml, requestClientDocument.xhtml, requestClientDocument.xhtml, tabsClient.xhtml, tabsClient.xhtml > > > The rich:findComponent does not retrieve the component - What we want to achieve is to send .click() event on a command button. We got different errors depending the tests we made such as syntax error. > The involved code: > ------------------ > {code} > > > > value="#{msg['common.command.cancel']}" > onclick="#{rich:findComponent('#{activity.id}-closeCmd')}.click();;return false;" > render="#{tab.id}-tabsClient" > immediate="true" /> > {code} > The error we got: > ---------------- > {code} > syntax error - [Stopper sur une erreur] - jsf.js.jsf?ln=javax.faces (ligne 1) > .click();return false; > {code} > The corresponding view source: > ------------------------------ > {code} > onclick="jsf.util.chain(this,event,".click();return false;", > "RichFaces.ajax( \"tabbedForm:TAB_CLIENT\\u002D1\\u002Drcd\\u002DcancelCreateCmd\",event,{\"incId\":\"1\"} )"); > return false;" > name="tabbedForm:TAB_CLIENT-1-rcd-cancelCreateCmd" id="tabbedForm:TAB_CLIENT-1-rcd-cancelCreateCmd"> > {code} > The generated javaScript under firebug: > -------------------------------------- > {code} > function onclick(event) { > jsf.util.chain(this, event, ".click();return false;", "RichFaces.ajax(\"tabbedForm:TAB_CLIENT\\u002D1\\u002Drcd\\u002DcancelCreateCmd\",event,{\"incId\":\"1\"} )"); > return false; > } > {code} > If we hard code the Id instead of the calculated one we got following error: > {code} > uncaught exception: Syntax error, unrecognized expression: TAB_CLIENT-1-TAB_RCD-closeCmd > Line 0 > {code} > The generated javaScript under firebug: > -------------------------------------- > {code} > function anonymous(event) { > rich: > findComponent("TAB_CLIENT-1-TAB_RCD-closeCmd").click(); > return false; > } > {code} > If we use directly jQuery: > {code} > > > > value="#{msg['common.command.cancel']}" > onclick="$('##{activity.id}-closeCmd').click();return false;" > render="desktopTabPanel" > immediate="true" /> > {code} > {code} > missing ; before statement > http://localhost:12000/crm/javax.faces.resource/jsf.js.jsf?ln=javax.faces > Line 1 > {code} > If we hardcode an existing static Id, we got the error as shown the screen capture: > {code} > function onclick(event) { > jsf.util.chain(this, event, "org.richfaces.component.UICommandButton at 39de2ca.click();", "RichFaces.ajax(\"tabbedForm:TAB_CLIENT\\u002D1\\u002Drcd\\u002DcancelCreateCmd\",event,{\"incId\":\"1\"} )"); > return false; > } > {code} > {code} > value="#{msg['common.command.cancel']}" > onclick="#{rich:findComponent('qsearchClient')}.click();" > render="#{tab.id}-tabsClient" > immediate="true" />  > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 6 14:18:41 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Tue, 6 Mar 2012 14:18:41 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11970) Ajax event create exception on form submission when defined on dataTable inside that form In-Reply-To: <1907532891.33570.1328789028473.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1984151675.71412.1331061521328.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-11970: ------------------------------- Fix Version/s: 4.3.0.Milestone1 Shimon - thanks for the debug work and identifying the source of the problem. If you could submit a pull request with this fix in place, that would be even better (should you be interested in doing so, check out the [Contributor Getting Started Guide|https://community.jboss.org/wiki/ContributorGettingStartedGuide]) > Ajax event create exception on form submission when defined on dataTable inside that form > ----------------------------------------------------------------------------------------- > > Key: RF-11970 > URL: https://issues.jboss.org/browse/RF-11970 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.1.0.Final > Environment: All > Reporter: shimon lifshitz > Fix For: 4.3.0.Milestone1 > > > I defined ajax support event="rowclick" on rich:dataTable. This table is defined inside a form. When I tried to submit the form (h:command). I got an exception: > {code} > Caused by: java.lang.NullPointerException > at org.richfaces.renderkit.DataTableRenderer.doDecode(DataTableRenderer.java:111) > at org.richfaces.renderkit.RendererBase.decode(RendererBase.java:80) > at javax.faces.component.UIComponentBase.decode(UIComponentBase.java:787) > {code} > Problem can be easily fixed by addind check for null in relevent line: > {code} > if (!behaviorEvent.startsWith(ROW)) { ---> > if (behaviorEvent == null ||!behaviorEvent.startsWith(ROW)) > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 6 14:20:36 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Tue, 6 Mar 2012 14:20:36 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12000) TabPanel - Backing bean initialization when a same bean manages multiple dynamic tabs In-Reply-To: <572385267.36048.1329946356737.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <573618106.71414.1331061636156.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12000: ------------------------------- Fix Version/s: 4.3-Tracking Forum Reference: https://community.jboss.org/message/718460#718460 (was: https://community.jboss.org/message/718460#718460) There is some ongoing work at the moment, investigating using a the UIRepeat mechanism to back the TabPanel, rather than a UIOutput component. This should provide a better mechanism for adding dynamic panels. > TabPanel - Backing bean initialization when a same bean manages multiple dynamic tabs > ------------------------------------------------------------------------------------- > > Key: RF-12000 > URL: https://issues.jboss.org/browse/RF-12000 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Jean ANDRE > Fix For: 4.3-Tracking > > > See the conversation : https://community.jboss.org/message/718460#718460 > Based on the work done, it is more clear about what we need. When a tabPanel, contains dynamic tabs handle by the same backing-bean (because of the same include xhtml), we need a way, a reliable manner to initialize the backing bean when the user switch from a tab to another tab. It might be a specific tag, as rich:bean init="#{.....initialize(params)}". This tab should be executed first, before any other calls of the backing bean whatever its place inside the xhtml page. If several such tags exist wherever (template, include), they must be executed in their natural order, from the deeper to the top of the page hierarchy. > So, what we need is a contextual initialization, because the @PostContruct is not well suitable for that situation and also a more simple solution rather trying to do it by the PhaseListener (and what about the context???). > Related links around of this feature: > - http://www.coderanch.com/t/213757/JSF/java/initialize-backing-bean-before-page > - http://stackoverflow.com/questions/8132394/backing-bean-initialization > - http://www.icefaces.org/JForum/posts/list/13260.page > - http://cagataycivici.wordpress.com/2006/06/06/managed_beans_aware_of_the/ > - http://boardreader.com/thread/how_to_initialize_a_backing_bean_before_w2nvX36qxy.html > Thank you -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 6 14:22:36 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Tue, 6 Mar 2012 14:22:36 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12003) Including h:head breaks f:ajax events of commandButton In-Reply-To: <135907437.40978.1330081357692.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <280625553.71417.1331061756269.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem reassigned RF-12003: ---------------------------------- Assignee: Juraj Huska Excellent work Juraj - thanks for diggin into this. If you could file an upstream issue, and close this RichFaces issue, that would excellent. > Including h:head breaks f:ajax events of commandButton > ------------------------------------------------------ > > Key: RF-12003 > URL: https://issues.jboss.org/browse/RF-12003 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: base functionality > Affects Versions: 4.1.0.Final, 4.2.0.CR1 > Environment: JBoss 7.0.2 Final, JBoss 7.1.0 Final, RichFaces 4.2.0 Final, 4.1.0 Final, Chrome and Safari > Reporter: Joern Ohmen > Assignee: Juraj Huska > Priority: Critical > Labels: Header, JSF2.0, RichFaces4 > Attachments: brokenRFHheadAdded.png > > > If I add h:head-Tag to my page, the ajax events of the h:commandButton are not working. The example should show up a panel with a click on a button, but nothing happens. The example is working when h:head is removed. I use a ConversationScoped Bean. > {code} > > > xmlns:h="http://java.sun.com/jsf/html" > xmlns:f="http://java.sun.com/jsf/core" > xmlns:ui="http://java.sun.com/jsf/facelets" > xmlns:fn="http://java.sun.com/jsp/jstl/functions" > xmlns:a4j="http://richfaces.org/a4j" > xmlns:rich="http://richfaces.org/rich"> > > Test > > > listener="#{testController.beginConversation}" /> > > > > > action="#{testController.changeRenderInputPanel}"> > > > rendered="#{testController.renderInputPanel}"> > > > > > > > > {code} > {code} > import java.io.Serializable; > import javax.enterprise.context.Conversation; > import javax.enterprise.context.ConversationScoped; > import javax.inject.Inject; > import javax.inject.Named; > import org.apache.commons.logging.Log; > @Named > @ConversationScoped > public class TestController implements Serializable{ > private static final long serialVersionUID = 1L; > > @Inject > private Conversation conversation; > > private String newCommentAuthor; > > private boolean renderInputPanel = true; > > @Inject > private Log logger; > > public boolean isRenderInputPanel() { > return renderInputPanel; > } > public void setRenderInputPanel(boolean renderInputPanel) { > this.renderInputPanel = renderInputPanel; > } > > public void changeRenderInputPanel() { > this.setRenderInputPanel(!isRenderInputPanel()); > logger.info("render panel: " + renderInputPanel); > } > public String getNewCommentAuthor() { > return newCommentAuthor; > } > public void setNewCommentAuthor(String newCommentAuthor) { > this.newCommentAuthor = newCommentAuthor; > } > public void beginConversation() { > if (conversation.isTransient()) { > conversation.setTimeout(120000); > conversation.begin(); > } > } > public void endConversation() { > if (!conversation.isTransient()) { > conversation.end(); > return; > } > } > } > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 6 14:26:36 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Tue, 6 Mar 2012 14:26:36 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12004) rich:dataTable. DataModel data & rowIndex are not synchronized when using breakRowBefore In-Reply-To: <1570155572.44239.1330333297321.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <148444614.71429.1331061996127.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12004: ------------------------------- Fix Version/s: 4.Future > rich:dataTable. DataModel data & rowIndex are not synchronized when using breakRowBefore > ---------------------------------------------------------------------------------------- > > Key: RF-12004 > URL: https://issues.jboss.org/browse/RF-12004 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.1.0.Final > Reporter: Logan MAUZAIZE > Priority: Minor > Labels: DataModel, breakRowBefore, isRowAvailable, rich:dataTable, rowData, rowIndex > Fix For: 4.Future > > > When activating breakRowBefore, the rowIndex of DataTable is using _physical_ row (TR tag) where as rowData is using _logical_ row. > It causes the following incorrect behaviors (when selecting a valid line) : > _if physical row index is greater than (or equal to) logical row count_ > * isRowAvailable() returns false > * getRowData() throws NoRowAvailableException > * Using both getRowIndex() and source data (ie from a backing-bean) causes RowIndexOutOfBoundException > _if physical row index is lower than logical row count and greather than zero_ > * getRowData() doesn't return the matching row data > * Using both getRowIndex() and source data (ie from a backing-bean) doesn't return the matching row data > Note: Row filter usage haven't been tested and may cause more unexpected behavior. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 6 14:28:36 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Tue, 6 Mar 2012 14:28:36 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12005) Issues of VDL docs in 4.2.0.Final In-Reply-To: <1573569927.44313.1330335036519.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <177465407.71432.1331062116497.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12005: ------------------------------- Fix Version/s: 4.3.0.Milestone1 Component/s: cdk > Issues of VDL docs in 4.2.0.Final > --------------------------------- > > Key: RF-12005 > URL: https://issues.jboss.org/browse/RF-12005 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: cdk, doc > Affects Versions: 4.2.0.Final > Reporter: Pavol Pitonak > Fix For: 4.3.0.Milestone1 > > > a4j:queue > * attribute onevent undocumented (shouldn't be removed?) > rich:toScript() > * what is this? it is not documented neither in Developer Guide nor in Component Reference > rich:graphValidator > * attributes groups, summary, type and value have strange description > rich:hashParam > * value false java.util.Map Not used, it is computed automatically > * shouldn't it be hidden if it is not used? > rich:notifyMessage(s) > * no component description > rich:notifyStack > * attribute position - all available options should be listed > rich:treeModelAdaptor > * no component description > rich:treeSelectionChangeListener > * no component description > rich:treeToggleListener > * no component description > rich:validator > * no component description -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 6 14:30:36 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Tue, 6 Mar 2012 14:30:36 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12006) Some of resources like jquery.focus.js and ckeditor.js are not packaged In-Reply-To: <83400370.44769.1330343496187.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <950161369.71434.1331062236183.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem reassigned RF-12006: ---------------------------------- Assignee: Luk?? Fry? To be clear, this issue deals with resource packaging wehn resourceOptimization is enabled? Is the above resource still placed in the mapping file? Does this result in the resource not getting served? Seems like a significant bug if that's the case. > Some of resources like jquery.focus.js and ckeditor.js are not packaged > ----------------------------------------------------------------------- > > Key: RF-12006 > URL: https://issues.jboss.org/browse/RF-12006 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: cdk > Affects Versions: 4.2.0.Final > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Priority: Minor > > In build of {{dist/static-resources}}, some of components are not packaged: > * {{jquery.focus.js}} > * {{ckeditor.js}} > It it not convenient to package {{ckeditor.js}}, but this issue might affect more resources. > Further investigations required. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 6 14:32:37 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Tue, 6 Mar 2012 14:32:37 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12009) Showcase: wrong look of page header in Opera Mobile In-Reply-To: <208215608.44849.1330346556934.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <694200894.71448.1331062357565.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem reassigned RF-12009: ---------------------------------- Assignee: Luk?? Fry? Lukas, so far the mobile compatibility targets Webkit based browsers. Does the rest of the mobile showcase work well in the Opera Mobile browser? If so, then it's worth addressing this issue, otherwise, we should treat Opera Mobile issues as a whole. > Showcase: wrong look of page header in Opera Mobile > --------------------------------------------------- > > Key: RF-12009 > URL: https://issues.jboss.org/browse/RF-12009 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: mobile > Affects Versions: 4.2.0.Final > Environment: http://showcase.richfaces.org/ > Opera Mobile v 12.00.ADR-1202131246 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Attachments: Android.jpg, Opera.jpg > > > The header in Opera Mobile does not have the background. > It also means the AJAX status (which is white) is not shown when loading new page. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 6 14:36:36 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Tue, 6 Mar 2012 14:36:36 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12012) rich:contextMenu re-render problem In-Reply-To: <739413833.48708.1330440217630.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1193090039.71482.1331062596937.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12674125#comment-12674125 ] Brian Leathem commented on RF-12012: ------------------------------------ Philip - thanks for taking the time to file an issue. To me this seems like a duplicate of RF-11973, with the same workaround. Can you point out anything that makes this a distinct issue? If not, I will close this issue as a duplicate, and address the problem when we address RF-11973. > rich:contextMenu re-render problem > ---------------------------------- > > Key: RF-12012 > URL: https://issues.jboss.org/browse/RF-12012 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-menu > Affects Versions: 4.2.0.Final > Environment: Apache Tomcat/7.0.23 , Mojarra 2.1.5, RichFaces 4.2.0.Final > Reporter: Philip Maes > Priority: Critical > Labels: waiting_on_user > > I have a extendedDataTable with a contextMenu attached to it. > When the selection changes on the extendedDataTable, a a4j:jsFunction is called. This jsFunction renders the contextMenu. > {quote} > onselectionchange="selChange('dtLivingCosts')" > ... > > ... > action="#{fhIndBean.selectionListener()}" > status="none" render="dtLivingCosts, contextMenu_dtLivingCosts"> > > > ... > attached="true" mode="ajax" > > ... > > {quote} > The problem is that as soon as I right-click, the contextMenu appears, the ajax request is sent and received, the view is partially updated (dtLivingCosts, contextMenu_dtLivingCosts) and then the contextMenu disappears and won't appear anymore. > I noticed that the javascript code generated by RichFaces for the contextMenu is not rerendered as you can see on these two screenshots. The first one shows the code when the page is generated for the first time. The second one, when a right-click has been done on a row in the extendedDataTable: > http://img848.imageshack.us/img848/8876/cm1j.png > http://img19.imageshack.us/img19/5170/cm2c.png > A possible workaround is to refresh only menuItems of the contextMenu (https://issues.jboss.org/browse/RF-11973). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 6 14:38:37 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Tue, 6 Mar 2012 14:38:37 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12013) Deadlock in push component In-Reply-To: <654291399.48838.1330441536575.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <765107013.71487.1331062717098.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem reassigned RF-12013: ---------------------------------- Assignee: Luk?? Fry? Lukas, please assess and schedule this issue as appropriate. > Deadlock in push component > -------------------------- > > Key: RF-12013 > URL: https://issues.jboss.org/browse/RF-12013 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Affects Versions: 4.2.0.Final > Reporter: Stian Thorgersen > Assignee: Luk?? Fry? > > Deadlocked threads in the push component prevented server from stopping. Not sure whether or not this happened when I initiated shutdown or if these where hanging around for a while. > Relevant output from jstack: > {code} > Found one Java-level deadlock: > ============================= > "push-publish-thread-1": > waiting to lock monitor 0x0000000042650238 (object 0x00000000e5ed5a50, a org.richfaces.application.push.impl.RequestImpl), > which is held by "Atmosphere-AsyncWrite-0" > "Atmosphere-AsyncWrite-0": > waiting to lock monitor 0x00000000427d9ec0 (object 0x00000000e5ed59a0, a org.richfaces.application.push.impl.SessionImpl), > which is held by "push-publish-thread-1" > Java stack information for the threads listed above: > =================================================== > "push-publish-thread-1": > at org.richfaces.application.push.impl.RequestImpl.postMessages(RequestImpl.java:85) > - waiting to lock <0x00000000e5ed5a50> (a org.richfaces.application.push.impl.RequestImpl) > at org.richfaces.application.push.impl.SessionImpl.push(SessionImpl.java:237) > - locked <0x00000000e5ed59a0> (a org.richfaces.application.push.impl.SessionImpl) > at org.richfaces.application.push.impl.TopicImpl$TopicContext.publishMessages(TopicImpl.java:88) > at org.richfaces.application.push.impl.TopicImpl$PublishTask.run(TopicImpl.java:53) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:662) > "Atmosphere-AsyncWrite-0": > at org.richfaces.application.push.impl.SessionImpl.disconnect(SessionImpl.java:117) > - waiting to lock <0x00000000e5ed59a0> (a org.richfaces.application.push.impl.SessionImpl) > at org.richfaces.application.push.impl.RequestImpl.disconnect(RequestImpl.java:107) > at org.richfaces.application.push.impl.RequestImpl.onResume(RequestImpl.java:115) > at org.atmosphere.cpr.AtmosphereResourceImpl.onResume(AtmosphereResourceImpl.java:651) > at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:600) > at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:584) > at org.atmosphere.cpr.AtmosphereResourceImpl.resume(AtmosphereResourceImpl.java:185) > - locked <0x00000000e5ee3380> (a org.atmosphere.cpr.AtmosphereResourceEventImpl) > at org.richfaces.application.push.impl.RequestImpl.onBroadcast(RequestImpl.java:129) > - locked <0x00000000e5ed5a50> (a org.richfaces.application.push.impl.RequestImpl) > at org.atmosphere.cpr.AtmosphereResourceImpl.onBroadcast(AtmosphereResourceImpl.java:663) > at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:608) > at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:584) > at org.atmosphere.cpr.DefaultBroadcaster.executeAsyncWrite(DefaultBroadcaster.java:713) > at org.atmosphere.cpr.DefaultBroadcaster$3.run(DefaultBroadcaster.java:747) > - locked <0x00000000e5ed5a88> (a org.atmosphere.cpr.AtmosphereResourceImpl) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:662) > Found 1 deadlock. > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 6 14:38:38 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Tue, 6 Mar 2012 14:38:38 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12018) Typo in BOM: jsf-api should be jsp-api In-Reply-To: <269810633.51309.1330504476269.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <80312054.71509.1331062718168.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12018: ------------------------------- Fix Version/s: 4.2.1.CR1 > Typo in BOM: jsf-api should be jsp-api > -------------------------------------- > > Key: RF-12018 > URL: https://issues.jboss.org/browse/RF-12018 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 4.2.0.Final > Reporter: Marek Novotny > Priority: Minor > Fix For: 4.2.1.CR1 > > > This typo is not causing any issue, it is just confusing. > usage of version: > https://github.com/richfaces/build/blob/4.2.0.20120215-Final/bom/pom.xml#L245 > definition of version: > https://github.com/richfaces/build/blob/4.2.0.20120215-Final/bom/pom.xml#L62 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 6 14:40:37 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Tue, 6 Mar 2012 14:40:37 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12020) Reduce number of absolute opened files In-Reply-To: <756676139.61444.1330674096251.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1015384607.71511.1331062837346.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12020: ------------------------------- Fix Version/s: 4.2.1.CR1 4.Future Assigning to 4.2.1.CR1 to address inclusion of the patch. The issue of fixing the underlying problem will be bumped to 4.Future, as this is only poses a problem building in restricted build environments. > Reduce number of absolute opened files > -------------------------------------- > > Key: RF-12020 > URL: https://issues.jboss.org/browse/RF-12020 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: cdk > Affects Versions: 4.2.0.Final > Environment: linux > Reporter: Marek Novotny > Fix For: 4.2.1.CR1, 4.Future > > Attachments: cdk-generator.patch > > > While RF Components is compiled, it normally over goes under limit for maximum open files. > I did some change which helped a little, but there will be probably bigger effect if the logic is re-factored to not open all files at the same time in generator/src/main/java/org/richfaces/cdk/templatecompiler/RendererClassGenerator.java of render method. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 6 14:42:36 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Tue, 6 Mar 2012 14:42:36 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12021) Compilation of Input UI component logs 2 errors about faces-config.xml In-Reply-To: <518462150.61467.1330674576214.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <2143113894.71516.1331062956185.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem reassigned RF-12021: ---------------------------------- Assignee: Brian Leathem > Compilation of Input UI component logs 2 errors about faces-config.xml > ---------------------------------------------------------------------- > > Key: RF-12021 > URL: https://issues.jboss.org/browse/RF-12021 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.2.0.Final > Reporter: Marek Novotny > Assignee: Brian Leathem > > Compilation of RF UI Components specifically Input UI has got 2 errors in log - related to bad faces-config.xml on line number 29 and 240. > The following is snippet of log: > {noformat} > [INFO] ------------------------------------------------------------------------ > [INFO] Building RichFaces UI Components: Input UI 4.2.0.Final > [INFO] ------------------------------------------------------------------------ > [INFO] > [INFO] --- maven-enforcer-plugin:1.0-redhat-1:enforce (enforce-java-version) @ richfaces-ui-input-ui --- > [INFO] The requirePluginVersions rule is currently not compatible with Maven3. > [INFO] > [INFO] --- maven-enforcer-plugin:1.0-redhat-1:enforce (enforce-maven-version) @ richfaces-ui-input-ui --- > [INFO] The requirePluginVersions rule is currently not compatible with Maven3. > [INFO] > [INFO] --- maven-cdk-plugin:4.2.0.Final-redhat-1:generate (cdk-generate-sources) @ richfaces-ui-input-ui --- > [Error] faces-config.xml:29:71: cvc-complex-type.2.4.a: Invalid content was found starting with element 'xi:include'. One of '{"http://java.sun.com/xml/ns/javaee":property, "http://java.sun.com/xml/ns/javaee":component-extension}' is expected. > [Error] faces-config.xml:240:71: cvc-complex-type.2.4.a: Invalid content was found starting with element 'xi:include'. One of '{"http://java.sun.com/xml/ns/javaee":property, "http://java.sun.com/xml/ns/javaee":component-extension}' is expected. > {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 6 14:42:36 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Tue, 6 Mar 2012 14:42:36 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12022) showcase - UAgentInfo is not serialized In-Reply-To: <1295764103.70688.1331047297172.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1401743521.71518.1331062956251.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12022: ------------------------------- Fix Version/s: 4.3.0.Milestone1 > showcase - UAgentInfo is not serialized > --------------------------------------- > > Key: RF-12022 > URL: https://issues.jboss.org/browse/RF-12022 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: showcase > Affects Versions: 4.2.0.Final > Environment: -showcase, > -Tomcat 6,7, > -arquillian tests > Reporter: Juraj Huska > Priority: Trivial > Fix For: 4.3.0.Milestone1 > > > When running functional tests for showcase with Arquillian on Tomcat 6 or 7, I am encountering following exception during showcase undeploying process: > {code} > WARNING: Cannot serialize session attribute userAgent for session E4F43AA62674D093726971AC8361F9F8 > java.io.NotSerializableException: org.richfaces.demo.ui.UAgentInfo > at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1164) > at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1518) > at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1483) > at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1400) > at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1158) > at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:330) > at org.apache.catalina.session.StandardSession.writeObject(StandardSession.java:1585) > at org.apache.catalina.session.StandardSession.writeObjectData(StandardSession.java:1015) > at org.apache.catalina.session.StandardManager.doUnload(StandardManager.java:528) > at org.apache.catalina.session.StandardManager.unload(StandardManager.java:469) > at org.apache.catalina.session.StandardManager.stop(StandardManager.java:678) > at org.apache.catalina.core.StandardContext.stop(StandardContext.java:4882) > at org.apache.catalina.manager.ManagerServlet.undeploy(ManagerServlet.java:1390) > at org.apache.catalina.manager.ManagerServlet.doGet(ManagerServlet.java:382) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:617) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) > at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:563) > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293) > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:859) > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:602) > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489) > at java.lang.Thread.run(Thread.java:662) > {code} > UAgentInfo is used by UserAgentProcessor(session scoped bean) and therefore IMHO should be serialized. When I made it serialize-able, the exception disappeared. I did not notice any broken functionality by this exception, and same for the fixed one showcase, only cleaner test output. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 6 14:42:36 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Tue, 6 Mar 2012 14:42:36 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12023) comboBox in dataTable In-Reply-To: <1186358326.70819.1331048742987.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1626382553.71521.1331062956355.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12023: ------------------------------- Fix Version/s: 4.3-Tracking > comboBox in dataTable > ---------------------- > > Key: RF-12023 > URL: https://issues.jboss.org/browse/RF-12023 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects, component-tables > Affects Versions: 4.1.0.Final > Environment: All > Reporter: Bertrand P > Labels: richfaces > Fix For: 4.3-Tracking > > Original Estimate: 1 day, 4 hours > Remaining Estimate: 1 day, 4 hours > > When a is in a of a , the row is selected when comboBox is selected. > A workaround is: , but that doesn't work when the arrow is clicked. > Because the arrow is generated in an independent span: > > > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 6 15:19:40 2012 From: jira-events at lists.jboss.org (RH Bugzilla Integration (JIRA)) Date: Tue, 6 Mar 2012 15:19:40 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12019) Upstream mojarra issue requires IE9 to be in compatibility mode In-Reply-To: <676753656.53754.1330535076071.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1078416747.71647.1331065180115.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] RH Bugzilla Integration updated RF-12019: ----------------------------------------- Bugzilla Update: Perform > Upstream mojarra issue requires IE9 to be in compatibility mode > --------------------------------------------------------------- > > Key: RF-12019 > URL: https://issues.jboss.org/browse/RF-12019 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: third-party > Reporter: Brian Leathem > Fix For: 4.3-Tracking > > > An upstream issue with mojarra ([JAVASERVERFACES-2063|http://java.net/jira/browse/JAVASERVERFACES-2063]) requires that IE9 be placed in compatibility mode. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 6 15:19:40 2012 From: jira-events at lists.jboss.org (RH Bugzilla Integration (JIRA)) Date: Tue, 6 Mar 2012 15:19:40 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12019) Upstream mojarra issue requires IE9 to be in compatibility mode In-Reply-To: <676753656.53754.1330535076071.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <266173146.71649.1331065180197.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] RH Bugzilla Integration updated RF-12019: ----------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=800628 > Upstream mojarra issue requires IE9 to be in compatibility mode > --------------------------------------------------------------- > > Key: RF-12019 > URL: https://issues.jboss.org/browse/RF-12019 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: third-party > Reporter: Brian Leathem > Fix For: 4.3-Tracking > > > An upstream issue with mojarra ([JAVASERVERFACES-2063|http://java.net/jira/browse/JAVASERVERFACES-2063]) requires that IE9 be placed in compatibility mode. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 6 15:40:36 2012 From: jira-events at lists.jboss.org (RH Bugzilla Integration (JIRA)) Date: Tue, 6 Mar 2012 15:40:36 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12019) Upstream mojarra issue requires IE9 to be in compatibility mode In-Reply-To: <676753656.53754.1330535076071.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <859971843.71768.1331066436245.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12674159#comment-12674159 ] RH Bugzilla Integration commented on RF-12019: ---------------------------------------------- Brian Leathem made a comment on [bug 800628|https://bugzilla.redhat.com/show_bug.cgi?id=800628] Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: An upstream issue (http://java.net/jira/browse/JAVASERVERFACES-2063) requires IE 9 to be run in compatibility mode. This can be accomplished by adding a meta tag to your page template, as described in: http://msdn.microsoft.com/en-us/library/cc288325(v=vs.85).aspx#SetMode. > Upstream mojarra issue requires IE9 to be in compatibility mode > --------------------------------------------------------------- > > Key: RF-12019 > URL: https://issues.jboss.org/browse/RF-12019 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: third-party > Reporter: Brian Leathem > Fix For: 4.3-Tracking > > > An upstream issue with mojarra ([JAVASERVERFACES-2063|http://java.net/jira/browse/JAVASERVERFACES-2063]) requires that IE9 be placed in compatibility mode. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 6 17:38:36 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 6 Mar 2012 17:38:36 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11994) Xcss2EcssConverter error handling f:importResource In-Reply-To: <377878399.29898.1329814962021.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <698617468.72065.1331073516313.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated RF-11994: ---------------------------- Git Pull Request: https://github.com/richfaces/core/pull/7 > Xcss2EcssConverter error handling f:importResource > -------------------------------------------------- > > Key: RF-11994 > URL: https://issues.jboss.org/browse/RF-11994 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.2.0.CR1 > Reporter: Dupont Dupont > Assignee: Dupont Dupont > > When using Xcss2EcssConverter to transform xcss to ecss, I've the following error : > Source xcss : > {code:xml} > > {code} > Is transformed to : > {noformat} > @import url("#{resource['META-INF/skins/charte/commun/css/sx_commun.ecss']"} > {noformat} > It should be : > {noformat} > @import url("#{resource['META-INF/skins/charte/commun/css/sx_commun.ecss']}"); > {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 6 17:41:36 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 6 Mar 2012 17:41:36 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11994) Xcss2EcssConverter error handling f:importResource In-Reply-To: <377878399.29898.1329814962021.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <487613147.72071.1331073696958.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12674200#comment-12674200 ] Luk?? Fry? edited comment on RF-11994 at 3/6/12 5:41 PM: --------------------------------------------------------- The pull request has been reviewed and merged. Thanks for your efforts! was (Author: lfryc): The pull request has been reviewed and merge. Thanks for your efforts! > Xcss2EcssConverter error handling f:importResource > -------------------------------------------------- > > Key: RF-11994 > URL: https://issues.jboss.org/browse/RF-11994 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.2.0.CR1 > Reporter: Dupont Dupont > Assignee: Dupont Dupont > Fix For: 4.3.0.Milestone1 > > > When using Xcss2EcssConverter to transform xcss to ecss, I've the following error : > Source xcss : > {code:xml} > > {code} > Is transformed to : > {noformat} > @import url("#{resource['META-INF/skins/charte/commun/css/sx_commun.ecss']"} > {noformat} > It should be : > {noformat} > @import url("#{resource['META-INF/skins/charte/commun/css/sx_commun.ecss']}"); > {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 6 18:50:37 2012 From: jira-events at lists.jboss.org (Karsten Wutzke (JIRA)) Date: Tue, 6 Mar 2012 18:50:37 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11592) RichFaces 4.1 Milestone changes for fileUpload component incompatible with Apache MyFaces Orchestra conversation scope In-Reply-To: <1839758620.29810.1319638185453.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <948204292.72295.1331077837221.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12674228#comment-12674228 ] Karsten Wutzke commented on RF-11592: ------------------------------------- I also get this exception: {code}org.richfaces.exception.FileUploadException: Exception parsing multipart request: Request prolog cannot be read at org.richfaces.request.MultipartRequestParser.parse(MultipartRequestParser.java:156) at org.richfaces.request.MultipartRequest25.parseIfNecessary(MultipartRequest25.java:77) at org.richfaces.request.MultipartRequest25.getParameter(MultipartRequest25.java:114) at com.sun.faces.context.RequestParameterMap.containsKey(RequestParameterMap.java:99) at java.util.Collections$UnmodifiableMap.containsKey(Collections.java:1337) at org.jboss.weld.jsf.WeldPhaseListener.getConversationId(WeldPhaseListener.java:171) at org.jboss.weld.jsf.WeldPhaseListener.activateConversations(WeldPhaseListener.java:99) at org.jboss.weld.jsf.WeldPhaseListener.beforePhase(WeldPhaseListener.java:85) at com.sun.faces.lifecycle.Phase.handleBeforePhase(Phase.java:228) at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:99) at com.sun.faces.lifecycle.RestoreViewPhase.doPhase(RestoreViewPhase.java:116) at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:593) at org.apache.catalina.core.StandardWrapper.service(StandardWrapper.java:1542) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:343) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:217) at org.jboss.solder.servlet.exception.CatchExceptionFilter.doFilter(CatchExceptionFilter.java:65) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:256) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:217) at org.jboss.solder.servlet.event.ServletEventBridgeFilter.doFilter(ServletEventBridgeFilter.java:74) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:256) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:217) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:279) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:655) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:595) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:161) at org.apache.catalina.connector.CoyoteAdapter.doService(CoyoteAdapter.java:331) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:231) at com.sun.enterprise.v3.services.impl.ContainerMapper$AdapterCallable.call(ContainerMapper.java:317) at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:195) at com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:849) at com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:746) at com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:1045) at com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:228) at com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:137) at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:104) at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:90) at com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:79) at com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:54) at com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:59) at com.sun.grizzly.ContextTask.run(ContextTask.java:71) at com.sun.grizzly.util.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:532) at com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:513) at java.lang.Thread.run(Thread.java:722) Caused by: java.io.IOException: Request prolog cannot be read at org.richfaces.request.MultipartRequestParser.readProlog(MultipartRequestParser.java:270) at org.richfaces.request.MultipartRequestParser.initialize(MultipartRequestParser.java:172) at org.richfaces.request.MultipartRequestParser.parse(MultipartRequestParser.java:148) ... 44 more{code} {code}java.lang.NullPointerException at com.sun.faces.context.PartialViewContextImpl.createPartialResponseWriter(PartialViewContextImpl.java:441) at com.sun.faces.context.PartialViewContextImpl.access$300(PartialViewContextImpl.java:71) at com.sun.faces.context.PartialViewContextImpl$DelayedInitPartialResponseWriter.getWrapped(PartialViewContextImpl.java:582) at javax.faces.context.PartialResponseWriter.startDocument(PartialResponseWriter.java:115) at com.sun.faces.context.AjaxExceptionHandlerImpl.handlePartialResponseError(AjaxExceptionHandlerImpl.java:199) at com.sun.faces.context.AjaxExceptionHandlerImpl.handle(AjaxExceptionHandlerImpl.java:123) at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:119) at com.sun.faces.lifecycle.RestoreViewPhase.doPhase(RestoreViewPhase.java:116) at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:593) at org.apache.catalina.core.StandardWrapper.service(StandardWrapper.java:1542) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:343) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:217) at org.jboss.solder.servlet.exception.CatchExceptionFilter.doFilter(CatchExceptionFilter.java:65) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:256) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:217) at org.jboss.solder.servlet.event.ServletEventBridgeFilter.doFilter(ServletEventBridgeFilter.java:74) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:256) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:217) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:279) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:655) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:595) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:161) at org.apache.catalina.connector.CoyoteAdapter.doService(CoyoteAdapter.java:331) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:231) at com.sun.enterprise.v3.services.impl.ContainerMapper$AdapterCallable.call(ContainerMapper.java:317) at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:195) at com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:849) at com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:746) at com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:1045) at com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:228) at com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:137) at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:104) at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:90) at com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:79) at com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:54) at com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:59) at com.sun.grizzly.ContextTask.run(ContextTask.java:71) at com.sun.grizzly.util.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:532) at com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:513) at java.lang.Thread.run(Thread.java:722){code} I'm using Windows 7, GlassFish 3.1.2, Mojarra 2.1.6 (SNAPSHOT 20111206), RichFaces 4.1.0.Final using *Firefox 12 Aurora* 12.0a2 (2012-02-14) I doubt this has to do with Myfaces. > RichFaces 4.1 Milestone changes for fileUpload component incompatible with Apache MyFaces Orchestra conversation scope > ---------------------------------------------------------------------------------------------------------------------- > > Key: RF-11592 > URL: https://issues.jboss.org/browse/RF-11592 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.1.0.Milestone1, 4.1.0.Milestone2, 4.1.0.Milestone3 > Environment: Mojarra 2.1.3, JBoss AS 5.0.1, Apache MyFaces Orchestra 1.4, Spring 3.0.4 > Reporter: Joshua Brookes > Labels: fileUpload, multipart/form-data, orchestra, regression, richfaces, richfaces4 > Fix For: 4.3-Tracking > > Attachments: fileUploadWeb.zip > > > There is a compatibility issue with recent changes in RichFaces 4.1 Milestone 1 and Apache MyFaces Orchestra conversation scope feature. When including the Orchestra jar in the application the fileUpload component stops working. Orchestra bundles a faces-config.xml that enables 2 FacesContext Factories and multiple PhaseListeners. This did not pose a problem with RichFaces 4.0.0.Final. > Here is a stacktrace that shows the error: > {code} > Oct 25, 2011 11:45:01 AM org.richfaces.request.MultipartRequest25 parseIfNecessary > SEVERE: Exception parsing multipart request: Request prolog cannot be read > org.richfaces.exception.FileUploadException: Exception parsing multipart request: Request prolog cannot be read > at org.richfaces.request.MultipartRequestParser.parse(MultipartRequestParser.java:156) > at org.richfaces.request.MultipartRequest25.parseIfNecessary(MultipartRequest25.java:77) > at org.richfaces.request.MultipartRequest25.getParameter(MultipartRequest25.java:114) > at com.sun.faces.context.RequestParameterMap.containsKey(RequestParameterMap.java:99) > at java.util.Collections$UnmodifiableMap.containsKey(Collections.java:1280) > at org.apache.myfaces.orchestra.frameworkAdapter.jsf.JsfFrameworkAdapter.containsRequestParameterAttribute(JsfFrameworkAdapter.java:105) > at org.apache.myfaces.orchestra.conversation.ConversationManager.findConversationContextId(ConversationManager.java:169) > at org.apache.myfaces.orchestra.conversation.ConversationManager.getCurrentRootConversationContext(ConversationManager.java:580) > at org.apache.myfaces.orchestra.lib.jsf.ContextLockRequestHandler.init(ContextLockRequestHandler.java:87) > at org.apache.myfaces.orchestra.lib.jsf.OrchestraFacesContextFactory$1.(OrchestraFacesContextFactory.java:122) > at org.apache.myfaces.orchestra.lib.jsf.OrchestraFacesContextFactory.getFacesContext(OrchestraFacesContextFactory.java:103) > at org.apache.myfaces.orchestra.requestParameterProvider.jsf.RequestParameterFacesContextFactory.getFacesContext(RequestParameterFacesContextFactory.java:93) > at org.richfaces.context.FileUploadFacesContextFactory.getFacesContext(FileUploadFacesContextFactory.java:136) > at com.sun.faces.context.InjectionFacesContextFactory.getFacesContext(InjectionFacesContextFactory.java:121) > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:583) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:638) > at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:446) > at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:382) > at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:310) > at org.apache.catalina.core.StandardHostValve.custom(StandardHostValve.java:416) > at org.apache.catalina.core.StandardHostValve.status(StandardHostValve.java:342) > at org.apache.catalina.core.StandardHostValve.throwable(StandardHostValve.java:286) > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:141) > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) > at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330) > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829) > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:598) > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) > at java.lang.Thread.run(Thread.java:619) > Caused by: java.io.IOException: Request prolog cannot be read > at org.richfaces.request.MultipartRequestParser.readProlog(MultipartRequestParser.java:270) > at org.richfaces.request.MultipartRequestParser.initialize(MultipartRequestParser.java:172) > at org.richfaces.request.MultipartRequestParser.parse(MultipartRequestParser.java:148) > ... 32 more > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 6 18:52:36 2012 From: jira-events at lists.jboss.org (Karsten Wutzke (JIRA)) Date: Tue, 6 Mar 2012 18:52:36 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11592) RichFaces 4.1 Milestone changes for fileUpload component incompatible with Apache MyFaces Orchestra conversation scope In-Reply-To: <1839758620.29810.1319638185453.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <262783936.72301.1331077956870.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karsten Wutzke updated RF-11592: -------------------------------- Attachment: server.log GlassFish server.log > RichFaces 4.1 Milestone changes for fileUpload component incompatible with Apache MyFaces Orchestra conversation scope > ---------------------------------------------------------------------------------------------------------------------- > > Key: RF-11592 > URL: https://issues.jboss.org/browse/RF-11592 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.1.0.Milestone1, 4.1.0.Milestone2, 4.1.0.Milestone3 > Environment: Mojarra 2.1.3, JBoss AS 5.0.1, Apache MyFaces Orchestra 1.4, Spring 3.0.4 > Reporter: Joshua Brookes > Labels: fileUpload, multipart/form-data, orchestra, regression, richfaces, richfaces4 > Fix For: 4.3-Tracking > > Attachments: fileUploadWeb.zip, server.log > > > There is a compatibility issue with recent changes in RichFaces 4.1 Milestone 1 and Apache MyFaces Orchestra conversation scope feature. When including the Orchestra jar in the application the fileUpload component stops working. Orchestra bundles a faces-config.xml that enables 2 FacesContext Factories and multiple PhaseListeners. This did not pose a problem with RichFaces 4.0.0.Final. > Here is a stacktrace that shows the error: > {code} > Oct 25, 2011 11:45:01 AM org.richfaces.request.MultipartRequest25 parseIfNecessary > SEVERE: Exception parsing multipart request: Request prolog cannot be read > org.richfaces.exception.FileUploadException: Exception parsing multipart request: Request prolog cannot be read > at org.richfaces.request.MultipartRequestParser.parse(MultipartRequestParser.java:156) > at org.richfaces.request.MultipartRequest25.parseIfNecessary(MultipartRequest25.java:77) > at org.richfaces.request.MultipartRequest25.getParameter(MultipartRequest25.java:114) > at com.sun.faces.context.RequestParameterMap.containsKey(RequestParameterMap.java:99) > at java.util.Collections$UnmodifiableMap.containsKey(Collections.java:1280) > at org.apache.myfaces.orchestra.frameworkAdapter.jsf.JsfFrameworkAdapter.containsRequestParameterAttribute(JsfFrameworkAdapter.java:105) > at org.apache.myfaces.orchestra.conversation.ConversationManager.findConversationContextId(ConversationManager.java:169) > at org.apache.myfaces.orchestra.conversation.ConversationManager.getCurrentRootConversationContext(ConversationManager.java:580) > at org.apache.myfaces.orchestra.lib.jsf.ContextLockRequestHandler.init(ContextLockRequestHandler.java:87) > at org.apache.myfaces.orchestra.lib.jsf.OrchestraFacesContextFactory$1.(OrchestraFacesContextFactory.java:122) > at org.apache.myfaces.orchestra.lib.jsf.OrchestraFacesContextFactory.getFacesContext(OrchestraFacesContextFactory.java:103) > at org.apache.myfaces.orchestra.requestParameterProvider.jsf.RequestParameterFacesContextFactory.getFacesContext(RequestParameterFacesContextFactory.java:93) > at org.richfaces.context.FileUploadFacesContextFactory.getFacesContext(FileUploadFacesContextFactory.java:136) > at com.sun.faces.context.InjectionFacesContextFactory.getFacesContext(InjectionFacesContextFactory.java:121) > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:583) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:638) > at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:446) > at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:382) > at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:310) > at org.apache.catalina.core.StandardHostValve.custom(StandardHostValve.java:416) > at org.apache.catalina.core.StandardHostValve.status(StandardHostValve.java:342) > at org.apache.catalina.core.StandardHostValve.throwable(StandardHostValve.java:286) > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:141) > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) > at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330) > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829) > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:598) > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) > at java.lang.Thread.run(Thread.java:619) > Caused by: java.io.IOException: Request prolog cannot be read > at org.richfaces.request.MultipartRequestParser.readProlog(MultipartRequestParser.java:270) > at org.richfaces.request.MultipartRequestParser.initialize(MultipartRequestParser.java:172) > at org.richfaces.request.MultipartRequestParser.parse(MultipartRequestParser.java:148) > ... 32 more > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 6 18:52:37 2012 From: jira-events at lists.jboss.org (Karsten Wutzke (JIRA)) Date: Tue, 6 Mar 2012 18:52:37 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11592) RichFaces 4.1 Milestone changes for fileUpload component incompatible with Apache MyFaces Orchestra conversation scope In-Reply-To: <1839758620.29810.1319638185453.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <559793704.72306.1331077957149.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12674230#comment-12674230 ] Karsten Wutzke commented on RF-11592: ------------------------------------- Note I can provide a webapp that demonstrates the problem, however I cannot make it public. Please PM me. > RichFaces 4.1 Milestone changes for fileUpload component incompatible with Apache MyFaces Orchestra conversation scope > ---------------------------------------------------------------------------------------------------------------------- > > Key: RF-11592 > URL: https://issues.jboss.org/browse/RF-11592 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.1.0.Milestone1, 4.1.0.Milestone2, 4.1.0.Milestone3 > Environment: Mojarra 2.1.3, JBoss AS 5.0.1, Apache MyFaces Orchestra 1.4, Spring 3.0.4 > Reporter: Joshua Brookes > Labels: fileUpload, multipart/form-data, orchestra, regression, richfaces, richfaces4 > Fix For: 4.3-Tracking > > Attachments: fileUploadWeb.zip, server.log > > > There is a compatibility issue with recent changes in RichFaces 4.1 Milestone 1 and Apache MyFaces Orchestra conversation scope feature. When including the Orchestra jar in the application the fileUpload component stops working. Orchestra bundles a faces-config.xml that enables 2 FacesContext Factories and multiple PhaseListeners. This did not pose a problem with RichFaces 4.0.0.Final. > Here is a stacktrace that shows the error: > {code} > Oct 25, 2011 11:45:01 AM org.richfaces.request.MultipartRequest25 parseIfNecessary > SEVERE: Exception parsing multipart request: Request prolog cannot be read > org.richfaces.exception.FileUploadException: Exception parsing multipart request: Request prolog cannot be read > at org.richfaces.request.MultipartRequestParser.parse(MultipartRequestParser.java:156) > at org.richfaces.request.MultipartRequest25.parseIfNecessary(MultipartRequest25.java:77) > at org.richfaces.request.MultipartRequest25.getParameter(MultipartRequest25.java:114) > at com.sun.faces.context.RequestParameterMap.containsKey(RequestParameterMap.java:99) > at java.util.Collections$UnmodifiableMap.containsKey(Collections.java:1280) > at org.apache.myfaces.orchestra.frameworkAdapter.jsf.JsfFrameworkAdapter.containsRequestParameterAttribute(JsfFrameworkAdapter.java:105) > at org.apache.myfaces.orchestra.conversation.ConversationManager.findConversationContextId(ConversationManager.java:169) > at org.apache.myfaces.orchestra.conversation.ConversationManager.getCurrentRootConversationContext(ConversationManager.java:580) > at org.apache.myfaces.orchestra.lib.jsf.ContextLockRequestHandler.init(ContextLockRequestHandler.java:87) > at org.apache.myfaces.orchestra.lib.jsf.OrchestraFacesContextFactory$1.(OrchestraFacesContextFactory.java:122) > at org.apache.myfaces.orchestra.lib.jsf.OrchestraFacesContextFactory.getFacesContext(OrchestraFacesContextFactory.java:103) > at org.apache.myfaces.orchestra.requestParameterProvider.jsf.RequestParameterFacesContextFactory.getFacesContext(RequestParameterFacesContextFactory.java:93) > at org.richfaces.context.FileUploadFacesContextFactory.getFacesContext(FileUploadFacesContextFactory.java:136) > at com.sun.faces.context.InjectionFacesContextFactory.getFacesContext(InjectionFacesContextFactory.java:121) > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:583) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:638) > at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:446) > at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:382) > at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:310) > at org.apache.catalina.core.StandardHostValve.custom(StandardHostValve.java:416) > at org.apache.catalina.core.StandardHostValve.status(StandardHostValve.java:342) > at org.apache.catalina.core.StandardHostValve.throwable(StandardHostValve.java:286) > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:141) > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) > at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330) > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829) > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:598) > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) > at java.lang.Thread.run(Thread.java:619) > Caused by: java.io.IOException: Request prolog cannot be read > at org.richfaces.request.MultipartRequestParser.readProlog(MultipartRequestParser.java:270) > at org.richfaces.request.MultipartRequestParser.initialize(MultipartRequestParser.java:172) > at org.richfaces.request.MultipartRequestParser.parse(MultipartRequestParser.java:148) > ... 32 more > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 6 18:56:36 2012 From: jira-events at lists.jboss.org (Karsten Wutzke (JIRA)) Date: Tue, 6 Mar 2012 18:56:36 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11592) RichFaces 4.1 Milestone changes for fileUpload component incompatible with Apache MyFaces Orchestra conversation scope In-Reply-To: <1839758620.29810.1319638185453.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <2034606744.72320.1331078196510.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12674229#comment-12674229 ] Karsten Wutzke edited comment on RF-11592 at 3/6/12 6:56 PM: ------------------------------------------------------------- GlassFish server.log attached was (Author: kwutzke): GlassFish server.log > RichFaces 4.1 Milestone changes for fileUpload component incompatible with Apache MyFaces Orchestra conversation scope > ---------------------------------------------------------------------------------------------------------------------- > > Key: RF-11592 > URL: https://issues.jboss.org/browse/RF-11592 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.1.0.Milestone1, 4.1.0.Milestone2, 4.1.0.Milestone3 > Environment: Mojarra 2.1.3, JBoss AS 5.0.1, Apache MyFaces Orchestra 1.4, Spring 3.0.4 > Reporter: Joshua Brookes > Labels: fileUpload, multipart/form-data, orchestra, regression, richfaces, richfaces4 > Fix For: 4.3-Tracking > > Attachments: fileUploadWeb.zip, server.log > > > There is a compatibility issue with recent changes in RichFaces 4.1 Milestone 1 and Apache MyFaces Orchestra conversation scope feature. When including the Orchestra jar in the application the fileUpload component stops working. Orchestra bundles a faces-config.xml that enables 2 FacesContext Factories and multiple PhaseListeners. This did not pose a problem with RichFaces 4.0.0.Final. > Here is a stacktrace that shows the error: > {code} > Oct 25, 2011 11:45:01 AM org.richfaces.request.MultipartRequest25 parseIfNecessary > SEVERE: Exception parsing multipart request: Request prolog cannot be read > org.richfaces.exception.FileUploadException: Exception parsing multipart request: Request prolog cannot be read > at org.richfaces.request.MultipartRequestParser.parse(MultipartRequestParser.java:156) > at org.richfaces.request.MultipartRequest25.parseIfNecessary(MultipartRequest25.java:77) > at org.richfaces.request.MultipartRequest25.getParameter(MultipartRequest25.java:114) > at com.sun.faces.context.RequestParameterMap.containsKey(RequestParameterMap.java:99) > at java.util.Collections$UnmodifiableMap.containsKey(Collections.java:1280) > at org.apache.myfaces.orchestra.frameworkAdapter.jsf.JsfFrameworkAdapter.containsRequestParameterAttribute(JsfFrameworkAdapter.java:105) > at org.apache.myfaces.orchestra.conversation.ConversationManager.findConversationContextId(ConversationManager.java:169) > at org.apache.myfaces.orchestra.conversation.ConversationManager.getCurrentRootConversationContext(ConversationManager.java:580) > at org.apache.myfaces.orchestra.lib.jsf.ContextLockRequestHandler.init(ContextLockRequestHandler.java:87) > at org.apache.myfaces.orchestra.lib.jsf.OrchestraFacesContextFactory$1.(OrchestraFacesContextFactory.java:122) > at org.apache.myfaces.orchestra.lib.jsf.OrchestraFacesContextFactory.getFacesContext(OrchestraFacesContextFactory.java:103) > at org.apache.myfaces.orchestra.requestParameterProvider.jsf.RequestParameterFacesContextFactory.getFacesContext(RequestParameterFacesContextFactory.java:93) > at org.richfaces.context.FileUploadFacesContextFactory.getFacesContext(FileUploadFacesContextFactory.java:136) > at com.sun.faces.context.InjectionFacesContextFactory.getFacesContext(InjectionFacesContextFactory.java:121) > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:583) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:638) > at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:446) > at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:382) > at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:310) > at org.apache.catalina.core.StandardHostValve.custom(StandardHostValve.java:416) > at org.apache.catalina.core.StandardHostValve.status(StandardHostValve.java:342) > at org.apache.catalina.core.StandardHostValve.throwable(StandardHostValve.java:286) > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:141) > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) > at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330) > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829) > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:598) > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) > at java.lang.Thread.run(Thread.java:619) > Caused by: java.io.IOException: Request prolog cannot be read > at org.richfaces.request.MultipartRequestParser.readProlog(MultipartRequestParser.java:270) > at org.richfaces.request.MultipartRequestParser.initialize(MultipartRequestParser.java:172) > at org.richfaces.request.MultipartRequestParser.parse(MultipartRequestParser.java:148) > ... 32 more > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 6 19:20:37 2012 From: jira-events at lists.jboss.org (Karsten Wutzke (JIRA)) Date: Tue, 6 Mar 2012 19:20:37 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-10128) File upload doesn't work with MyFaces In-Reply-To: <762375458.40353.1294228517967.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1789604945.72353.1331079637237.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-10128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12674235#comment-12674235 ] Karsten Wutzke commented on RF-10128: ------------------------------------- I'm facing https://issues.jboss.org/browse/RF-11592 without any MyFaces stuff. > File upload doesn't work with MyFaces > ------------------------------------- > > Key: RF-10128 > URL: https://issues.jboss.org/browse/RF-10128 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.0.0.Milestone5 > Environment: RichFaces 4.0.0.20101226-M5 r.20800 > Metamer 4.0.0.20110104-M5 r.20882 > Apache MyFaces JSF-2.0 Core Impl 2.0.2 > Apache Tomcat 6.0.29 > OpenJDK Runtime Environment 1.6.0_20-b20 @Linux > Chrome 8.0.552.224 @ Linux x86_64 > Reporter: Pavol Pitonak > Priority: Critical > Labels: myfaces > Fix For: 4.3.0.Milestone1 > > Attachments: fileUpload.png > > > 1. deploy Metamer > 2. open http://localhost:8080/metamer/faces/components/richFileUpload/simple.xhtml > 3. select some file > 4. click Upload > result: > nothing is uploaded, no other files can be uploaded -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 6 19:27:36 2012 From: jira-events at lists.jboss.org (Artur Mioduszewski (JIRA)) Date: Tue, 6 Mar 2012 19:27:36 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12024) rich:dataGrid component and a4j:status don't cooperate together Message-ID: <953422806.72367.1331080056746.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Artur Mioduszewski created RF-12024: --------------------------------------- Summary: rich:dataGrid component and a4j:status don't cooperate together Key: RF-12024 URL: https://issues.jboss.org/browse/RF-12024 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.2.0.Final, 4.1.0.Final Environment: JDK1.6, JBoss 6.0.Final, richfaces 4.1.Final/4.2.Final Reporter: Artur Mioduszewski rich:dataGrid component and a4j:status don't cooperate together. 1. PROBLEM: After clicking a4j:commandLink inside rich:dataGrid, rich:dataGrid behaves properly, but a4j:status component is not able to hide. 2. When I remove a4j:status component, everything is OK (but rerendering rich:dataGrid is taking a while, so I would like to get a4j:status component functionality on page) 3. a4j:commandButton present at that page (not shown in below code extract) cooperate to a4j:status corectly ------------------------- EXTRACT OF MY CODE: --------------------------------------------------------------------------- ----------------------------------------------------------------------------------------------------------------------- -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 6 19:29:36 2012 From: jira-events at lists.jboss.org (Artur Mioduszewski (JIRA)) Date: Tue, 6 Mar 2012 19:29:36 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12024) rich:dataGrid component and a4j:status don't cooperate together In-Reply-To: <953422806.72367.1331080056746.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <357261935.72378.1331080176158.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artur Mioduszewski updated RF-12024: ------------------------------------ Environment: JDK1.6, JBoss 6.0.Final, richfaces 4.1.0.Final/4.2.0.Final was: JDK1.6, JBoss 6.0.Final, richfaces 4.1.Final/4.2.Final > rich:dataGrid component and a4j:status don't cooperate together > --------------------------------------------------------------- > > Key: RF-12024 > URL: https://issues.jboss.org/browse/RF-12024 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.1.0.Final, 4.2.0.Final > Environment: JDK1.6, > JBoss 6.0.Final, > richfaces 4.1.0.Final/4.2.0.Final > Reporter: Artur Mioduszewski > > rich:dataGrid component and a4j:status don't cooperate together. > 1. PROBLEM: After clicking a4j:commandLink inside rich:dataGrid, rich:dataGrid behaves properly, but a4j:status component is not able to hide. > 2. When I remove a4j:status component, everything is OK (but rerendering rich:dataGrid is taking a while, so I would like to get a4j:status component functionality on page) > 3. a4j:commandButton present at that page (not shown in below code extract) cooperate to a4j:status corectly > ------------------------- EXTRACT OF MY CODE: --------------------------------------------------------------------------- > > columns="7" elements="168" styleClass="noPaddings"> > > > > > > > > > > > > > ----------------------------------------------------------------------------------------------------------------------- -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 6 19:54:40 2012 From: jira-events at lists.jboss.org (Artur Mioduszewski (JIRA)) Date: Tue, 6 Mar 2012 19:54:40 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12025) [rich:tabPanel] Switching tabs doesn't work correctly Message-ID: <564356619.72400.1331081680333.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Artur Mioduszewski created RF-12025: --------------------------------------- Summary: [rich:tabPanel] Switching tabs doesn't work correctly Key: RF-12025 URL: https://issues.jboss.org/browse/RF-12025 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.2.0.Final, 4.1.0.Final Environment: JDK1.6, JBoss 6.0.Final, richfaces 4.1.0.Final/4.2.0.Final Reporter: Artur Mioduszewski STEPS TO REPRODUCE A PROBLEM: 1. Switch tab: UserDataTab -> UserEmailTab (look on JBoss console) 2. Switch tab: UserEmailTab -> UserDataTab (look on JBoss console) 3. Switch tab: UserDataTab -> UserEmailTab (look on JBoss console) 4. Switch tab: UserEmailTab -> UserDataTab (look on JBoss console) 5. Switch tab: UserDataTab -> UserEmailTab (look on JBoss console) 6. Switch tab: UserEmailTab -> UserDataTab (look on JBoss console) ... Every tab switching caused more (perhaps 2 times more) calling of logger.debug("----preRenderHomeView"); ============================================================================================================================== ------------------------- XHTML FILE CODE EXTRACT: --------------------------------------------------------------------------- -------------------------------------------------------------------------------------------------------- HomeAction: public void preRenderHomeView() { logger.debug("----preRenderHomeView"); } -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 6 20:20:36 2012 From: jira-events at lists.jboss.org (Artur Mioduszewski (JIRA)) Date: Tue, 6 Mar 2012 20:20:36 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12024) rich:dataGrid component and a4j:status don't cooperate together In-Reply-To: <953422806.72367.1331080056746.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1019240402.72424.1331083236376.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artur Mioduszewski updated RF-12024: ------------------------------------ Description: rich:dataGrid component and a4j:status don't cooperate together. 1. PROBLEM: After clicking a4j:commandLink inside rich:dataGrid, rich:dataGrid behaves properly, but a4j:status component is not able to hide. 2. When I remove a4j:status component, everything is OK (but rerendering rich:dataGrid is taking a while, so I would like to get a4j:status component functionality on page) 3. a4j:commandButton present at that page (not shown in below code extract) cooperate to a4j:status correctly ------------- (I just have noticed: a4j:status component also does not cooperate correctly to richfaces tabs: durring first tab switching, a4j:status component is not able to hide After refresh: tabs and a4j:status component start to behave correctly ). ========================================================================================================================= ------------------------- EXTRACT OF MY CODE: --------------------------------------------------------------------------- ----------------------------------------------------------------------------------------------------------------------- was: rich:dataGrid component and a4j:status don't cooperate together. 1. PROBLEM: After clicking a4j:commandLink inside rich:dataGrid, rich:dataGrid behaves properly, but a4j:status component is not able to hide. 2. When I remove a4j:status component, everything is OK (but rerendering rich:dataGrid is taking a while, so I would like to get a4j:status component functionality on page) 3. a4j:commandButton present at that page (not shown in below code extract) cooperate to a4j:status corectly ------------------------- EXTRACT OF MY CODE: --------------------------------------------------------------------------- ----------------------------------------------------------------------------------------------------------------------- > rich:dataGrid component and a4j:status don't cooperate together > --------------------------------------------------------------- > > Key: RF-12024 > URL: https://issues.jboss.org/browse/RF-12024 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.1.0.Final, 4.2.0.Final > Environment: JDK1.6, > JBoss 6.0.Final, > richfaces 4.1.0.Final/4.2.0.Final > Reporter: Artur Mioduszewski > > rich:dataGrid component and a4j:status don't cooperate together. > 1. PROBLEM: After clicking a4j:commandLink inside rich:dataGrid, rich:dataGrid behaves properly, but a4j:status component is not able to hide. > 2. When I remove a4j:status component, everything is OK (but rerendering rich:dataGrid is taking a while, so I would like to get a4j:status component functionality on page) > 3. a4j:commandButton present at that page (not shown in below code extract) cooperate to a4j:status correctly > ------------- > (I just have noticed: a4j:status component also does not cooperate correctly to richfaces tabs: durring first tab switching, a4j:status component is not able to hide > After refresh: tabs and a4j:status component start to behave correctly ). > ========================================================================================================================= > ------------------------- EXTRACT OF MY CODE: --------------------------------------------------------------------------- > > columns="7" elements="168" styleClass="noPaddings"> > > > > > > > > > > > > > ----------------------------------------------------------------------------------------------------------------------- -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 6 20:27:36 2012 From: jira-events at lists.jboss.org (Artur Mioduszewski (JIRA)) Date: Tue, 6 Mar 2012 20:27:36 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12025) [rich:tabPanel] Switching tabs doesn't work correctly In-Reply-To: <564356619.72400.1331081680333.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <731872755.72432.1331083656424.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artur Mioduszewski updated RF-12025: ------------------------------------ Environment: JDK1.6, JBoss 6.0.Final, richfaces 4.1.0.Final/4.2.0.Final IE 9 was: JDK1.6, JBoss 6.0.Final, richfaces 4.1.0.Final/4.2.0.Final > [rich:tabPanel] Switching tabs doesn't work correctly > ----------------------------------------------------- > > Key: RF-12025 > URL: https://issues.jboss.org/browse/RF-12025 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.1.0.Final, 4.2.0.Final > Environment: JDK1.6, > JBoss 6.0.Final, > richfaces 4.1.0.Final/4.2.0.Final > IE 9 > Reporter: Artur Mioduszewski > > STEPS TO REPRODUCE A PROBLEM: > 1. Switch tab: UserDataTab -> UserEmailTab (look on JBoss console) > 2. Switch tab: UserEmailTab -> UserDataTab (look on JBoss console) > 3. Switch tab: UserDataTab -> UserEmailTab (look on JBoss console) > 4. Switch tab: UserEmailTab -> UserDataTab (look on JBoss console) > 5. Switch tab: UserDataTab -> UserEmailTab (look on JBoss console) > 6. Switch tab: UserEmailTab -> UserDataTab (look on JBoss console) > ... > Every tab switching caused more (perhaps 2 times more) calling of logger.debug("----preRenderHomeView"); > ============================================================================================================================== > ------------------------- XHTML FILE CODE EXTRACT: --------------------------------------------------------------------------- > > > > > > > > > > > > > > -------------------------------------------------------------------------------------------------------- > HomeAction: > public void preRenderHomeView() > { > logger.debug("----preRenderHomeView"); > } -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 6 20:27:36 2012 From: jira-events at lists.jboss.org (Artur Mioduszewski (JIRA)) Date: Tue, 6 Mar 2012 20:27:36 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12024) rich:dataGrid component and a4j:status don't cooperate together In-Reply-To: <953422806.72367.1331080056746.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <79271874.72434.1331083656481.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artur Mioduszewski updated RF-12024: ------------------------------------ Environment: JDK1.6, JBoss 6.0.Final, richfaces 4.1.0.Final/4.2.0.Final IE 9 was: JDK1.6, JBoss 6.0.Final, richfaces 4.1.0.Final/4.2.0.Final > rich:dataGrid component and a4j:status don't cooperate together > --------------------------------------------------------------- > > Key: RF-12024 > URL: https://issues.jboss.org/browse/RF-12024 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.1.0.Final, 4.2.0.Final > Environment: JDK1.6, > JBoss 6.0.Final, > richfaces 4.1.0.Final/4.2.0.Final > IE 9 > Reporter: Artur Mioduszewski > > rich:dataGrid component and a4j:status don't cooperate together. > 1. PROBLEM: After clicking a4j:commandLink inside rich:dataGrid, rich:dataGrid behaves properly, but a4j:status component is not able to hide. > 2. When I remove a4j:status component, everything is OK (but rerendering rich:dataGrid is taking a while, so I would like to get a4j:status component functionality on page) > 3. a4j:commandButton present at that page (not shown in below code extract) cooperate to a4j:status correctly > ------------- > (I just have noticed: a4j:status component also does not cooperate correctly to richfaces tabs: durring first tab switching, a4j:status component is not able to hide > After refresh: tabs and a4j:status component start to behave correctly ). > ========================================================================================================================= > ------------------------- EXTRACT OF MY CODE: --------------------------------------------------------------------------- > > columns="7" elements="168" styleClass="noPaddings"> > > > > > > > > > > > > > ----------------------------------------------------------------------------------------------------------------------- -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 6 21:04:37 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Tue, 6 Mar 2012 21:04:37 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12025) [rich:tabPanel] Switching tabs doesn't work correctly In-Reply-To: <564356619.72400.1331081680333.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1872425385.72482.1331085877522.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12025: ------------------------------- Description: Every tab switching caused more (perhaps 2 times more) calling of logger.debug("----preRenderHomeView"); {code:title=XHTML FILE CODE EXTRACT} {code} {code:title="HomeAction"} public void preRenderHomeView() { logger.debug("----preRenderHomeView"); } {code} was: STEPS TO REPRODUCE A PROBLEM: 1. Switch tab: UserDataTab -> UserEmailTab (look on JBoss console) 2. Switch tab: UserEmailTab -> UserDataTab (look on JBoss console) 3. Switch tab: UserDataTab -> UserEmailTab (look on JBoss console) 4. Switch tab: UserEmailTab -> UserDataTab (look on JBoss console) 5. Switch tab: UserDataTab -> UserEmailTab (look on JBoss console) 6. Switch tab: UserEmailTab -> UserDataTab (look on JBoss console) ... Every tab switching caused more (perhaps 2 times more) calling of logger.debug("----preRenderHomeView"); ============================================================================================================================== ------------------------- XHTML FILE CODE EXTRACT: --------------------------------------------------------------------------- -------------------------------------------------------------------------------------------------------- HomeAction: public void preRenderHomeView() { logger.debug("----preRenderHomeView"); } Steps to Reproduce: # Switch tab: UserDataTab -> UserEmailTab (look on JBoss console) # Switch tab: UserEmailTab -> UserDataTab (look on JBoss console) # Switch tab: UserDataTab -> UserEmailTab (look on JBoss console) # Switch tab: UserEmailTab -> UserDataTab (look on JBoss console) # Switch tab: UserDataTab -> UserEmailTab (look on JBoss console) # Switch tab: UserEmailTab -> UserDataTab (look on JBoss console) Component/s: component-panels-layout-themes > [rich:tabPanel] Switching tabs doesn't work correctly > ----------------------------------------------------- > > Key: RF-12025 > URL: https://issues.jboss.org/browse/RF-12025 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.1.0.Final, 4.2.0.Final > Environment: JDK1.6, > JBoss 6.0.Final, > richfaces 4.1.0.Final/4.2.0.Final > IE 9 > Reporter: Artur Mioduszewski > > Every tab switching caused more (perhaps 2 times more) calling of logger.debug("----preRenderHomeView"); > {code:title=XHTML FILE CODE EXTRACT} > > > > > > > > > > > > > > {code} > {code:title="HomeAction"} > public void preRenderHomeView() { > logger.debug("----preRenderHomeView"); > } > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 7 02:44:36 2012 From: jira-events at lists.jboss.org (Artur Mioduszewski (JIRA)) Date: Wed, 7 Mar 2012 02:44:36 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12024) rich:dataGrid component and a4j:status don't cooperate together In-Reply-To: <953422806.72367.1331080056746.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1309066849.72677.1331106276655.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artur Mioduszewski updated RF-12024: ------------------------------------ Description: rich:dataGrid component and a4j:status don't cooperate together. 1. PROBLEM: After clicking a4j:commandLink inside rich:dataGrid, rich:dataGrid behaves properly, but a4j:status component is not able to hide. 2. When I remove a4j:status component, everything is OK (but rerendering rich:dataGrid is taking a while, so I would like to get a4j:status component functionality on page) 3. a4j:commandButton present at that page (not shown in below code extract) cooperate to a4j:status correctly ------------- (I just have noticed: a4j:status component also does not cooperate correctly to richfaces tabs: durring first tab switching, a4j:status component is not able to hide After refresh: tabs and a4j:status component start to behave correctly ). {code:title="XHTML FILE CODE EXTRACT"} {code} was: rich:dataGrid component and a4j:status don't cooperate together. 1. PROBLEM: After clicking a4j:commandLink inside rich:dataGrid, rich:dataGrid behaves properly, but a4j:status component is not able to hide. 2. When I remove a4j:status component, everything is OK (but rerendering rich:dataGrid is taking a while, so I would like to get a4j:status component functionality on page) 3. a4j:commandButton present at that page (not shown in below code extract) cooperate to a4j:status correctly ------------- (I just have noticed: a4j:status component also does not cooperate correctly to richfaces tabs: durring first tab switching, a4j:status component is not able to hide After refresh: tabs and a4j:status component start to behave correctly ). ========================================================================================================================= ------------------------- EXTRACT OF MY CODE: --------------------------------------------------------------------------- ----------------------------------------------------------------------------------------------------------------------- > rich:dataGrid component and a4j:status don't cooperate together > --------------------------------------------------------------- > > Key: RF-12024 > URL: https://issues.jboss.org/browse/RF-12024 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.1.0.Final, 4.2.0.Final > Environment: JDK1.6, > JBoss 6.0.Final, > richfaces 4.1.0.Final/4.2.0.Final > IE 9 > Reporter: Artur Mioduszewski > > rich:dataGrid component and a4j:status don't cooperate together. > 1. PROBLEM: After clicking a4j:commandLink inside rich:dataGrid, rich:dataGrid behaves properly, but a4j:status component is not able to hide. > 2. When I remove a4j:status component, everything is OK (but rerendering rich:dataGrid is taking a while, so I would like to get a4j:status component functionality on page) > 3. a4j:commandButton present at that page (not shown in below code extract) cooperate to a4j:status correctly > ------------- > (I just have noticed: a4j:status component also does not cooperate correctly to richfaces tabs: durring first tab switching, a4j:status component is not able to hide > After refresh: tabs and a4j:status component start to behave correctly ). > {code:title="XHTML FILE CODE EXTRACT"} > > columns="7" elements="168" styleClass="noPaddings"> > > > > > > > > > > > > > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 7 08:13:36 2012 From: jira-events at lists.jboss.org (Ulf Almehed (JIRA)) Date: Wed, 7 Mar 2012 08:13:36 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12026) Javascript error in AjaxRequests on FireFox "invalid 'in' operand event" Message-ID: <1447882664.73686.1331126016454.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Ulf Almehed created RF-12026: -------------------------------- Summary: Javascript error in AjaxRequests on FireFox "invalid 'in' operand event" Key: RF-12026 URL: https://issues.jboss.org/browse/RF-12026 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: core Affects Versions: 4.2.0.Final Environment: FireFox 3.6.27 Reporter: Ulf Almehed Ajax request fails with javascript error "invalid 'in' operand event", richfaces-queue.js line 130. This was introduced by the fix in RF-11943. Checking for existence of layerX fails if event isn't an Object (but a simple type). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 7 10:00:38 2012 From: jira-events at lists.jboss.org (RH Bugzilla Integration (JIRA)) Date: Wed, 7 Mar 2012 10:00:38 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12021) Compilation of Input UI component logs 2 errors about faces-config.xml In-Reply-To: <518462150.61467.1330674576214.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1925643138.74141.1331132438222.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] RH Bugzilla Integration updated RF-12021: ----------------------------------------- Bugzilla Update: Perform > Compilation of Input UI component logs 2 errors about faces-config.xml > ---------------------------------------------------------------------- > > Key: RF-12021 > URL: https://issues.jboss.org/browse/RF-12021 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.2.0.Final > Reporter: Marek Novotny > Assignee: Brian Leathem > > Compilation of RF UI Components specifically Input UI has got 2 errors in log - related to bad faces-config.xml on line number 29 and 240. > The following is snippet of log: > {noformat} > [INFO] ------------------------------------------------------------------------ > [INFO] Building RichFaces UI Components: Input UI 4.2.0.Final > [INFO] ------------------------------------------------------------------------ > [INFO] > [INFO] --- maven-enforcer-plugin:1.0-redhat-1:enforce (enforce-java-version) @ richfaces-ui-input-ui --- > [INFO] The requirePluginVersions rule is currently not compatible with Maven3. > [INFO] > [INFO] --- maven-enforcer-plugin:1.0-redhat-1:enforce (enforce-maven-version) @ richfaces-ui-input-ui --- > [INFO] The requirePluginVersions rule is currently not compatible with Maven3. > [INFO] > [INFO] --- maven-cdk-plugin:4.2.0.Final-redhat-1:generate (cdk-generate-sources) @ richfaces-ui-input-ui --- > [Error] faces-config.xml:29:71: cvc-complex-type.2.4.a: Invalid content was found starting with element 'xi:include'. One of '{"http://java.sun.com/xml/ns/javaee":property, "http://java.sun.com/xml/ns/javaee":component-extension}' is expected. > [Error] faces-config.xml:240:71: cvc-complex-type.2.4.a: Invalid content was found starting with element 'xi:include'. One of '{"http://java.sun.com/xml/ns/javaee":property, "http://java.sun.com/xml/ns/javaee":component-extension}' is expected. > {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 7 10:00:38 2012 From: jira-events at lists.jboss.org (RH Bugzilla Integration (JIRA)) Date: Wed, 7 Mar 2012 10:00:38 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12021) Compilation of Input UI component logs 2 errors about faces-config.xml In-Reply-To: <518462150.61467.1330674576214.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1162581219.74145.1331132438937.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] RH Bugzilla Integration updated RF-12021: ----------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=801048 > Compilation of Input UI component logs 2 errors about faces-config.xml > ---------------------------------------------------------------------- > > Key: RF-12021 > URL: https://issues.jboss.org/browse/RF-12021 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.2.0.Final > Reporter: Marek Novotny > Assignee: Brian Leathem > > Compilation of RF UI Components specifically Input UI has got 2 errors in log - related to bad faces-config.xml on line number 29 and 240. > The following is snippet of log: > {noformat} > [INFO] ------------------------------------------------------------------------ > [INFO] Building RichFaces UI Components: Input UI 4.2.0.Final > [INFO] ------------------------------------------------------------------------ > [INFO] > [INFO] --- maven-enforcer-plugin:1.0-redhat-1:enforce (enforce-java-version) @ richfaces-ui-input-ui --- > [INFO] The requirePluginVersions rule is currently not compatible with Maven3. > [INFO] > [INFO] --- maven-enforcer-plugin:1.0-redhat-1:enforce (enforce-maven-version) @ richfaces-ui-input-ui --- > [INFO] The requirePluginVersions rule is currently not compatible with Maven3. > [INFO] > [INFO] --- maven-cdk-plugin:4.2.0.Final-redhat-1:generate (cdk-generate-sources) @ richfaces-ui-input-ui --- > [Error] faces-config.xml:29:71: cvc-complex-type.2.4.a: Invalid content was found starting with element 'xi:include'. One of '{"http://java.sun.com/xml/ns/javaee":property, "http://java.sun.com/xml/ns/javaee":component-extension}' is expected. > [Error] faces-config.xml:240:71: cvc-complex-type.2.4.a: Invalid content was found starting with element 'xi:include'. One of '{"http://java.sun.com/xml/ns/javaee":property, "http://java.sun.com/xml/ns/javaee":component-extension}' is expected. > {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 7 10:00:39 2012 From: jira-events at lists.jboss.org (RH Bugzilla Integration (JIRA)) Date: Wed, 7 Mar 2012 10:00:39 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12021) Compilation of Input UI component logs 2 errors about faces-config.xml In-Reply-To: <518462150.61467.1330674576214.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <444633272.74148.1331132439266.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12674754#comment-12674754 ] RH Bugzilla Integration commented on RF-12021: ---------------------------------------------- Marek Novotny made a comment on [bug 801048|https://bugzilla.redhat.com/show_bug.cgi?id=801048] Compilation of RF UI Components specifically Input UI has got 2 errors in log - related to bad faces-config.xml on line number 29 and 240. The following is snippet of log: [INFO] ------------------------------------------------------------------------ [INFO] Building RichFaces UI Components: Input UI 4.2.0.Final [INFO] ------------------------------------------------------------------------ [INFO] [INFO] --- maven-enforcer-plugin:1.0-redhat-1:enforce (enforce-java-version) @ richfaces-ui-input-ui --- [INFO] The requirePluginVersions rule is currently not compatible with Maven3. [INFO] [INFO] --- maven-enforcer-plugin:1.0-redhat-1:enforce (enforce-maven-version) @ richfaces-ui-input-ui --- [INFO] The requirePluginVersions rule is currently not compatible with Maven3. [INFO] [INFO] --- maven-cdk-plugin:4.2.0.Final-redhat-1:generate (cdk-generate-sources) @ richfaces-ui-input-ui --- [Error] faces-config.xml:29:71: cvc-complex-type.2.4.a: Invalid content was found starting with element 'xi:include'. One of '{"http://java.sun.com/xml/ns/javaee":property, "http://java.sun.com/xml/ns/javaee":component-extension}' is expected. [Error] faces-config.xml:240:71: cvc-complex-type.2.4.a: Invalid content was found starting with element 'xi:include'. One of '{"http://java.sun.com/xml/ns/javaee":property, "http://java.sun.com/xml/ns/javaee":component-extension}' is expected. > Compilation of Input UI component logs 2 errors about faces-config.xml > ---------------------------------------------------------------------- > > Key: RF-12021 > URL: https://issues.jboss.org/browse/RF-12021 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.2.0.Final > Reporter: Marek Novotny > Assignee: Brian Leathem > > Compilation of RF UI Components specifically Input UI has got 2 errors in log - related to bad faces-config.xml on line number 29 and 240. > The following is snippet of log: > {noformat} > [INFO] ------------------------------------------------------------------------ > [INFO] Building RichFaces UI Components: Input UI 4.2.0.Final > [INFO] ------------------------------------------------------------------------ > [INFO] > [INFO] --- maven-enforcer-plugin:1.0-redhat-1:enforce (enforce-java-version) @ richfaces-ui-input-ui --- > [INFO] The requirePluginVersions rule is currently not compatible with Maven3. > [INFO] > [INFO] --- maven-enforcer-plugin:1.0-redhat-1:enforce (enforce-maven-version) @ richfaces-ui-input-ui --- > [INFO] The requirePluginVersions rule is currently not compatible with Maven3. > [INFO] > [INFO] --- maven-cdk-plugin:4.2.0.Final-redhat-1:generate (cdk-generate-sources) @ richfaces-ui-input-ui --- > [Error] faces-config.xml:29:71: cvc-complex-type.2.4.a: Invalid content was found starting with element 'xi:include'. One of '{"http://java.sun.com/xml/ns/javaee":property, "http://java.sun.com/xml/ns/javaee":component-extension}' is expected. > [Error] faces-config.xml:240:71: cvc-complex-type.2.4.a: Invalid content was found starting with element 'xi:include'. One of '{"http://java.sun.com/xml/ns/javaee":property, "http://java.sun.com/xml/ns/javaee":component-extension}' is expected. > {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 7 12:25:36 2012 From: jira-events at lists.jboss.org (Karsten Wutzke (JIRA)) Date: Wed, 7 Mar 2012 12:25:36 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12027) Add a maximum number of selectable elements to rich:pickList Message-ID: <102106719.74777.1331141136257.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Karsten Wutzke created RF-12027: ----------------------------------- Summary: Add a maximum number of selectable elements to rich:pickList Key: RF-12027 URL: https://issues.jboss.org/browse/RF-12027 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Environment: any Reporter: Karsten Wutzke Please add a maximum number of selectable elements to rich:pickList via an attribute like maxItems="n" or maxValues="n" -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 7 14:39:37 2012 From: jira-events at lists.jboss.org (Karsten Wutzke (JIRA)) Date: Wed, 7 Mar 2012 14:39:37 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11592) RichFaces 4.1 Milestone changes for fileUpload component incompatible with Apache MyFaces Orchestra conversation scope In-Reply-To: <1839758620.29810.1319638185453.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1066435768.75138.1331149177080.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12674869#comment-12674869 ] Karsten Wutzke commented on RF-11592: ------------------------------------- My issue seems to be http://java.net/jira/browse/GLASSFISH-18444 (as seen here: https://community.jboss.org/thread/196311) > RichFaces 4.1 Milestone changes for fileUpload component incompatible with Apache MyFaces Orchestra conversation scope > ---------------------------------------------------------------------------------------------------------------------- > > Key: RF-11592 > URL: https://issues.jboss.org/browse/RF-11592 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.1.0.Milestone1, 4.1.0.Milestone2, 4.1.0.Milestone3 > Environment: Mojarra 2.1.3, JBoss AS 5.0.1, Apache MyFaces Orchestra 1.4, Spring 3.0.4 > Reporter: Joshua Brookes > Labels: fileUpload, multipart/form-data, orchestra, regression, richfaces, richfaces4 > Fix For: 4.3-Tracking > > Attachments: fileUploadWeb.zip, server.log > > > There is a compatibility issue with recent changes in RichFaces 4.1 Milestone 1 and Apache MyFaces Orchestra conversation scope feature. When including the Orchestra jar in the application the fileUpload component stops working. Orchestra bundles a faces-config.xml that enables 2 FacesContext Factories and multiple PhaseListeners. This did not pose a problem with RichFaces 4.0.0.Final. > Here is a stacktrace that shows the error: > {code} > Oct 25, 2011 11:45:01 AM org.richfaces.request.MultipartRequest25 parseIfNecessary > SEVERE: Exception parsing multipart request: Request prolog cannot be read > org.richfaces.exception.FileUploadException: Exception parsing multipart request: Request prolog cannot be read > at org.richfaces.request.MultipartRequestParser.parse(MultipartRequestParser.java:156) > at org.richfaces.request.MultipartRequest25.parseIfNecessary(MultipartRequest25.java:77) > at org.richfaces.request.MultipartRequest25.getParameter(MultipartRequest25.java:114) > at com.sun.faces.context.RequestParameterMap.containsKey(RequestParameterMap.java:99) > at java.util.Collections$UnmodifiableMap.containsKey(Collections.java:1280) > at org.apache.myfaces.orchestra.frameworkAdapter.jsf.JsfFrameworkAdapter.containsRequestParameterAttribute(JsfFrameworkAdapter.java:105) > at org.apache.myfaces.orchestra.conversation.ConversationManager.findConversationContextId(ConversationManager.java:169) > at org.apache.myfaces.orchestra.conversation.ConversationManager.getCurrentRootConversationContext(ConversationManager.java:580) > at org.apache.myfaces.orchestra.lib.jsf.ContextLockRequestHandler.init(ContextLockRequestHandler.java:87) > at org.apache.myfaces.orchestra.lib.jsf.OrchestraFacesContextFactory$1.(OrchestraFacesContextFactory.java:122) > at org.apache.myfaces.orchestra.lib.jsf.OrchestraFacesContextFactory.getFacesContext(OrchestraFacesContextFactory.java:103) > at org.apache.myfaces.orchestra.requestParameterProvider.jsf.RequestParameterFacesContextFactory.getFacesContext(RequestParameterFacesContextFactory.java:93) > at org.richfaces.context.FileUploadFacesContextFactory.getFacesContext(FileUploadFacesContextFactory.java:136) > at com.sun.faces.context.InjectionFacesContextFactory.getFacesContext(InjectionFacesContextFactory.java:121) > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:583) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:638) > at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:446) > at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:382) > at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:310) > at org.apache.catalina.core.StandardHostValve.custom(StandardHostValve.java:416) > at org.apache.catalina.core.StandardHostValve.status(StandardHostValve.java:342) > at org.apache.catalina.core.StandardHostValve.throwable(StandardHostValve.java:286) > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:141) > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) > at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330) > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829) > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:598) > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) > at java.lang.Thread.run(Thread.java:619) > Caused by: java.io.IOException: Request prolog cannot be read > at org.richfaces.request.MultipartRequestParser.readProlog(MultipartRequestParser.java:270) > at org.richfaces.request.MultipartRequestParser.initialize(MultipartRequestParser.java:172) > at org.richfaces.request.MultipartRequestParser.parse(MultipartRequestParser.java:148) > ... 32 more > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 7 14:41:36 2012 From: jira-events at lists.jboss.org (Karsten Wutzke (JIRA)) Date: Wed, 7 Mar 2012 14:41:36 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11592) RichFaces 4.1 Milestone changes for fileUpload component incompatible with Apache MyFaces Orchestra conversation scope In-Reply-To: <1839758620.29810.1319638185453.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <866436563.75148.1331149296331.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12674871#comment-12674871 ] Karsten Wutzke commented on RF-11592: ------------------------------------- My issue seems to be http://java.net/jira/browse/GLASSFISH-18444 (as seen here: https://community.jboss.org/thread/196311) > RichFaces 4.1 Milestone changes for fileUpload component incompatible with Apache MyFaces Orchestra conversation scope > ---------------------------------------------------------------------------------------------------------------------- > > Key: RF-11592 > URL: https://issues.jboss.org/browse/RF-11592 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.1.0.Milestone1, 4.1.0.Milestone2, 4.1.0.Milestone3 > Environment: Mojarra 2.1.3, JBoss AS 5.0.1, Apache MyFaces Orchestra 1.4, Spring 3.0.4 > Reporter: Joshua Brookes > Labels: fileUpload, multipart/form-data, orchestra, regression, richfaces, richfaces4 > Fix For: 4.3-Tracking > > Attachments: fileUploadWeb.zip, server.log > > > There is a compatibility issue with recent changes in RichFaces 4.1 Milestone 1 and Apache MyFaces Orchestra conversation scope feature. When including the Orchestra jar in the application the fileUpload component stops working. Orchestra bundles a faces-config.xml that enables 2 FacesContext Factories and multiple PhaseListeners. This did not pose a problem with RichFaces 4.0.0.Final. > Here is a stacktrace that shows the error: > {code} > Oct 25, 2011 11:45:01 AM org.richfaces.request.MultipartRequest25 parseIfNecessary > SEVERE: Exception parsing multipart request: Request prolog cannot be read > org.richfaces.exception.FileUploadException: Exception parsing multipart request: Request prolog cannot be read > at org.richfaces.request.MultipartRequestParser.parse(MultipartRequestParser.java:156) > at org.richfaces.request.MultipartRequest25.parseIfNecessary(MultipartRequest25.java:77) > at org.richfaces.request.MultipartRequest25.getParameter(MultipartRequest25.java:114) > at com.sun.faces.context.RequestParameterMap.containsKey(RequestParameterMap.java:99) > at java.util.Collections$UnmodifiableMap.containsKey(Collections.java:1280) > at org.apache.myfaces.orchestra.frameworkAdapter.jsf.JsfFrameworkAdapter.containsRequestParameterAttribute(JsfFrameworkAdapter.java:105) > at org.apache.myfaces.orchestra.conversation.ConversationManager.findConversationContextId(ConversationManager.java:169) > at org.apache.myfaces.orchestra.conversation.ConversationManager.getCurrentRootConversationContext(ConversationManager.java:580) > at org.apache.myfaces.orchestra.lib.jsf.ContextLockRequestHandler.init(ContextLockRequestHandler.java:87) > at org.apache.myfaces.orchestra.lib.jsf.OrchestraFacesContextFactory$1.(OrchestraFacesContextFactory.java:122) > at org.apache.myfaces.orchestra.lib.jsf.OrchestraFacesContextFactory.getFacesContext(OrchestraFacesContextFactory.java:103) > at org.apache.myfaces.orchestra.requestParameterProvider.jsf.RequestParameterFacesContextFactory.getFacesContext(RequestParameterFacesContextFactory.java:93) > at org.richfaces.context.FileUploadFacesContextFactory.getFacesContext(FileUploadFacesContextFactory.java:136) > at com.sun.faces.context.InjectionFacesContextFactory.getFacesContext(InjectionFacesContextFactory.java:121) > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:583) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:638) > at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:446) > at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:382) > at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:310) > at org.apache.catalina.core.StandardHostValve.custom(StandardHostValve.java:416) > at org.apache.catalina.core.StandardHostValve.status(StandardHostValve.java:342) > at org.apache.catalina.core.StandardHostValve.throwable(StandardHostValve.java:286) > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:141) > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) > at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330) > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829) > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:598) > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) > at java.lang.Thread.run(Thread.java:619) > Caused by: java.io.IOException: Request prolog cannot be read > at org.richfaces.request.MultipartRequestParser.readProlog(MultipartRequestParser.java:270) > at org.richfaces.request.MultipartRequestParser.initialize(MultipartRequestParser.java:172) > at org.richfaces.request.MultipartRequestParser.parse(MultipartRequestParser.java:148) > ... 32 more > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 7 15:28:36 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 7 Mar 2012 15:28:36 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12000) TabPanel - Backing bean initialization when a same bean manages multiple dynamic tabs In-Reply-To: <572385267.36048.1329946356737.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1249505189.75217.1331152116320.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12000: ------------------------------- Component/s: component-panels-layout-themes Forum Reference: https://community.jboss.org/message/718460#718460 (was: https://community.jboss.org/message/718460#718460) > TabPanel - Backing bean initialization when a same bean manages multiple dynamic tabs > ------------------------------------------------------------------------------------- > > Key: RF-12000 > URL: https://issues.jboss.org/browse/RF-12000 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Reporter: Jean ANDRE > Fix For: 4.3-Tracking > > > See the conversation : https://community.jboss.org/message/718460#718460 > Based on the work done, it is more clear about what we need. When a tabPanel, contains dynamic tabs handle by the same backing-bean (because of the same include xhtml), we need a way, a reliable manner to initialize the backing bean when the user switch from a tab to another tab. It might be a specific tag, as rich:bean init="#{.....initialize(params)}". This tab should be executed first, before any other calls of the backing bean whatever its place inside the xhtml page. If several such tags exist wherever (template, include), they must be executed in their natural order, from the deeper to the top of the page hierarchy. > So, what we need is a contextual initialization, because the @PostContruct is not well suitable for that situation and also a more simple solution rather trying to do it by the PhaseListener (and what about the context???). > Related links around of this feature: > - http://www.coderanch.com/t/213757/JSF/java/initialize-backing-bean-before-page > - http://stackoverflow.com/questions/8132394/backing-bean-initialization > - http://www.icefaces.org/JForum/posts/list/13260.page > - http://cagataycivici.wordpress.com/2006/06/06/managed_beans_aware_of_the/ > - http://boardreader.com/thread/how_to_initialize_a_backing_bean_before_w2nvX36qxy.html > Thank you -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 7 15:32:36 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 7 Mar 2012 15:32:36 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11560) Showcase on OpenShift Express: Push stops to work after first long-polling request In-Reply-To: <703843376.3936.1318926525118.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1428635344.75232.1331152356483.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-11560: ------------------------------- Fix Version/s: (was: 4.3-Tracking) Priority: Major (was: Critical) Assignee: Jan Papousek (was: Luk?? Fry?) Component/s: component-push/poll Jan, it's not clear from your last comment whether the summary/description of this issue still applies. If you are describing a new problem, please file a new issue and close this one. Otherwise, please clarify the state of this issue with a comment. > Showcase on OpenShift Express: Push stops to work after first long-polling request > ---------------------------------------------------------------------------------- > > Key: RF-11560 > URL: https://issues.jboss.org/browse/RF-11560 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll, showcase > Affects Versions: 4.1.0.Milestone3 > Reporter: Luk?? Fry? > Assignee: Jan Papousek > > Both demos affected: TopicsContext and Push CDI. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 7 15:36:37 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 7 Mar 2012 15:36:37 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11108) Showcase GAE support is broken: NoClassDefFound: InitialContext In-Reply-To: <2010466994.39420.1310033183774.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <59838048.75236.1331152597073.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-11108. -------------------------------- Assignee: Brian Leathem (was: Luk?? Fry?) Fix Version/s: (was: 4.3-Tracking) Resolution: Won't Fix While RichFaces on GAE remains a priority for us, we are no longer deploying the showcase to GAE. > Showcase GAE support is broken: NoClassDefFound: InitialContext > --------------------------------------------------------------- > > Key: RF-11108 > URL: https://issues.jboss.org/browse/RF-11108 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: examples, showcase > Affects Versions: 4.1.0.Milestone1 > Reporter: Luk?? Fry? > Assignee: Brian Leathem > > When running mvn gae:run -Pgae > deployment ends with NoClassDefFound: InitialContext. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 7 15:36:39 2012 From: jira-events at lists.jboss.org (RH Bugzilla Integration (JIRA)) Date: Wed, 7 Mar 2012 15:36:39 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11739) Components that don't require jsf.js can break ResourceMapping In-Reply-To: <445024762.41821.1322186680654.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <442643798.75247.1331152599477.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] RH Bugzilla Integration updated RF-11739: ----------------------------------------- Bugzilla Update: Perform Forum Reference: http://community.jboss.org/message/642770#642770, http://community.jboss.org/message/638045#638045 (was: http://community.jboss.org/message/642770#642770, http://community.jboss.org/message/638045#638045) > Components that don't require jsf.js can break ResourceMapping > -------------------------------------------------------------- > > Key: RF-11739 > URL: https://issues.jboss.org/browse/RF-11739 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: resource handling > Affects Versions: 4.0.0.CR1 > Reporter: Brian Leathem > Assignee: Luk?? Fry? > Fix For: 4.3-Tracking > > > This bug is only observable when resourceMapping is enabled. > If a component doesn't require jsf.js, and it is the first component to require a resource, it will trigger packed.js to redner before jsf.js. This breaks some of the scripts in packed.js, that require jsf.js. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 7 15:36:40 2012 From: jira-events at lists.jboss.org (RH Bugzilla Integration (JIRA)) Date: Wed, 7 Mar 2012 15:36:40 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11739) Components that don't require jsf.js can break ResourceMapping In-Reply-To: <445024762.41821.1322186680654.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1287560660.75251.1331152600126.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] RH Bugzilla Integration updated RF-11739: ----------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=801172 Forum Reference: http://community.jboss.org/message/642770#642770, http://community.jboss.org/message/638045#638045 (was: http://community.jboss.org/message/642770#642770, http://community.jboss.org/message/638045#638045) > Components that don't require jsf.js can break ResourceMapping > -------------------------------------------------------------- > > Key: RF-11739 > URL: https://issues.jboss.org/browse/RF-11739 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: resource handling > Affects Versions: 4.0.0.CR1 > Reporter: Brian Leathem > Assignee: Luk?? Fry? > Fix For: 4.3-Tracking > > > This bug is only observable when resourceMapping is enabled. > If a component doesn't require jsf.js, and it is the first component to require a resource, it will trigger packed.js to redner before jsf.js. This breaks some of the scripts in packed.js, that require jsf.js. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 7 15:42:36 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 7 Mar 2012 15:42:36 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11255) Notify - the messages are not displayed (MyFaces) In-Reply-To: <923449259.9455.1312964784560.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1698621729.75266.1331152956740.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-11255: ------------------------------- Fix Version/s: 4.3.0.Milestone1 (was: 4.3-Tracking) > Notify - the messages are not displayed (MyFaces) > ------------------------------------------------- > > Key: RF-11255 > URL: https://issues.jboss.org/browse/RF-11255 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.1.0.Milestone1 > Environment: RichFaces 4.1.0-SNAPSHOT r.d0f9c11eb0dacc1444c0a3182b12567e28aef6bc > Metamer 4.1.0-SNAPSHOT r.22610 > Apache MyFaces JSF-2.1 Core Impl 2.1.1 > Apache Tomcat 6.0.32 > OpenJDK Runtime Environment 1.6.0_22-b22 @Linux > Internet Explorer 8.0 @ Win32 > Reporter: Jan Papousek > Assignee: Luk?? Fry? > Labels: myfaces > Fix For: 4.3.0.Milestone1 > > > The messages and validator messages are not displayed. This can be reproduced in Metamer: > - faces/components/richNotify/simple.xhtml > - faces/components/richNotify/validation.xhtml -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 7 15:44:36 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 7 Mar 2012 15:44:36 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11440) Migrate the Seam Faces module into a RichFaces module. In-Reply-To: <1940562171.84403.1317221727057.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <2081053892.75268.1331153076199.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-11440. -------------------------------- Assignee: Brian Leathem Fix Version/s: (was: 4.3-Tracking) Resolution: Rejected Seam Faces CDI extensions will be moved to the DeltaSpike project. Any RichFaces specific CDI extensions we develop will be considered individually. > Migrate the Seam Faces module into a RichFaces module. > ------------------------------------------------------ > > Key: RF-11440 > URL: https://issues.jboss.org/browse/RF-11440 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: build/distribution > Reporter: Brian Leathem > Assignee: Brian Leathem > > Further development of the Seam Faces collections of JSF and CDI extensions will continue in the RichFaces project, as an independent and option RichFaces module. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 7 15:46:39 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 7 Mar 2012 15:46:39 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11590) showcase - only first push is done using Atmosphere CR2 In-Reply-To: <1926719144.28309.1319617905803.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1425789888.75280.1331153199277.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-11590: ------------------------------- Fix Version/s: (was: 4.3-Tracking) Assignee: Juraj Huska (was: Luk?? Fry?) Juraj, would you verify whether or not this is still an issue, as we upgraded the Atmosphere library in the RichFaces 4.2.0.Final release. > showcase - only first push is done using Atmosphere CR2 > ------------------------------------------------------- > > Key: RF-11590 > URL: https://issues.jboss.org/browse/RF-11590 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll, showcase > Affects Versions: 4.1.0.Milestone3 > Environment: app: showcase > container: Tomcat 6.0.32 > Reporter: Juraj Huska > Assignee: Juraj Huska > > Only the first push is done in demos for a4j:push component in showcase. No exception is thrown, or any other warning is generated. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 7 15:52:37 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 7 Mar 2012 15:52:37 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11618) Build with jsf_profile=myfaces does not work In-Reply-To: <738657218.39980.1320064305124.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1251133853.75314.1331153557236.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-11618: ------------------------------- Fix Version/s: 4.3.0.Milestone1 (was: 4.3-Tracking) > Build with jsf_profile=myfaces does not work > -------------------------------------------- > > Key: RF-11618 > URL: https://issues.jboss.org/browse/RF-11618 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 4.1.0.Milestone4 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Labels: myfaces > Fix For: 4.3.0.Milestone1 > > > When using jsf_profile=myfaces, build does not work. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 7 15:52:37 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 7 Mar 2012 15:52:37 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11668) CDK should support arbitrary objects with the tag In-Reply-To: <508966317.72263.1320861765215.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1913464677.75316.1331153557726.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-11668: ------------------------------- Fix Version/s: 4.3.0.Milestone1 (was: 4.3-Tracking) > CDK should support arbitrary objects with the tag > -------------------------------------------------------------- > > Key: RF-11668 > URL: https://issues.jboss.org/browse/RF-11668 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: cdk > Reporter: Brian Leathem > Fix For: 4.3.0.Milestone1 > > > The __ tag should accept arbitrary classes in the _type_ parameter, and perform the cast in the generated code. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 7 16:00:25 2012 From: jira-events at lists.jboss.org (RH Bugzilla Integration (JIRA)) Date: Wed, 7 Mar 2012 16:00:25 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11739) Components that don't require jsf.js can break ResourceMapping In-Reply-To: <445024762.41821.1322186680654.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1789810763.75335.1331154025997.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12674890#comment-12674890 ] RH Bugzilla Integration commented on RF-11739: ---------------------------------------------- Karel Piwko made a comment on [bug 801172|https://bugzilla.redhat.com/show_bug.cgi?id=801172] Possible reason why that happens: While comparing ER1 and ER2 releases: /tmp/richfaces-components-ui-4.2.0.Final-redhat-1.jar.diffjars.Dfb/META-INF/richfaces/staticResourceMapping/Packed.properties contains line 117 javax.faces\:jsf.js=org.richfaces.staticResource/4.2.0.Final-redhat-1/Packed/packed/packed.js which load packed.js before jquery.js. Kudos to Lukas Fryc for discovering this issue. > Components that don't require jsf.js can break ResourceMapping > -------------------------------------------------------------- > > Key: RF-11739 > URL: https://issues.jboss.org/browse/RF-11739 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: resource handling > Affects Versions: 4.0.0.CR1 > Reporter: Brian Leathem > Assignee: Luk?? Fry? > Fix For: 4.3-Tracking > > > This bug is only observable when resourceMapping is enabled. > If a component doesn't require jsf.js, and it is the first component to require a resource, it will trigger packed.js to redner before jsf.js. This breaks some of the scripts in packed.js, that require jsf.js. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 7 16:00:27 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 7 Mar 2012 16:00:27 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11589) showcase - a Warning is generated when there is interaction with Atmosphere CR2 framework In-Reply-To: <26512795.28270.1319616945421.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <951050557.75338.1331154027338.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-11589: ------------------------------- Assignee: Juraj Huska Fix Version/s: (was: 4.3-Tracking) Juraj, please verify with the updated Atmosphere available with RichFaces 4.2.0.Final > showcase - a Warning is generated when there is interaction with Atmosphere CR2 framework > ----------------------------------------------------------------------------------------- > > Key: RF-11589 > URL: https://issues.jboss.org/browse/RF-11589 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-push/poll, showcase > Affects Versions: 4.1.0.Milestone3 > Environment: app: showcase > container: JBoss AS 7.0.2.Final, , JBoss 6.0.0.Final, Tomcat 6.0.0.32 > Reporter: Juraj Huska > Assignee: Juraj Huska > Priority: Minor > > An WARNING is generated when there is any interaction with Atmosphere CR2 framework in showcase push demos. > The warning: > {code} > 10:08:12,102 WARNING [org.atmosphere.cpr.AtmosphereResourceImpl] (http-localhost.localdomain-127.0.0.1-8080-2) Broadcaster DefaultBroadcaster9dd3cbac-4e33-482d-8c8c-cd2c0936e695 has been destroyed and cannot be re-used. Recreating a new one with the same name. You can turn off that mechanism by adding, in web.xml, org.atmosphere.cpr.recoverFromDestroyedBroadcaster set to false > {code} > The demos however work as expected. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 7 16:01:36 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 7 Mar 2012 16:01:36 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12019) Upstream mojarra issue requires IE9 to be in compatibility mode In-Reply-To: <676753656.53754.1330535076071.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <262262283.75340.1331154096975.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12019: ------------------------------- Fix Version/s: 4.3.0.Milestone1 (was: 4.3-Tracking) Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=800628 (was: https://bugzilla.redhat.com/show_bug.cgi?id=800628) > Upstream mojarra issue requires IE9 to be in compatibility mode > --------------------------------------------------------------- > > Key: RF-12019 > URL: https://issues.jboss.org/browse/RF-12019 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: third-party > Reporter: Brian Leathem > Fix For: 4.3.0.Milestone1 > > > An upstream issue with mojarra ([JAVASERVERFACES-2063|http://java.net/jira/browse/JAVASERVERFACES-2063]) requires that IE9 be placed in compatibility mode. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 7 16:03:38 2012 From: jira-events at lists.jboss.org (RH Bugzilla Integration (JIRA)) Date: Wed, 7 Mar 2012 16:03:38 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11739) Components that don't require jsf.js can break ResourceMapping In-Reply-To: <445024762.41821.1322186680654.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <149291965.75345.1331154219020.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12674893#comment-12674893 ] RH Bugzilla Integration commented on RF-11739: ---------------------------------------------- Karel Piwko made a comment on [bug 801172|https://bugzilla.redhat.com/show_bug.cgi?id=801172] Likely caused by wrong classpath ordering in file https://github.com/richfaces/components/blob/develop/dist/static-resources/pom.xml > Components that don't require jsf.js can break ResourceMapping > -------------------------------------------------------------- > > Key: RF-11739 > URL: https://issues.jboss.org/browse/RF-11739 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: resource handling > Affects Versions: 4.0.0.CR1 > Reporter: Brian Leathem > Assignee: Luk?? Fry? > Fix For: 4.3-Tracking > > > This bug is only observable when resourceMapping is enabled. > If a component doesn't require jsf.js, and it is the first component to require a resource, it will trigger packed.js to redner before jsf.js. This breaks some of the scripts in packed.js, that require jsf.js. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 7 16:05:40 2012 From: jira-events at lists.jboss.org (RH Bugzilla Integration (JIRA)) Date: Wed, 7 Mar 2012 16:05:40 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11739) Components that don't require jsf.js can break ResourceMapping In-Reply-To: <445024762.41821.1322186680654.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <521271699.75385.1331154340820.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12674897#comment-12674897 ] RH Bugzilla Integration commented on RF-11739: ---------------------------------------------- Karel Piwko made a comment on [bug 801172|https://bugzilla.redhat.com/show_bug.cgi?id=801172] The classpath ordering is influenced by scope of artifacts. This concrete issue happened because /home/kpiwko/installations/wfk/2.0.0.ER2/jboss-wfk-2.0.0.ER2-maven-repository/org/richfaces/richfaces-root-parent/4.2.0.Final-redhat-1/richfaces-root-parent-4.2.0.Final-redhat-1.pom com.sun.faces jsf-impl line 846 was switched from test to compile scope. > Components that don't require jsf.js can break ResourceMapping > -------------------------------------------------------------- > > Key: RF-11739 > URL: https://issues.jboss.org/browse/RF-11739 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: resource handling > Affects Versions: 4.0.0.CR1 > Reporter: Brian Leathem > Assignee: Luk?? Fry? > Fix For: 4.3-Tracking > > > This bug is only observable when resourceMapping is enabled. > If a component doesn't require jsf.js, and it is the first component to require a resource, it will trigger packed.js to redner before jsf.js. This breaks some of the scripts in packed.js, that require jsf.js. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 7 16:19:38 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 7 Mar 2012 16:19:38 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11821) RF4 extendedDataTable rowClasses not working in lazyloading of rows as it was working in Richfaces3.3.3.Final In-Reply-To: <377651505.17009.1324039329660.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <625242273.75447.1331155178177.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12674904#comment-12674904 ] Luk?? Fry? commented on RF-11821: --------------------------------- Ulf: Thanks for the efforts you put to fixing this bug and sending the pull request. It's highly appreciated! > RF4 extendedDataTable rowClasses not working in lazyloading of rows as it was working in Richfaces3.3.3.Final > ------------------------------------------------------------------------------------------------------------- > > Key: RF-11821 > URL: https://issues.jboss.org/browse/RF-11821 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.1.0.CR2 > Environment: Windows XP 32 bit OS, Mozilla Firefox 8.0, Google Chrome 16.0.912.63, IE 7 and 8 > Reporter: Saroj Padhy > Labels: extendedDataTable, lazy-loaded, rowClasses > Fix For: 4.3.0.Milestone1 > > > The attribute in extendedDataTable component, "rowClasses" not working as it used to work in Richfaces3.3.3.Final version. > Normally rowClasses usage is as below: > .. > .. > And in CSS file we define, > tr.odd { > background-color: #F3F3F3; > } > tr.even { > background-color: #FFFFFF; > } > So the row colors differ as odd and even row background colors. > This is not working in Richfaces4 extendedDataTable component when rows are getting loaded on request (lazyloading). All rows shows odd background color. > There is a work around for this issue, which is only working in Mozilla browser. > Link:http://community.jboss.org/thread/168326?tstart=0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 7 16:23:36 2012 From: jira-events at lists.jboss.org (Jean ANDRE (JIRA)) Date: Wed, 7 Mar 2012 16:23:36 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12028) a4j:outputPanel - Error message enhancement Message-ID: <1368665910.75459.1331155416313.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Jean ANDRE created RF-12028: ------------------------------- Summary: a4j:outputPanel - Error message enhancement Key: RF-12028 URL: https://issues.jboss.org/browse/RF-12028 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Environment: JSF / Mojarra 2.1.6 - cssparser-0.9.6 - guava-11.0.1 - hibernate-validator-4.2.0.Final - springframework 3.0.6.RELEASE - richfaces--4.2.0.Final - sac-1.3 - FireFox 10 - WAS 8.0.0.1 / Windows 7 Reporter: Jean ANDRE When we set an non existing attribute on a4j:outputPanel, for eg. "class" because we have converted a div to a a4j:outputPanel, the error message displayed at the user interface does not inform the developer about the faulty component neither pinpoint the bad attribute. The message we got is only : > Error 500: javax.servlet.ServletException: Setter not found for property class This error message is not very helpful to debug.... ;) {code} {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 7 16:25:37 2012 From: jira-events at lists.jboss.org (Jean ANDRE (JIRA)) Date: Wed, 7 Mar 2012 16:25:37 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12028) a4j:outputPanel - Error message enhancement In-Reply-To: <1368665910.75459.1331155416313.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <80756005.75463.1331155537873.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean ANDRE updated RF-12028: ---------------------------- Description: When we set an non existing attribute on a4j:outputPanel, for eg. "class" because we have converted a div to a a4j:outputPanel, the error message displayed at the user interface does not inform the developer about the faulty component. The message we got is only : > Error 500: javax.servlet.ServletException: Setter not found for property class This error message is not very helpful to debug.... ;) {code} {code} was: When we set an non existing attribute on a4j:outputPanel, for eg. "class" because we have converted a div to a a4j:outputPanel, the error message displayed at the user interface does not inform the developer about the faulty component neither pinpoint the bad attribute. The message we got is only : > Error 500: javax.servlet.ServletException: Setter not found for property class This error message is not very helpful to debug.... ;) {code} {code} > a4j:outputPanel - Error message enhancement > ------------------------------------------- > > Key: RF-12028 > URL: https://issues.jboss.org/browse/RF-12028 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Environment: JSF / Mojarra 2.1.6 - cssparser-0.9.6 - guava-11.0.1 - hibernate-validator-4.2.0.Final - springframework 3.0.6.RELEASE - richfaces--4.2.0.Final - sac-1.3 - FireFox 10 - WAS 8.0.0.1 / Windows 7 > Reporter: Jean ANDRE > > When we set an non existing attribute on a4j:outputPanel, for eg. "class" because we have converted a div to a a4j:outputPanel, the error message displayed at the user interface does not inform the developer about the faulty component. The message we got is only : > > Error 500: javax.servlet.ServletException: Setter not found for property class > This error message is not very helpful to debug.... ;) > {code} > layout="block" > class="dark-box" > rendered="#{productBean.expanded eq true}"> > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 7 16:27:36 2012 From: jira-events at lists.jboss.org (Jean ANDRE (JIRA)) Date: Wed, 7 Mar 2012 16:27:36 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12028) a4j:outputPanel - Error message enhancement In-Reply-To: <1368665910.75459.1331155416313.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <2035113012.75470.1331155656420.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean ANDRE updated RF-12028: ---------------------------- Description: When we set an non existing attribute on a4j:outputPanel, for eg. "class" because we have converted a div to a a4j:outputPanel, the error message displayed at the user interface does not inform the developer about the faulty component. The message we got is only : > Error 500: javax.servlet.ServletException: Setter not found for property class This error message is not very helpful to debug.... ;) {code} {code} We should have, as usual, the line of the XHTML file or the component name, the line number, well something more accurate that really help to go faster. was: When we set an non existing attribute on a4j:outputPanel, for eg. "class" because we have converted a div to a a4j:outputPanel, the error message displayed at the user interface does not inform the developer about the faulty component. The message we got is only : > Error 500: javax.servlet.ServletException: Setter not found for property class This error message is not very helpful to debug.... ;) {code} {code} > a4j:outputPanel - Error message enhancement > ------------------------------------------- > > Key: RF-12028 > URL: https://issues.jboss.org/browse/RF-12028 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Environment: JSF / Mojarra 2.1.6 - cssparser-0.9.6 - guava-11.0.1 - hibernate-validator-4.2.0.Final - springframework 3.0.6.RELEASE - richfaces--4.2.0.Final - sac-1.3 - FireFox 10 - WAS 8.0.0.1 / Windows 7 > Reporter: Jean ANDRE > > When we set an non existing attribute on a4j:outputPanel, for eg. "class" because we have converted a div to a a4j:outputPanel, the error message displayed at the user interface does not inform the developer about the faulty component. The message we got is only : > > Error 500: javax.servlet.ServletException: Setter not found for property class > This error message is not very helpful to debug.... ;) > {code} > layout="block" > class="dark-box" > rendered="#{productBean.expanded eq true}"> > {code} > We should have, as usual, the line of the XHTML file or the component name, the line number, well something more accurate that really help to go faster. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 7 17:57:36 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 7 Mar 2012 17:57:36 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12029) AbstractTogglePanel should extend UIRepeat, instead of UIOutput Message-ID: <1430073926.75557.1331161056577.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Brian Leathem created RF-12029: ---------------------------------- Summary: AbstractTogglePanel should extend UIRepeat, instead of UIOutput Key: RF-12029 URL: https://issues.jboss.org/browse/RF-12029 Project: RichFaces Issue Type: Enhancement Security Level: Public (Everyone can see) Components: component-output Reporter: Brian Leathem Assignee: Bernard Labno Valid uses exist for dynamically generating rich:tab, rich:togglePanelItem, rich:accordionItem. Current techniques for supporting this use case involve using c:forEach, which is a problem since c: tags are processed too early to nicely support dynamic use cases. One idea to support this use case, is to have AbstractTogglePanel extend UIRepeat, instead of UIOutput to better dynamic child components. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 7 18:01:36 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 7 Mar 2012 18:01:36 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12029) AbstractTogglePanel should extend UIRepeat, instead of UIOutput In-Reply-To: <1430073926.75557.1331161056577.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1284143263.75568.1331161296908.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12674926#comment-12674926 ] Brian Leathem commented on RF-12029: ------------------------------------ Summary of a discussion in IRC: {quote} (02:35:14 AM) blabno: AbstractTogglePanel was extending UIOutput (i guess for holding info about selected tab), i've changed this (basically c'n'p necessary stuff from UIOutput to ATogP) and now ATogP extends UIRepeat ... (08:31:55 AM) blabno: ok, I understand, well, as with carousel component i've noticed that there are use cases where component may be used as iterative or non-iterative (08:32:26 AM) blabno: i.e. we want to have fixed 3 tabs, so we hardcode (08:33:22 AM) blabno: this is how i've done it for carousel and it works like a charm (08:33:42 AM) blabno: however here with those tabs it's very hard (08:34:17 AM) blabno: especiale because of that getActiveItem method (used in many places to see if tab should be executed,updated,validated,etc) (08:35:18 AM) blabno: so the datamodel (in case of iterative case) is being visited over and over again (08:36:33 AM) blabno: the impl of that method is very annoying (08:36:51 AM) blabno: first it gets activeItem which is string (08:37:12 AM) blabno: then runs over all tabs to see if that tab is disabled (08:37:29 AM) blabno: and in such case it switches to the first item (08:37:46 AM) blabno: but anyways, optimization can be done later, right now i'm having problem with ajax (08:37:54 AM) blabno: client and server switches work great (08:40:25 AM) blabno: in short the problem is with switching tab in ajax mode (08:41:18 AM) bleathem: what goes wrong? (08:41:26 AM) blabno: partialContext first wants to estblish which components should be executed, and only later it sets submited value (selected tab) so the new tab is not rendered in response (08:41:56 AM) blabno: because (i suspect) getActiveItem points to old tab and is changed when submitted value is set (08:42:23 AM) blabno: and that getActiveItem is used in determining if tab should be processed (08:43:07 AM) blabno: i must have messed sth up, cause old version of component worked, but i'm stuck and fresh eye would be handy {quote} > AbstractTogglePanel should extend UIRepeat, instead of UIOutput > --------------------------------------------------------------- > > Key: RF-12029 > URL: https://issues.jboss.org/browse/RF-12029 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-output > Reporter: Brian Leathem > Assignee: Bernard Labno > > Valid uses exist for dynamically generating rich:tab, rich:togglePanelItem, rich:accordionItem. Current techniques for supporting this use case involve using c:forEach, which is a problem since c: tags are processed too early to nicely support dynamic use cases. > One idea to support this use case, is to have AbstractTogglePanel extend UIRepeat, instead of UIOutput to better dynamic child components. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 7 19:47:41 2012 From: jira-events at lists.jboss.org (RH Bugzilla Integration (JIRA)) Date: Wed, 7 Mar 2012 19:47:41 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12019) Upstream mojarra issue requires IE9 to be in compatibility mode In-Reply-To: <676753656.53754.1330535076071.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1697044613.75775.1331167661324.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12674943#comment-12674943 ] RH Bugzilla Integration commented on RF-12019: ---------------------------------------------- Rebecca Newton made a comment on [bug 800628|https://bugzilla.redhat.com/show_bug.cgi?id=800628] Brian, is this bug closed (Fixed Issue) or open (Known Issue)? If this is the last we will ever hear about it, it should be a closed issue. If the solution to run in compatibility mode is a temporary workaround and a full fix will be found later, it should be a known issue. And, is this the information the customer needs, to add the meta tag (taken from the included link)?: Specifying Document Compatibility Modes Document compatibility modes allow you to control the way Internet Explorer interprets and displays your webpage. To specify a specific document mode for your webpage, use the meta element to include an X-UA-Compatible header in your webpage. The following example specifies EmulateIE7 mode. My webpage

Content goes here.

Thanks! > Upstream mojarra issue requires IE9 to be in compatibility mode > --------------------------------------------------------------- > > Key: RF-12019 > URL: https://issues.jboss.org/browse/RF-12019 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: third-party > Reporter: Brian Leathem > Fix For: 4.3.0.Milestone1 > > > An upstream issue with mojarra ([JAVASERVERFACES-2063|http://java.net/jira/browse/JAVASERVERFACES-2063]) requires that IE9 be placed in compatibility mode. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 7 19:47:41 2012 From: jira-events at lists.jboss.org (RH Bugzilla Integration (JIRA)) Date: Wed, 7 Mar 2012 19:47:41 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12019) Upstream mojarra issue requires IE9 to be in compatibility mode In-Reply-To: <676753656.53754.1330535076071.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1998596535.75776.1331167661353.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12674944#comment-12674944 ] RH Bugzilla Integration commented on RF-12019: ---------------------------------------------- Rebecca Newton made a comment on [bug 800628|https://bugzilla.redhat.com/show_bug.cgi?id=800628] Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1 +1,3 @@ -An upstream issue (http://java.net/jira/browse/JAVASERVERFACES-2063) requires IE 9 to be run in compatibility mode. This can be accomplished by adding a meta tag to your page template, as described in: http://msdn.microsoft.com/en-us/library/cc288325(v=vs.85).aspx#SetMode.+An upstream issue requires IE 9 to be run in compatibility mode. To run Internet Explorer 9 in compatibility mode, add a meta tag to your page like this: + +This can be accomplished by adding a meta tag to your page template, as described in: http://msdn.microsoft.com/en-us/library/cc288325(v=vs.85).aspx#SetMode. > Upstream mojarra issue requires IE9 to be in compatibility mode > --------------------------------------------------------------- > > Key: RF-12019 > URL: https://issues.jboss.org/browse/RF-12019 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: third-party > Reporter: Brian Leathem > Fix For: 4.3.0.Milestone1 > > > An upstream issue with mojarra ([JAVASERVERFACES-2063|http://java.net/jira/browse/JAVASERVERFACES-2063]) requires that IE9 be placed in compatibility mode. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 7 20:02:36 2012 From: jira-events at lists.jboss.org (RH Bugzilla Integration (JIRA)) Date: Wed, 7 Mar 2012 20:02:36 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12019) Upstream mojarra issue requires IE9 to be in compatibility mode In-Reply-To: <676753656.53754.1330535076071.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1938602888.75814.1331168556349.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12674948#comment-12674948 ] RH Bugzilla Integration commented on RF-12019: ---------------------------------------------- Brian Leathem made a comment on [bug 800628|https://bugzilla.redhat.com/show_bug.cgi?id=800628] Hi Bec, This is an open, known issue, with a workaround. It is an upstream issue that has been resolved, and we will incorporate the fix in out next micro release (4.2.1). The code snippet you extracted from the linked page is indeed the correct instructions for the workaround. > Upstream mojarra issue requires IE9 to be in compatibility mode > --------------------------------------------------------------- > > Key: RF-12019 > URL: https://issues.jboss.org/browse/RF-12019 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: third-party > Reporter: Brian Leathem > Fix For: 4.3.0.Milestone1 > > > An upstream issue with mojarra ([JAVASERVERFACES-2063|http://java.net/jira/browse/JAVASERVERFACES-2063]) requires that IE9 be placed in compatibility mode. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 7 20:28:36 2012 From: jira-events at lists.jboss.org (RH Bugzilla Integration (JIRA)) Date: Wed, 7 Mar 2012 20:28:36 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12019) Upstream mojarra issue requires IE9 to be in compatibility mode In-Reply-To: <676753656.53754.1330535076071.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <299920255.75844.1331170116391.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12674953#comment-12674953 ] RH Bugzilla Integration commented on RF-12019: ---------------------------------------------- Rebecca Newton made a comment on [bug 800628|https://bugzilla.redhat.com/show_bug.cgi?id=800628] Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1,3 +1,14 @@ An upstream issue requires IE 9 to be run in compatibility mode. To run Internet Explorer 9 in compatibility mode, add a meta tag to your page like this: -This can be accomplished by adding a meta tag to your page template, as described in: http://msdn.microsoft.com/en-us/library/cc288325(v=vs.85).aspx#SetMode.+ + + + + My webpage + + +

Content goes here.

+ + + +See http://msdn.microsoft.com/en-us/library/cc288325(v=vs.85).aspx#SetMode.for more information. > Upstream mojarra issue requires IE9 to be in compatibility mode > --------------------------------------------------------------- > > Key: RF-12019 > URL: https://issues.jboss.org/browse/RF-12019 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: third-party > Reporter: Brian Leathem > Fix For: 4.3.0.Milestone1 > > > An upstream issue with mojarra ([JAVASERVERFACES-2063|http://java.net/jira/browse/JAVASERVERFACES-2063]) requires that IE9 be placed in compatibility mode. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 8 04:00:37 2012 From: jira-events at lists.jboss.org (Rene O (JIRA)) Date: Thu, 8 Mar 2012 04:00:37 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12030) rich:dataScroller doesn't work if a rich:message exists inside of a collapsed rich:collapsiblePanel with switchType='ajax' Message-ID: <474795285.76394.1331197237559.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Rene O created RF-12030: --------------------------- Summary: rich:dataScroller doesn't work if a rich:message exists inside of a collapsed rich:collapsiblePanel with switchType='ajax' Key: RF-12030 URL: https://issues.jboss.org/browse/RF-12030 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.2.0.Final Environment: tomcat 7, richfaces-4.2.0.Final, myfaces-2.1.6 Reporter: Rene O rich:dataScroller doesn't work if a rich:message exists inside of a collapsed rich:collapsiblePanel with switchType='ajax' Steps to reproduce this issue: 1. use dataScroller to switch table-pages. you can see, that this works. 2. collaps collapsiblePanel 3. if collapsiblePanel is collapsed, the dataScroller doesn't react anymore. 4. if you use switchType='client' everything works correct {code:title=examplepage.xhtml} JSF Test if rich:message doesn't exists, everything works... ColA #{item.itemA} {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 8 04:24:36 2012 From: jira-events at lists.jboss.org (Andries Ehlers (JIRA)) Date: Thu, 8 Mar 2012 04:24:36 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12031) rich:validator does not work after re render (ajax) Message-ID: <245851677.76479.1331198676205.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Andries Ehlers created RF-12031: ----------------------------------- Summary: rich:validator does not work after re render (ajax) Key: RF-12031 URL: https://issues.jboss.org/browse/RF-12031 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.2.0.Final Reporter: Andries Ehlers When you have a simple inputText component with rich:validator inside, validation works perfectly when you move focus away from the component - validation messages display, e.g: {code:xml|borderStyle=solid} {code} If the above code resides in a panel, which is conditionally rendered, then ceases to function when you re-render the panel with ajax, eg: {code:xml|borderStyle=solid}
{code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 8 08:03:36 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?J=C3=A1n_Jamrich_=28JIRA=29?=) Date: Thu, 8 Mar 2012 08:03:36 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11902) [rich:autocomplete] add attribute queueId In-Reply-To: <1022848615.10266.1326969138391.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1108170142.77276.1331211816402.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] J?n Jamrich reassigned RF-11902: -------------------------------- Assignee: (was: J?n Jamrich) Issue simulated in Metamer using code snippet provided by reporter. See following commit for more details: https://github.com/richfaces/qa/commit/eb60f82f7b80f6e6d1a1f4762b4a981d41a18466 > [rich:autocomplete] add attribute queueId > ----------------------------------------- > > Key: RF-11902 > URL: https://issues.jboss.org/browse/RF-11902 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 4.1.0.Final > Reporter: Rene O > > It would be nice if rich:autocomplete has an attribute queueId like a4j:ajax component. With this you will have more control over the ajax requests if ajax mode is enabled within autocomplete component. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 8 10:35:40 2012 From: jira-events at lists.jboss.org (Jean ANDRE (JIRA)) Date: Thu, 8 Mar 2012 10:35:40 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12032) rich:calendar : Ajax request - Error message enhancement - sql.Date Message-ID: <1406650855.77949.1331220940774.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Jean ANDRE created RF-12032: ------------------------------- Summary: rich:calendar : Ajax request - Error message enhancement - sql.Date Key: RF-12032 URL: https://issues.jboss.org/browse/RF-12032 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Environment: cssparser-0.9.6 - guava-11.0.1 - hibernate-validator-4.2.0.Final - JSF/Mojarra 2.1.6 - springframework-3.0.6.RELEASE - richfaces-4.2.0.Final - sac-1.3.jar - Windows 7, WAS 8.0.0.1, Servlet 2.5 - Java 6. Reporter: Jean ANDRE When a backing-bean have a type of sql.Date which is mapped to a rich:calendar, there is an conversion error due to the rich:calendar component uses util.Date by default. Unfortunately, we do not see any error message at the screen when an ajax request is sent and returned back to us. What we got, and thanks to Firebug, is the text below as an answer from our Ajax request POST. Nothing is rendered at the screen and the method of the backing bean is not called. {code} class javax.faces.component.UpdateModelException {code} Our code looks like this (we remove unecessary field and decoration): {code} {code} Is is possible to have a message returned back to the UI??? or is there a way to handle this error properly? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 8 10:39:36 2012 From: jira-events at lists.jboss.org (Jean ANDRE (JIRA)) Date: Thu, 8 Mar 2012 10:39:36 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12032) rich:calendar : Ajax request - Error message enhancement - sql.Date In-Reply-To: <1406650855.77949.1331220940774.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <655044029.77976.1331221176406.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean ANDRE updated RF-12032: ---------------------------- Description: When a backing-bean have a type of sql.Date which is mapped to a rich:calendar, there is an conversion error due to the rich:calendar component uses util.Date by default. Unfortunately, we do not see any error message at the screen when an ajax request is sent and returned back to us. What we got, and thanks to Firebug, is the text below as an answer from our Ajax request POST. Nothing is rendered at the screen and the method of the backing bean is not called. {code} class javax.faces.component.UpdateModelException {code} Our code looks like this (we remove unecessary field and decoration): {code} {code} Is is possible to have a message returned back to the UI??? or is there a way to handle this error properly? Other information ================= The form is inside a dynamic tab - Fragment are also include dynamically - we use c:if et subView as shown below: {code} {code} was: When a backing-bean have a type of sql.Date which is mapped to a rich:calendar, there is an conversion error due to the rich:calendar component uses util.Date by default. Unfortunately, we do not see any error message at the screen when an ajax request is sent and returned back to us. What we got, and thanks to Firebug, is the text below as an answer from our Ajax request POST. Nothing is rendered at the screen and the method of the backing bean is not called. {code} class javax.faces.component.UpdateModelException {code} Our code looks like this (we remove unecessary field and decoration): {code} {code} Is is possible to have a message returned back to the UI??? or is there a way to handle this error properly? > rich:calendar : Ajax request - Error message enhancement - sql.Date > ------------------------------------------------------------------- > > Key: RF-12032 > URL: https://issues.jboss.org/browse/RF-12032 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Environment: cssparser-0.9.6 - guava-11.0.1 - hibernate-validator-4.2.0.Final - JSF/Mojarra 2.1.6 - springframework-3.0.6.RELEASE - richfaces-4.2.0.Final - sac-1.3.jar - Windows 7, WAS 8.0.0.1, Servlet 2.5 - Java 6. > Reporter: Jean ANDRE > > When a backing-bean have a type of sql.Date which is mapped to a rich:calendar, there is an conversion error due to the rich:calendar component uses util.Date by default. Unfortunately, we do not see any error message at the screen when an ajax request is sent and returned back to us. > What we got, and thanks to Firebug, is the text below as an answer from our Ajax request POST. Nothing is rendered at the screen and the method of the backing bean is not called. > {code} > > class javax.faces.component.UpdateModelException > {code} > Our code looks like this (we remove unecessary field and decoration): > {code} > > > > > value="#{msg['common.command.add.phone']}" > action="#{createClientController.doAddPhone}"> > > > > > > > value="#{phoneBean.effectiveDate}" > popup="true" > showApplyButton="false" > enableManualInput="true" > datePattern="#{msg['client.date.format']}" > inputSize="12" > styleClass="calendar"> > > > > > > > > {code} > Is is possible to have a message returned back to the UI??? or is there a way to handle this error properly? > Other information > ================= > The form is inside a dynamic tab - Fragment are also include dynamically - we use c:if et subView as shown below: > {code} > > > > > > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 8 10:53:36 2012 From: jira-events at lists.jboss.org (Jean ANDRE (JIRA)) Date: Thu, 8 Mar 2012 10:53:36 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12032) rich:calendar : Ajax request - Error message enhancement - sql.Date In-Reply-To: <1406650855.77949.1331220940774.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1711131224.78101.1331222016229.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean ANDRE updated RF-12032: ---------------------------- Attachment: rich_calendar_errorMsg_Enhancement.png Here a sample of our screen to give you only an idea of our form. > rich:calendar : Ajax request - Error message enhancement - sql.Date > ------------------------------------------------------------------- > > Key: RF-12032 > URL: https://issues.jboss.org/browse/RF-12032 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Environment: cssparser-0.9.6 - guava-11.0.1 - hibernate-validator-4.2.0.Final - JSF/Mojarra 2.1.6 - springframework-3.0.6.RELEASE - richfaces-4.2.0.Final - sac-1.3.jar - Windows 7, WAS 8.0.0.1, Servlet 2.5 - Java 6. > Reporter: Jean ANDRE > Attachments: rich_calendar_errorMsg_Enhancement.png > > > When a backing-bean have a type of sql.Date which is mapped to a rich:calendar, there is an conversion error due to the rich:calendar component uses util.Date by default. Unfortunately, we do not see any error message at the screen when an ajax request is sent and returned back to us. > What we got, and thanks to Firebug, is the text below as an answer from our Ajax request POST. Nothing is rendered at the screen and the method of the backing bean is not called. > {code} > > class javax.faces.component.UpdateModelException > {code} > Our code looks like this (we remove unecessary field and decoration): > {code} > > > > > value="#{msg['common.command.add.phone']}" > action="#{createClientController.doAddPhone}"> > > > > > > > value="#{phoneBean.effectiveDate}" > popup="true" > showApplyButton="false" > enableManualInput="true" > datePattern="#{msg['client.date.format']}" > inputSize="12" > styleClass="calendar"> > > > > > > > > {code} > Is is possible to have a message returned back to the UI??? or is there a way to handle this error properly? > Other information > ================= > The form is inside a dynamic tab - Fragment are also include dynamically - we use c:if et subView as shown below: > {code} > > > > > > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 8 15:37:36 2012 From: jira-events at lists.jboss.org (Jean ANDRE (JIRA)) Date: Thu, 8 Mar 2012 15:37:36 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11763) javascript error : item is undefined on nested tabPanel with switchType='ajax' In-Reply-To: <984864127.56421.1322674601141.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <822625650.78834.1331239056362.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean ANDRE updated RF-11763: ---------------------------- Steps to Reproduce: See also RF-11750 but basically we have two level of tab:Panel (a.k.a nested tab). See screen shot. The parent tab is ajax switchType The child tab is ajax swithType - When 'client' switchType is working but from our side, refreshing the whole page is performance penalty as we have many 'customer' files opened at the same. Each file (which is a tab) can contains at least 6 tabs up to 15. was: See also RF-11750 but basically we have two level of tab:Panel (a.k.a nested tab). See screen shot. The parent tab is ajax switchType The child tab is ajax swithType - When 'client' switchType is working well but not ajax available...:( > javascript error : item is undefined on nested tabPanel with switchType='ajax' > ------------------------------------------------------------------------------ > > Key: RF-11763 > URL: https://issues.jboss.org/browse/RF-11763 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.1.0.CR1 > Environment: Websphere 8 - RAD 8 - JSF Mojorra 2.1.4 - Spring 3.0.6 Final - Use @Inject @Named @SessionScoped as annotations - Firefox 7.0.1 - Windows 7 (6.1 sp1) - AspectJ 1.6.12 / AJDT > Reporter: Jean ANDRE > Priority: Blocker > Fix For: 4.Future > > Attachments: screenshot-1.jpg > > > See also RF-11750 for the context. > Briefly, we have nested tabPanel - The firs tabPanel is made of static and dynamic tabPanel. One tabPanel contains the search form. When the user performs a search and for each search we open a new tab that contains the result list. When the user click on an item, we update the tab with the detailed information. > The detailed information is made of 6 tabs - There are like a subtabs from the parent tabs. When we set the switchType to 'client' the tab performs well. But as we want that the same tab serves as form to edit and view the detailed information, we want to refresh the tab to display the inputText instead of the outputText. This is the edit mode. > Then, we need to refresh the tab and we decided to pass in ajax switchType for theses subTab. Owener, switching to the 'ajax' triggers a javascript error that blocks the UI. None tab is selectable, user cannot switch from a tab to another tab. Moreover we failed to refresh the tab but the reason is still unknown. > Javascript error is : > {code} > item is undefined - [Stopper sur une erreur] if (!item.disabled && item.getName() === itemName) { > toggle...chfaces (ligne 363) > http://localhost:12000/crm/javax.faces.resource/togglePanel.js.jsf?ln=org.richfaces > {code} > The involved code is (where >>>> is): > {code} > /** > * @private > * */ > __getItemIndex : function (itemName) { > var item; > for (var i = 0; i < this.items.length; i++) { > item = this.items[i]; > >>>>>> if (!item.disabled && item.getName() === itemName) { > return i; > } > } > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 8 15:49:36 2012 From: jira-events at lists.jboss.org (Jean ANDRE (JIRA)) Date: Thu, 8 Mar 2012 15:49:36 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11763) javascript error : item is undefined on nested tabPanel with switchType='ajax' In-Reply-To: <984864127.56421.1322674601141.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1160413021.78866.1331239776503.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12675292#comment-12675292 ] Jean ANDRE commented on RF-11763: --------------------------------- This bug is still here in 4.2 - Actually, we are in 'server' mode, but in 'client' mode, ajax request with "@form' lost the current tab - it like refreshing the whole page. ActiveItem does not seems take in account in this mode. It would be nice to resolve this bug because 'sever' or 'client' switchType is so-so. In fact, this bug does not allow us to switch from a tab to another tab. See also the 2 second screen shot to give you an idea of the bug and also of our screen. > javascript error : item is undefined on nested tabPanel with switchType='ajax' > ------------------------------------------------------------------------------ > > Key: RF-11763 > URL: https://issues.jboss.org/browse/RF-11763 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.1.0.CR1 > Environment: Websphere 8 - RAD 8 - JSF Mojorra 2.1.4 - Spring 3.0.6 Final - Use @Inject @Named @SessionScoped as annotations - Firefox 7.0.1 - Windows 7 (6.1 sp1) - AspectJ 1.6.12 / AJDT > Reporter: Jean ANDRE > Priority: Blocker > Fix For: 4.Future > > Attachments: RF-11763_ScreenShot.png, screenshot-1.jpg > > > See also RF-11750 for the context. > Briefly, we have nested tabPanel - The firs tabPanel is made of static and dynamic tabPanel. One tabPanel contains the search form. When the user performs a search and for each search we open a new tab that contains the result list. When the user click on an item, we update the tab with the detailed information. > The detailed information is made of 6 tabs - There are like a subtabs from the parent tabs. When we set the switchType to 'client' the tab performs well. But as we want that the same tab serves as form to edit and view the detailed information, we want to refresh the tab to display the inputText instead of the outputText. This is the edit mode. > Then, we need to refresh the tab and we decided to pass in ajax switchType for theses subTab. Owener, switching to the 'ajax' triggers a javascript error that blocks the UI. None tab is selectable, user cannot switch from a tab to another tab. Moreover we failed to refresh the tab but the reason is still unknown. > Javascript error is : > {code} > item is undefined - [Stopper sur une erreur] if (!item.disabled && item.getName() === itemName) { > toggle...chfaces (ligne 363) > http://localhost:12000/crm/javax.faces.resource/togglePanel.js.jsf?ln=org.richfaces > {code} > The involved code is (where >>>> is): > {code} > /** > * @private > * */ > __getItemIndex : function (itemName) { > var item; > for (var i = 0; i < this.items.length; i++) { > item = this.items[i]; > >>>>>> if (!item.disabled && item.getName() === itemName) { > return i; > } > } > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 8 15:49:37 2012 From: jira-events at lists.jboss.org (Jean ANDRE (JIRA)) Date: Thu, 8 Mar 2012 15:49:37 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11763) javascript error : item is undefined on nested tabPanel with switchType='ajax' In-Reply-To: <984864127.56421.1322674601141.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1799117644.78873.1331239777078.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean ANDRE updated RF-11763: ---------------------------- Attachment: RF-11763_ScreenShot.png Screen shot - JavaScript error during the tab switch. > javascript error : item is undefined on nested tabPanel with switchType='ajax' > ------------------------------------------------------------------------------ > > Key: RF-11763 > URL: https://issues.jboss.org/browse/RF-11763 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.1.0.CR1 > Environment: Websphere 8 - RAD 8 - JSF Mojorra 2.1.4 - Spring 3.0.6 Final - Use @Inject @Named @SessionScoped as annotations - Firefox 7.0.1 - Windows 7 (6.1 sp1) - AspectJ 1.6.12 / AJDT > Reporter: Jean ANDRE > Priority: Blocker > Fix For: 4.Future > > Attachments: RF-11763_ScreenShot.png, screenshot-1.jpg > > > See also RF-11750 for the context. > Briefly, we have nested tabPanel - The firs tabPanel is made of static and dynamic tabPanel. One tabPanel contains the search form. When the user performs a search and for each search we open a new tab that contains the result list. When the user click on an item, we update the tab with the detailed information. > The detailed information is made of 6 tabs - There are like a subtabs from the parent tabs. When we set the switchType to 'client' the tab performs well. But as we want that the same tab serves as form to edit and view the detailed information, we want to refresh the tab to display the inputText instead of the outputText. This is the edit mode. > Then, we need to refresh the tab and we decided to pass in ajax switchType for theses subTab. Owener, switching to the 'ajax' triggers a javascript error that blocks the UI. None tab is selectable, user cannot switch from a tab to another tab. Moreover we failed to refresh the tab but the reason is still unknown. > Javascript error is : > {code} > item is undefined - [Stopper sur une erreur] if (!item.disabled && item.getName() === itemName) { > toggle...chfaces (ligne 363) > http://localhost:12000/crm/javax.faces.resource/togglePanel.js.jsf?ln=org.richfaces > {code} > The involved code is (where >>>> is): > {code} > /** > * @private > * */ > __getItemIndex : function (itemName) { > var item; > for (var i = 0; i < this.items.length; i++) { > item = this.items[i]; > >>>>>> if (!item.disabled && item.getName() === itemName) { > return i; > } > } > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 8 15:55:36 2012 From: jira-events at lists.jboss.org (Jean ANDRE (JIRA)) Date: Thu, 8 Mar 2012 15:55:36 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11763) javascript error : item is undefined on nested tabPanel with switchType='ajax' In-Reply-To: <984864127.56421.1322674601141.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <53775961.78891.1331240136185.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12675296#comment-12675296 ] Jean ANDRE commented on RF-11763: --------------------------------- Due to the error, the ajax response is partial. {code} ]]>
{code} > javascript error : item is undefined on nested tabPanel with switchType='ajax' > ------------------------------------------------------------------------------ > > Key: RF-11763 > URL: https://issues.jboss.org/browse/RF-11763 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.1.0.CR1 > Environment: Websphere 8 - RAD 8 - JSF Mojorra 2.1.4 - Spring 3.0.6 Final - Use @Inject @Named @SessionScoped as annotations - Firefox 7.0.1 - Windows 7 (6.1 sp1) - AspectJ 1.6.12 / AJDT > Reporter: Jean ANDRE > Priority: Blocker > Fix For: 4.Future > > Attachments: RF-11763_ScreenShot.png, screenshot-1.jpg > > > See also RF-11750 for the context. > Briefly, we have nested tabPanel - The firs tabPanel is made of static and dynamic tabPanel. One tabPanel contains the search form. When the user performs a search and for each search we open a new tab that contains the result list. When the user click on an item, we update the tab with the detailed information. > The detailed information is made of 6 tabs - There are like a subtabs from the parent tabs. When we set the switchType to 'client' the tab performs well. But as we want that the same tab serves as form to edit and view the detailed information, we want to refresh the tab to display the inputText instead of the outputText. This is the edit mode. > Then, we need to refresh the tab and we decided to pass in ajax switchType for theses subTab. Owener, switching to the 'ajax' triggers a javascript error that blocks the UI. None tab is selectable, user cannot switch from a tab to another tab. Moreover we failed to refresh the tab but the reason is still unknown. > Javascript error is : > {code} > item is undefined - [Stopper sur une erreur] if (!item.disabled && item.getName() === itemName) { > toggle...chfaces (ligne 363) > http://localhost:12000/crm/javax.faces.resource/togglePanel.js.jsf?ln=org.richfaces > {code} > The involved code is (where >>>> is): > {code} > /** > * @private > * */ > __getItemIndex : function (itemName) { > var item; > for (var i = 0; i < this.items.length; i++) { > item = this.items[i]; > >>>>>> if (!item.disabled && item.getName() === itemName) { > return i; > } > } > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 8 16:15:37 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Marek_B=C4=99dkowski_=28JIRA=29?=) Date: Thu, 8 Mar 2012 16:15:37 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-8608) rich:effect name does not properly create the JS function to be called In-Reply-To: <1051306858.1271854511462.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com> Message-ID: <454452341.78908.1331241337121.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-8608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marek B?dkowski updated RF-8608: -------------------------------- Attachment: processEffect.js.patch Patch to processEffect removing with and eval statements. > rich:effect name does not properly create the JS function to be called > ---------------------------------------------------------------------- > > Key: RF-8608 > URL: https://issues.jboss.org/browse/RF-8608 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-misc, regression > Affects Versions: 3.3.3.Final > Reporter: Tomas Cerny > Fix For: 3.Future > > Attachments: processEffect.js.patch, richFacesRegister.xhtml > > > rich:effect name does not properly create the JS function.. > Consider your documentation example: > >
...
> > > > > it worked on the older version but in 3.3.3 so I must downgrade :| > This is my browser complaint: > Error: Effect[A.type] is not a constructor > Source File: http://localhost/a4j/g/3_3_3.Final/org/richfaces/ui.pack.js > Line: 15201 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 8 16:17:36 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Marek_B=C4=99dkowski_=28JIRA=29?=) Date: Thu, 8 Mar 2012 16:17:36 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-8608) rich:effect name does not properly create the JS function to be called In-Reply-To: <1051306858.1271854511462.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com> Message-ID: <506041663.78915.1331241456461.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-8608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12675300#comment-12675300 ] Marek B?dkowski commented on RF-8608: ------------------------------------- If you experience this problem and still using richfaces 3.3.x - please ignore comment above by Thomas Cerny, it doesn't change anything (btw I've no idea how it should since it's just swapping variable name in the local context). To make it quick - just apply the supplied patch (processEffect.js.patch) to the formentioned processEffect.js file - current solution there uses two of the top 10 JS worst practices: with and eval :) Enjoy! > rich:effect name does not properly create the JS function to be called > ---------------------------------------------------------------------- > > Key: RF-8608 > URL: https://issues.jboss.org/browse/RF-8608 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-misc, regression > Affects Versions: 3.3.3.Final > Reporter: Tomas Cerny > Fix For: 3.Future > > Attachments: processEffect.js.patch, richFacesRegister.xhtml > > > rich:effect name does not properly create the JS function.. > Consider your documentation example: > >
...
> > > > > it worked on the older version but in 3.3.3 so I must downgrade :| > This is my browser complaint: > Error: Effect[A.type] is not a constructor > Source File: http://localhost/a4j/g/3_3_3.Final/org/richfaces/ui.pack.js > Line: 15201 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 8 16:17:36 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Marek_B=C4=99dkowski_=28JIRA=29?=) Date: Thu, 8 Mar 2012 16:17:36 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-8608) rich:effect name does not properly create the JS function to be called In-Reply-To: <1051306858.1271854511462.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com> Message-ID: <903141810.78922.1331241456945.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-8608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12675300#comment-12675300 ] Marek B?dkowski edited comment on RF-8608 at 3/8/12 4:17 PM: ------------------------------------------------------------- If you experience this problem and still using richfaces 3.3.x - please ignore comment above by Thomas Cerny, swapping local variable names seemed to make no difference in my environment. To make it quick - just apply the supplied patch (processEffect.js.patch) to the formentioned processEffect.js file - I got rid of 'with' and 'eval' evils and seems to work :) Enjoy! was (Author: bendi): If you experience this problem and still using richfaces 3.3.x - please ignore comment above by Thomas Cerny, it doesn't change anything (btw I've no idea how it should since it's just swapping variable name in the local context). To make it quick - just apply the supplied patch (processEffect.js.patch) to the formentioned processEffect.js file - current solution there uses two of the top 10 JS worst practices: with and eval :) Enjoy! > rich:effect name does not properly create the JS function to be called > ---------------------------------------------------------------------- > > Key: RF-8608 > URL: https://issues.jboss.org/browse/RF-8608 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-misc, regression > Affects Versions: 3.3.3.Final > Reporter: Tomas Cerny > Fix For: 3.Future > > Attachments: processEffect.js.patch, richFacesRegister.xhtml > > > rich:effect name does not properly create the JS function.. > Consider your documentation example: > >
...
> > > > > it worked on the older version but in 3.3.3 so I must downgrade :| > This is my browser complaint: > Error: Effect[A.type] is not a constructor > Source File: http://localhost/a4j/g/3_3_3.Final/org/richfaces/ui.pack.js > Line: 15201 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 8 16:19:36 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Marek_B=C4=99dkowski_=28JIRA=29?=) Date: Thu, 8 Mar 2012 16:19:36 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-8608) rich:effect name does not properly create the JS function to be called In-Reply-To: <1051306858.1271854511462.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com> Message-ID: <2086289423.78929.1331241576642.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-8608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12675300#comment-12675300 ] Marek B?dkowski edited comment on RF-8608 at 3/8/12 4:19 PM: ------------------------------------------------------------- Hi Since the problem still exists in 3.3.3.Final I decided to prepare a patch (processEffect.js.patch) to the formentioned processEffect.js file - I got rid of 'with' and 'eval' evils and seems to do the trick :) @Thomas - I tried swapping variable name from params to myparams but it made no difference. was (Author: bendi): If you experience this problem and still using richfaces 3.3.x - please ignore comment above by Thomas Cerny, swapping local variable names seemed to make no difference in my environment. To make it quick - just apply the supplied patch (processEffect.js.patch) to the formentioned processEffect.js file - I got rid of 'with' and 'eval' evils and seems to work :) Enjoy! > rich:effect name does not properly create the JS function to be called > ---------------------------------------------------------------------- > > Key: RF-8608 > URL: https://issues.jboss.org/browse/RF-8608 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-misc, regression > Affects Versions: 3.3.3.Final > Reporter: Tomas Cerny > Fix For: 3.Future > > Attachments: processEffect.js.patch, richFacesRegister.xhtml > > > rich:effect name does not properly create the JS function.. > Consider your documentation example: > >
...
> > > > > it worked on the older version but in 3.3.3 so I must downgrade :| > This is my browser complaint: > Error: Effect[A.type] is not a constructor > Source File: http://localhost/a4j/g/3_3_3.Final/org/richfaces/ui.pack.js > Line: 15201 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 9 09:42:37 2012 From: jira-events at lists.jboss.org (RH Bugzilla Integration (JIRA)) Date: Fri, 9 Mar 2012 09:42:37 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11739) Components that don't require jsf.js can break ResourceMapping In-Reply-To: <445024762.41821.1322186680654.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <2038048861.81724.1331304157193.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12675510#comment-12675510 ] RH Bugzilla Integration commented on RF-11739: ---------------------------------------------- Marek Novotny changed the Status of [bug 801172|https://bugzilla.redhat.com/show_bug.cgi?id=801172] from NEW to ASSIGNED > Components that don't require jsf.js can break ResourceMapping > -------------------------------------------------------------- > > Key: RF-11739 > URL: https://issues.jboss.org/browse/RF-11739 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: resource handling > Affects Versions: 4.0.0.CR1 > Reporter: Brian Leathem > Assignee: Luk?? Fry? > Fix For: 4.3-Tracking > > > This bug is only observable when resourceMapping is enabled. > If a component doesn't require jsf.js, and it is the first component to require a resource, it will trigger packed.js to redner before jsf.js. This breaks some of the scripts in packed.js, that require jsf.js. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 9 14:08:36 2012 From: jira-events at lists.jboss.org (RH Bugzilla Integration (JIRA)) Date: Fri, 9 Mar 2012 14:08:36 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11739) Components that don't require jsf.js can break ResourceMapping In-Reply-To: <445024762.41821.1322186680654.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <650145397.82355.1331320116752.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12675587#comment-12675587 ] RH Bugzilla Integration commented on RF-11739: ---------------------------------------------- Marek Novotny changed the Status of [bug 801172|https://bugzilla.redhat.com/show_bug.cgi?id=801172] from ASSIGNED to ON_DEV > Components that don't require jsf.js can break ResourceMapping > -------------------------------------------------------------- > > Key: RF-11739 > URL: https://issues.jboss.org/browse/RF-11739 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: resource handling > Affects Versions: 4.0.0.CR1 > Reporter: Brian Leathem > Assignee: Luk?? Fry? > Fix For: 4.3-Tracking > > > This bug is only observable when resourceMapping is enabled. > If a component doesn't require jsf.js, and it is the first component to require a resource, it will trigger packed.js to redner before jsf.js. This breaks some of the scripts in packed.js, that require jsf.js. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 9 14:08:36 2012 From: jira-events at lists.jboss.org (RH Bugzilla Integration (JIRA)) Date: Fri, 9 Mar 2012 14:08:36 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11739) Components that don't require jsf.js can break ResourceMapping In-Reply-To: <445024762.41821.1322186680654.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1125290668.82356.1331320116811.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12675588#comment-12675588 ] RH Bugzilla Integration commented on RF-11739: ---------------------------------------------- Marek Novotny made a comment on [bug 801172|https://bugzilla.redhat.com/show_bug.cgi?id=801172] I have found where the origin intention for changing the scope was. Showcase hides jboss profile for variable dependency-scope for jsf-impl. > Components that don't require jsf.js can break ResourceMapping > -------------------------------------------------------------- > > Key: RF-11739 > URL: https://issues.jboss.org/browse/RF-11739 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: resource handling > Affects Versions: 4.0.0.CR1 > Reporter: Brian Leathem > Assignee: Luk?? Fry? > Fix For: 4.3-Tracking > > > This bug is only observable when resourceMapping is enabled. > If a component doesn't require jsf.js, and it is the first component to require a resource, it will trigger packed.js to redner before jsf.js. This breaks some of the scripts in packed.js, that require jsf.js. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 9 14:52:36 2012 From: jira-events at lists.jboss.org (RH Bugzilla Integration (JIRA)) Date: Fri, 9 Mar 2012 14:52:36 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11739) Components that don't require jsf.js can break ResourceMapping In-Reply-To: <445024762.41821.1322186680654.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <857126560.82424.1331322756340.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12675601#comment-12675601 ] RH Bugzilla Integration commented on RF-11739: ---------------------------------------------- Marek Novotny made a comment on [bug 801172|https://bugzilla.redhat.com/show_bug.cgi?id=801172] After rebuild, the line with: javax.faces\:jsf.js disappeared, so I consider that as fixed. > Components that don't require jsf.js can break ResourceMapping > -------------------------------------------------------------- > > Key: RF-11739 > URL: https://issues.jboss.org/browse/RF-11739 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: resource handling > Affects Versions: 4.0.0.CR1 > Reporter: Brian Leathem > Assignee: Luk?? Fry? > Fix For: 4.3-Tracking > > > This bug is only observable when resourceMapping is enabled. > If a component doesn't require jsf.js, and it is the first component to require a resource, it will trigger packed.js to redner before jsf.js. This breaks some of the scripts in packed.js, that require jsf.js. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 9 15:24:36 2012 From: jira-events at lists.jboss.org (Josh Hill (JIRA)) Date: Fri, 9 Mar 2012 15:24:36 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12033) ExtendedDataTable doesn't show up in tabpanel with switchType="client" Message-ID: <1476360638.82467.1331324676272.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Josh Hill created RF-12033: ------------------------------ Summary: ExtendedDataTable doesn't show up in tabpanel with switchType="client" Key: RF-12033 URL: https://issues.jboss.org/browse/RF-12033 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-tables Affects Versions: 4.2.0.Final Environment: FireFox 10.0.2 (works in IE7) GlassFish 3.1 Reporter: Josh Hill Attachments: richfaces-test.zip testcase attached 1. Open test1.xhtml 2. Switch to Tab Two Expected Result: ExtendedDataTable shows up Actual Result: Grey bar shows up Workaround is to set switchType to "ajax" instead of "client" -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 9 15:24:36 2012 From: jira-events at lists.jboss.org (Josh Hill (JIRA)) Date: Fri, 9 Mar 2012 15:24:36 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12033) ExtendedDataTable doesn't show up in tabpanel with switchType="client" In-Reply-To: <1476360638.82467.1331324676272.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <659926780.82475.1331324676608.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Hill updated RF-12033: --------------------------- Attachment: richfaces-test.zip > ExtendedDataTable doesn't show up in tabpanel with switchType="client" > ---------------------------------------------------------------------- > > Key: RF-12033 > URL: https://issues.jboss.org/browse/RF-12033 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.2.0.Final > Environment: FireFox 10.0.2 (works in IE7) > GlassFish 3.1 > Reporter: Josh Hill > Attachments: richfaces-test.zip > > > testcase attached > 1. Open test1.xhtml > 2. Switch to Tab Two > Expected Result: ExtendedDataTable shows up > Actual Result: Grey bar shows up > Workaround is to set switchType to "ajax" instead of "client" -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 9 15:47:36 2012 From: jira-events at lists.jboss.org (RH Bugzilla Integration (JIRA)) Date: Fri, 9 Mar 2012 15:47:36 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11739) Components that don't require jsf.js can break ResourceMapping In-Reply-To: <445024762.41821.1322186680654.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <2003835680.82537.1331326056641.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12675617#comment-12675617 ] RH Bugzilla Integration commented on RF-11739: ---------------------------------------------- Marek Novotny changed the Status of [bug 801172|https://bugzilla.redhat.com/show_bug.cgi?id=801172] from ON_DEV to ON_QA > Components that don't require jsf.js can break ResourceMapping > -------------------------------------------------------------- > > Key: RF-11739 > URL: https://issues.jboss.org/browse/RF-11739 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: resource handling > Affects Versions: 4.0.0.CR1 > Reporter: Brian Leathem > Assignee: Luk?? Fry? > Fix For: 4.3-Tracking > > > This bug is only observable when resourceMapping is enabled. > If a component doesn't require jsf.js, and it is the first component to require a resource, it will trigger packed.js to redner before jsf.js. This breaks some of the scripts in packed.js, that require jsf.js. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 9 17:45:36 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Fri, 9 Mar 2012 17:45:36 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12029) AbstractTogglePanel should extend UIRepeat, instead of UIOutput In-Reply-To: <1430073926.75557.1331161056577.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <295199497.82674.1331333136535.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12675636#comment-12675636 ] Brian Leathem commented on RF-12029: ------------------------------------ To get the error to work: {quote} uncomment dynamic panel with ajax fragment on facelet in demo {quote} > AbstractTogglePanel should extend UIRepeat, instead of UIOutput > --------------------------------------------------------------- > > Key: RF-12029 > URL: https://issues.jboss.org/browse/RF-12029 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-output > Reporter: Brian Leathem > Assignee: Bernard Labno > > Valid uses exist for dynamically generating rich:tab, rich:togglePanelItem, rich:accordionItem. Current techniques for supporting this use case involve using c:forEach, which is a problem since c: tags are processed too early to nicely support dynamic use cases. > One idea to support this use case, is to have AbstractTogglePanel extend UIRepeat, instead of UIOutput to better dynamic child components. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Sun Mar 11 00:45:47 2012 From: jira-events at lists.jboss.org (Sunil Chauraha (JIRA)) Date: Sun, 11 Mar 2012 00:45:47 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12034) Accepting multiple date format in rich calendar Message-ID: <2086963364.234.1331444747307.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Sunil Chauraha created RF-12034: ----------------------------------- Summary: Accepting multiple date format in rich calendar Key: RF-12034 URL: https://issues.jboss.org/browse/RF-12034 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Sunil Chauraha -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Sun Mar 11 00:51:47 2012 From: jira-events at lists.jboss.org (Sunil Chauraha (JIRA)) Date: Sun, 11 Mar 2012 00:51:47 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12034) Accepting multiple date format in rich calendar In-Reply-To: <2086963364.234.1331444747307.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <145394468.238.1331445107295.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil Chauraha updated RF-12034: -------------------------------- Labels: richfaces (was: ) Description: Sometimes it is required to deal with multiple date formats in rich:calendar in both calendar selection and manual input. But here we can define only one date pattern. Could it be possible to accept for this component to accept multiple date formats, based on locale or other requirement. I could write a workaround using javascript but this would be great if we can do it by defining just the date patterns inside the component. My javascript solution is here : https://community.jboss.org/wiki/AcceptingMultipleDateFormatsInRichcalendar Complexity: Medium Component/s: component-input > Accepting multiple date format in rich calendar > ----------------------------------------------- > > Key: RF-12034 > URL: https://issues.jboss.org/browse/RF-12034 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-input > Reporter: Sunil Chauraha > Labels: richfaces > > Sometimes it is required to deal with multiple date formats in rich:calendar in both calendar selection and manual input. > But here we can define only one date pattern. > Could it be possible to accept for this component to accept multiple date formats, based on locale or other requirement. > I could write a workaround using javascript but this would be great if we can do it by defining just the date patterns inside the component. > My javascript solution is here : https://community.jboss.org/wiki/AcceptingMultipleDateFormatsInRichcalendar -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 12 05:09:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 12 Mar 2012 05:09:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12006) Some of resources like jquery.focus.js and ckeditor.js are not packaged In-Reply-To: <83400370.44769.1330343496187.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <275125264.1001.1331543387908.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12675840#comment-12675840 ] Luk?? Fry? commented on RF-12006: --------------------------------- These resources are referenced correctly, they are not only part of the package, which seems as {{richfaces-resources-maven-plugin}}. > Some of resources like jquery.focus.js and ckeditor.js are not packaged > ----------------------------------------------------------------------- > > Key: RF-12006 > URL: https://issues.jboss.org/browse/RF-12006 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: cdk > Affects Versions: 4.2.0.Final > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Priority: Minor > > In build of {{dist/static-resources}}, some of components are not packaged: > * {{jquery.focus.js}} > * {{ckeditor.js}} > It it not convenient to package {{ckeditor.js}}, but this issue might affect more resources. > Further investigations required. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 12 05:13:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 12 Mar 2012 05:13:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12009) Showcase: wrong look of page header in Opera Mobile In-Reply-To: <208215608.44849.1330346556934.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1856086145.1020.1331543627747.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12675842#comment-12675842 ] Luk?? Fry? commented on RF-12009: --------------------------------- I have tried several various samples and these works fine (can't speak about all of the samples, since it would need complete manual testing). > Showcase: wrong look of page header in Opera Mobile > --------------------------------------------------- > > Key: RF-12009 > URL: https://issues.jboss.org/browse/RF-12009 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: mobile > Affects Versions: 4.2.0.Final > Environment: http://showcase.richfaces.org/ > Opera Mobile v 12.00.ADR-1202131246 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Labels: mobile, mobile-opera > Attachments: Android.jpg, Opera.jpg > > > The header in Opera Mobile does not have the background. > It also means the AJAX status (which is white) is not shown when loading new page. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 12 05:13:48 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 12 Mar 2012 05:13:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12009) Showcase: wrong look of page header in Opera Mobile In-Reply-To: <208215608.44849.1330346556934.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <740792552.1024.1331543628027.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12675843#comment-12675843 ] Luk?? Fry? commented on RF-12009: --------------------------------- I would suggest to consider fix in later phases of 4.3. > Showcase: wrong look of page header in Opera Mobile > --------------------------------------------------- > > Key: RF-12009 > URL: https://issues.jboss.org/browse/RF-12009 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: mobile > Affects Versions: 4.2.0.Final > Environment: http://showcase.richfaces.org/ > Opera Mobile v 12.00.ADR-1202131246 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Labels: mobile, mobile-opera > Attachments: Android.jpg, Opera.jpg > > > The header in Opera Mobile does not have the background. > It also means the AJAX status (which is white) is not shown when loading new page. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 12 05:13:48 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 12 Mar 2012 05:13:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12009) Showcase: wrong look of page header in Opera Mobile In-Reply-To: <208215608.44849.1330346556934.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <2067343665.1025.1331543628067.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated RF-12009: ---------------------------- Priority: Minor (was: Major) > Showcase: wrong look of page header in Opera Mobile > --------------------------------------------------- > > Key: RF-12009 > URL: https://issues.jboss.org/browse/RF-12009 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: mobile > Affects Versions: 4.2.0.Final > Environment: http://showcase.richfaces.org/ > Opera Mobile v 12.00.ADR-1202131246 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Priority: Minor > Labels: mobile, mobile-opera > Attachments: Android.jpg, Opera.jpg > > > The header in Opera Mobile does not have the background. > It also means the AJAX status (which is white) is not shown when loading new page. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 12 05:13:48 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 12 Mar 2012 05:13:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12009) Showcase: wrong look of page header in Opera Mobile In-Reply-To: <208215608.44849.1330346556934.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1222864596.1027.1331543628141.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated RF-12009: ---------------------------- Assignee: (was: Luk?? Fry?) > Showcase: wrong look of page header in Opera Mobile > --------------------------------------------------- > > Key: RF-12009 > URL: https://issues.jboss.org/browse/RF-12009 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: mobile > Affects Versions: 4.2.0.Final > Environment: http://showcase.richfaces.org/ > Opera Mobile v 12.00.ADR-1202131246 > Reporter: Luk?? Fry? > Priority: Minor > Labels: mobile, mobile-opera > Attachments: Android.jpg, Opera.jpg > > > The header in Opera Mobile does not have the background. > It also means the AJAX status (which is white) is not shown when loading new page. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 12 07:46:48 2012 From: jira-events at lists.jboss.org (RH Bugzilla Integration (JIRA)) Date: Mon, 12 Mar 2012 07:46:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11739) Components that don't require jsf.js can break ResourceMapping In-Reply-To: <445024762.41821.1322186680654.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <193095829.1696.1331552808384.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12675918#comment-12675918 ] RH Bugzilla Integration commented on RF-11739: ---------------------------------------------- Karel Piwko changed the Status of [bug 801172|https://bugzilla.redhat.com/show_bug.cgi?id=801172] from ON_QA to VERIFIED > Components that don't require jsf.js can break ResourceMapping > -------------------------------------------------------------- > > Key: RF-11739 > URL: https://issues.jboss.org/browse/RF-11739 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: resource handling > Affects Versions: 4.0.0.CR1 > Reporter: Brian Leathem > Assignee: Luk?? Fry? > Fix For: 4.3-Tracking > > > This bug is only observable when resourceMapping is enabled. > If a component doesn't require jsf.js, and it is the first component to require a resource, it will trigger packed.js to redner before jsf.js. This breaks some of the scripts in packed.js, that require jsf.js. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 12 07:46:48 2012 From: jira-events at lists.jboss.org (RH Bugzilla Integration (JIRA)) Date: Mon, 12 Mar 2012 07:46:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11739) Components that don't require jsf.js can break ResourceMapping In-Reply-To: <445024762.41821.1322186680654.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1958058112.1701.1331552808989.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12675919#comment-12675919 ] RH Bugzilla Integration commented on RF-11739: ---------------------------------------------- Marek Novotny made a comment on [bug 801172|https://bugzilla.redhat.com/show_bug.cgi?id=801172] Referenced built jar in MEAD is here http://download.devel.redhat.com/brewroot/work/tasks/9529/4139529/org/richfaces/ui/richfaces-components-ui/4.2.0.Final-redhat-1/richfaces-components-ui-4.2.0.Final-redhat-1.jar > Components that don't require jsf.js can break ResourceMapping > -------------------------------------------------------------- > > Key: RF-11739 > URL: https://issues.jboss.org/browse/RF-11739 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: resource handling > Affects Versions: 4.0.0.CR1 > Reporter: Brian Leathem > Assignee: Luk?? Fry? > Fix For: 4.3-Tracking > > > This bug is only observable when resourceMapping is enabled. > If a component doesn't require jsf.js, and it is the first component to require a resource, it will trigger packed.js to redner before jsf.js. This breaks some of the scripts in packed.js, that require jsf.js. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 12 07:46:49 2012 From: jira-events at lists.jboss.org (RH Bugzilla Integration (JIRA)) Date: Mon, 12 Mar 2012 07:46:49 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11739) Components that don't require jsf.js can break ResourceMapping In-Reply-To: <445024762.41821.1322186680654.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1003425657.1702.1331552809073.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12675920#comment-12675920 ] RH Bugzilla Integration commented on RF-11739: ---------------------------------------------- Karel Piwko made a comment on [bug 801172|https://bugzilla.redhat.com/show_bug.cgi?id=801172] Verified fix in WFK 2.0.0.ER3. > Components that don't require jsf.js can break ResourceMapping > -------------------------------------------------------------- > > Key: RF-11739 > URL: https://issues.jboss.org/browse/RF-11739 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: resource handling > Affects Versions: 4.0.0.CR1 > Reporter: Brian Leathem > Assignee: Luk?? Fry? > Fix For: 4.3-Tracking > > > This bug is only observable when resourceMapping is enabled. > If a component doesn't require jsf.js, and it is the first component to require a resource, it will trigger packed.js to redner before jsf.js. This breaks some of the scripts in packed.js, that require jsf.js. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 12 09:09:47 2012 From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA)) Date: Mon, 12 Mar 2012 09:09:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12035) Switchable panels do not work after rerendering whole page Message-ID: <1502418805.1981.1331557787347.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Pavol Pitonak created RF-12035: ---------------------------------- Summary: Switchable panels do not work after rerendering whole page Key: RF-12035 URL: https://issues.jboss.org/browse/RF-12035 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-panels-layout-themes Affects Versions: 4.2.0.Final Environment: RichFaces 4.2.1-SNAPSHOT Metamer 4.2.1-SNAPSHOT Mojarra 2.1.7-jbossorg-1 JBoss AS 7.1.1.Final OpenJDK Runtime Environment 1.6.0_24-b24 @ Linux Chrome 17.0.963.79 @ Linux i686 Reporter: Pavol Pitonak # deploy Metamer and open http://localhost:8080/metamer/faces/components/richAccordion/simple.xhtml # click on panel 3 # verify that panel 3 is displayed # click rerender all button (4th button in page header) # verify that panel 3 is displayed # click on panel 2 # click on panel 2 result: * accordion is not switched to panel 2 on first click, second click is necessary * there is the same problem with rich:collapsiblePanel -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 12 10:30:47 2012 From: jira-events at lists.jboss.org (Juraj Huska (JIRA)) Date: Mon, 12 Mar 2012 10:30:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12036) showcase - rich:progressBar - client side mode of progressBar halts another progress bar in AJAX mode Message-ID: <653082305.2290.1331562647939.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Juraj Huska created RF-12036: -------------------------------- Summary: showcase - rich:progressBar - client side mode of progressBar halts another progress bar in AJAX mode Key: RF-12036 URL: https://issues.jboss.org/browse/RF-12036 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-output, showcase Affects Versions: 4.2.0.Final Environment: browsers: Firefox 10, Chrome 17 Reporter: Juraj Huska When you have open both samples for the rich:progressBar at the same browser(in separated cards), and run Ajax mode one and during of execution of this one also the client mode one, then the Ajax one is halted. The server updates are still coming for that Ajax one, however the visual state is not updated. It is not restored even when the second one is completed. This is noticeable on showcase since RF 4.0.0.Final, and reproducible on GAE or OpenShift accounts. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 12 11:02:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Mon, 12 Mar 2012 11:02:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12037) Fileupload:onbegin, oncomplete and onbeforedomupdate does not work Message-ID: <59538813.2564.1331564567977.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Ji?? ?tefek created RF-12037: -------------------------------- Summary: Fileupload:onbegin, oncomplete and onbeforedomupdate does not work Key: RF-12037 URL: https://issues.jboss.org/browse/RF-12037 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-input Affects Versions: 4.2.0.Final Environment: RichFaces 4.2.1-SNAPSHOT Metamer 4.2.1-SNAPSHOT Mojarra 2.1.5-SNAPSHOT JBoss AS 7.1.0.Final OpenJDK Runtime Environment 1.6.0_24-b24 @ Linux Firefox 10.0.1 @ Linux x86_64 Chrome 17.0.963.56 @ Linux i686 Reporter: Ji?? ?tefek # Deploy metamer # open http://localhost:8080/metamer/faces/components/richFileUpload/simple.xhtml # Attribute onbegin=alert('1') # Attribute onbeforedomupdate=alert('2') # Attribute oncomplete=alert('3') # Upload file # 3 alerts should show -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 12 11:04:49 2012 From: jira-events at lists.jboss.org (Juraj Huska (JIRA)) Date: Mon, 12 Mar 2012 11:04:49 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11590) showcase - only first push is done using Atmosphere CR2 In-Reply-To: <1926719144.28309.1319617905803.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <561353362.2576.1331564689159.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12676013#comment-12676013 ] Juraj Huska commented on RF-11590: ---------------------------------- I have verified that it is OK for releases 4.2.0.Final and higher. > showcase - only first push is done using Atmosphere CR2 > ------------------------------------------------------- > > Key: RF-11590 > URL: https://issues.jboss.org/browse/RF-11590 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll, showcase > Affects Versions: 4.1.0.Milestone3 > Environment: app: showcase > container: Tomcat 6.0.32 > Reporter: Juraj Huska > Assignee: Juraj Huska > > Only the first push is done in demos for a4j:push component in showcase. No exception is thrown, or any other warning is generated. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 12 11:06:47 2012 From: jira-events at lists.jboss.org (Juraj Huska (JIRA)) Date: Mon, 12 Mar 2012 11:06:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11590) showcase - only first push is done using Atmosphere CR2 In-Reply-To: <1926719144.28309.1319617905803.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <406911584.2581.1331564807728.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj Huska resolved RF-11590. ------------------------------ Resolution: Done > showcase - only first push is done using Atmosphere CR2 > ------------------------------------------------------- > > Key: RF-11590 > URL: https://issues.jboss.org/browse/RF-11590 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll, showcase > Affects Versions: 4.1.0.Milestone3 > Environment: app: showcase > container: Tomcat 6.0.32 > Reporter: Juraj Huska > Assignee: Juraj Huska > > Only the first push is done in demos for a4j:push component in showcase. No exception is thrown, or any other warning is generated. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 12 11:06:47 2012 From: jira-events at lists.jboss.org (Juraj Huska (JIRA)) Date: Mon, 12 Mar 2012 11:06:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11590) showcase - only first push is done using Atmosphere CR2 In-Reply-To: <1926719144.28309.1319617905803.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <2085419780.2586.1331564807950.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj Huska reopened RF-11590: ------------------------------ Sorry accidentally closed after verification, therefore reopening > showcase - only first push is done using Atmosphere CR2 > ------------------------------------------------------- > > Key: RF-11590 > URL: https://issues.jboss.org/browse/RF-11590 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll, showcase > Affects Versions: 4.1.0.Milestone3 > Environment: app: showcase > container: Tomcat 6.0.32 > Reporter: Juraj Huska > Assignee: Juraj Huska > > Only the first push is done in demos for a4j:push component in showcase. No exception is thrown, or any other warning is generated. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 12 11:06:48 2012 From: jira-events at lists.jboss.org (RH Bugzilla Integration (JIRA)) Date: Mon, 12 Mar 2012 11:06:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11983) Showcase: push sample doesn't work In-Reply-To: <1110785355.5085.1329395076292.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <555921577.2590.1331564808256.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] RH Bugzilla Integration updated RF-11983: ----------------------------------------- Bugzilla Update: Perform > Showcase: push sample doesn't work > ---------------------------------- > > Key: RF-11983 > URL: https://issues.jboss.org/browse/RF-11983 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Environment: JBoos AS 7.0.2.Final (in default configuration) / JBoss AS 7.1.0.Final and Firefox 8.0 > Reporter: Jan Papousek > Assignee: Luk?? Fry? > Fix For: 4.3-Tracking > > > {code:title=JBoss AS 7.1.0.Final} > 13:13:03,702 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/showcase].[Faces Servlet]] (http--127.0.0.1-8080-1) Servlet.service() for servlet Faces Servlet threw exception: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:397) [guava-10.0.1.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl.createTopic(JMSTopicsContextImpl.java:281) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.TopicsContext.getOrCreateTopic(TopicsContext.java:48) [richfaces-core-api-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.SessionImpl.createSubscriptions(SessionImpl.java:182) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.SessionImpl.subscribe(SessionImpl.java:177) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.resource.PushResource.encode(PushResource.java:88) [richfaces-components-ui-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.resource.UserResourceWrapperImpl.encode(UserResourceWrapperImpl.java:188) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.resource.ResourceHandlerImpl.handleResourceRequest(ResourceHandlerImpl.java:222) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:591) [jboss-jsf-api_2.1_spec-2.0.0.Final.jar:2.0.0.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.10.Final.jar:] > at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:62) [weld-core-1.1.5.AS71.Final.jar:2012-02-10 15:31] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.10.Final.jar:] > at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.1.0.Final.jar:7.1.0.Final] > at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:154) [jboss-as-web-7.1.0.Final.jar:7.1.0.Final] > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.10.Final.jar:] > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.10.Final.jar:] > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.10.Final.jar:] > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.10.Final.jar:] > at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_22] > Caused by: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:207) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:195) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingValueReference.compute(ComputingConcurrentHashMap.java:355) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.compute(ComputingConcurrentHashMap.java:184) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.getOrCompute(ComputingConcurrentHashMap.java:153) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap.getOrCompute(ComputingConcurrentHashMap.java:69) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:393) [guava-10.0.1.jar:] > ... 25 more > Caused by: javax.naming.NameNotFoundException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:97) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:177) > at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:113) > at javax.naming.InitialContext.lookup(InitialContext.java:396) [rt.jar:1.6.0_22] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.createConnection(JMSTopicsContextImpl.java:98) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.start(JMSTopicsContextImpl.java:123) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:199) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > ... 31 more > 13:13:04,263 SEVERE [org.richfaces.demo.push.MessageProducerRunnable] (MessageProducerThread) javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:397) [guava-10.0.1.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl.createTopic(JMSTopicsContextImpl.java:281) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.TopicsContext.getOrCreateTopic(TopicsContext.java:48) [richfaces-core-api-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.TopicsContext.publish(TopicsContext.java:69) [richfaces-core-api-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.demo.push.TopicsContextMessageProducer.sendMessage(TopicsContextMessageProducer.java:46) [classes:] > at org.richfaces.demo.push.MessageProducerRunnable.run(MessageProducerRunnable.java:57) [classes:] > at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_22] > Caused by: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:207) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:195) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingValueReference.compute(ComputingConcurrentHashMap.java:355) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.compute(ComputingConcurrentHashMap.java:184) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.getOrCompute(ComputingConcurrentHashMap.java:153) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap.getOrCompute(ComputingConcurrentHashMap.java:69) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:393) [guava-10.0.1.jar:] > ... 6 more > Caused by: javax.naming.NameNotFoundException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:97) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:177) > at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:113) > at javax.naming.InitialContext.lookup(InitialContext.java:396) [rt.jar:1.6.0_22] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.createConnection(JMSTopicsContextImpl.java:98) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.start(JMSTopicsContextImpl.java:123) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:199) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > ... 12 more > {code} > {code:title=JBoss AS 7.0.2.Final using default configuration} > 13:16:26,372 WARNING [javax.enterprise.resource.webcontainer.jsf.lifecycle] (http--0%3A0%3A0%3A0%3A0%3A0%3A0%3A0-8080-5) #{pushBean.sendMessage}: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory: javax.faces.FacesException: #{pushBean.sendMessage}: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:118) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > at javax.faces.component.UICommand.broadcast(UICommand.java:315) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:794) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:1259) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:81) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > at org.richfaces.demo.arrangeablemodel.PersistenceLifecycle.execute(PersistenceLifecycle.java:58) [classes:] > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:593) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:67) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:139) [jboss-as-web-7.0.2.Final.jar:7.0.2.Final] > at org.jboss.as.web.NamingValve.invoke(NamingValve.java:57) [jboss-as-web-7.0.2.Final.jar:7.0.2.Final] > at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:49) [jboss-as-jpa-7.0.2.Final.jar:7.0.2.Final] > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:154) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:667) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:952) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at java.lang.Thread.run(Thread.java:662) [:1.6.0_22] > Caused by: javax.faces.el.EvaluationException: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:102) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:102) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > ... 26 more > Caused by: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:397) [guava-10.0.1.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl.createTopic(JMSTopicsContextImpl.java:281) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.TopicsContext.getOrCreateTopic(TopicsContext.java:48) [richfaces-core-api-4.2.0.Final.jar:] > at org.richfaces.application.push.TopicsContext.publish(TopicsContext.java:69) [richfaces-core-api-4.2.0.Final.jar:] > at org.richfaces.application.push.TopicsContext$Proxy$_$$_WeldClientProxy.publish(TopicsContext$Proxy$_$$_WeldClientProxy.java) [richfaces-core-api-4.2.0.Final.jar:] > at org.richfaces.cdi.push.PushCDIExtension$PushObserverMethod.notify(PushCDIExtension.java:144) [richfaces-core-impl-4.2.0.Final.jar:] > at org.jboss.weld.manager.BeanManagerImpl.notifyObservers(BeanManagerImpl.java:635) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:628) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.jboss.weld.event.EventImpl.fire(EventImpl.java:75) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.richfaces.demo.push.PushBean.sendMessage(PushBean.java:65) [classes:] > at org.richfaces.demo.push.PushBean$Proxy$_$$_WeldClientProxy.sendMessage(PushBean$Proxy$_$$_WeldClientProxy.java) [classes:] > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_22] > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_22] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_22] > at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_22] > at org.apache.el.parser.AstValue.invoke(AstValue.java:196) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:276) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.jboss.weld.util.el.ForwardingMethodExpression.invoke(ForwardingMethodExpression.java:43) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.jboss.weld.el.WeldMethodExpression.invoke(WeldMethodExpression.java:56) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at com.sun.faces.facelets.el.TagMethodExpression.invoke(TagMethodExpression.java:105) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:88) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > ... 27 more > Caused by: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:207) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:195) [richfaces-core-impl-4.2.0.Final.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingValueReference.compute(ComputingConcurrentHashMap.java:355) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.compute(ComputingConcurrentHashMap.java:184) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.getOrCompute(ComputingConcurrentHashMap.java:153) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap.getOrCompute(ComputingConcurrentHashMap.java:69) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:393) [guava-10.0.1.jar:] > ... 47 more > Caused by: javax.naming.NameNotFoundException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:87) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:173) > at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:47) > at javax.naming.InitialContext.lookup(InitialContext.java:396) [:1.6.0_22] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.createConnection(JMSTopicsContextImpl.java:98) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.start(JMSTopicsContextImpl.java:123) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:199) [richfaces-core-impl-4.2.0.Final.jar:] > ... 53 more > 13:16:28,949 SEVERE [org.richfaces.demo.push.MessageProducerRunnable] (MessageProducerThread) javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:397) [guava-10.0.1.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl.createTopic(JMSTopicsContextImpl.java:281) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.TopicsContext.getOrCreateTopic(TopicsContext.java:48) [richfaces-core-api-4.2.0.Final.jar:] > at org.richfaces.application.push.TopicsContext.publish(TopicsContext.java:69) [richfaces-core-api-4.2.0.Final.jar:] > at org.richfaces.demo.push.TopicsContextMessageProducer.sendMessage(TopicsContextMessageProducer.java:46) [classes:] > at org.richfaces.demo.push.MessageProducerRunnable.run(MessageProducerRunnable.java:57) [classes:] > at java.lang.Thread.run(Thread.java:662) [:1.6.0_22] > Caused by: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:207) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:195) [richfaces-core-impl-4.2.0.Final.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingValueReference.compute(ComputingConcurrentHashMap.java:355) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.compute(ComputingConcurrentHashMap.java:184) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.getOrCompute(ComputingConcurrentHashMap.java:153) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap.getOrCompute(ComputingConcurrentHashMap.java:69) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:393) [guava-10.0.1.jar:] > ... 6 more > Caused by: javax.naming.NameNotFoundException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:87) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:173) > at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:47) > at javax.naming.InitialContext.lookup(InitialContext.java:396) [:1.6.0_22] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.createConnection(JMSTopicsContextImpl.java:98) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.start(JMSTopicsContextImpl.java:123) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:199) [richfaces-core-impl-4.2.0.Final.jar:] > ... 12 more > {code} > ---- > - Showcase on Openshift Express is working (yeah, there is a really big delay, but it's working). > - Sample in Metamer is also working. > - When the JBoss AS 7.0.2.Final is running with "--server-config standalone-preview.xml", the CDI push demo works correctly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 12 11:06:48 2012 From: jira-events at lists.jboss.org (RH Bugzilla Integration (JIRA)) Date: Mon, 12 Mar 2012 11:06:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11983) Showcase: push sample doesn't work In-Reply-To: <1110785355.5085.1329395076292.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <612942910.2594.1331564808513.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] RH Bugzilla Integration updated RF-11983: ----------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=802444 > Showcase: push sample doesn't work > ---------------------------------- > > Key: RF-11983 > URL: https://issues.jboss.org/browse/RF-11983 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Environment: JBoos AS 7.0.2.Final (in default configuration) / JBoss AS 7.1.0.Final and Firefox 8.0 > Reporter: Jan Papousek > Assignee: Luk?? Fry? > Fix For: 4.3-Tracking > > > {code:title=JBoss AS 7.1.0.Final} > 13:13:03,702 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/showcase].[Faces Servlet]] (http--127.0.0.1-8080-1) Servlet.service() for servlet Faces Servlet threw exception: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:397) [guava-10.0.1.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl.createTopic(JMSTopicsContextImpl.java:281) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.TopicsContext.getOrCreateTopic(TopicsContext.java:48) [richfaces-core-api-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.SessionImpl.createSubscriptions(SessionImpl.java:182) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.SessionImpl.subscribe(SessionImpl.java:177) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.resource.PushResource.encode(PushResource.java:88) [richfaces-components-ui-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.resource.UserResourceWrapperImpl.encode(UserResourceWrapperImpl.java:188) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.resource.ResourceHandlerImpl.handleResourceRequest(ResourceHandlerImpl.java:222) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:591) [jboss-jsf-api_2.1_spec-2.0.0.Final.jar:2.0.0.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.10.Final.jar:] > at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:62) [weld-core-1.1.5.AS71.Final.jar:2012-02-10 15:31] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.10.Final.jar:] > at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.1.0.Final.jar:7.1.0.Final] > at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:154) [jboss-as-web-7.1.0.Final.jar:7.1.0.Final] > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.10.Final.jar:] > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.10.Final.jar:] > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.10.Final.jar:] > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.10.Final.jar:] > at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_22] > Caused by: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:207) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:195) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingValueReference.compute(ComputingConcurrentHashMap.java:355) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.compute(ComputingConcurrentHashMap.java:184) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.getOrCompute(ComputingConcurrentHashMap.java:153) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap.getOrCompute(ComputingConcurrentHashMap.java:69) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:393) [guava-10.0.1.jar:] > ... 25 more > Caused by: javax.naming.NameNotFoundException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:97) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:177) > at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:113) > at javax.naming.InitialContext.lookup(InitialContext.java:396) [rt.jar:1.6.0_22] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.createConnection(JMSTopicsContextImpl.java:98) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.start(JMSTopicsContextImpl.java:123) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:199) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > ... 31 more > 13:13:04,263 SEVERE [org.richfaces.demo.push.MessageProducerRunnable] (MessageProducerThread) javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:397) [guava-10.0.1.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl.createTopic(JMSTopicsContextImpl.java:281) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.TopicsContext.getOrCreateTopic(TopicsContext.java:48) [richfaces-core-api-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.TopicsContext.publish(TopicsContext.java:69) [richfaces-core-api-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.demo.push.TopicsContextMessageProducer.sendMessage(TopicsContextMessageProducer.java:46) [classes:] > at org.richfaces.demo.push.MessageProducerRunnable.run(MessageProducerRunnable.java:57) [classes:] > at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_22] > Caused by: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:207) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:195) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingValueReference.compute(ComputingConcurrentHashMap.java:355) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.compute(ComputingConcurrentHashMap.java:184) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.getOrCompute(ComputingConcurrentHashMap.java:153) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap.getOrCompute(ComputingConcurrentHashMap.java:69) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:393) [guava-10.0.1.jar:] > ... 6 more > Caused by: javax.naming.NameNotFoundException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:97) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:177) > at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:113) > at javax.naming.InitialContext.lookup(InitialContext.java:396) [rt.jar:1.6.0_22] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.createConnection(JMSTopicsContextImpl.java:98) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.start(JMSTopicsContextImpl.java:123) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:199) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > ... 12 more > {code} > {code:title=JBoss AS 7.0.2.Final using default configuration} > 13:16:26,372 WARNING [javax.enterprise.resource.webcontainer.jsf.lifecycle] (http--0%3A0%3A0%3A0%3A0%3A0%3A0%3A0-8080-5) #{pushBean.sendMessage}: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory: javax.faces.FacesException: #{pushBean.sendMessage}: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:118) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > at javax.faces.component.UICommand.broadcast(UICommand.java:315) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:794) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:1259) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:81) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > at org.richfaces.demo.arrangeablemodel.PersistenceLifecycle.execute(PersistenceLifecycle.java:58) [classes:] > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:593) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:67) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:139) [jboss-as-web-7.0.2.Final.jar:7.0.2.Final] > at org.jboss.as.web.NamingValve.invoke(NamingValve.java:57) [jboss-as-web-7.0.2.Final.jar:7.0.2.Final] > at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:49) [jboss-as-jpa-7.0.2.Final.jar:7.0.2.Final] > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:154) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:667) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:952) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at java.lang.Thread.run(Thread.java:662) [:1.6.0_22] > Caused by: javax.faces.el.EvaluationException: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:102) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:102) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > ... 26 more > Caused by: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:397) [guava-10.0.1.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl.createTopic(JMSTopicsContextImpl.java:281) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.TopicsContext.getOrCreateTopic(TopicsContext.java:48) [richfaces-core-api-4.2.0.Final.jar:] > at org.richfaces.application.push.TopicsContext.publish(TopicsContext.java:69) [richfaces-core-api-4.2.0.Final.jar:] > at org.richfaces.application.push.TopicsContext$Proxy$_$$_WeldClientProxy.publish(TopicsContext$Proxy$_$$_WeldClientProxy.java) [richfaces-core-api-4.2.0.Final.jar:] > at org.richfaces.cdi.push.PushCDIExtension$PushObserverMethod.notify(PushCDIExtension.java:144) [richfaces-core-impl-4.2.0.Final.jar:] > at org.jboss.weld.manager.BeanManagerImpl.notifyObservers(BeanManagerImpl.java:635) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:628) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.jboss.weld.event.EventImpl.fire(EventImpl.java:75) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.richfaces.demo.push.PushBean.sendMessage(PushBean.java:65) [classes:] > at org.richfaces.demo.push.PushBean$Proxy$_$$_WeldClientProxy.sendMessage(PushBean$Proxy$_$$_WeldClientProxy.java) [classes:] > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_22] > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_22] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_22] > at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_22] > at org.apache.el.parser.AstValue.invoke(AstValue.java:196) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:276) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.jboss.weld.util.el.ForwardingMethodExpression.invoke(ForwardingMethodExpression.java:43) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.jboss.weld.el.WeldMethodExpression.invoke(WeldMethodExpression.java:56) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at com.sun.faces.facelets.el.TagMethodExpression.invoke(TagMethodExpression.java:105) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:88) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > ... 27 more > Caused by: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:207) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:195) [richfaces-core-impl-4.2.0.Final.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingValueReference.compute(ComputingConcurrentHashMap.java:355) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.compute(ComputingConcurrentHashMap.java:184) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.getOrCompute(ComputingConcurrentHashMap.java:153) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap.getOrCompute(ComputingConcurrentHashMap.java:69) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:393) [guava-10.0.1.jar:] > ... 47 more > Caused by: javax.naming.NameNotFoundException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:87) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:173) > at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:47) > at javax.naming.InitialContext.lookup(InitialContext.java:396) [:1.6.0_22] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.createConnection(JMSTopicsContextImpl.java:98) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.start(JMSTopicsContextImpl.java:123) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:199) [richfaces-core-impl-4.2.0.Final.jar:] > ... 53 more > 13:16:28,949 SEVERE [org.richfaces.demo.push.MessageProducerRunnable] (MessageProducerThread) javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:397) [guava-10.0.1.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl.createTopic(JMSTopicsContextImpl.java:281) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.TopicsContext.getOrCreateTopic(TopicsContext.java:48) [richfaces-core-api-4.2.0.Final.jar:] > at org.richfaces.application.push.TopicsContext.publish(TopicsContext.java:69) [richfaces-core-api-4.2.0.Final.jar:] > at org.richfaces.demo.push.TopicsContextMessageProducer.sendMessage(TopicsContextMessageProducer.java:46) [classes:] > at org.richfaces.demo.push.MessageProducerRunnable.run(MessageProducerRunnable.java:57) [classes:] > at java.lang.Thread.run(Thread.java:662) [:1.6.0_22] > Caused by: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:207) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:195) [richfaces-core-impl-4.2.0.Final.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingValueReference.compute(ComputingConcurrentHashMap.java:355) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.compute(ComputingConcurrentHashMap.java:184) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.getOrCompute(ComputingConcurrentHashMap.java:153) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap.getOrCompute(ComputingConcurrentHashMap.java:69) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:393) [guava-10.0.1.jar:] > ... 6 more > Caused by: javax.naming.NameNotFoundException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:87) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:173) > at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:47) > at javax.naming.InitialContext.lookup(InitialContext.java:396) [:1.6.0_22] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.createConnection(JMSTopicsContextImpl.java:98) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.start(JMSTopicsContextImpl.java:123) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:199) [richfaces-core-impl-4.2.0.Final.jar:] > ... 12 more > {code} > ---- > - Showcase on Openshift Express is working (yeah, there is a really big delay, but it's working). > - Sample in Metamer is also working. > - When the JBoss AS 7.0.2.Final is running with "--server-config standalone-preview.xml", the CDI push demo works correctly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 12 11:08:47 2012 From: jira-events at lists.jboss.org (Juraj Huska (JIRA)) Date: Mon, 12 Mar 2012 11:08:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11590) showcase - only first push is done using Atmosphere CR2 In-Reply-To: <1926719144.28309.1319617905803.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <98098408.2612.1331564927399.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj Huska reassigned RF-11590: -------------------------------- Assignee: (was: Juraj Huska) > showcase - only first push is done using Atmosphere CR2 > ------------------------------------------------------- > > Key: RF-11590 > URL: https://issues.jboss.org/browse/RF-11590 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll, showcase > Affects Versions: 4.1.0.Milestone3 > Environment: app: showcase > container: Tomcat 6.0.32 > Reporter: Juraj Huska > > Only the first push is done in demos for a4j:push component in showcase. No exception is thrown, or any other warning is generated. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 12 11:18:49 2012 From: jira-events at lists.jboss.org (Juraj Huska (JIRA)) Date: Mon, 12 Mar 2012 11:18:49 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11590) showcase - only first push is done using Atmosphere CR2 In-Reply-To: <1926719144.28309.1319617905803.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <178698583.2675.1331565529754.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj Huska closed RF-11590. ---------------------------- Resolution: Done fixed with upgrading of Atmosphere framework in 4.2.0.Final release. > showcase - only first push is done using Atmosphere CR2 > ------------------------------------------------------- > > Key: RF-11590 > URL: https://issues.jboss.org/browse/RF-11590 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll, showcase > Affects Versions: 4.1.0.Milestone3 > Environment: app: showcase > container: Tomcat 6.0.32 > Reporter: Juraj Huska > > Only the first push is done in demos for a4j:push component in showcase. No exception is thrown, or any other warning is generated. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 12 12:00:48 2012 From: jira-events at lists.jboss.org (Jean ANDRE (JIRA)) Date: Mon, 12 Mar 2012 12:00:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12038) IE8 - Object does not support this property or method - a4j:jsFunction Message-ID: <1674243330.3069.1331568048477.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Jean ANDRE created RF-12038: ------------------------------- Summary: IE8 - Object does not support this property or method - a4j:jsFunction Key: RF-12038 URL: https://issues.jboss.org/browse/RF-12038 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.2.0.Final Environment: cssparser-0.9.6- guava-11.0.1 - hibernate-validator-4.2.0.Final - JSF/Mojarra 2.1.6 - springframework-3.0.6.RELEASE - sac-1.3 - Windows 7 - IE 8.0.1.7601.17514 Reporter: Jean ANDRE Under IE8, IE reports the following error message due to a javascript error. However, the page are well displayed and the application is running ok. Object doesn't support this property or method line 177 caracter 1 Object doesn't support this property or method line 177 caracter 99 Under IE Debugger, the line is: {code} closeTab=function(tabId){RichFaces.ajax("closeTab",null,{"incId":"1","parameters":{"tabId":tabId} } )};< The caracter 99, is..............................................................................| (here) {code} This is a code generated by a4j:jsFunction from the XHTML {code} {code} The rendered code is : {code} {code} See also this link as we got almost a similar: https://bugzilla.redhat.com/show_bug.cgi?id=601360. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 12 12:04:47 2012 From: jira-events at lists.jboss.org (Jean ANDRE (JIRA)) Date: Mon, 12 Mar 2012 12:04:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12038) IE8 - Object does not support this property or method - a4j:jsFunction In-Reply-To: <1674243330.3069.1331568048477.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <2140521297.3083.1331568287346.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean ANDRE updated RF-12038: ---------------------------- Attachment: index.xhtml The XHTML page where the error appears - Line 299 > IE8 - Object does not support this property or method - a4j:jsFunction > ---------------------------------------------------------------------- > > Key: RF-12038 > URL: https://issues.jboss.org/browse/RF-12038 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.2.0.Final > Environment: cssparser-0.9.6- guava-11.0.1 - hibernate-validator-4.2.0.Final - JSF/Mojarra 2.1.6 - springframework-3.0.6.RELEASE - sac-1.3 - Windows 7 - IE 8.0.1.7601.17514 > Reporter: Jean ANDRE > Attachments: index.xhtml > > > Under IE8, IE reports the following error message due to a javascript error. However, the page are well displayed and the application is running ok. > Object doesn't support this property or method line 177 caracter 1 > Object doesn't support this property or method line 177 caracter 99 > Under IE Debugger, the line is: > {code} > closeTab=function(tabId){RichFaces.ajax("closeTab",null,{"incId":"1","parameters":{"tabId":tabId} } )};< > The caracter 99, is..............................................................................| (here) > {code} > This is a code generated by a4j:jsFunction from the XHTML > {code} > > > > > > > {code} > The rendered code is : > {code} > > > > {code} > See also this link as we got almost a similar: https://bugzilla.redhat.com/show_bug.cgi?id=601360. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 12 12:30:47 2012 From: jira-events at lists.jboss.org (Juraj Huska (JIRA)) Date: Mon, 12 Mar 2012 12:30:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11589) showcase - a Warning is generated when there is interaction with Atmosphere CR2 framework In-Reply-To: <26512795.28270.1319616945421.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <515952031.3417.1331569847892.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12676113#comment-12676113 ] Juraj Huska commented on RF-11589: ---------------------------------- I can not reproduce this issue anymore with releases 4.2.0.Final and higher. > showcase - a Warning is generated when there is interaction with Atmosphere CR2 framework > ----------------------------------------------------------------------------------------- > > Key: RF-11589 > URL: https://issues.jboss.org/browse/RF-11589 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-push/poll, showcase > Affects Versions: 4.1.0.Milestone3 > Environment: app: showcase > container: JBoss AS 7.0.2.Final, , JBoss 6.0.0.Final, Tomcat 6.0.0.32 > Reporter: Juraj Huska > Assignee: Juraj Huska > Priority: Minor > > An WARNING is generated when there is any interaction with Atmosphere CR2 framework in showcase push demos. > The warning: > {code} > 10:08:12,102 WARNING [org.atmosphere.cpr.AtmosphereResourceImpl] (http-localhost.localdomain-127.0.0.1-8080-2) Broadcaster DefaultBroadcaster9dd3cbac-4e33-482d-8c8c-cd2c0936e695 has been destroyed and cannot be re-used. Recreating a new one with the same name. You can turn off that mechanism by adding, in web.xml, org.atmosphere.cpr.recoverFromDestroyedBroadcaster set to false > {code} > The demos however work as expected. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 12 12:32:47 2012 From: jira-events at lists.jboss.org (Juraj Huska (JIRA)) Date: Mon, 12 Mar 2012 12:32:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11589) showcase - a Warning is generated when there is interaction with Atmosphere CR2 framework In-Reply-To: <26512795.28270.1319616945421.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <626366682.3423.1331569967429.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj Huska resolved RF-11589. ------------------------------ Resolution: Done fixed with upgrade of Atmosphere framework in RF 4.2.0.Final release > showcase - a Warning is generated when there is interaction with Atmosphere CR2 framework > ----------------------------------------------------------------------------------------- > > Key: RF-11589 > URL: https://issues.jboss.org/browse/RF-11589 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-push/poll, showcase > Affects Versions: 4.1.0.Milestone3 > Environment: app: showcase > container: JBoss AS 7.0.2.Final, , JBoss 6.0.0.Final, Tomcat 6.0.0.32 > Reporter: Juraj Huska > Assignee: Juraj Huska > Priority: Minor > > An WARNING is generated when there is any interaction with Atmosphere CR2 framework in showcase push demos. > The warning: > {code} > 10:08:12,102 WARNING [org.atmosphere.cpr.AtmosphereResourceImpl] (http-localhost.localdomain-127.0.0.1-8080-2) Broadcaster DefaultBroadcaster9dd3cbac-4e33-482d-8c8c-cd2c0936e695 has been destroyed and cannot be re-used. Recreating a new one with the same name. You can turn off that mechanism by adding, in web.xml, org.atmosphere.cpr.recoverFromDestroyedBroadcaster set to false > {code} > The demos however work as expected. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 12 12:32:47 2012 From: jira-events at lists.jboss.org (Juraj Huska (JIRA)) Date: Mon, 12 Mar 2012 12:32:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11589) showcase - a Warning is generated when there is interaction with Atmosphere CR2 framework In-Reply-To: <26512795.28270.1319616945421.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <2024429729.3426.1331569967579.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj Huska closed RF-11589. ---------------------------- > showcase - a Warning is generated when there is interaction with Atmosphere CR2 framework > ----------------------------------------------------------------------------------------- > > Key: RF-11589 > URL: https://issues.jboss.org/browse/RF-11589 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-push/poll, showcase > Affects Versions: 4.1.0.Milestone3 > Environment: app: showcase > container: JBoss AS 7.0.2.Final, , JBoss 6.0.0.Final, Tomcat 6.0.0.32 > Reporter: Juraj Huska > Assignee: Juraj Huska > Priority: Minor > > An WARNING is generated when there is any interaction with Atmosphere CR2 framework in showcase push demos. > The warning: > {code} > 10:08:12,102 WARNING [org.atmosphere.cpr.AtmosphereResourceImpl] (http-localhost.localdomain-127.0.0.1-8080-2) Broadcaster DefaultBroadcaster9dd3cbac-4e33-482d-8c8c-cd2c0936e695 has been destroyed and cannot be re-used. Recreating a new one with the same name. You can turn off that mechanism by adding, in web.xml, org.atmosphere.cpr.recoverFromDestroyedBroadcaster set to false > {code} > The demos however work as expected. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 13 00:51:48 2012 From: jira-events at lists.jboss.org (RH Bugzilla Integration (JIRA)) Date: Tue, 13 Mar 2012 00:51:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11983) Showcase: push sample doesn't work In-Reply-To: <1110785355.5085.1329395076292.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <267422553.4969.1331614308371.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12676281#comment-12676281 ] RH Bugzilla Integration commented on RF-11983: ---------------------------------------------- Rebecca Newton made a comment on [bug 802444|https://bugzilla.redhat.com/show_bug.cgi?id=802444] Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1,18 +1,6 @@ -The default installation of JBoss Enterprise Application Platform comes secured by default. RichFaces Showcase example uses JMS Push functionality, which is secured as well. +Both the default installation of JBoss Enterprise Application Platform and JMS Push, which is required by RichFaces Showcase example, are secured by default. To deploy the application, choose one of the following options: -Users wishing to deploy the application needs to do one of the following additional configurations: +1. Add a new user ApplicationRealm with the $JBOSS_HOME/bin/add-user.bat/sh script, with the role: guest. - +2. Modify web.xml in the RichFaces Showcase to contain created credentials: -1/ Add an user to via ApplicationRealm via $JBOSS_HOME/bin/add-user.bat/sh script into roles guest. +adkslfjasdfk - +3. Disable security for HornetQ completely.-2/ Modify web.xml in the RichFaces Showcase to contain created credentials, e.g.: - - - org.richfaces.push.jms.connectionUsername - guest - - - org.richfaces.push.jms.connectionPassword - password - - -The other way is to disable security for HornetQ completely. > Showcase: push sample doesn't work > ---------------------------------- > > Key: RF-11983 > URL: https://issues.jboss.org/browse/RF-11983 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Environment: JBoos AS 7.0.2.Final (in default configuration) / JBoss AS 7.1.0.Final and Firefox 8.0 > Reporter: Jan Papousek > Assignee: Luk?? Fry? > Fix For: 4.3-Tracking > > > {code:title=JBoss AS 7.1.0.Final} > 13:13:03,702 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/showcase].[Faces Servlet]] (http--127.0.0.1-8080-1) Servlet.service() for servlet Faces Servlet threw exception: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:397) [guava-10.0.1.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl.createTopic(JMSTopicsContextImpl.java:281) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.TopicsContext.getOrCreateTopic(TopicsContext.java:48) [richfaces-core-api-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.SessionImpl.createSubscriptions(SessionImpl.java:182) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.SessionImpl.subscribe(SessionImpl.java:177) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.resource.PushResource.encode(PushResource.java:88) [richfaces-components-ui-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.resource.UserResourceWrapperImpl.encode(UserResourceWrapperImpl.java:188) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.resource.ResourceHandlerImpl.handleResourceRequest(ResourceHandlerImpl.java:222) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:591) [jboss-jsf-api_2.1_spec-2.0.0.Final.jar:2.0.0.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.10.Final.jar:] > at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:62) [weld-core-1.1.5.AS71.Final.jar:2012-02-10 15:31] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.10.Final.jar:] > at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.1.0.Final.jar:7.1.0.Final] > at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:154) [jboss-as-web-7.1.0.Final.jar:7.1.0.Final] > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.10.Final.jar:] > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.10.Final.jar:] > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.10.Final.jar:] > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.10.Final.jar:] > at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_22] > Caused by: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:207) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:195) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingValueReference.compute(ComputingConcurrentHashMap.java:355) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.compute(ComputingConcurrentHashMap.java:184) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.getOrCompute(ComputingConcurrentHashMap.java:153) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap.getOrCompute(ComputingConcurrentHashMap.java:69) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:393) [guava-10.0.1.jar:] > ... 25 more > Caused by: javax.naming.NameNotFoundException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:97) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:177) > at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:113) > at javax.naming.InitialContext.lookup(InitialContext.java:396) [rt.jar:1.6.0_22] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.createConnection(JMSTopicsContextImpl.java:98) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.start(JMSTopicsContextImpl.java:123) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:199) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > ... 31 more > 13:13:04,263 SEVERE [org.richfaces.demo.push.MessageProducerRunnable] (MessageProducerThread) javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:397) [guava-10.0.1.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl.createTopic(JMSTopicsContextImpl.java:281) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.TopicsContext.getOrCreateTopic(TopicsContext.java:48) [richfaces-core-api-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.TopicsContext.publish(TopicsContext.java:69) [richfaces-core-api-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.demo.push.TopicsContextMessageProducer.sendMessage(TopicsContextMessageProducer.java:46) [classes:] > at org.richfaces.demo.push.MessageProducerRunnable.run(MessageProducerRunnable.java:57) [classes:] > at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_22] > Caused by: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:207) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:195) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingValueReference.compute(ComputingConcurrentHashMap.java:355) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.compute(ComputingConcurrentHashMap.java:184) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.getOrCompute(ComputingConcurrentHashMap.java:153) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap.getOrCompute(ComputingConcurrentHashMap.java:69) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:393) [guava-10.0.1.jar:] > ... 6 more > Caused by: javax.naming.NameNotFoundException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:97) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:177) > at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:113) > at javax.naming.InitialContext.lookup(InitialContext.java:396) [rt.jar:1.6.0_22] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.createConnection(JMSTopicsContextImpl.java:98) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.start(JMSTopicsContextImpl.java:123) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:199) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > ... 12 more > {code} > {code:title=JBoss AS 7.0.2.Final using default configuration} > 13:16:26,372 WARNING [javax.enterprise.resource.webcontainer.jsf.lifecycle] (http--0%3A0%3A0%3A0%3A0%3A0%3A0%3A0-8080-5) #{pushBean.sendMessage}: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory: javax.faces.FacesException: #{pushBean.sendMessage}: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:118) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > at javax.faces.component.UICommand.broadcast(UICommand.java:315) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:794) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:1259) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:81) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > at org.richfaces.demo.arrangeablemodel.PersistenceLifecycle.execute(PersistenceLifecycle.java:58) [classes:] > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:593) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:67) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:139) [jboss-as-web-7.0.2.Final.jar:7.0.2.Final] > at org.jboss.as.web.NamingValve.invoke(NamingValve.java:57) [jboss-as-web-7.0.2.Final.jar:7.0.2.Final] > at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:49) [jboss-as-jpa-7.0.2.Final.jar:7.0.2.Final] > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:154) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:667) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:952) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at java.lang.Thread.run(Thread.java:662) [:1.6.0_22] > Caused by: javax.faces.el.EvaluationException: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:102) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:102) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > ... 26 more > Caused by: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:397) [guava-10.0.1.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl.createTopic(JMSTopicsContextImpl.java:281) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.TopicsContext.getOrCreateTopic(TopicsContext.java:48) [richfaces-core-api-4.2.0.Final.jar:] > at org.richfaces.application.push.TopicsContext.publish(TopicsContext.java:69) [richfaces-core-api-4.2.0.Final.jar:] > at org.richfaces.application.push.TopicsContext$Proxy$_$$_WeldClientProxy.publish(TopicsContext$Proxy$_$$_WeldClientProxy.java) [richfaces-core-api-4.2.0.Final.jar:] > at org.richfaces.cdi.push.PushCDIExtension$PushObserverMethod.notify(PushCDIExtension.java:144) [richfaces-core-impl-4.2.0.Final.jar:] > at org.jboss.weld.manager.BeanManagerImpl.notifyObservers(BeanManagerImpl.java:635) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:628) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.jboss.weld.event.EventImpl.fire(EventImpl.java:75) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.richfaces.demo.push.PushBean.sendMessage(PushBean.java:65) [classes:] > at org.richfaces.demo.push.PushBean$Proxy$_$$_WeldClientProxy.sendMessage(PushBean$Proxy$_$$_WeldClientProxy.java) [classes:] > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_22] > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_22] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_22] > at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_22] > at org.apache.el.parser.AstValue.invoke(AstValue.java:196) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:276) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.jboss.weld.util.el.ForwardingMethodExpression.invoke(ForwardingMethodExpression.java:43) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.jboss.weld.el.WeldMethodExpression.invoke(WeldMethodExpression.java:56) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at com.sun.faces.facelets.el.TagMethodExpression.invoke(TagMethodExpression.java:105) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:88) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > ... 27 more > Caused by: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:207) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:195) [richfaces-core-impl-4.2.0.Final.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingValueReference.compute(ComputingConcurrentHashMap.java:355) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.compute(ComputingConcurrentHashMap.java:184) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.getOrCompute(ComputingConcurrentHashMap.java:153) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap.getOrCompute(ComputingConcurrentHashMap.java:69) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:393) [guava-10.0.1.jar:] > ... 47 more > Caused by: javax.naming.NameNotFoundException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:87) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:173) > at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:47) > at javax.naming.InitialContext.lookup(InitialContext.java:396) [:1.6.0_22] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.createConnection(JMSTopicsContextImpl.java:98) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.start(JMSTopicsContextImpl.java:123) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:199) [richfaces-core-impl-4.2.0.Final.jar:] > ... 53 more > 13:16:28,949 SEVERE [org.richfaces.demo.push.MessageProducerRunnable] (MessageProducerThread) javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:397) [guava-10.0.1.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl.createTopic(JMSTopicsContextImpl.java:281) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.TopicsContext.getOrCreateTopic(TopicsContext.java:48) [richfaces-core-api-4.2.0.Final.jar:] > at org.richfaces.application.push.TopicsContext.publish(TopicsContext.java:69) [richfaces-core-api-4.2.0.Final.jar:] > at org.richfaces.demo.push.TopicsContextMessageProducer.sendMessage(TopicsContextMessageProducer.java:46) [classes:] > at org.richfaces.demo.push.MessageProducerRunnable.run(MessageProducerRunnable.java:57) [classes:] > at java.lang.Thread.run(Thread.java:662) [:1.6.0_22] > Caused by: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:207) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:195) [richfaces-core-impl-4.2.0.Final.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingValueReference.compute(ComputingConcurrentHashMap.java:355) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.compute(ComputingConcurrentHashMap.java:184) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.getOrCompute(ComputingConcurrentHashMap.java:153) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap.getOrCompute(ComputingConcurrentHashMap.java:69) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:393) [guava-10.0.1.jar:] > ... 6 more > Caused by: javax.naming.NameNotFoundException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:87) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:173) > at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:47) > at javax.naming.InitialContext.lookup(InitialContext.java:396) [:1.6.0_22] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.createConnection(JMSTopicsContextImpl.java:98) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.start(JMSTopicsContextImpl.java:123) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:199) [richfaces-core-impl-4.2.0.Final.jar:] > ... 12 more > {code} > ---- > - Showcase on Openshift Express is working (yeah, there is a really big delay, but it's working). > - Sample in Metamer is also working. > - When the JBoss AS 7.0.2.Final is running with "--server-config standalone-preview.xml", the CDI push demo works correctly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 13 00:53:47 2012 From: jira-events at lists.jboss.org (RH Bugzilla Integration (JIRA)) Date: Tue, 13 Mar 2012 00:53:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11983) Showcase: push sample doesn't work In-Reply-To: <1110785355.5085.1329395076292.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1631509332.4973.1331614427548.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12676282#comment-12676282 ] RH Bugzilla Integration commented on RF-11983: ---------------------------------------------- Rebecca Newton made a comment on [bug 802444|https://bugzilla.redhat.com/show_bug.cgi?id=802444] Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -2,5 +2,11 @@ 1. Add a new user ApplicationRealm with the $JBOSS_HOME/bin/add-user.bat/sh script, with the role: guest. 2. Modify web.xml in the RichFaces Showcase to contain created credentials: -adkslfjasdfk + +- org.richfaces.push.jms.connectionUsername guest + + + org.richfaces.push.jms.connectionPassword + password + 3. Disable security for HornetQ completely. > Showcase: push sample doesn't work > ---------------------------------- > > Key: RF-11983 > URL: https://issues.jboss.org/browse/RF-11983 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Environment: JBoos AS 7.0.2.Final (in default configuration) / JBoss AS 7.1.0.Final and Firefox 8.0 > Reporter: Jan Papousek > Assignee: Luk?? Fry? > Fix For: 4.3-Tracking > > > {code:title=JBoss AS 7.1.0.Final} > 13:13:03,702 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/showcase].[Faces Servlet]] (http--127.0.0.1-8080-1) Servlet.service() for servlet Faces Servlet threw exception: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:397) [guava-10.0.1.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl.createTopic(JMSTopicsContextImpl.java:281) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.TopicsContext.getOrCreateTopic(TopicsContext.java:48) [richfaces-core-api-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.SessionImpl.createSubscriptions(SessionImpl.java:182) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.SessionImpl.subscribe(SessionImpl.java:177) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.resource.PushResource.encode(PushResource.java:88) [richfaces-components-ui-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.resource.UserResourceWrapperImpl.encode(UserResourceWrapperImpl.java:188) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.resource.ResourceHandlerImpl.handleResourceRequest(ResourceHandlerImpl.java:222) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:591) [jboss-jsf-api_2.1_spec-2.0.0.Final.jar:2.0.0.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.10.Final.jar:] > at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:62) [weld-core-1.1.5.AS71.Final.jar:2012-02-10 15:31] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.10.Final.jar:] > at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.1.0.Final.jar:7.1.0.Final] > at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:154) [jboss-as-web-7.1.0.Final.jar:7.1.0.Final] > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.10.Final.jar:] > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.10.Final.jar:] > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.10.Final.jar:] > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.10.Final.jar:] > at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_22] > Caused by: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:207) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:195) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingValueReference.compute(ComputingConcurrentHashMap.java:355) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.compute(ComputingConcurrentHashMap.java:184) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.getOrCompute(ComputingConcurrentHashMap.java:153) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap.getOrCompute(ComputingConcurrentHashMap.java:69) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:393) [guava-10.0.1.jar:] > ... 25 more > Caused by: javax.naming.NameNotFoundException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:97) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:177) > at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:113) > at javax.naming.InitialContext.lookup(InitialContext.java:396) [rt.jar:1.6.0_22] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.createConnection(JMSTopicsContextImpl.java:98) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.start(JMSTopicsContextImpl.java:123) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:199) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > ... 31 more > 13:13:04,263 SEVERE [org.richfaces.demo.push.MessageProducerRunnable] (MessageProducerThread) javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:397) [guava-10.0.1.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl.createTopic(JMSTopicsContextImpl.java:281) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.TopicsContext.getOrCreateTopic(TopicsContext.java:48) [richfaces-core-api-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.TopicsContext.publish(TopicsContext.java:69) [richfaces-core-api-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.demo.push.TopicsContextMessageProducer.sendMessage(TopicsContextMessageProducer.java:46) [classes:] > at org.richfaces.demo.push.MessageProducerRunnable.run(MessageProducerRunnable.java:57) [classes:] > at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_22] > Caused by: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:207) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:195) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingValueReference.compute(ComputingConcurrentHashMap.java:355) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.compute(ComputingConcurrentHashMap.java:184) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.getOrCompute(ComputingConcurrentHashMap.java:153) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap.getOrCompute(ComputingConcurrentHashMap.java:69) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:393) [guava-10.0.1.jar:] > ... 6 more > Caused by: javax.naming.NameNotFoundException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:97) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:177) > at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:113) > at javax.naming.InitialContext.lookup(InitialContext.java:396) [rt.jar:1.6.0_22] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.createConnection(JMSTopicsContextImpl.java:98) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.start(JMSTopicsContextImpl.java:123) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:199) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > ... 12 more > {code} > {code:title=JBoss AS 7.0.2.Final using default configuration} > 13:16:26,372 WARNING [javax.enterprise.resource.webcontainer.jsf.lifecycle] (http--0%3A0%3A0%3A0%3A0%3A0%3A0%3A0-8080-5) #{pushBean.sendMessage}: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory: javax.faces.FacesException: #{pushBean.sendMessage}: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:118) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > at javax.faces.component.UICommand.broadcast(UICommand.java:315) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:794) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:1259) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:81) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > at org.richfaces.demo.arrangeablemodel.PersistenceLifecycle.execute(PersistenceLifecycle.java:58) [classes:] > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:593) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:67) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:139) [jboss-as-web-7.0.2.Final.jar:7.0.2.Final] > at org.jboss.as.web.NamingValve.invoke(NamingValve.java:57) [jboss-as-web-7.0.2.Final.jar:7.0.2.Final] > at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:49) [jboss-as-jpa-7.0.2.Final.jar:7.0.2.Final] > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:154) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:667) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:952) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at java.lang.Thread.run(Thread.java:662) [:1.6.0_22] > Caused by: javax.faces.el.EvaluationException: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:102) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:102) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > ... 26 more > Caused by: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:397) [guava-10.0.1.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl.createTopic(JMSTopicsContextImpl.java:281) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.TopicsContext.getOrCreateTopic(TopicsContext.java:48) [richfaces-core-api-4.2.0.Final.jar:] > at org.richfaces.application.push.TopicsContext.publish(TopicsContext.java:69) [richfaces-core-api-4.2.0.Final.jar:] > at org.richfaces.application.push.TopicsContext$Proxy$_$$_WeldClientProxy.publish(TopicsContext$Proxy$_$$_WeldClientProxy.java) [richfaces-core-api-4.2.0.Final.jar:] > at org.richfaces.cdi.push.PushCDIExtension$PushObserverMethod.notify(PushCDIExtension.java:144) [richfaces-core-impl-4.2.0.Final.jar:] > at org.jboss.weld.manager.BeanManagerImpl.notifyObservers(BeanManagerImpl.java:635) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:628) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.jboss.weld.event.EventImpl.fire(EventImpl.java:75) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.richfaces.demo.push.PushBean.sendMessage(PushBean.java:65) [classes:] > at org.richfaces.demo.push.PushBean$Proxy$_$$_WeldClientProxy.sendMessage(PushBean$Proxy$_$$_WeldClientProxy.java) [classes:] > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_22] > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_22] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_22] > at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_22] > at org.apache.el.parser.AstValue.invoke(AstValue.java:196) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:276) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.jboss.weld.util.el.ForwardingMethodExpression.invoke(ForwardingMethodExpression.java:43) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.jboss.weld.el.WeldMethodExpression.invoke(WeldMethodExpression.java:56) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at com.sun.faces.facelets.el.TagMethodExpression.invoke(TagMethodExpression.java:105) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:88) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > ... 27 more > Caused by: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:207) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:195) [richfaces-core-impl-4.2.0.Final.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingValueReference.compute(ComputingConcurrentHashMap.java:355) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.compute(ComputingConcurrentHashMap.java:184) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.getOrCompute(ComputingConcurrentHashMap.java:153) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap.getOrCompute(ComputingConcurrentHashMap.java:69) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:393) [guava-10.0.1.jar:] > ... 47 more > Caused by: javax.naming.NameNotFoundException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:87) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:173) > at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:47) > at javax.naming.InitialContext.lookup(InitialContext.java:396) [:1.6.0_22] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.createConnection(JMSTopicsContextImpl.java:98) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.start(JMSTopicsContextImpl.java:123) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:199) [richfaces-core-impl-4.2.0.Final.jar:] > ... 53 more > 13:16:28,949 SEVERE [org.richfaces.demo.push.MessageProducerRunnable] (MessageProducerThread) javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:397) [guava-10.0.1.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl.createTopic(JMSTopicsContextImpl.java:281) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.TopicsContext.getOrCreateTopic(TopicsContext.java:48) [richfaces-core-api-4.2.0.Final.jar:] > at org.richfaces.application.push.TopicsContext.publish(TopicsContext.java:69) [richfaces-core-api-4.2.0.Final.jar:] > at org.richfaces.demo.push.TopicsContextMessageProducer.sendMessage(TopicsContextMessageProducer.java:46) [classes:] > at org.richfaces.demo.push.MessageProducerRunnable.run(MessageProducerRunnable.java:57) [classes:] > at java.lang.Thread.run(Thread.java:662) [:1.6.0_22] > Caused by: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:207) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:195) [richfaces-core-impl-4.2.0.Final.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingValueReference.compute(ComputingConcurrentHashMap.java:355) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.compute(ComputingConcurrentHashMap.java:184) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.getOrCompute(ComputingConcurrentHashMap.java:153) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap.getOrCompute(ComputingConcurrentHashMap.java:69) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:393) [guava-10.0.1.jar:] > ... 6 more > Caused by: javax.naming.NameNotFoundException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:87) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:173) > at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:47) > at javax.naming.InitialContext.lookup(InitialContext.java:396) [:1.6.0_22] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.createConnection(JMSTopicsContextImpl.java:98) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.start(JMSTopicsContextImpl.java:123) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:199) [richfaces-core-impl-4.2.0.Final.jar:] > ... 12 more > {code} > ---- > - Showcase on Openshift Express is working (yeah, there is a really big delay, but it's working). > - Sample in Metamer is also working. > - When the JBoss AS 7.0.2.Final is running with "--server-config standalone-preview.xml", the CDI push demo works correctly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 13 02:55:47 2012 From: jira-events at lists.jboss.org (SBS JIRA Integration (JIRA)) Date: Tue, 13 Mar 2012 02:55:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12023) comboBox in dataTable In-Reply-To: <1186358326.70819.1331048742987.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <329645732.5042.1331621747473.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] SBS JIRA Integration updated RF-12023: -------------------------------------- Forum Reference: https://community.jboss.org/message/723275#723275 > comboBox in dataTable > ---------------------- > > Key: RF-12023 > URL: https://issues.jboss.org/browse/RF-12023 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects, component-tables > Affects Versions: 4.1.0.Final > Environment: All > Reporter: Bertrand P > Labels: richfaces > Fix For: 4.3-Tracking > > Original Estimate: 1 day, 4 hours > Remaining Estimate: 1 day, 4 hours > > When a is in a of a , the row is selected when comboBox is selected. > A workaround is: , but that doesn't work when the arrow is clicked. > Because the arrow is generated in an independent span: > > > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 13 04:01:48 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Tue, 13 Mar 2012 04:01:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12039) fileupload: attribute data does not work Message-ID: <1594423263.5104.1331625708133.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Ji?? ?tefek created RF-12039: -------------------------------- Summary: fileupload: attribute data does not work Key: RF-12039 URL: https://issues.jboss.org/browse/RF-12039 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-input Affects Versions: 4.2.0.Final Environment: RichFaces 4.2.1-SNAPSHOT Metamer 4.2.1-SNAPSHOT Mojarra 2.1.5-SNAPSHOT JBoss Web 7.0.10.Final OpenJDK Runtime Environment 1.6.0_24-b24 @ Linux Firefox 10.0.1 @ Linux x86_64 Chrome 17.0.963.56 @ Linux i686 Reporter: Ji?? ?tefek # Deploy metamer # open http://localhost:8080/metamer/faces/components/richFileUpload/simple.xhtml # Set attribute data = 'RichFaces 4' # Set attribute onuploadcomplete = alert(event.data) # Upload file # Alert with "RichFaces 4" should show -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 13 04:37:47 2012 From: jira-events at lists.jboss.org (Stian Thorgersen (JIRA)) Date: Tue, 13 Mar 2012 04:37:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12013) Deadlock in push component In-Reply-To: <654291399.48838.1330441536575.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <568515786.5161.1331627867674.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12676302#comment-12676302 ] Stian Thorgersen commented on RF-12013: --------------------------------------- Happened again now, this time it was caused by a re-deploy > Deadlock in push component > -------------------------- > > Key: RF-12013 > URL: https://issues.jboss.org/browse/RF-12013 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Affects Versions: 4.2.0.Final > Reporter: Stian Thorgersen > Assignee: Luk?? Fry? > > Deadlocked threads in the push component prevented server from stopping. Not sure whether or not this happened when I initiated shutdown or if these where hanging around for a while. > Relevant output from jstack: > {code} > Found one Java-level deadlock: > ============================= > "push-publish-thread-1": > waiting to lock monitor 0x0000000042650238 (object 0x00000000e5ed5a50, a org.richfaces.application.push.impl.RequestImpl), > which is held by "Atmosphere-AsyncWrite-0" > "Atmosphere-AsyncWrite-0": > waiting to lock monitor 0x00000000427d9ec0 (object 0x00000000e5ed59a0, a org.richfaces.application.push.impl.SessionImpl), > which is held by "push-publish-thread-1" > Java stack information for the threads listed above: > =================================================== > "push-publish-thread-1": > at org.richfaces.application.push.impl.RequestImpl.postMessages(RequestImpl.java:85) > - waiting to lock <0x00000000e5ed5a50> (a org.richfaces.application.push.impl.RequestImpl) > at org.richfaces.application.push.impl.SessionImpl.push(SessionImpl.java:237) > - locked <0x00000000e5ed59a0> (a org.richfaces.application.push.impl.SessionImpl) > at org.richfaces.application.push.impl.TopicImpl$TopicContext.publishMessages(TopicImpl.java:88) > at org.richfaces.application.push.impl.TopicImpl$PublishTask.run(TopicImpl.java:53) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:662) > "Atmosphere-AsyncWrite-0": > at org.richfaces.application.push.impl.SessionImpl.disconnect(SessionImpl.java:117) > - waiting to lock <0x00000000e5ed59a0> (a org.richfaces.application.push.impl.SessionImpl) > at org.richfaces.application.push.impl.RequestImpl.disconnect(RequestImpl.java:107) > at org.richfaces.application.push.impl.RequestImpl.onResume(RequestImpl.java:115) > at org.atmosphere.cpr.AtmosphereResourceImpl.onResume(AtmosphereResourceImpl.java:651) > at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:600) > at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:584) > at org.atmosphere.cpr.AtmosphereResourceImpl.resume(AtmosphereResourceImpl.java:185) > - locked <0x00000000e5ee3380> (a org.atmosphere.cpr.AtmosphereResourceEventImpl) > at org.richfaces.application.push.impl.RequestImpl.onBroadcast(RequestImpl.java:129) > - locked <0x00000000e5ed5a50> (a org.richfaces.application.push.impl.RequestImpl) > at org.atmosphere.cpr.AtmosphereResourceImpl.onBroadcast(AtmosphereResourceImpl.java:663) > at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:608) > at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:584) > at org.atmosphere.cpr.DefaultBroadcaster.executeAsyncWrite(DefaultBroadcaster.java:713) > at org.atmosphere.cpr.DefaultBroadcaster$3.run(DefaultBroadcaster.java:747) > - locked <0x00000000e5ed5a88> (a org.atmosphere.cpr.AtmosphereResourceImpl) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:662) > Found 1 deadlock. > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 13 10:15:49 2012 From: jira-events at lists.jboss.org (Jean ANDRE (JIRA)) Date: Tue, 13 Mar 2012 10:15:49 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12038) IE8 - Object does not support this property or method - a4j:jsFunction In-Reply-To: <1674243330.3069.1331568048477.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1304031747.6315.1331648149291.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean ANDRE updated RF-12038: ---------------------------- Attachment: NestedWeb.zip We have prepared a simple but realistic application that demonstrates the bug. Please read the readme.txt file for more information. Do not hesitate to request additional information. > IE8 - Object does not support this property or method - a4j:jsFunction > ---------------------------------------------------------------------- > > Key: RF-12038 > URL: https://issues.jboss.org/browse/RF-12038 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.2.0.Final > Environment: cssparser-0.9.6- guava-11.0.1 - hibernate-validator-4.2.0.Final - JSF/Mojarra 2.1.6 - springframework-3.0.6.RELEASE - sac-1.3 - Windows 7 - IE 8.0.1.7601.17514 > Reporter: Jean ANDRE > Attachments: index.xhtml, NestedWeb.zip > > > Under IE8, IE reports the following error message due to a javascript error. However, the page are well displayed and the application is running ok. > Object doesn't support this property or method line 177 caracter 1 > Object doesn't support this property or method line 177 caracter 99 > Under IE Debugger, the line is: > {code} > closeTab=function(tabId){RichFaces.ajax("closeTab",null,{"incId":"1","parameters":{"tabId":tabId} } )};< > The caracter 99, is..............................................................................| (here) > {code} > This is a code generated by a4j:jsFunction from the XHTML > {code} > > > > > > > {code} > The rendered code is : > {code} > > > > {code} > See also this link as we got almost a similar: https://bugzilla.redhat.com/show_bug.cgi?id=601360. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 13 11:43:47 2012 From: jira-events at lists.jboss.org (Juraj Huska (JIRA)) Date: Tue, 13 Mar 2012 11:43:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12003) Including h:head breaks f:ajax events of commandButton In-Reply-To: <135907437.40978.1330081357692.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <749152919.6674.1331653427489.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj Huska resolved RF-12003. ------------------------------ Resolution: Done I have filled upstream issue which can be accessible [here|http://java.net/jira/browse/JAVASERVERFACES-2345]. > Including h:head breaks f:ajax events of commandButton > ------------------------------------------------------ > > Key: RF-12003 > URL: https://issues.jboss.org/browse/RF-12003 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: base functionality > Affects Versions: 4.1.0.Final, 4.2.0.CR1 > Environment: JBoss 7.0.2 Final, JBoss 7.1.0 Final, RichFaces 4.2.0 Final, 4.1.0 Final, Chrome and Safari > Reporter: Joern Ohmen > Assignee: Juraj Huska > Priority: Critical > Labels: Header, JSF2.0, RichFaces4 > Attachments: brokenRFHheadAdded.png > > > If I add h:head-Tag to my page, the ajax events of the h:commandButton are not working. The example should show up a panel with a click on a button, but nothing happens. The example is working when h:head is removed. I use a ConversationScoped Bean. > {code} > > > xmlns:h="http://java.sun.com/jsf/html" > xmlns:f="http://java.sun.com/jsf/core" > xmlns:ui="http://java.sun.com/jsf/facelets" > xmlns:fn="http://java.sun.com/jsp/jstl/functions" > xmlns:a4j="http://richfaces.org/a4j" > xmlns:rich="http://richfaces.org/rich"> > > Test > > > listener="#{testController.beginConversation}" /> > > > > > action="#{testController.changeRenderInputPanel}"> > > > rendered="#{testController.renderInputPanel}"> > > > > > > > > {code} > {code} > import java.io.Serializable; > import javax.enterprise.context.Conversation; > import javax.enterprise.context.ConversationScoped; > import javax.inject.Inject; > import javax.inject.Named; > import org.apache.commons.logging.Log; > @Named > @ConversationScoped > public class TestController implements Serializable{ > private static final long serialVersionUID = 1L; > > @Inject > private Conversation conversation; > > private String newCommentAuthor; > > private boolean renderInputPanel = true; > > @Inject > private Log logger; > > public boolean isRenderInputPanel() { > return renderInputPanel; > } > public void setRenderInputPanel(boolean renderInputPanel) { > this.renderInputPanel = renderInputPanel; > } > > public void changeRenderInputPanel() { > this.setRenderInputPanel(!isRenderInputPanel()); > logger.info("render panel: " + renderInputPanel); > } > public String getNewCommentAuthor() { > return newCommentAuthor; > } > public void setNewCommentAuthor(String newCommentAuthor) { > this.newCommentAuthor = newCommentAuthor; > } > public void beginConversation() { > if (conversation.isTransient()) { > conversation.setTimeout(120000); > conversation.begin(); > } > } > public void endConversation() { > if (!conversation.isTransient()) { > conversation.end(); > return; > } > } > } > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 13 11:43:47 2012 From: jira-events at lists.jboss.org (Juraj Huska (JIRA)) Date: Tue, 13 Mar 2012 11:43:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12003) Including h:head breaks f:ajax events of commandButton In-Reply-To: <135907437.40978.1330081357692.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <142269467.6678.1331653427895.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj Huska closed RF-12003. ---------------------------- > Including h:head breaks f:ajax events of commandButton > ------------------------------------------------------ > > Key: RF-12003 > URL: https://issues.jboss.org/browse/RF-12003 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: base functionality > Affects Versions: 4.1.0.Final, 4.2.0.CR1 > Environment: JBoss 7.0.2 Final, JBoss 7.1.0 Final, RichFaces 4.2.0 Final, 4.1.0 Final, Chrome and Safari > Reporter: Joern Ohmen > Assignee: Juraj Huska > Priority: Critical > Labels: Header, JSF2.0, RichFaces4 > Attachments: brokenRFHheadAdded.png > > > If I add h:head-Tag to my page, the ajax events of the h:commandButton are not working. The example should show up a panel with a click on a button, but nothing happens. The example is working when h:head is removed. I use a ConversationScoped Bean. > {code} > > > xmlns:h="http://java.sun.com/jsf/html" > xmlns:f="http://java.sun.com/jsf/core" > xmlns:ui="http://java.sun.com/jsf/facelets" > xmlns:fn="http://java.sun.com/jsp/jstl/functions" > xmlns:a4j="http://richfaces.org/a4j" > xmlns:rich="http://richfaces.org/rich"> > > Test > > > listener="#{testController.beginConversation}" /> > > > > > action="#{testController.changeRenderInputPanel}"> > > > rendered="#{testController.renderInputPanel}"> > > > > > > > > {code} > {code} > import java.io.Serializable; > import javax.enterprise.context.Conversation; > import javax.enterprise.context.ConversationScoped; > import javax.inject.Inject; > import javax.inject.Named; > import org.apache.commons.logging.Log; > @Named > @ConversationScoped > public class TestController implements Serializable{ > private static final long serialVersionUID = 1L; > > @Inject > private Conversation conversation; > > private String newCommentAuthor; > > private boolean renderInputPanel = true; > > @Inject > private Log logger; > > public boolean isRenderInputPanel() { > return renderInputPanel; > } > public void setRenderInputPanel(boolean renderInputPanel) { > this.renderInputPanel = renderInputPanel; > } > > public void changeRenderInputPanel() { > this.setRenderInputPanel(!isRenderInputPanel()); > logger.info("render panel: " + renderInputPanel); > } > public String getNewCommentAuthor() { > return newCommentAuthor; > } > public void setNewCommentAuthor(String newCommentAuthor) { > this.newCommentAuthor = newCommentAuthor; > } > public void beginConversation() { > if (conversation.isTransient()) { > conversation.setTimeout(120000); > conversation.begin(); > } > } > public void endConversation() { > if (!conversation.isTransient()) { > conversation.end(); > return; > } > } > } > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 13 11:45:47 2012 From: jira-events at lists.jboss.org (Edilmar Alves (JIRA)) Date: Tue, 13 Mar 2012 11:45:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11345) If two extendedDataTable placed on the page, both lose horizontal scroll. In-Reply-To: <1151360355.22349.1314110597689.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1811634074.6697.1331653547542.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12676481#comment-12676481 ] Edilmar Alves commented on RF-11345: ------------------------------------ I have the same problem with RF4.1, and I submitted a sample code in this forum link: https://community.jboss.org/message/723003 > If two extendedDataTable placed on the page, both lose horizontal scroll. > ------------------------------------------------------------------------- > > Key: RF-11345 > URL: https://issues.jboss.org/browse/RF-11345 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.0.0.Final > Environment: Windows xp sp3, java (jdk1.6.0_26), jboss-6.0.0, RichFaces 4.0.0 Final, Browsers: Firefox 5.0, IE7, Google Chrom. > Reporter: Vitaliy Pavlov > Labels: extendedDataTable, richfaces, scroll > Fix For: 4.Future > > Original Estimate: 2 weeks > Remaining Estimate: 2 weeks > > If two extendedDataTable put on page, both extendedDataTables lose horizontal scroll. > Vertical scroll is still working. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 13 13:12:48 2012 From: jira-events at lists.jboss.org (Jean ANDRE (JIRA)) Date: Tue, 13 Mar 2012 13:12:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12040) Multi-form document - command button (submit) does not work after rendering Message-ID: <375257168.7025.1331658768095.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Jean ANDRE created RF-12040: ------------------------------- Summary: Multi-form document - command button (submit) does not work after rendering Key: RF-12040 URL: https://issues.jboss.org/browse/RF-12040 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Environment: cssparser-0.9.6 - guava-11.0.1 - hibernate-validator-4.2.0.Final - JSF/Mojarra 2.1.6 - springframework-3.0.6.RELEASE - sac-1.3 - Windows 7 - FireFox 10 - RichFaces 4.2 Final Reporter: Jean ANDRE We have one page that contains two forms. The first form contain a menus bar (ajax switchType) while the second contains a tabPanel (also in ajax switchType). When a user select a menu, we select the corresponding tab that contains a submit button. Once the tab is selected, the submit button does not work. We have to click twice for submitting. 1) If we move the menu bar inside the second forms, it is working. 2) If we set the menu bar in client switchType, selecting the menu doesn't do anything. 3) If we set the menu bar in server switchType it's working. As the rendering is well executed, the submit button should works but is not whatever we set as render="@all, or any valid id". We have prepared a small application that demonstrates the case. This is a simple but realistic application. Edit the index.xhtml to play with the menu. Let us know if we doing something wrong. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 13 13:22:47 2012 From: jira-events at lists.jboss.org (Jean ANDRE (JIRA)) Date: Tue, 13 Mar 2012 13:22:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12040) Multi-form document - command button (submit) does not work after rendering In-Reply-To: <375257168.7025.1331658768095.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <93542900.7054.1331659367304.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean ANDRE updated RF-12040: ---------------------------- Description: We have one page that contains two forms. The first form contain a menus bar (ajax switchType) while the second contains a tabPanel (also in ajax switchType). When a user select a menu, we select the corresponding tab that contains a submit button. Once the tab is selected, the submit button does not work. We have to click twice for submitting. 1) If we move the menu bar inside the second forms, it is working. 2) If we set the menu bar in client switchType, selecting the menu doesn't do anything. 3) If we set the menu bar in server switchType it's working. As the rendering is well executed, the submit button should works but is not whatever we set as render="@all, or any valid id". We have prepared a small application that demonstrates the case. This is a simple but realistic application. Edit the index.xhtml to play with the menu. Let us know if we doing something wrong. Note also that the JIRA JAVASERVERFACES-2016 was reopened :[JIRA] Reopened: (JAVASERVERFACES-2016) Resources not loaded when using a dynamic ui:inlclude and rendered via ajax [ http://java.net/jira/browse/JAVASERVERFACES-2016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] was: We have one page that contains two forms. The first form contain a menus bar (ajax switchType) while the second contains a tabPanel (also in ajax switchType). When a user select a menu, we select the corresponding tab that contains a submit button. Once the tab is selected, the submit button does not work. We have to click twice for submitting. 1) If we move the menu bar inside the second forms, it is working. 2) If we set the menu bar in client switchType, selecting the menu doesn't do anything. 3) If we set the menu bar in server switchType it's working. As the rendering is well executed, the submit button should works but is not whatever we set as render="@all, or any valid id". We have prepared a small application that demonstrates the case. This is a simple but realistic application. Edit the index.xhtml to play with the menu. Let us know if we doing something wrong. Steps to Reproduce: 1) Setup the application, read the readme.txt file 2) Once the index page is displayed, the menu "Items Management" is selected by default 3) Click one the first static tab "Tab S-#1" 4) From the menu, select the menu "items management" 5) Then click on button "New List" 6) A list of item should be displayed was: 1) Setup the application, read the readme.txt file 2) Once the index page is displayed, the menu "Items Management" is selected by default 3) Click one the first static tab "Tab S-#1" 4) From the menu, select the menu "items management" 5) Then click on button "New List" > Multi-form document - command button (submit) does not work after rendering > --------------------------------------------------------------------------- > > Key: RF-12040 > URL: https://issues.jboss.org/browse/RF-12040 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Environment: cssparser-0.9.6 - guava-11.0.1 - hibernate-validator-4.2.0.Final - JSF/Mojarra 2.1.6 - springframework-3.0.6.RELEASE - sac-1.3 - Windows 7 - FireFox 10 - RichFaces 4.2 Final > Reporter: Jean ANDRE > > We have one page that contains two forms. The first form contain a menus bar (ajax switchType) while the second contains a tabPanel (also in ajax switchType). When a user select a menu, we select the corresponding tab that contains a submit button. Once the tab is selected, the submit button does not work. We have to click twice for submitting. > 1) If we move the menu bar inside the second forms, it is working. > 2) If we set the menu bar in client switchType, selecting the menu doesn't do anything. > 3) If we set the menu bar in server switchType it's working. > As the rendering is well executed, the submit button should works but is not whatever we set as render="@all, or any valid id". > We have prepared a small application that demonstrates the case. This is a simple but realistic application. Edit the index.xhtml to play with the menu. Let us know if we doing something wrong. > Note also that the JIRA JAVASERVERFACES-2016 was reopened :[JIRA] Reopened: (JAVASERVERFACES-2016) Resources not loaded when using a dynamic ui:inlclude and rendered via ajax > [ http://java.net/jira/browse/JAVASERVERFACES-2016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 14 03:37:48 2012 From: jira-events at lists.jboss.org (Gabor Nagy (JIRA)) Date: Wed, 14 Mar 2012 03:37:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11606) rich:select : doesn't cast selectItem value In-Reply-To: <1015553429.37674.1319809245181.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1424694505.7900.1331710668998.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12676604#comment-12676604 ] Gabor Nagy commented on RF-11606: --------------------------------- Same with enums (of course). > rich:select : doesn't cast selectItem value > ------------------------------------------- > > Key: RF-11606 > URL: https://issues.jboss.org/browse/RF-11606 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 4.1.0.Milestone2 > Environment: Internet Explorer 8, Google Chrome 14, Oracle Weblogic 11g > Reporter: Frederic Allard > Labels: rich:select, richfaces4 > Fix For: 4.3-Tracking > > > If you define f:selectItem(s) directly in the xhtml file as children of a rich:select, the values of the selectItem(s) are not cast to the bound value of the rich:select. > This results in the value to be not selected by the rich:select after rendering the page. > As the documentation of the component says: "The rich:select component is designed to replace standard h:selectOneMenu." > The h:selectOneMenu casts and selects the value in this case. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 14 04:11:50 2012 From: jira-events at lists.jboss.org (Dmitry Tsekhmistrov (JIRA)) Date: Wed, 14 Mar 2012 04:11:50 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11954) RF 3.3.3 Columnresizing of ExtendedDataTables does not work properly anymore on Firefox 10 and newer. In-Reply-To: <360403425.23388.1328471028849.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <703256353.7986.1331712710464.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12676610#comment-12676610 ] Dmitry Tsekhmistrov commented on RF-11954: ------------------------------------------ Also is reproduced on Win XP with Firefox 11. Have anyone solved it? > RF 3.3.3 Columnresizing of ExtendedDataTables does not work properly anymore on Firefox 10 and newer. > ----------------------------------------------------------------------------------------------------- > > Key: RF-11954 > URL: https://issues.jboss.org/browse/RF-11954 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 3.3.3.Final > Environment: Windows 7 with Firefox 10 or Firefox 13 (nightly) > archlinux with Firefox 10 > Reporter: Christian Peter > Fix For: 3.Future > > > Using the showcase for richfaces 3.3.3.... > Take a look into: > https://community.jboss.org/thread/194728?tstart=0 > I'm not sure if this is a RF issue or just a bug in the firefox javascript engine. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 14 04:51:48 2012 From: jira-events at lists.jboss.org (Markus Staab (JIRA)) Date: Wed, 14 Mar 2012 04:51:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12041) BeanValidator: no way to use BeanValidation with a custom config Message-ID: <1809953065.8110.1331715108624.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Markus Staab created RF-12041: --------------------------------- Summary: BeanValidator: no way to use BeanValidation with a custom config Key: RF-12041 URL: https://issues.jboss.org/browse/RF-12041 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 3.3.3.Final Environment: Liferay 5.2.4, Portlet 2.0, JSF 1.2 Reporter: Markus Staab The BeanValidator class bootstraps a whole new BeanValidation context in its constructor: {code} BeanValidator() { // Enforce class to load ValidatorFactory.class.getName(); // Check Factory, to avoid instantiation errors // https://jira.jboss.org/jira/browse/RF-7226 validatorFactory = Validation .buildDefaultValidatorFactory(); validatorContext = validatorFactory.usingContext(); MessageInterpolator jsfMessageInterpolator = new JsfMessageInterpolator( validatorFactory.getMessageInterpolator()); validatorContext.messageInterpolator(jsfMessageInterpolator); } {/code} because of this, there is no way to use the programmatic configuration feature of BeanValidation. I tried to pre-configure a custom MessageInterpolator with {code} Configuration config = Validation.byDefaultProvider().configure(); config.messageInterpolator( new MyInterpolator() ); {/code} but this configuration change is not taken into account by the BeanValidator of Richfaces. ATM the only way to achive this sort of customization is to use a META-INF/validation.xml -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 14 04:51:50 2012 From: jira-events at lists.jboss.org (Markus Staab (JIRA)) Date: Wed, 14 Mar 2012 04:51:50 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12041) BeanValidator: no way to use BeanValidation with a custom config In-Reply-To: <1809953065.8110.1331715108624.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1012420263.8119.1331715110234.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Markus Staab updated RF-12041: ------------------------------ Description: The BeanValidator class bootstraps a whole new BeanValidation context in its constructor: {code} BeanValidator() { // Enforce class to load ValidatorFactory.class.getName(); // Check Factory, to avoid instantiation errors // https://jira.jboss.org/jira/browse/RF-7226 validatorFactory = Validation .buildDefaultValidatorFactory(); validatorContext = validatorFactory.usingContext(); MessageInterpolator jsfMessageInterpolator = new JsfMessageInterpolator( validatorFactory.getMessageInterpolator()); validatorContext.messageInterpolator(jsfMessageInterpolator); } {code} because of this, there is no way to use the programmatic configuration feature of BeanValidation. I tried to pre-configure a custom MessageInterpolator with {code} Configuration config = Validation.byDefaultProvider().configure(); config.messageInterpolator( new MyInterpolator() ); {code} but this configuration change is not taken into account by the BeanValidator of Richfaces. ATM the only way to achive this sort of customization is to use a META-INF/validation.xml was: The BeanValidator class bootstraps a whole new BeanValidation context in its constructor: {code} BeanValidator() { // Enforce class to load ValidatorFactory.class.getName(); // Check Factory, to avoid instantiation errors // https://jira.jboss.org/jira/browse/RF-7226 validatorFactory = Validation .buildDefaultValidatorFactory(); validatorContext = validatorFactory.usingContext(); MessageInterpolator jsfMessageInterpolator = new JsfMessageInterpolator( validatorFactory.getMessageInterpolator()); validatorContext.messageInterpolator(jsfMessageInterpolator); } {/code} because of this, there is no way to use the programmatic configuration feature of BeanValidation. I tried to pre-configure a custom MessageInterpolator with {code} Configuration config = Validation.byDefaultProvider().configure(); config.messageInterpolator( new MyInterpolator() ); {/code} but this configuration change is not taken into account by the BeanValidator of Richfaces. ATM the only way to achive this sort of customization is to use a META-INF/validation.xml > BeanValidator: no way to use BeanValidation with a custom config > ---------------------------------------------------------------- > > Key: RF-12041 > URL: https://issues.jboss.org/browse/RF-12041 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 3.3.3.Final > Environment: Liferay 5.2.4, Portlet 2.0, JSF 1.2 > Reporter: Markus Staab > > The BeanValidator class bootstraps a whole new BeanValidation context in its constructor: > {code} > BeanValidator() { > // Enforce class to load > ValidatorFactory.class.getName(); > // Check Factory, to avoid instantiation errors > // https://jira.jboss.org/jira/browse/RF-7226 > validatorFactory = Validation > .buildDefaultValidatorFactory(); > validatorContext = validatorFactory.usingContext(); > MessageInterpolator jsfMessageInterpolator = new JsfMessageInterpolator( > validatorFactory.getMessageInterpolator()); > validatorContext.messageInterpolator(jsfMessageInterpolator); > } > {code} > because of this, there is no way to use the programmatic configuration feature of BeanValidation. > I tried to pre-configure a custom MessageInterpolator with > {code} > Configuration config = Validation.byDefaultProvider().configure(); > config.messageInterpolator( new MyInterpolator() ); > {code} > but this configuration change is not taken into account by the BeanValidator of Richfaces. > ATM the only way to achive this sort of customization is to use a META-INF/validation.xml -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 14 04:55:48 2012 From: jira-events at lists.jboss.org (Markus Staab (JIRA)) Date: Wed, 14 Mar 2012 04:55:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12041) BeanValidator: no way to use BeanValidation with a custom config In-Reply-To: <1809953065.8110.1331715108624.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1320502019.8130.1331715348162.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12676629#comment-12676629 ] Markus Staab commented on RF-12041: ----------------------------------- same problem when bootstrapping the pre-configuration like this. {code} ValidatorFactory validatorFactory = Validation.buildDefaultValidatorFactory(); ValidatorContext validatorContext = validatorFactory.usingContext(); validatorContext.messageInterpolator( new DpdResourceBundle() ); {code} > BeanValidator: no way to use BeanValidation with a custom config > ---------------------------------------------------------------- > > Key: RF-12041 > URL: https://issues.jboss.org/browse/RF-12041 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 3.3.3.Final > Environment: Liferay 5.2.4, Portlet 2.0, JSF 1.2 > Reporter: Markus Staab > > The BeanValidator class bootstraps a whole new BeanValidation context in its constructor: > {code} > BeanValidator() { > // Enforce class to load > ValidatorFactory.class.getName(); > // Check Factory, to avoid instantiation errors > // https://jira.jboss.org/jira/browse/RF-7226 > validatorFactory = Validation > .buildDefaultValidatorFactory(); > validatorContext = validatorFactory.usingContext(); > MessageInterpolator jsfMessageInterpolator = new JsfMessageInterpolator( > validatorFactory.getMessageInterpolator()); > validatorContext.messageInterpolator(jsfMessageInterpolator); > } > {code} > because of this, there is no way to use the programmatic configuration feature of BeanValidation. > I tried to pre-configure a custom MessageInterpolator with > {code} > Configuration config = Validation.byDefaultProvider().configure(); > config.messageInterpolator( new MyInterpolator() ); > {code} > but this configuration change is not taken into account by the BeanValidator of Richfaces. > ATM the only way to achive this sort of customization is to use a META-INF/validation.xml -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 14 04:55:48 2012 From: jira-events at lists.jboss.org (Markus Staab (JIRA)) Date: Wed, 14 Mar 2012 04:55:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12041) BeanValidator: no way to use BeanValidation with a custom config In-Reply-To: <1809953065.8110.1331715108624.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1575021941.8132.1331715348457.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12676629#comment-12676629 ] Markus Staab edited comment on RF-12041 at 3/14/12 4:55 AM: ------------------------------------------------------------ same problem when bootstrapping the pre-configuration like this. {code} ValidatorFactory validatorFactory = Validation.buildDefaultValidatorFactory(); ValidatorContext validatorContext = validatorFactory.usingContext(); validatorContext.messageInterpolator( new MyInterpolator() ); {code} was (Author: maggus): same problem when bootstrapping the pre-configuration like this. {code} ValidatorFactory validatorFactory = Validation.buildDefaultValidatorFactory(); ValidatorContext validatorContext = validatorFactory.usingContext(); validatorContext.messageInterpolator( new DpdResourceBundle() ); {code} > BeanValidator: no way to use BeanValidation with a custom config > ---------------------------------------------------------------- > > Key: RF-12041 > URL: https://issues.jboss.org/browse/RF-12041 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 3.3.3.Final > Environment: Liferay 5.2.4, Portlet 2.0, JSF 1.2 > Reporter: Markus Staab > > The BeanValidator class bootstraps a whole new BeanValidation context in its constructor: > {code} > BeanValidator() { > // Enforce class to load > ValidatorFactory.class.getName(); > // Check Factory, to avoid instantiation errors > // https://jira.jboss.org/jira/browse/RF-7226 > validatorFactory = Validation > .buildDefaultValidatorFactory(); > validatorContext = validatorFactory.usingContext(); > MessageInterpolator jsfMessageInterpolator = new JsfMessageInterpolator( > validatorFactory.getMessageInterpolator()); > validatorContext.messageInterpolator(jsfMessageInterpolator); > } > {code} > because of this, there is no way to use the programmatic configuration feature of BeanValidation. > I tried to pre-configure a custom MessageInterpolator with > {code} > Configuration config = Validation.byDefaultProvider().configure(); > config.messageInterpolator( new MyInterpolator() ); > {code} > but this configuration change is not taken into account by the BeanValidator of Richfaces. > ATM the only way to achive this sort of customization is to use a META-INF/validation.xml -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 14 04:55:49 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 14 Mar 2012 04:55:49 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12018) Typo in BOM: jsf-api should be jsp-api In-Reply-To: <269810633.51309.1330504476269.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <2123580119.8136.1331715349212.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? reassigned RF-12018: ------------------------------- Assignee: Luk?? Fry? > Typo in BOM: jsf-api should be jsp-api > -------------------------------------- > > Key: RF-12018 > URL: https://issues.jboss.org/browse/RF-12018 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 4.2.0.Final > Reporter: Marek Novotny > Assignee: Luk?? Fry? > Priority: Minor > Fix For: 4.2.1.CR1 > > > This typo is not causing any issue, it is just confusing. > usage of version: > https://github.com/richfaces/build/blob/4.2.0.20120215-Final/bom/pom.xml#L245 > definition of version: > https://github.com/richfaces/build/blob/4.2.0.20120215-Final/bom/pom.xml#L62 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 14 04:55:50 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 14 Mar 2012 04:55:50 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-10941) a4j:command* components misses default behavior event In-Reply-To: <1049007299.42458.1303309173106.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1086322591.8139.1331715350929.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-10941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? reassigned RF-10941: ------------------------------- Assignee: Luk?? Fry? > a4j:command* components misses default behavior event > ----------------------------------------------------- > > Key: RF-10941 > URL: https://issues.jboss.org/browse/RF-10941 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.0.0.Final > Reporter: Ilya Shaikovsky > Assignee: Luk?? Fry? > Fix For: 4.2.1.CR1 > > Attachments: AbstractCommandButtonHierarchy.png > > > Excerpt from the thread: http://community.jboss.org/message/601191#601191\ > {quote} > ClientBehaviorHolder interface implementors supposed to provide default event for behaviors. And some RF components misses it. > {quote} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 14 04:57:48 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 14 Mar 2012 04:57:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11833) Label for calendar results in non-valid markup In-Reply-To: <1824573501.21859.1324327990123.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1388212226.8142.1331715468621.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? reassigned RF-11833: ------------------------------- Assignee: Luk?? Fry? > Label for calendar results in non-valid markup > ---------------------------------------------- > > Key: RF-11833 > URL: https://issues.jboss.org/browse/RF-11833 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.1.0.Final > Reporter: Pavol Pitonak > Assignee: Luk?? Fry? > Priority: Trivial > Fix For: 4.2.1.CR1 > > > The code in first code snippet results in markup below which is not valid. The for attribute of the label element must refer to a form control, e.g. the actual input inside calendar (that with ID dateForm:fromDateInputDate). > {code:xml} > > > {code} > {code:xml} > > > > > ... > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 14 04:57:48 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 14 Mar 2012 04:57:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11990) client-side validation and ajax calls create maleformed javascript In-Reply-To: <941910750.25122.1329496418429.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <2067231743.8146.1331715468936.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? reassigned RF-11990: ------------------------------- Assignee: Luk?? Fry? > client-side validation and ajax calls create maleformed javascript > ------------------------------------------------------------------ > > Key: RF-11990 > URL: https://issues.jboss.org/browse/RF-11990 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-validators > Affects Versions: 4.0.0.Final, 4.1.0.Final > Environment: MyFaces 2.1.5, Hibernate-Validation 4.2.0.Final > Reporter: Daniel G > Assignee: Luk?? Fry? > Priority: Minor > Labels: javascript, richfaces, validation > Fix For: 4.2.1.CR1 > > > Using rich:validation and f:ajax together, maleformed JavaScript is generated. > I'm having a composite component, that has to be able to refresh given other components on change, but the JavaScript code generated by: > {quote} > > > > {quote} > is missing a comma between the Chain parameters. > see the red {color:red}'{color} > {quote} > onchange="jsf.util.chain(document.getElementById('idForm:bNr:input'), > event,'jsf.ajax.request(\'idForm:bNr:input\',event,\{render:\'idForm:idToolBar:idSaveButton\',\'javax.faces.behavior.event\':\'change\'\}){color:red}''{color}idForm_3AbNr_3Ainput_3Av(event,"idForm:kopf:bezugNr:input","idForm:kopf:bezugNr:input")'); return false;" /> > {quote} > the code is tanken from 4.0.0.Final, but looks similar in 4.1.0.Final -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 14 04:57:49 2012 From: jira-events at lists.jboss.org (Markus Staab (JIRA)) Date: Wed, 14 Mar 2012 04:57:49 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11755) ScrollableDataTableRowKeyConverter expects Integer as RowKey Type In-Reply-To: <2144406349.53746.1322648440937.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <261804092.8152.1331715469628.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12676630#comment-12676630 ] Markus Staab commented on RF-11755: ----------------------------------- Any change to get this fixed, when I provide a PullRequest? > ScrollableDataTableRowKeyConverter expects Integer as RowKey Type > ----------------------------------------------------------------- > > Key: RF-11755 > URL: https://issues.jboss.org/browse/RF-11755 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 3.3.3.Final > Environment: Liferay 5.2.4, JSF 1.2_15, Richfaces 3.3.3, Portlet 2.0 > Reporter: Markus Staab > Fix For: 3.Future > > > The ScrollableDataTableRowKeyConverter which is used by the scrollableDataTable expects the rowKey to be an Integer. > Since we use the primary of our database as a rowKey and this is of type Long, we got in trouble with this component. > The converter would be more compatible with this situation if it would check against Long instead of Integer. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 14 04:57:49 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 14 Mar 2012 04:57:49 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12020) Reduce number of absolute opened files In-Reply-To: <756676139.61444.1330674096251.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1553236950.8155.1331715469820.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? reassigned RF-12020: ------------------------------- Assignee: Luk?? Fry? > Reduce number of absolute opened files > -------------------------------------- > > Key: RF-12020 > URL: https://issues.jboss.org/browse/RF-12020 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: cdk > Affects Versions: 4.2.0.Final > Environment: linux > Reporter: Marek Novotny > Assignee: Luk?? Fry? > Fix For: 4.2.1.CR1, 4.Future > > Attachments: cdk-generator.patch > > > While RF Components is compiled, it normally over goes under limit for maximum open files. > I did some change which helped a little, but there will be probably bigger effect if the logic is re-factored to not open all files at the same time in generator/src/main/java/org/richfaces/cdk/templatecompiler/RendererClassGenerator.java of render method. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 14 04:59:51 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 14 Mar 2012 04:59:51 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11905) showcase - shutdown of the JBoss AS with showcase deployed throws DB error In-Reply-To: <567082387.11072.1326986119167.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <339275076.8171.1331715591908.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? reassigned RF-11905: ------------------------------- Assignee: Luk?? Fry? > showcase - shutdown of the JBoss AS with showcase deployed throws DB error > -------------------------------------------------------------------------- > > Key: RF-11905 > URL: https://issues.jboss.org/browse/RF-11905 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: showcase > Affects Versions: 4.1.0.Final > Environment: container: JBoss AS 7.1.0.CR1b, 7.0.2.Final > app: showcase 4.2.0-SNAPSHOT > Reporter: Juraj Huska > Assignee: Luk?? Fry? > Priority: Minor > Fix For: 4.2.1.CR1 > > > When shutting down JBoss AS 7 with showcase deployed, then the DB error is thrown: > {code} > 16:09:52,334 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] HHH000231: Schema export unsuccessful: org.h2.jdbc.JdbcSQLException: Database is already closed (to disable automatic closing at VM shutdown, add ";DB_CLOSE_ON_EXIT=FALSE" to the db URL) [90121-161] > at org.h2.message.DbException.getJdbcSQLException(DbException.java:329) > at org.h2.message.DbException.get(DbException.java:169) > at org.h2.message.DbException.get(DbException.java:146) > at org.h2.message.DbException.get(DbException.java:135) > at org.h2.jdbc.JdbcConnection.checkClosed(JdbcConnection.java:1394) > at org.h2.jdbc.JdbcConnection.checkClosed(JdbcConnection.java:1369) > at org.h2.jdbc.JdbcConnection.createStatement(JdbcConnection.java:191) > at org.jboss.jca.adapters.jdbc.WrappedConnection.createStatement(WrappedConnection.java:301) > at org.hibernate.tool.hbm2ddl.DatabaseExporter.(DatabaseExporter.java:54) [hibernate-core-4.0.0.Final.jar:4.0.0.Final] > at org.hibernate.tool.hbm2ddl.SchemaExport.execute(SchemaExport.java:368) [hibernate-core-4.0.0.Final.jar:4.0.0.Final] > at org.hibernate.tool.hbm2ddl.SchemaExport.drop(SchemaExport.java:319) [hibernate-core-4.0.0.Final.jar:4.0.0.Final] > at org.hibernate.tool.hbm2ddl.SchemaExport.drop(SchemaExport.java:315) [hibernate-core-4.0.0.Final.jar:4.0.0.Final] > at org.hibernate.internal.SessionFactoryImpl.close(SessionFactoryImpl.java:1305) [hibernate-core-4.0.0.Final.jar:4.0.0.Final] > at org.hibernate.ejb.EntityManagerFactoryImpl.close(EntityManagerFactoryImpl.java:126) [hibernate-entitymanager-4.0.0.Final.jar:4.0.0.Final] > at org.richfaces.demo.arrangeablemodel.PersistenceService.destroy(PersistenceService.java:159) [classes:] > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_22] > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_22] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_22] > at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_22] > at org.jboss.as.ee.component.ManagedReferenceLifecycleMethodInterceptorFactory$ManagedReferenceLifecycleMethodInterceptor.processInvocation(ManagedReferenceLifecycleMethodInterceptorFactory.java:130) [jboss-as-ee-7.1.0.CR1b.jar:7.1.0.CR1b] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final] > at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final] > at org.jboss.as.ee.component.ManagedReferenceReleaseInterceptorFactory$ManagedReferenceReleaseInterceptor.processInvocation(ManagedReferenceReleaseInterceptorFactory.java:90) [jboss-as-ee-7.1.0.CR1b.jar:7.1.0.CR1b] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final] > at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final] > at org.jboss.as.ee.component.TCCLInterceptor.processInvocation(TCCLInterceptor.java:45) [jboss-as-ee-7.1.0.CR1b.jar:7.1.0.CR1b] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final] > at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final] > at org.jboss.as.ee.component.BasicComponentInstance.destroy(BasicComponentInstance.java:122) [jboss-as-ee-7.1.0.CR1b.jar:7.1.0.CR1b] > at org.jboss.as.web.deployment.component.WebComponentInstantiator$2.release(WebComponentInstantiator.java:102) [jboss-as-web-7.1.0.CR1b.jar:7.1.0.CR1b] > at org.jboss.as.web.deployment.WebInjectionContainer.destroyInstance(WebInjectionContainer.java:67) [jboss-as-web-7.1.0.CR1b.jar:7.1.0.CR1b] > at org.jboss.as.web.deployment.jsf.JsfInjectionProvider.invokePreDestroy(JsfInjectionProvider.java:56) [jboss-as-web-7.1.0.CR1b.jar:7.1.0.CR1b] > at com.sun.faces.mgbean.BeanBuilder.destroy(BeanBuilder.java:116) [jsf-impl-2.1.5-jbossorg-1.jar:2.1.5-SNAPSHOT] > at com.sun.faces.mgbean.BeanManager.destroy(BeanManager.java:283) [jsf-impl-2.1.5-jbossorg-1.jar:2.1.5-SNAPSHOT] > at com.sun.faces.application.WebappLifecycleListener.handleAttributeEvent(WebappLifecycleListener.java:314) [jsf-impl-2.1.5-jbossorg-1.jar:2.1.5-SNAPSHOT] > at com.sun.faces.application.WebappLifecycleListener.contextDestroyed(WebappLifecycleListener.java:368) [jsf-impl-2.1.5-jbossorg-1.jar:2.1.5-SNAPSHOT] > at com.sun.faces.config.ConfigureListener.contextDestroyed(ConfigureListener.java:308) [jsf-impl-2.1.5-jbossorg-1.jar:2.1.5-SNAPSHOT] > at org.apache.catalina.core.StandardContext.listenerStop(StandardContext.java:3489) [jbossweb-7.0.7.Final.jar:] > at org.apache.catalina.core.StandardContext.stop(StandardContext.java:3999) [jbossweb-7.0.7.Final.jar:] > at org.jboss.as.web.deployment.WebDeploymentService.stop(WebDeploymentService.java:96) [jboss-as-web-7.1.0.CR1b.jar:7.1.0.CR1b] > at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:1909) > at org.jboss.msc.service.ServiceControllerImpl$StopTask.run(ServiceControllerImpl.java:1872) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_22] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_22] > at java.lang.Thread.run(Thread.java:662) [:1.6.0_22] > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 14 04:59:52 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 14 Mar 2012 04:59:52 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11978) Graph Validator - does not mark context to fail validation In-Reply-To: <1183055506.1477.1329142441059.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1405150887.8173.1331715592361.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? reassigned RF-11978: ------------------------------- Assignee: Luk?? Fry? > Graph Validator - does not mark context to fail validation > ---------------------------------------------------------- > > Key: RF-11978 > URL: https://issues.jboss.org/browse/RF-11978 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-validators > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Priority: Minor > Fix For: 4.2.1.CR1 > > > GraphValidator is using BeanValidator to check that instance does not failed [1], > and it calls [{{facesContext.renderResponse()}}|http://docs.oracle.com/javaee/6/api/javax/faces/context/FacesContext.html#renderResponse()] when beanValidation returns some message. > However it does not call [{{facesContext.validationFailed()}}|http://docs.oracle.com/javaee/6/api/javax/faces/context/FacesContext.html#isValidationFailed()]. > [1] https://github.com/richfaces/components/blob/develop/validator/ui/src/main/java/org/richfaces/component/AbstractGraphValidator.java#L213 > ---- > This causes problem when another component reads the [{{FacesContext.isValidationFailed()}}|http://docs.oracle.com/javaee/6/api/javax/faces/context/FacesContext.html#isValidationFailed()] flag in order to distinguish is it should proceed or not, like in following snippet. > ---- > Following snippet is part of the wizard using togglePanel and toggleControl in order to switch panels. > When user hits Continue button, togglePanel is switched regardless the graphValidator validation failed or not - when validation for another component like {{h:inputText}} fails, toggleControl does not switch. > {code:XML} > ... > > > > > > > > > > > > > > > > > > > > > > > > > ... > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 14 04:59:52 2012 From: jira-events at lists.jboss.org (Markus Staab (JIRA)) Date: Wed, 14 Mar 2012 04:59:52 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11755) ScrollableDataTableRowKeyConverter expects Integer as RowKey Type In-Reply-To: <2144406349.53746.1322648440937.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1581899583.8176.1331715592483.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12676630#comment-12676630 ] Markus Staab edited comment on RF-11755 at 3/14/12 4:59 AM: ------------------------------------------------------------ Any chance to get this fixed, when I provide a PullRequest? was (Author: maggus): Any change to get this fixed, when I provide a PullRequest? > ScrollableDataTableRowKeyConverter expects Integer as RowKey Type > ----------------------------------------------------------------- > > Key: RF-11755 > URL: https://issues.jboss.org/browse/RF-11755 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 3.3.3.Final > Environment: Liferay 5.2.4, JSF 1.2_15, Richfaces 3.3.3, Portlet 2.0 > Reporter: Markus Staab > Fix For: 3.Future > > > The ScrollableDataTableRowKeyConverter which is used by the scrollableDataTable expects the rowKey to be an Integer. > Since we use the primary of our database as a rowKey and this is of type Long, we got in trouble with this component. > The converter would be more compatible with this situation if it would check against Long instead of Integer. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 14 07:50:47 2012 From: jira-events at lists.jboss.org (Jean ANDRE (JIRA)) Date: Wed, 14 Mar 2012 07:50:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12040) Multi-form document - command button (submit) does not work after rendering In-Reply-To: <375257168.7025.1331658768095.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <694737638.8552.1331725847298.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean ANDRE updated RF-12040: ---------------------------- Steps to Reproduce: 1) Setup the application, read the readme.txt file 2) Once the index page is displayed, the tab "Items Management" is selected by default 3) Click one the first static tab "Tab S-#1" 4) From the menu, select the menu "items management" 5) Then click on button "New List" 6) A list of item should be displayed But at the step 5, you have to click twice the button or to do F5 that refresh the whole page, it is like restarting the appl. from the beginning. was: 1) Setup the application, read the readme.txt file 2) Once the index page is displayed, the menu "Items Management" is selected by default 3) Click one the first static tab "Tab S-#1" 4) From the menu, select the menu "items management" 5) Then click on button "New List" 6) A list of item should be displayed > Multi-form document - command button (submit) does not work after rendering > --------------------------------------------------------------------------- > > Key: RF-12040 > URL: https://issues.jboss.org/browse/RF-12040 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Environment: cssparser-0.9.6 - guava-11.0.1 - hibernate-validator-4.2.0.Final - JSF/Mojarra 2.1.6 - springframework-3.0.6.RELEASE - sac-1.3 - Windows 7 - FireFox 10 - RichFaces 4.2 Final > Reporter: Jean ANDRE > Attachments: NestedWebWithMenu.zip > > > We have one page that contains two forms. The first form contain a menus bar (ajax switchType) while the second contains a tabPanel (also in ajax switchType). When a user select a menu, we select the corresponding tab that contains a submit button. Once the tab is selected, the submit button does not work. We have to click twice for submitting. > 1) If we move the menu bar inside the second forms, it is working. > 2) If we set the menu bar in client switchType, selecting the menu doesn't do anything. > 3) If we set the menu bar in server switchType it's working. > As the rendering is well executed, the submit button should works but is not whatever we set as render="@all, or any valid id". > We have prepared a small application that demonstrates the case. This is a simple but realistic application. Edit the index.xhtml to play with the menu. Let us know if we doing something wrong. > Note also that the JIRA JAVASERVERFACES-2016 was reopened :[JIRA] Reopened: (JAVASERVERFACES-2016) Resources not loaded when using a dynamic ui:inlclude and rendered via ajax > [ http://java.net/jira/browse/JAVASERVERFACES-2016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 14 08:49:48 2012 From: jira-events at lists.jboss.org (RH Bugzilla Integration (JIRA)) Date: Wed, 14 Mar 2012 08:49:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11983) Showcase: push sample doesn't work In-Reply-To: <1110785355.5085.1329395076292.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <593082722.8913.1331729388171.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12676700#comment-12676700 ] RH Bugzilla Integration commented on RF-11983: ---------------------------------------------- Karel Piwko made a comment on [bug 802444|https://bugzilla.redhat.com/show_bug.cgi?id=802444] Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1,12 +1,14 @@ -Both the default installation of JBoss Enterprise Application Platform and JMS Push, which is required by RichFaces Showcase example, are secured by default. To deploy the application, choose one of the following options: +Both the default installation of JBoss Enterprise Application Platform and JMS Push, which is required by RichFaces Showcase example, are secured by default. To deploy the application, you have add an user to a secured ApplicationRealm via following commands: -1. Add a new user ApplicationRealm with the $JBOSS_HOME/bin/add-user.bat/sh script, with the role: guest. -2. Modify web.xml in the RichFaces Showcase to contain created credentials: +1. Add a new user ApplicationRealm with the $JBOSS_HOME/bin/add-user.bat or add-user.sh script, with the role: guest. + +2. Modify web.xml in the RichFaces Showcase. Replace ${username} and ${password} with actual credentials. + -- org.richfaces.push.jms.connectionUsername guest + org.richfaces.push.jms.connectionUsername ${username} org.richfaces.push.jms.connectionPassword - password + ${password} - + -3. Disable security for HornetQ completely. > Showcase: push sample doesn't work > ---------------------------------- > > Key: RF-11983 > URL: https://issues.jboss.org/browse/RF-11983 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Environment: JBoos AS 7.0.2.Final (in default configuration) / JBoss AS 7.1.0.Final and Firefox 8.0 > Reporter: Jan Papousek > Assignee: Luk?? Fry? > Fix For: 4.3-Tracking > > > {code:title=JBoss AS 7.1.0.Final} > 13:13:03,702 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/showcase].[Faces Servlet]] (http--127.0.0.1-8080-1) Servlet.service() for servlet Faces Servlet threw exception: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:397) [guava-10.0.1.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl.createTopic(JMSTopicsContextImpl.java:281) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.TopicsContext.getOrCreateTopic(TopicsContext.java:48) [richfaces-core-api-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.SessionImpl.createSubscriptions(SessionImpl.java:182) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.SessionImpl.subscribe(SessionImpl.java:177) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.resource.PushResource.encode(PushResource.java:88) [richfaces-components-ui-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.resource.UserResourceWrapperImpl.encode(UserResourceWrapperImpl.java:188) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.resource.ResourceHandlerImpl.handleResourceRequest(ResourceHandlerImpl.java:222) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:591) [jboss-jsf-api_2.1_spec-2.0.0.Final.jar:2.0.0.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.10.Final.jar:] > at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:62) [weld-core-1.1.5.AS71.Final.jar:2012-02-10 15:31] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.10.Final.jar:] > at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.1.0.Final.jar:7.1.0.Final] > at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:154) [jboss-as-web-7.1.0.Final.jar:7.1.0.Final] > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.10.Final.jar:] > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.10.Final.jar:] > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.10.Final.jar:] > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.10.Final.jar:] > at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_22] > Caused by: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:207) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:195) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingValueReference.compute(ComputingConcurrentHashMap.java:355) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.compute(ComputingConcurrentHashMap.java:184) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.getOrCompute(ComputingConcurrentHashMap.java:153) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap.getOrCompute(ComputingConcurrentHashMap.java:69) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:393) [guava-10.0.1.jar:] > ... 25 more > Caused by: javax.naming.NameNotFoundException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:97) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:177) > at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:113) > at javax.naming.InitialContext.lookup(InitialContext.java:396) [rt.jar:1.6.0_22] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.createConnection(JMSTopicsContextImpl.java:98) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.start(JMSTopicsContextImpl.java:123) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:199) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > ... 31 more > 13:13:04,263 SEVERE [org.richfaces.demo.push.MessageProducerRunnable] (MessageProducerThread) javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:397) [guava-10.0.1.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl.createTopic(JMSTopicsContextImpl.java:281) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.TopicsContext.getOrCreateTopic(TopicsContext.java:48) [richfaces-core-api-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.TopicsContext.publish(TopicsContext.java:69) [richfaces-core-api-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.demo.push.TopicsContextMessageProducer.sendMessage(TopicsContextMessageProducer.java:46) [classes:] > at org.richfaces.demo.push.MessageProducerRunnable.run(MessageProducerRunnable.java:57) [classes:] > at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_22] > Caused by: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:207) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:195) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingValueReference.compute(ComputingConcurrentHashMap.java:355) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.compute(ComputingConcurrentHashMap.java:184) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.getOrCompute(ComputingConcurrentHashMap.java:153) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap.getOrCompute(ComputingConcurrentHashMap.java:69) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:393) [guava-10.0.1.jar:] > ... 6 more > Caused by: javax.naming.NameNotFoundException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:97) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:177) > at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:113) > at javax.naming.InitialContext.lookup(InitialContext.java:396) [rt.jar:1.6.0_22] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.createConnection(JMSTopicsContextImpl.java:98) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.start(JMSTopicsContextImpl.java:123) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:199) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > ... 12 more > {code} > {code:title=JBoss AS 7.0.2.Final using default configuration} > 13:16:26,372 WARNING [javax.enterprise.resource.webcontainer.jsf.lifecycle] (http--0%3A0%3A0%3A0%3A0%3A0%3A0%3A0-8080-5) #{pushBean.sendMessage}: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory: javax.faces.FacesException: #{pushBean.sendMessage}: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:118) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > at javax.faces.component.UICommand.broadcast(UICommand.java:315) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:794) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:1259) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:81) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > at org.richfaces.demo.arrangeablemodel.PersistenceLifecycle.execute(PersistenceLifecycle.java:58) [classes:] > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:593) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:67) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:139) [jboss-as-web-7.0.2.Final.jar:7.0.2.Final] > at org.jboss.as.web.NamingValve.invoke(NamingValve.java:57) [jboss-as-web-7.0.2.Final.jar:7.0.2.Final] > at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:49) [jboss-as-jpa-7.0.2.Final.jar:7.0.2.Final] > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:154) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:667) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:952) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at java.lang.Thread.run(Thread.java:662) [:1.6.0_22] > Caused by: javax.faces.el.EvaluationException: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:102) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:102) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > ... 26 more > Caused by: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:397) [guava-10.0.1.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl.createTopic(JMSTopicsContextImpl.java:281) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.TopicsContext.getOrCreateTopic(TopicsContext.java:48) [richfaces-core-api-4.2.0.Final.jar:] > at org.richfaces.application.push.TopicsContext.publish(TopicsContext.java:69) [richfaces-core-api-4.2.0.Final.jar:] > at org.richfaces.application.push.TopicsContext$Proxy$_$$_WeldClientProxy.publish(TopicsContext$Proxy$_$$_WeldClientProxy.java) [richfaces-core-api-4.2.0.Final.jar:] > at org.richfaces.cdi.push.PushCDIExtension$PushObserverMethod.notify(PushCDIExtension.java:144) [richfaces-core-impl-4.2.0.Final.jar:] > at org.jboss.weld.manager.BeanManagerImpl.notifyObservers(BeanManagerImpl.java:635) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:628) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.jboss.weld.event.EventImpl.fire(EventImpl.java:75) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.richfaces.demo.push.PushBean.sendMessage(PushBean.java:65) [classes:] > at org.richfaces.demo.push.PushBean$Proxy$_$$_WeldClientProxy.sendMessage(PushBean$Proxy$_$$_WeldClientProxy.java) [classes:] > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_22] > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_22] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_22] > at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_22] > at org.apache.el.parser.AstValue.invoke(AstValue.java:196) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:276) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.jboss.weld.util.el.ForwardingMethodExpression.invoke(ForwardingMethodExpression.java:43) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.jboss.weld.el.WeldMethodExpression.invoke(WeldMethodExpression.java:56) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at com.sun.faces.facelets.el.TagMethodExpression.invoke(TagMethodExpression.java:105) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:88) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > ... 27 more > Caused by: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:207) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:195) [richfaces-core-impl-4.2.0.Final.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingValueReference.compute(ComputingConcurrentHashMap.java:355) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.compute(ComputingConcurrentHashMap.java:184) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.getOrCompute(ComputingConcurrentHashMap.java:153) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap.getOrCompute(ComputingConcurrentHashMap.java:69) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:393) [guava-10.0.1.jar:] > ... 47 more > Caused by: javax.naming.NameNotFoundException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:87) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:173) > at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:47) > at javax.naming.InitialContext.lookup(InitialContext.java:396) [:1.6.0_22] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.createConnection(JMSTopicsContextImpl.java:98) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.start(JMSTopicsContextImpl.java:123) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:199) [richfaces-core-impl-4.2.0.Final.jar:] > ... 53 more > 13:16:28,949 SEVERE [org.richfaces.demo.push.MessageProducerRunnable] (MessageProducerThread) javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:397) [guava-10.0.1.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl.createTopic(JMSTopicsContextImpl.java:281) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.TopicsContext.getOrCreateTopic(TopicsContext.java:48) [richfaces-core-api-4.2.0.Final.jar:] > at org.richfaces.application.push.TopicsContext.publish(TopicsContext.java:69) [richfaces-core-api-4.2.0.Final.jar:] > at org.richfaces.demo.push.TopicsContextMessageProducer.sendMessage(TopicsContextMessageProducer.java:46) [classes:] > at org.richfaces.demo.push.MessageProducerRunnable.run(MessageProducerRunnable.java:57) [classes:] > at java.lang.Thread.run(Thread.java:662) [:1.6.0_22] > Caused by: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:207) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:195) [richfaces-core-impl-4.2.0.Final.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingValueReference.compute(ComputingConcurrentHashMap.java:355) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.compute(ComputingConcurrentHashMap.java:184) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.getOrCompute(ComputingConcurrentHashMap.java:153) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap.getOrCompute(ComputingConcurrentHashMap.java:69) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:393) [guava-10.0.1.jar:] > ... 6 more > Caused by: javax.naming.NameNotFoundException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:87) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:173) > at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:47) > at javax.naming.InitialContext.lookup(InitialContext.java:396) [:1.6.0_22] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.createConnection(JMSTopicsContextImpl.java:98) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.start(JMSTopicsContextImpl.java:123) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:199) [richfaces-core-impl-4.2.0.Final.jar:] > ... 12 more > {code} > ---- > - Showcase on Openshift Express is working (yeah, there is a really big delay, but it's working). > - Sample in Metamer is also working. > - When the JBoss AS 7.0.2.Final is running with "--server-config standalone-preview.xml", the CDI push demo works correctly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 14 08:52:47 2012 From: jira-events at lists.jboss.org (RH Bugzilla Integration (JIRA)) Date: Wed, 14 Mar 2012 08:52:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11983) Showcase: push sample doesn't work In-Reply-To: <1110785355.5085.1329395076292.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <141347776.8918.1331729567349.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12676702#comment-12676702 ] RH Bugzilla Integration commented on RF-11983: ---------------------------------------------- Karel Piwko made a private comment on [bug 802444|https://bugzilla.redhat.com/show_bug.cgi?id=802444] > Showcase: push sample doesn't work > ---------------------------------- > > Key: RF-11983 > URL: https://issues.jboss.org/browse/RF-11983 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Environment: JBoos AS 7.0.2.Final (in default configuration) / JBoss AS 7.1.0.Final and Firefox 8.0 > Reporter: Jan Papousek > Assignee: Luk?? Fry? > Fix For: 4.3-Tracking > > > {code:title=JBoss AS 7.1.0.Final} > 13:13:03,702 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/showcase].[Faces Servlet]] (http--127.0.0.1-8080-1) Servlet.service() for servlet Faces Servlet threw exception: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:397) [guava-10.0.1.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl.createTopic(JMSTopicsContextImpl.java:281) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.TopicsContext.getOrCreateTopic(TopicsContext.java:48) [richfaces-core-api-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.SessionImpl.createSubscriptions(SessionImpl.java:182) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.SessionImpl.subscribe(SessionImpl.java:177) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.resource.PushResource.encode(PushResource.java:88) [richfaces-components-ui-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.resource.UserResourceWrapperImpl.encode(UserResourceWrapperImpl.java:188) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.resource.ResourceHandlerImpl.handleResourceRequest(ResourceHandlerImpl.java:222) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:591) [jboss-jsf-api_2.1_spec-2.0.0.Final.jar:2.0.0.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.10.Final.jar:] > at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:62) [weld-core-1.1.5.AS71.Final.jar:2012-02-10 15:31] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.10.Final.jar:] > at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.1.0.Final.jar:7.1.0.Final] > at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:154) [jboss-as-web-7.1.0.Final.jar:7.1.0.Final] > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.10.Final.jar:] > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.10.Final.jar:] > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.10.Final.jar:] > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.10.Final.jar:] > at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_22] > Caused by: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:207) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:195) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingValueReference.compute(ComputingConcurrentHashMap.java:355) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.compute(ComputingConcurrentHashMap.java:184) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.getOrCompute(ComputingConcurrentHashMap.java:153) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap.getOrCompute(ComputingConcurrentHashMap.java:69) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:393) [guava-10.0.1.jar:] > ... 25 more > Caused by: javax.naming.NameNotFoundException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:97) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:177) > at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:113) > at javax.naming.InitialContext.lookup(InitialContext.java:396) [rt.jar:1.6.0_22] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.createConnection(JMSTopicsContextImpl.java:98) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.start(JMSTopicsContextImpl.java:123) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:199) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > ... 31 more > 13:13:04,263 SEVERE [org.richfaces.demo.push.MessageProducerRunnable] (MessageProducerThread) javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:397) [guava-10.0.1.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl.createTopic(JMSTopicsContextImpl.java:281) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.TopicsContext.getOrCreateTopic(TopicsContext.java:48) [richfaces-core-api-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.TopicsContext.publish(TopicsContext.java:69) [richfaces-core-api-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.demo.push.TopicsContextMessageProducer.sendMessage(TopicsContextMessageProducer.java:46) [classes:] > at org.richfaces.demo.push.MessageProducerRunnable.run(MessageProducerRunnable.java:57) [classes:] > at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_22] > Caused by: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:207) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:195) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingValueReference.compute(ComputingConcurrentHashMap.java:355) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.compute(ComputingConcurrentHashMap.java:184) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.getOrCompute(ComputingConcurrentHashMap.java:153) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap.getOrCompute(ComputingConcurrentHashMap.java:69) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:393) [guava-10.0.1.jar:] > ... 6 more > Caused by: javax.naming.NameNotFoundException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:97) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:177) > at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:113) > at javax.naming.InitialContext.lookup(InitialContext.java:396) [rt.jar:1.6.0_22] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.createConnection(JMSTopicsContextImpl.java:98) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.start(JMSTopicsContextImpl.java:123) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:199) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > ... 12 more > {code} > {code:title=JBoss AS 7.0.2.Final using default configuration} > 13:16:26,372 WARNING [javax.enterprise.resource.webcontainer.jsf.lifecycle] (http--0%3A0%3A0%3A0%3A0%3A0%3A0%3A0-8080-5) #{pushBean.sendMessage}: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory: javax.faces.FacesException: #{pushBean.sendMessage}: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:118) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > at javax.faces.component.UICommand.broadcast(UICommand.java:315) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:794) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:1259) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:81) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > at org.richfaces.demo.arrangeablemodel.PersistenceLifecycle.execute(PersistenceLifecycle.java:58) [classes:] > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:593) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:67) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:139) [jboss-as-web-7.0.2.Final.jar:7.0.2.Final] > at org.jboss.as.web.NamingValve.invoke(NamingValve.java:57) [jboss-as-web-7.0.2.Final.jar:7.0.2.Final] > at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:49) [jboss-as-jpa-7.0.2.Final.jar:7.0.2.Final] > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:154) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:667) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:952) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at java.lang.Thread.run(Thread.java:662) [:1.6.0_22] > Caused by: javax.faces.el.EvaluationException: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:102) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:102) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > ... 26 more > Caused by: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:397) [guava-10.0.1.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl.createTopic(JMSTopicsContextImpl.java:281) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.TopicsContext.getOrCreateTopic(TopicsContext.java:48) [richfaces-core-api-4.2.0.Final.jar:] > at org.richfaces.application.push.TopicsContext.publish(TopicsContext.java:69) [richfaces-core-api-4.2.0.Final.jar:] > at org.richfaces.application.push.TopicsContext$Proxy$_$$_WeldClientProxy.publish(TopicsContext$Proxy$_$$_WeldClientProxy.java) [richfaces-core-api-4.2.0.Final.jar:] > at org.richfaces.cdi.push.PushCDIExtension$PushObserverMethod.notify(PushCDIExtension.java:144) [richfaces-core-impl-4.2.0.Final.jar:] > at org.jboss.weld.manager.BeanManagerImpl.notifyObservers(BeanManagerImpl.java:635) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:628) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.jboss.weld.event.EventImpl.fire(EventImpl.java:75) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.richfaces.demo.push.PushBean.sendMessage(PushBean.java:65) [classes:] > at org.richfaces.demo.push.PushBean$Proxy$_$$_WeldClientProxy.sendMessage(PushBean$Proxy$_$$_WeldClientProxy.java) [classes:] > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_22] > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_22] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_22] > at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_22] > at org.apache.el.parser.AstValue.invoke(AstValue.java:196) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:276) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.jboss.weld.util.el.ForwardingMethodExpression.invoke(ForwardingMethodExpression.java:43) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.jboss.weld.el.WeldMethodExpression.invoke(WeldMethodExpression.java:56) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at com.sun.faces.facelets.el.TagMethodExpression.invoke(TagMethodExpression.java:105) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:88) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > ... 27 more > Caused by: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:207) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:195) [richfaces-core-impl-4.2.0.Final.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingValueReference.compute(ComputingConcurrentHashMap.java:355) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.compute(ComputingConcurrentHashMap.java:184) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.getOrCompute(ComputingConcurrentHashMap.java:153) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap.getOrCompute(ComputingConcurrentHashMap.java:69) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:393) [guava-10.0.1.jar:] > ... 47 more > Caused by: javax.naming.NameNotFoundException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:87) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:173) > at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:47) > at javax.naming.InitialContext.lookup(InitialContext.java:396) [:1.6.0_22] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.createConnection(JMSTopicsContextImpl.java:98) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.start(JMSTopicsContextImpl.java:123) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:199) [richfaces-core-impl-4.2.0.Final.jar:] > ... 53 more > 13:16:28,949 SEVERE [org.richfaces.demo.push.MessageProducerRunnable] (MessageProducerThread) javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:397) [guava-10.0.1.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl.createTopic(JMSTopicsContextImpl.java:281) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.TopicsContext.getOrCreateTopic(TopicsContext.java:48) [richfaces-core-api-4.2.0.Final.jar:] > at org.richfaces.application.push.TopicsContext.publish(TopicsContext.java:69) [richfaces-core-api-4.2.0.Final.jar:] > at org.richfaces.demo.push.TopicsContextMessageProducer.sendMessage(TopicsContextMessageProducer.java:46) [classes:] > at org.richfaces.demo.push.MessageProducerRunnable.run(MessageProducerRunnable.java:57) [classes:] > at java.lang.Thread.run(Thread.java:662) [:1.6.0_22] > Caused by: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:207) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:195) [richfaces-core-impl-4.2.0.Final.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingValueReference.compute(ComputingConcurrentHashMap.java:355) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.compute(ComputingConcurrentHashMap.java:184) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.getOrCompute(ComputingConcurrentHashMap.java:153) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap.getOrCompute(ComputingConcurrentHashMap.java:69) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:393) [guava-10.0.1.jar:] > ... 6 more > Caused by: javax.naming.NameNotFoundException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:87) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:173) > at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:47) > at javax.naming.InitialContext.lookup(InitialContext.java:396) [:1.6.0_22] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.createConnection(JMSTopicsContextImpl.java:98) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.start(JMSTopicsContextImpl.java:123) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:199) [richfaces-core-impl-4.2.0.Final.jar:] > ... 12 more > {code} > ---- > - Showcase on Openshift Express is working (yeah, there is a really big delay, but it's working). > - Sample in Metamer is also working. > - When the JBoss AS 7.0.2.Final is running with "--server-config standalone-preview.xml", the CDI push demo works correctly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 14 08:54:48 2012 From: jira-events at lists.jboss.org (RH Bugzilla Integration (JIRA)) Date: Wed, 14 Mar 2012 08:54:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11983) Showcase: push sample doesn't work In-Reply-To: <1110785355.5085.1329395076292.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1893793447.8924.1331729688098.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12676703#comment-12676703 ] RH Bugzilla Integration commented on RF-11983: ---------------------------------------------- Karel Piwko made a private comment on [bug 802444|https://bugzilla.redhat.com/show_bug.cgi?id=802444] > Showcase: push sample doesn't work > ---------------------------------- > > Key: RF-11983 > URL: https://issues.jboss.org/browse/RF-11983 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Environment: JBoos AS 7.0.2.Final (in default configuration) / JBoss AS 7.1.0.Final and Firefox 8.0 > Reporter: Jan Papousek > Assignee: Luk?? Fry? > Fix For: 4.3-Tracking > > > {code:title=JBoss AS 7.1.0.Final} > 13:13:03,702 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/showcase].[Faces Servlet]] (http--127.0.0.1-8080-1) Servlet.service() for servlet Faces Servlet threw exception: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:397) [guava-10.0.1.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl.createTopic(JMSTopicsContextImpl.java:281) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.TopicsContext.getOrCreateTopic(TopicsContext.java:48) [richfaces-core-api-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.SessionImpl.createSubscriptions(SessionImpl.java:182) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.SessionImpl.subscribe(SessionImpl.java:177) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.resource.PushResource.encode(PushResource.java:88) [richfaces-components-ui-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.resource.UserResourceWrapperImpl.encode(UserResourceWrapperImpl.java:188) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.resource.ResourceHandlerImpl.handleResourceRequest(ResourceHandlerImpl.java:222) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:591) [jboss-jsf-api_2.1_spec-2.0.0.Final.jar:2.0.0.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.10.Final.jar:] > at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:62) [weld-core-1.1.5.AS71.Final.jar:2012-02-10 15:31] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.10.Final.jar:] > at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.1.0.Final.jar:7.1.0.Final] > at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:154) [jboss-as-web-7.1.0.Final.jar:7.1.0.Final] > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.10.Final.jar:] > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.10.Final.jar:] > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.10.Final.jar:] > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.10.Final.jar:] > at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_22] > Caused by: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:207) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:195) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingValueReference.compute(ComputingConcurrentHashMap.java:355) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.compute(ComputingConcurrentHashMap.java:184) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.getOrCompute(ComputingConcurrentHashMap.java:153) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap.getOrCompute(ComputingConcurrentHashMap.java:69) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:393) [guava-10.0.1.jar:] > ... 25 more > Caused by: javax.naming.NameNotFoundException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:97) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:177) > at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:113) > at javax.naming.InitialContext.lookup(InitialContext.java:396) [rt.jar:1.6.0_22] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.createConnection(JMSTopicsContextImpl.java:98) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.start(JMSTopicsContextImpl.java:123) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:199) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > ... 31 more > 13:13:04,263 SEVERE [org.richfaces.demo.push.MessageProducerRunnable] (MessageProducerThread) javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:397) [guava-10.0.1.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl.createTopic(JMSTopicsContextImpl.java:281) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.TopicsContext.getOrCreateTopic(TopicsContext.java:48) [richfaces-core-api-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.TopicsContext.publish(TopicsContext.java:69) [richfaces-core-api-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.demo.push.TopicsContextMessageProducer.sendMessage(TopicsContextMessageProducer.java:46) [classes:] > at org.richfaces.demo.push.MessageProducerRunnable.run(MessageProducerRunnable.java:57) [classes:] > at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_22] > Caused by: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:207) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:195) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingValueReference.compute(ComputingConcurrentHashMap.java:355) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.compute(ComputingConcurrentHashMap.java:184) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.getOrCompute(ComputingConcurrentHashMap.java:153) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap.getOrCompute(ComputingConcurrentHashMap.java:69) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:393) [guava-10.0.1.jar:] > ... 6 more > Caused by: javax.naming.NameNotFoundException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:97) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:177) > at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:113) > at javax.naming.InitialContext.lookup(InitialContext.java:396) [rt.jar:1.6.0_22] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.createConnection(JMSTopicsContextImpl.java:98) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.start(JMSTopicsContextImpl.java:123) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:199) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > ... 12 more > {code} > {code:title=JBoss AS 7.0.2.Final using default configuration} > 13:16:26,372 WARNING [javax.enterprise.resource.webcontainer.jsf.lifecycle] (http--0%3A0%3A0%3A0%3A0%3A0%3A0%3A0-8080-5) #{pushBean.sendMessage}: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory: javax.faces.FacesException: #{pushBean.sendMessage}: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:118) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > at javax.faces.component.UICommand.broadcast(UICommand.java:315) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:794) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:1259) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:81) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > at org.richfaces.demo.arrangeablemodel.PersistenceLifecycle.execute(PersistenceLifecycle.java:58) [classes:] > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:593) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:67) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:139) [jboss-as-web-7.0.2.Final.jar:7.0.2.Final] > at org.jboss.as.web.NamingValve.invoke(NamingValve.java:57) [jboss-as-web-7.0.2.Final.jar:7.0.2.Final] > at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:49) [jboss-as-jpa-7.0.2.Final.jar:7.0.2.Final] > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:154) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:667) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:952) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at java.lang.Thread.run(Thread.java:662) [:1.6.0_22] > Caused by: javax.faces.el.EvaluationException: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:102) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:102) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > ... 26 more > Caused by: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:397) [guava-10.0.1.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl.createTopic(JMSTopicsContextImpl.java:281) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.TopicsContext.getOrCreateTopic(TopicsContext.java:48) [richfaces-core-api-4.2.0.Final.jar:] > at org.richfaces.application.push.TopicsContext.publish(TopicsContext.java:69) [richfaces-core-api-4.2.0.Final.jar:] > at org.richfaces.application.push.TopicsContext$Proxy$_$$_WeldClientProxy.publish(TopicsContext$Proxy$_$$_WeldClientProxy.java) [richfaces-core-api-4.2.0.Final.jar:] > at org.richfaces.cdi.push.PushCDIExtension$PushObserverMethod.notify(PushCDIExtension.java:144) [richfaces-core-impl-4.2.0.Final.jar:] > at org.jboss.weld.manager.BeanManagerImpl.notifyObservers(BeanManagerImpl.java:635) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:628) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.jboss.weld.event.EventImpl.fire(EventImpl.java:75) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.richfaces.demo.push.PushBean.sendMessage(PushBean.java:65) [classes:] > at org.richfaces.demo.push.PushBean$Proxy$_$$_WeldClientProxy.sendMessage(PushBean$Proxy$_$$_WeldClientProxy.java) [classes:] > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_22] > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_22] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_22] > at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_22] > at org.apache.el.parser.AstValue.invoke(AstValue.java:196) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:276) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.jboss.weld.util.el.ForwardingMethodExpression.invoke(ForwardingMethodExpression.java:43) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.jboss.weld.el.WeldMethodExpression.invoke(WeldMethodExpression.java:56) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at com.sun.faces.facelets.el.TagMethodExpression.invoke(TagMethodExpression.java:105) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:88) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > ... 27 more > Caused by: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:207) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:195) [richfaces-core-impl-4.2.0.Final.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingValueReference.compute(ComputingConcurrentHashMap.java:355) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.compute(ComputingConcurrentHashMap.java:184) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.getOrCompute(ComputingConcurrentHashMap.java:153) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap.getOrCompute(ComputingConcurrentHashMap.java:69) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:393) [guava-10.0.1.jar:] > ... 47 more > Caused by: javax.naming.NameNotFoundException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:87) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:173) > at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:47) > at javax.naming.InitialContext.lookup(InitialContext.java:396) [:1.6.0_22] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.createConnection(JMSTopicsContextImpl.java:98) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.start(JMSTopicsContextImpl.java:123) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:199) [richfaces-core-impl-4.2.0.Final.jar:] > ... 53 more > 13:16:28,949 SEVERE [org.richfaces.demo.push.MessageProducerRunnable] (MessageProducerThread) javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:397) [guava-10.0.1.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl.createTopic(JMSTopicsContextImpl.java:281) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.TopicsContext.getOrCreateTopic(TopicsContext.java:48) [richfaces-core-api-4.2.0.Final.jar:] > at org.richfaces.application.push.TopicsContext.publish(TopicsContext.java:69) [richfaces-core-api-4.2.0.Final.jar:] > at org.richfaces.demo.push.TopicsContextMessageProducer.sendMessage(TopicsContextMessageProducer.java:46) [classes:] > at org.richfaces.demo.push.MessageProducerRunnable.run(MessageProducerRunnable.java:57) [classes:] > at java.lang.Thread.run(Thread.java:662) [:1.6.0_22] > Caused by: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:207) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:195) [richfaces-core-impl-4.2.0.Final.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingValueReference.compute(ComputingConcurrentHashMap.java:355) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.compute(ComputingConcurrentHashMap.java:184) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.getOrCompute(ComputingConcurrentHashMap.java:153) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap.getOrCompute(ComputingConcurrentHashMap.java:69) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:393) [guava-10.0.1.jar:] > ... 6 more > Caused by: javax.naming.NameNotFoundException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:87) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:173) > at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:47) > at javax.naming.InitialContext.lookup(InitialContext.java:396) [:1.6.0_22] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.createConnection(JMSTopicsContextImpl.java:98) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.start(JMSTopicsContextImpl.java:123) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:199) [richfaces-core-impl-4.2.0.Final.jar:] > ... 12 more > {code} > ---- > - Showcase on Openshift Express is working (yeah, there is a really big delay, but it's working). > - Sample in Metamer is also working. > - When the JBoss AS 7.0.2.Final is running with "--server-config standalone-preview.xml", the CDI push demo works correctly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 14 09:28:47 2012 From: jira-events at lists.jboss.org (Karel Piwko (JIRA)) Date: Wed, 14 Mar 2012 09:28:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11983) Showcase: push sample doesn't work In-Reply-To: <1110785355.5085.1329395076292.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <300589682.9039.1331731727580.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12676716#comment-12676716 ] Karel Piwko commented on RF-11983: ---------------------------------- Lukas, can you change default password to be different than username? AS7 does not allow you have password the same as username. > Showcase: push sample doesn't work > ---------------------------------- > > Key: RF-11983 > URL: https://issues.jboss.org/browse/RF-11983 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Environment: JBoos AS 7.0.2.Final (in default configuration) / JBoss AS 7.1.0.Final and Firefox 8.0 > Reporter: Jan Papousek > Assignee: Luk?? Fry? > Fix For: 4.3-Tracking > > > {code:title=JBoss AS 7.1.0.Final} > 13:13:03,702 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/showcase].[Faces Servlet]] (http--127.0.0.1-8080-1) Servlet.service() for servlet Faces Servlet threw exception: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:397) [guava-10.0.1.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl.createTopic(JMSTopicsContextImpl.java:281) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.TopicsContext.getOrCreateTopic(TopicsContext.java:48) [richfaces-core-api-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.SessionImpl.createSubscriptions(SessionImpl.java:182) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.SessionImpl.subscribe(SessionImpl.java:177) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.resource.PushResource.encode(PushResource.java:88) [richfaces-components-ui-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.resource.UserResourceWrapperImpl.encode(UserResourceWrapperImpl.java:188) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.resource.ResourceHandlerImpl.handleResourceRequest(ResourceHandlerImpl.java:222) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:591) [jboss-jsf-api_2.1_spec-2.0.0.Final.jar:2.0.0.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.10.Final.jar:] > at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:62) [weld-core-1.1.5.AS71.Final.jar:2012-02-10 15:31] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.10.Final.jar:] > at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.1.0.Final.jar:7.1.0.Final] > at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:154) [jboss-as-web-7.1.0.Final.jar:7.1.0.Final] > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.10.Final.jar:] > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.10.Final.jar:] > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.10.Final.jar:] > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.10.Final.jar:] > at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_22] > Caused by: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:207) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:195) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingValueReference.compute(ComputingConcurrentHashMap.java:355) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.compute(ComputingConcurrentHashMap.java:184) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.getOrCompute(ComputingConcurrentHashMap.java:153) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap.getOrCompute(ComputingConcurrentHashMap.java:69) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:393) [guava-10.0.1.jar:] > ... 25 more > Caused by: javax.naming.NameNotFoundException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:97) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:177) > at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:113) > at javax.naming.InitialContext.lookup(InitialContext.java:396) [rt.jar:1.6.0_22] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.createConnection(JMSTopicsContextImpl.java:98) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.start(JMSTopicsContextImpl.java:123) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:199) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > ... 31 more > 13:13:04,263 SEVERE [org.richfaces.demo.push.MessageProducerRunnable] (MessageProducerThread) javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:397) [guava-10.0.1.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl.createTopic(JMSTopicsContextImpl.java:281) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.TopicsContext.getOrCreateTopic(TopicsContext.java:48) [richfaces-core-api-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.TopicsContext.publish(TopicsContext.java:69) [richfaces-core-api-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.demo.push.TopicsContextMessageProducer.sendMessage(TopicsContextMessageProducer.java:46) [classes:] > at org.richfaces.demo.push.MessageProducerRunnable.run(MessageProducerRunnable.java:57) [classes:] > at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_22] > Caused by: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:207) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:195) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingValueReference.compute(ComputingConcurrentHashMap.java:355) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.compute(ComputingConcurrentHashMap.java:184) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.getOrCompute(ComputingConcurrentHashMap.java:153) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap.getOrCompute(ComputingConcurrentHashMap.java:69) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:393) [guava-10.0.1.jar:] > ... 6 more > Caused by: javax.naming.NameNotFoundException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:97) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:177) > at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:113) > at javax.naming.InitialContext.lookup(InitialContext.java:396) [rt.jar:1.6.0_22] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.createConnection(JMSTopicsContextImpl.java:98) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.start(JMSTopicsContextImpl.java:123) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:199) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > ... 12 more > {code} > {code:title=JBoss AS 7.0.2.Final using default configuration} > 13:16:26,372 WARNING [javax.enterprise.resource.webcontainer.jsf.lifecycle] (http--0%3A0%3A0%3A0%3A0%3A0%3A0%3A0-8080-5) #{pushBean.sendMessage}: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory: javax.faces.FacesException: #{pushBean.sendMessage}: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:118) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > at javax.faces.component.UICommand.broadcast(UICommand.java:315) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:794) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:1259) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:81) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > at org.richfaces.demo.arrangeablemodel.PersistenceLifecycle.execute(PersistenceLifecycle.java:58) [classes:] > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:593) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:67) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:139) [jboss-as-web-7.0.2.Final.jar:7.0.2.Final] > at org.jboss.as.web.NamingValve.invoke(NamingValve.java:57) [jboss-as-web-7.0.2.Final.jar:7.0.2.Final] > at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:49) [jboss-as-jpa-7.0.2.Final.jar:7.0.2.Final] > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:154) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:667) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:952) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at java.lang.Thread.run(Thread.java:662) [:1.6.0_22] > Caused by: javax.faces.el.EvaluationException: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:102) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:102) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > ... 26 more > Caused by: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:397) [guava-10.0.1.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl.createTopic(JMSTopicsContextImpl.java:281) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.TopicsContext.getOrCreateTopic(TopicsContext.java:48) [richfaces-core-api-4.2.0.Final.jar:] > at org.richfaces.application.push.TopicsContext.publish(TopicsContext.java:69) [richfaces-core-api-4.2.0.Final.jar:] > at org.richfaces.application.push.TopicsContext$Proxy$_$$_WeldClientProxy.publish(TopicsContext$Proxy$_$$_WeldClientProxy.java) [richfaces-core-api-4.2.0.Final.jar:] > at org.richfaces.cdi.push.PushCDIExtension$PushObserverMethod.notify(PushCDIExtension.java:144) [richfaces-core-impl-4.2.0.Final.jar:] > at org.jboss.weld.manager.BeanManagerImpl.notifyObservers(BeanManagerImpl.java:635) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:628) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.jboss.weld.event.EventImpl.fire(EventImpl.java:75) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.richfaces.demo.push.PushBean.sendMessage(PushBean.java:65) [classes:] > at org.richfaces.demo.push.PushBean$Proxy$_$$_WeldClientProxy.sendMessage(PushBean$Proxy$_$$_WeldClientProxy.java) [classes:] > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_22] > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_22] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_22] > at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_22] > at org.apache.el.parser.AstValue.invoke(AstValue.java:196) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:276) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.jboss.weld.util.el.ForwardingMethodExpression.invoke(ForwardingMethodExpression.java:43) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.jboss.weld.el.WeldMethodExpression.invoke(WeldMethodExpression.java:56) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at com.sun.faces.facelets.el.TagMethodExpression.invoke(TagMethodExpression.java:105) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:88) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > ... 27 more > Caused by: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:207) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:195) [richfaces-core-impl-4.2.0.Final.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingValueReference.compute(ComputingConcurrentHashMap.java:355) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.compute(ComputingConcurrentHashMap.java:184) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.getOrCompute(ComputingConcurrentHashMap.java:153) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap.getOrCompute(ComputingConcurrentHashMap.java:69) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:393) [guava-10.0.1.jar:] > ... 47 more > Caused by: javax.naming.NameNotFoundException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:87) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:173) > at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:47) > at javax.naming.InitialContext.lookup(InitialContext.java:396) [:1.6.0_22] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.createConnection(JMSTopicsContextImpl.java:98) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.start(JMSTopicsContextImpl.java:123) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:199) [richfaces-core-impl-4.2.0.Final.jar:] > ... 53 more > 13:16:28,949 SEVERE [org.richfaces.demo.push.MessageProducerRunnable] (MessageProducerThread) javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:397) [guava-10.0.1.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl.createTopic(JMSTopicsContextImpl.java:281) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.TopicsContext.getOrCreateTopic(TopicsContext.java:48) [richfaces-core-api-4.2.0.Final.jar:] > at org.richfaces.application.push.TopicsContext.publish(TopicsContext.java:69) [richfaces-core-api-4.2.0.Final.jar:] > at org.richfaces.demo.push.TopicsContextMessageProducer.sendMessage(TopicsContextMessageProducer.java:46) [classes:] > at org.richfaces.demo.push.MessageProducerRunnable.run(MessageProducerRunnable.java:57) [classes:] > at java.lang.Thread.run(Thread.java:662) [:1.6.0_22] > Caused by: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:207) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:195) [richfaces-core-impl-4.2.0.Final.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingValueReference.compute(ComputingConcurrentHashMap.java:355) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.compute(ComputingConcurrentHashMap.java:184) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.getOrCompute(ComputingConcurrentHashMap.java:153) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap.getOrCompute(ComputingConcurrentHashMap.java:69) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:393) [guava-10.0.1.jar:] > ... 6 more > Caused by: javax.naming.NameNotFoundException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:87) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:173) > at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:47) > at javax.naming.InitialContext.lookup(InitialContext.java:396) [:1.6.0_22] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.createConnection(JMSTopicsContextImpl.java:98) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.start(JMSTopicsContextImpl.java:123) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:199) [richfaces-core-impl-4.2.0.Final.jar:] > ... 12 more > {code} > ---- > - Showcase on Openshift Express is working (yeah, there is a really big delay, but it's working). > - Sample in Metamer is also working. > - When the JBoss AS 7.0.2.Final is running with "--server-config standalone-preview.xml", the CDI push demo works correctly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 14 11:07:47 2012 From: jira-events at lists.jboss.org (Jan Papousek (JIRA)) Date: Wed, 14 Mar 2012 11:07:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12042) Metamer: rich:contextMenu doesn't disappear after clicking out of the menu Message-ID: <1422678186.9420.1331737667612.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Jan Papousek created RF-12042: --------------------------------- Summary: Metamer: rich:contextMenu doesn't disappear after clicking out of the menu Key: RF-12042 URL: https://issues.jboss.org/browse/RF-12042 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-menu Affects Versions: 4.2.0.Final Environment: ?RichFaces 4.2.1-SNAPSHOT ?Metamer 4.2.1-SNAPSHOT ?Mojarra 2.1.5-SNAPSHOT ?JBoss AS 7.1.0.Final ?Java(TM) SE Runtime Environment 1.6.0_31-b04 @ Linux ?Internet Explorer 9.0 @ Win32 Reporter: Jan Papousek -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 14 11:11:47 2012 From: jira-events at lists.jboss.org (Jan Papousek (JIRA)) Date: Wed, 14 Mar 2012 11:11:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12043) Metamer: rich:contextMenu isn't rendered correctly in IE 9 compatibility mode Message-ID: <714594071.9445.1331737907625.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Jan Papousek created RF-12043: --------------------------------- Summary: Metamer: rich:contextMenu isn't rendered correctly in IE 9 compatibility mode Key: RF-12043 URL: https://issues.jboss.org/browse/RF-12043 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-menu Affects Versions: 4.2.0.Final Environment: RichFaces 4.2.1-SNAPSHOT Metamer 4.2.1-SNAPSHOT Mojarra 2.1.5-SNAPSHOT JBoss AS 7.1.0.Final Java(TM) SE Runtime Environment 1.6.0_31-b04 @ Linux Internet Explorer 7.0 @ Win32 (this is IE 9 Compatibility Mode) Reporter: Jan Papousek -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 14 11:13:47 2012 From: jira-events at lists.jboss.org (Jan Papousek (JIRA)) Date: Wed, 14 Mar 2012 11:13:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12043) Metamer: rich:contextMenu isn't rendered correctly in IE 9 compatibility mode In-Reply-To: <714594071.9445.1331737907625.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1846914414.9450.1331738027508.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Papousek updated RF-12043: ------------------------------ Attachment: metamer-ie-9-rich_contextMenu.png > Metamer: rich:contextMenu isn't rendered correctly in IE 9 compatibility mode > ----------------------------------------------------------------------------- > > Key: RF-12043 > URL: https://issues.jboss.org/browse/RF-12043 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-menu > Affects Versions: 4.2.0.Final > Environment: RichFaces 4.2.1-SNAPSHOT > Metamer 4.2.1-SNAPSHOT > Mojarra 2.1.5-SNAPSHOT > JBoss AS 7.1.0.Final > Java(TM) SE Runtime Environment 1.6.0_31-b04 @ Linux > Internet Explorer 7.0 @ Win32 (this is IE 9 Compatibility Mode) > Reporter: Jan Papousek > Labels: IE9 > Attachments: metamer-ie-9-rich_contextMenu.png > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 14 11:13:48 2012 From: jira-events at lists.jboss.org (Jan Papousek (JIRA)) Date: Wed, 14 Mar 2012 11:13:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12043) Metamer: rich:contextMenu isn't rendered correctly in IE 9 compatibility mode In-Reply-To: <714594071.9445.1331737907625.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1506163575.9458.1331738028208.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Papousek updated RF-12043: ------------------------------ Labels: IE9 (was: ) > Metamer: rich:contextMenu isn't rendered correctly in IE 9 compatibility mode > ----------------------------------------------------------------------------- > > Key: RF-12043 > URL: https://issues.jboss.org/browse/RF-12043 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-menu > Affects Versions: 4.2.0.Final > Environment: RichFaces 4.2.1-SNAPSHOT > Metamer 4.2.1-SNAPSHOT > Mojarra 2.1.5-SNAPSHOT > JBoss AS 7.1.0.Final > Java(TM) SE Runtime Environment 1.6.0_31-b04 @ Linux > Internet Explorer 7.0 @ Win32 (this is IE 9 Compatibility Mode) > Reporter: Jan Papousek > Labels: IE9 > Attachments: metamer-ie-9-rich_contextMenu.png > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 14 11:37:47 2012 From: jira-events at lists.jboss.org (Jan Papousek (JIRA)) Date: Wed, 14 Mar 2012 11:37:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12044) Metamer: @preventDefault attribute of rich:hotKey component doesn't work in IE 9 and Google Chrome Message-ID: <283065864.9549.1331739467659.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Jan Papousek created RF-12044: --------------------------------- Summary: Metamer: @preventDefault attribute of rich:hotKey component doesn't work in IE 9 and Google Chrome Key: RF-12044 URL: https://issues.jboss.org/browse/RF-12044 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-misc Affects Versions: 4.1.0.Final Environment: RichFaces 4.2.1-SNAPSHOT Metamer 4.2.1-SNAPSHOT Mojarra 2.1.5-SNAPSHOT JBoss AS 7.1.0.Final Java(TM) SE Runtime Environment 1.6.0_31-b04 @ Linux Chrome 17.0.963.78 @ Linux i686 ?RichFaces 4.2.1-SNAPSHOT ?Metamer 4.2.1-SNAPSHOT ?Mojarra 2.1.5-SNAPSHOT ?JBoss AS 7.1.0.Final ?Java(TM) SE Runtime Environment 1.6.0_31-b04 @ Linux ?Internet Explorer 9.0 @ Win32 Reporter: Jan Papousek It's working correctly in Firefox 10. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 14 11:41:47 2012 From: jira-events at lists.jboss.org (Jan Papousek (JIRA)) Date: Wed, 14 Mar 2012 11:41:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12042) Metamer: rich:contextMenu doesn't disappear after clicking out of the menu in IE9 and Google Chrome In-Reply-To: <1422678186.9420.1331737667612.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <631444617.9566.1331739707745.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Papousek updated RF-12042: ------------------------------ Summary: Metamer: rich:contextMenu doesn't disappear after clicking out of the menu in IE9 and Google Chrome (was: Metamer: rich:contextMenu doesn't disappear after clicking out of the menu) Labels: Chrome IE9 (was: IE9) > Metamer: rich:contextMenu doesn't disappear after clicking out of the menu in IE9 and Google Chrome > --------------------------------------------------------------------------------------------------- > > Key: RF-12042 > URL: https://issues.jboss.org/browse/RF-12042 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-menu > Affects Versions: 4.2.0.Final > Environment: ?RichFaces 4.2.1-SNAPSHOT > ?Metamer 4.2.1-SNAPSHOT > ?Mojarra 2.1.5-SNAPSHOT > ?JBoss AS 7.1.0.Final > ?Java(TM) SE Runtime Environment 1.6.0_31-b04 @ Linux > ?Internet Explorer 9.0 @ Win32 > Reporter: Jan Papousek > Labels: Chrome, IE9 > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 14 11:41:47 2012 From: jira-events at lists.jboss.org (Jan Papousek (JIRA)) Date: Wed, 14 Mar 2012 11:41:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12042) Metamer: rich:contextMenu doesn't disappear after clicking out of the menu in IE9 and Google Chrome In-Reply-To: <1422678186.9420.1331737667612.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1569903893.9568.1331739707817.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Papousek updated RF-12042: ------------------------------ Environment: ?RichFaces 4.2.1-SNAPSHOT ?Metamer 4.2.1-SNAPSHOT ?Mojarra 2.1.5-SNAPSHOT ?JBoss AS 7.1.0.Final ?Java(TM) SE Runtime Environment 1.6.0_31-b04 @ Linux ?Internet Explorer 9.0 @ Win32 RichFaces 4.2.1-SNAPSHOT Metamer 4.2.1-SNAPSHOT Mojarra 2.1.5-SNAPSHOT JBoss AS 7.1.0.Final Java(TM) SE Runtime Environment 1.6.0_31-b04 @ Linux Chrome 17.0.963.78 @ Linux i686 was: ?RichFaces 4.2.1-SNAPSHOT ?Metamer 4.2.1-SNAPSHOT ?Mojarra 2.1.5-SNAPSHOT ?JBoss AS 7.1.0.Final ?Java(TM) SE Runtime Environment 1.6.0_31-b04 @ Linux ?Internet Explorer 9.0 @ Win32 > Metamer: rich:contextMenu doesn't disappear after clicking out of the menu in IE9 and Google Chrome > --------------------------------------------------------------------------------------------------- > > Key: RF-12042 > URL: https://issues.jboss.org/browse/RF-12042 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-menu > Affects Versions: 4.2.0.Final > Environment: ?RichFaces 4.2.1-SNAPSHOT > ?Metamer 4.2.1-SNAPSHOT > ?Mojarra 2.1.5-SNAPSHOT > ?JBoss AS 7.1.0.Final > ?Java(TM) SE Runtime Environment 1.6.0_31-b04 @ Linux > ?Internet Explorer 9.0 @ Win32 > RichFaces 4.2.1-SNAPSHOT > Metamer 4.2.1-SNAPSHOT > Mojarra 2.1.5-SNAPSHOT > JBoss AS 7.1.0.Final > Java(TM) SE Runtime Environment 1.6.0_31-b04 @ Linux > Chrome 17.0.963.78 @ Linux i686 > Reporter: Jan Papousek > Labels: Chrome, IE9 > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 14 11:43:48 2012 From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA)) Date: Wed, 14 Mar 2012 11:43:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-10383) Showcase: add samples for listeners In-Reply-To: <1782521794.5980.1296495639551.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <2071819358.9574.1331739828918.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-10383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavol Pitonak reassigned RF-10383: ---------------------------------- Assignee: Brian Leathem (was: Ilya Shaikovsky) > Showcase: add samples for listeners > ----------------------------------- > > Key: RF-10383 > URL: https://issues.jboss.org/browse/RF-10383 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: examples, showcase > Affects Versions: 4.0.0.Milestone5 > Reporter: Pavol Pitonak > Assignee: Brian Leathem > Fix For: 4.Future > > > Add samples for following tags so that community knows they exist and how to use them: > * rich:itemChangeListener > * rich:panelToggleListener > * rich:treeSelectionChangeListener > * rich:treeToggleListener -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 14 11:45:47 2012 From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA)) Date: Wed, 14 Mar 2012 11:45:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-7932) photoalbum: tree with albums collapses after drag&drop In-Reply-To: <2103165271.1254293089386.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com> Message-ID: <1046369587.9578.1331739947970.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-7932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavol Pitonak resolved RF-7932. ------------------------------- Resolution: Won't Fix Left for community to resolve. > photoalbum: tree with albums collapses after drag&drop > ------------------------------------------------------ > > Key: RF-7932 > URL: https://issues.jboss.org/browse/RF-7932 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: examples > Affects Versions: 3.3.2.GA > Environment: JBoss AS 5.1, IE 7, FF 3.5 > Reporter: Pavol Pitonak > Priority: Minor > Fix For: 3.Future > > > When the user expands all albums and then d&d a picture from one album to another one, picture is moved and the tree is collapsed -- usability problem. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 14 11:45:50 2012 From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA)) Date: Wed, 14 Mar 2012 11:45:50 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-8347) Demo: Tree with D&D -- not rendered correctly In-Reply-To: <850614813.1265211081831.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com> Message-ID: <906597916.9583.1331739950362.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-8347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavol Pitonak resolved RF-8347. ------------------------------- Resolution: Won't Fix Left for community to resolve. > Demo: Tree with D&D -- not rendered correctly > --------------------------------------------- > > Key: RF-8347 > URL: https://issues.jboss.org/browse/RF-8347 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: examples > Affects Versions: 3.3.3.CR1 > Environment: Linux, FF 3.5, Chrome 5, JSF 2 > Reporter: Pavol Pitonak > Fix For: 3.Future > > Attachments: tree-dnd.png, tree-laguna.png, tree-ruby.png > > > 1. open richfaces-demo > 2. navigate to the page with tree using D&D (3rd tab) > result: tree is rendered wrong, see attached screenshot > 3. D&D one picture to the trash (in Chrome) > result: tree disappears -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 14 11:47:47 2012 From: jira-events at lists.jboss.org (Jan Papousek (JIRA)) Date: Wed, 14 Mar 2012 11:47:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12044) Metamer: @preventDefault attribute of rich:hotKey component doesn't work in IE 9 and Google Chrome In-Reply-To: <283065864.9549.1331739467659.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1337752252.9586.1331740067435.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Papousek updated RF-12044: ------------------------------ Affects Version/s: 4.2.0.Final (was: 4.1.0.Final) > Metamer: @preventDefault attribute of rich:hotKey component doesn't work in IE 9 and Google Chrome > -------------------------------------------------------------------------------------------------- > > Key: RF-12044 > URL: https://issues.jboss.org/browse/RF-12044 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-misc > Affects Versions: 4.2.0.Final > Environment: RichFaces 4.2.1-SNAPSHOT > Metamer 4.2.1-SNAPSHOT > Mojarra 2.1.5-SNAPSHOT > JBoss AS 7.1.0.Final > Java(TM) SE Runtime Environment 1.6.0_31-b04 @ Linux > Chrome 17.0.963.78 @ Linux i686 > ?RichFaces 4.2.1-SNAPSHOT > ?Metamer 4.2.1-SNAPSHOT > ?Mojarra 2.1.5-SNAPSHOT > ?JBoss AS 7.1.0.Final > ?Java(TM) SE Runtime Environment 1.6.0_31-b04 @ Linux > ?Internet Explorer 9.0 @ Win32 > Reporter: Jan Papousek > Labels: Chrome, IE9 > > It's working correctly in Firefox 10. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 14 11:49:47 2012 From: jira-events at lists.jboss.org (Jan Papousek (JIRA)) Date: Wed, 14 Mar 2012 11:49:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12045) Metamer: focusing of rich:inplaceInput behaves in Google Chrome differently than in other browsers Message-ID: <645136326.9592.1331740187653.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Jan Papousek created RF-12045: --------------------------------- Summary: Metamer: focusing of rich:inplaceInput behaves in Google Chrome differently than in other browsers Key: RF-12045 URL: https://issues.jboss.org/browse/RF-12045 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-input Affects Versions: 4.2.0.Final Environment: RichFaces 4.2.1-SNAPSHOT Metamer 4.2.1-SNAPSHOT Mojarra 2.1.5-SNAPSHOT JBoss AS 7.1.0.Final Java(TM) SE Runtime Environment 1.6.0_31-b04 @ Linux Chrome 17.0.963.78 @ Linux i686 Reporter: Jan Papousek Priority: Optional After clicking on rich:inplaceInput in Firefox, the cursor is placed in the beginning of the input and nothing is selected. Doing the same in Google Chrome - the text in the input is selected. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 14 11:49:48 2012 From: jira-events at lists.jboss.org (Jan Papousek (JIRA)) Date: Wed, 14 Mar 2012 11:49:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12045) Metamer: focusing of rich:inplaceInput behaves in Google Chrome differently than in other browsers In-Reply-To: <645136326.9592.1331740187653.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1522831974.9606.1331740188840.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Papousek updated RF-12045: ------------------------------ Description: After clicking on rich:inplaceInput in Firefox, the cursor is placed in the beginning of the input and nothing is selected. Doing the same in Google Chrome - the text in the input is selected. EDIT: It happens only after the first click on the input. was:After clicking on rich:inplaceInput in Firefox, the cursor is placed in the beginning of the input and nothing is selected. Doing the same in Google Chrome - the text in the input is selected. > Metamer: focusing of rich:inplaceInput behaves in Google Chrome differently than in other browsers > -------------------------------------------------------------------------------------------------- > > Key: RF-12045 > URL: https://issues.jboss.org/browse/RF-12045 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.2.0.Final > Environment: RichFaces 4.2.1-SNAPSHOT > Metamer 4.2.1-SNAPSHOT > Mojarra 2.1.5-SNAPSHOT > JBoss AS 7.1.0.Final > Java(TM) SE Runtime Environment 1.6.0_31-b04 @ Linux > Chrome 17.0.963.78 @ Linux i686 > Reporter: Jan Papousek > Priority: Optional > Labels: Chrome > > After clicking on rich:inplaceInput in Firefox, the cursor is placed in the beginning of the input and nothing is selected. Doing the same in Google Chrome - the text in the input is selected. > EDIT: It happens only after the first click on the input. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 14 12:59:49 2012 From: jira-events at lists.jboss.org (Jean ANDRE (JIRA)) Date: Wed, 14 Mar 2012 12:59:49 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11763) javascript error : item is undefined on nested tabPanel with switchType='ajax' In-Reply-To: <984864127.56421.1322674601141.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <824988840.9824.1331744389009.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean ANDRE updated RF-11763: ---------------------------- Attachment: RF-11763_ScreenShot_Undefined.png Hello RichFaces Team, Actually we're looking for the bug by producing the smaller application we can. Here is a screen shot of what we have found but we still do not understand why there is an undefined element in the object. We have also produce a workbench with the same functionalities, program structure and complexity and this workbench does not have this kind of error. So, the bug is particular to the application. See you soon. > javascript error : item is undefined on nested tabPanel with switchType='ajax' > ------------------------------------------------------------------------------ > > Key: RF-11763 > URL: https://issues.jboss.org/browse/RF-11763 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.1.0.CR1 > Environment: Websphere 8 - RAD 8 - JSF Mojorra 2.1.4 - Spring 3.0.6 Final - Use @Inject @Named @SessionScoped as annotations - Firefox 7.0.1 - Windows 7 (6.1 sp1) - AspectJ 1.6.12 / AJDT > Reporter: Jean ANDRE > Priority: Blocker > Fix For: 4.Future > > Attachments: RF-11763_ScreenShot.png, RF-11763_ScreenShot_Undefined.png, screenshot-1.jpg > > > See also RF-11750 for the context. > Briefly, we have nested tabPanel - The firs tabPanel is made of static and dynamic tabPanel. One tabPanel contains the search form. When the user performs a search and for each search we open a new tab that contains the result list. When the user click on an item, we update the tab with the detailed information. > The detailed information is made of 6 tabs - There are like a subtabs from the parent tabs. When we set the switchType to 'client' the tab performs well. But as we want that the same tab serves as form to edit and view the detailed information, we want to refresh the tab to display the inputText instead of the outputText. This is the edit mode. > Then, we need to refresh the tab and we decided to pass in ajax switchType for theses subTab. Owener, switching to the 'ajax' triggers a javascript error that blocks the UI. None tab is selectable, user cannot switch from a tab to another tab. Moreover we failed to refresh the tab but the reason is still unknown. > Javascript error is : > {code} > item is undefined - [Stopper sur une erreur] if (!item.disabled && item.getName() === itemName) { > toggle...chfaces (ligne 363) > http://localhost:12000/crm/javax.faces.resource/togglePanel.js.jsf?ln=org.richfaces > {code} > The involved code is (where >>>> is): > {code} > /** > * @private > * */ > __getItemIndex : function (itemName) { > var item; > for (var i = 0; i < this.items.length; i++) { > item = this.items[i]; > >>>>>> if (!item.disabled && item.getName() === itemName) { > return i; > } > } > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 14 13:38:48 2012 From: jira-events at lists.jboss.org (Juraj Huska (JIRA)) Date: Wed, 14 Mar 2012 13:38:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11965) showcase - a4j:push - error thrown after creating topic for pushCdi In-Reply-To: <1869426390.30466.1328703648739.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1584126285.9963.1331746728338.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj Huska reopened RF-11965: ------------------------------ I can reproduce this issue again. The behavior is that during first deployment on JBoss AS 7.1.0.Final this exception is thrown, next deployments go fine, it is occurring again when using freshly unzipped AS distribution. > showcase - a4j:push - error thrown after creating topic for pushCdi > ------------------------------------------------------------------- > > Key: RF-11965 > URL: https://issues.jboss.org/browse/RF-11965 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll, showcase > Affects Versions: 4.2.0.Final > Environment: container: JBoss AS 7.1.0.CR1b > Reporter: Juraj Huska > Assignee: Luk?? Fry? > Priority: Minor > Labels: waiting_on_user > > When deploying showcase 4.2.0.CR1 then after pushCdi topic created an error is thrown: > {code} > 18:13:42,211 INFO [org.richfaces.demo.push.JMSInitializer] (MSC service thread 1-2) initializing > 18:13:42,219 INFO [org.richfaces.demo.push.JMSInitializer] (MSC service thread 1-2) AS7MessagingProviderManagement initialized > 18:13:42,219 INFO [org.richfaces.demo.push.JMSInitializer] (MSC service thread 1-2) creating topic pushJms > 18:13:42,761 INFO [org.richfaces.demo.push.JMSInitializer] (MSC service thread 1-2) creating topic pushTopicsContext > 18:13:42,802 INFO [org.richfaces.demo.push.JMSInitializer] (MSC service thread 1-2) creating topic pushCdi > 18:13:42,972 SEVERE [org.richfaces.demo.push.MessageProducerRunnable] (MessageProducerThread) javax.faces.FacesException: topic/pushTopicsContext -- service jboss.naming.context.java.topic.$ > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:397) [guava-10.0.1.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl.createTopic(JMSTopicsContextImpl.java:281) [richfaces-core-impl-4.2.0.CR1.jar:] > at org.richfaces.application.push.TopicsContext.getOrCreateTopic(TopicsContext.java:48) [richfaces-core-api-4.2.0.CR1.jar:] > at org.richfaces.application.push.TopicsContext.publish(TopicsContext.java:69) [richfaces-core-api-4.2.0.CR1.jar:] > at org.richfaces.demo.push.TopicsContextMessageProducer.sendMessage(TopicsContextMessageProducer.java:46) [classes:] > at org.richfaces.demo.push.MessageProducerRunnable.run(MessageProducerRunnable.java:57) [classes:] > at java.lang.Thread.run(Thread.java:662) [:1.6.0_22] > Caused by: javax.faces.FacesException: topic/pushTopicsContext -- service jboss.naming.context.java.topic.pushTopicsContext > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:207) [richfaces-core-impl-4.2.0.CR1.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:195) [richfaces-core-impl-4.2.0.CR1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingValueReference.compute(ComputingConcurrentHashMap.java:355) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.compute(ComputingConcurrentHashMap.java:184) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.getOrCompute(ComputingConcurrentHashMap.java:153) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap.getOrCompute(ComputingConcurrentHashMap.java:69) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:393) [guava-10.0.1.jar:] > ... 6 more > Caused by: javax.naming.NameNotFoundException: topic/pushTopicsContext -- service jboss.naming.context.java.topic.pushTopicsContext > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:92) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:177) > at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:87) > at javax.naming.InitialContext.lookup(InitialContext.java:396) [:1.6.0_22] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.lookupTopic(JMSTopicsContextImpl.java:94) [richfaces-core-impl-4.2.0-20120130.140419-26.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.start(JMSTopicsContextImpl.java:125) [richfaces-core-impl-4.2.0-20120130.140419-26.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:199) [richfaces-core-impl-4.2.0-20120130.140419-26.jar:] > ... 12 more > {code} > The functionality of push demos is fine, just the tests are not passing on Hudson, which I have to investigate whether it is caused by this one. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 14 13:38:51 2012 From: jira-events at lists.jboss.org (Juraj Huska (JIRA)) Date: Wed, 14 Mar 2012 13:38:51 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11965) showcase - a4j:push - error thrown after creating topic for pushCdi In-Reply-To: <1869426390.30466.1328703648739.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1329106632.9989.1331746731191.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj Huska updated RF-11965: ----------------------------- Affects Version/s: 4.2.0.Final (was: 4.2.0.CR1) > showcase - a4j:push - error thrown after creating topic for pushCdi > ------------------------------------------------------------------- > > Key: RF-11965 > URL: https://issues.jboss.org/browse/RF-11965 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll, showcase > Affects Versions: 4.2.0.Final > Environment: container: JBoss AS 7.1.0.CR1b > Reporter: Juraj Huska > Assignee: Luk?? Fry? > Priority: Minor > Labels: waiting_on_user > > When deploying showcase 4.2.0.CR1 then after pushCdi topic created an error is thrown: > {code} > 18:13:42,211 INFO [org.richfaces.demo.push.JMSInitializer] (MSC service thread 1-2) initializing > 18:13:42,219 INFO [org.richfaces.demo.push.JMSInitializer] (MSC service thread 1-2) AS7MessagingProviderManagement initialized > 18:13:42,219 INFO [org.richfaces.demo.push.JMSInitializer] (MSC service thread 1-2) creating topic pushJms > 18:13:42,761 INFO [org.richfaces.demo.push.JMSInitializer] (MSC service thread 1-2) creating topic pushTopicsContext > 18:13:42,802 INFO [org.richfaces.demo.push.JMSInitializer] (MSC service thread 1-2) creating topic pushCdi > 18:13:42,972 SEVERE [org.richfaces.demo.push.MessageProducerRunnable] (MessageProducerThread) javax.faces.FacesException: topic/pushTopicsContext -- service jboss.naming.context.java.topic.$ > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:397) [guava-10.0.1.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl.createTopic(JMSTopicsContextImpl.java:281) [richfaces-core-impl-4.2.0.CR1.jar:] > at org.richfaces.application.push.TopicsContext.getOrCreateTopic(TopicsContext.java:48) [richfaces-core-api-4.2.0.CR1.jar:] > at org.richfaces.application.push.TopicsContext.publish(TopicsContext.java:69) [richfaces-core-api-4.2.0.CR1.jar:] > at org.richfaces.demo.push.TopicsContextMessageProducer.sendMessage(TopicsContextMessageProducer.java:46) [classes:] > at org.richfaces.demo.push.MessageProducerRunnable.run(MessageProducerRunnable.java:57) [classes:] > at java.lang.Thread.run(Thread.java:662) [:1.6.0_22] > Caused by: javax.faces.FacesException: topic/pushTopicsContext -- service jboss.naming.context.java.topic.pushTopicsContext > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:207) [richfaces-core-impl-4.2.0.CR1.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:195) [richfaces-core-impl-4.2.0.CR1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingValueReference.compute(ComputingConcurrentHashMap.java:355) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.compute(ComputingConcurrentHashMap.java:184) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.getOrCompute(ComputingConcurrentHashMap.java:153) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap.getOrCompute(ComputingConcurrentHashMap.java:69) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:393) [guava-10.0.1.jar:] > ... 6 more > Caused by: javax.naming.NameNotFoundException: topic/pushTopicsContext -- service jboss.naming.context.java.topic.pushTopicsContext > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:92) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:177) > at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:87) > at javax.naming.InitialContext.lookup(InitialContext.java:396) [:1.6.0_22] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.lookupTopic(JMSTopicsContextImpl.java:94) [richfaces-core-impl-4.2.0-20120130.140419-26.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.start(JMSTopicsContextImpl.java:125) [richfaces-core-impl-4.2.0-20120130.140419-26.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:199) [richfaces-core-impl-4.2.0-20120130.140419-26.jar:] > ... 12 more > {code} > The functionality of push demos is fine, just the tests are not passing on Hudson, which I have to investigate whether it is caused by this one. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 14 13:40:47 2012 From: jira-events at lists.jboss.org (Juraj Huska (JIRA)) Date: Wed, 14 Mar 2012 13:40:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11965) showcase - a4j:push - error thrown after creating topic for pushCdi In-Reply-To: <1869426390.30466.1328703648739.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1498065529.9995.1331746848001.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12676852#comment-12676852 ] Juraj Huska commented on RF-11965: ---------------------------------- It is the same for showcase built from WFK 2.0 sources against enterprise repositories and running on EAP6. > showcase - a4j:push - error thrown after creating topic for pushCdi > ------------------------------------------------------------------- > > Key: RF-11965 > URL: https://issues.jboss.org/browse/RF-11965 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll, showcase > Affects Versions: 4.2.0.Final > Environment: container: JBoss AS 7.1.0.CR1b > Reporter: Juraj Huska > Assignee: Luk?? Fry? > Priority: Minor > Labels: waiting_on_user > > When deploying showcase 4.2.0.CR1 then after pushCdi topic created an error is thrown: > {code} > 18:13:42,211 INFO [org.richfaces.demo.push.JMSInitializer] (MSC service thread 1-2) initializing > 18:13:42,219 INFO [org.richfaces.demo.push.JMSInitializer] (MSC service thread 1-2) AS7MessagingProviderManagement initialized > 18:13:42,219 INFO [org.richfaces.demo.push.JMSInitializer] (MSC service thread 1-2) creating topic pushJms > 18:13:42,761 INFO [org.richfaces.demo.push.JMSInitializer] (MSC service thread 1-2) creating topic pushTopicsContext > 18:13:42,802 INFO [org.richfaces.demo.push.JMSInitializer] (MSC service thread 1-2) creating topic pushCdi > 18:13:42,972 SEVERE [org.richfaces.demo.push.MessageProducerRunnable] (MessageProducerThread) javax.faces.FacesException: topic/pushTopicsContext -- service jboss.naming.context.java.topic.$ > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:397) [guava-10.0.1.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl.createTopic(JMSTopicsContextImpl.java:281) [richfaces-core-impl-4.2.0.CR1.jar:] > at org.richfaces.application.push.TopicsContext.getOrCreateTopic(TopicsContext.java:48) [richfaces-core-api-4.2.0.CR1.jar:] > at org.richfaces.application.push.TopicsContext.publish(TopicsContext.java:69) [richfaces-core-api-4.2.0.CR1.jar:] > at org.richfaces.demo.push.TopicsContextMessageProducer.sendMessage(TopicsContextMessageProducer.java:46) [classes:] > at org.richfaces.demo.push.MessageProducerRunnable.run(MessageProducerRunnable.java:57) [classes:] > at java.lang.Thread.run(Thread.java:662) [:1.6.0_22] > Caused by: javax.faces.FacesException: topic/pushTopicsContext -- service jboss.naming.context.java.topic.pushTopicsContext > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:207) [richfaces-core-impl-4.2.0.CR1.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:195) [richfaces-core-impl-4.2.0.CR1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingValueReference.compute(ComputingConcurrentHashMap.java:355) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.compute(ComputingConcurrentHashMap.java:184) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.getOrCompute(ComputingConcurrentHashMap.java:153) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap.getOrCompute(ComputingConcurrentHashMap.java:69) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:393) [guava-10.0.1.jar:] > ... 6 more > Caused by: javax.naming.NameNotFoundException: topic/pushTopicsContext -- service jboss.naming.context.java.topic.pushTopicsContext > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:92) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:177) > at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:87) > at javax.naming.InitialContext.lookup(InitialContext.java:396) [:1.6.0_22] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.lookupTopic(JMSTopicsContextImpl.java:94) [richfaces-core-impl-4.2.0-20120130.140419-26.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.start(JMSTopicsContextImpl.java:125) [richfaces-core-impl-4.2.0-20120130.140419-26.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:199) [richfaces-core-impl-4.2.0-20120130.140419-26.jar:] > ... 12 more > {code} > The functionality of push demos is fine, just the tests are not passing on Hudson, which I have to investigate whether it is caused by this one. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 14 14:25:47 2012 From: jira-events at lists.jboss.org (user user (JIRA)) Date: Wed, 14 Mar 2012 14:25:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11842) Support for macrosubstitutions in the contextMenu In-Reply-To: <846735312.26265.1324444329320.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <730848724.10070.1331749547772.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12676865#comment-12676865 ] user user commented on RF-11842: -------------------------------- This is very important feature, e.g. to have dynamic contextMenu for a table, and it is critical for RF 3-4 migration. Is is possible to make this fix available in sandbox component and/or next RF version? > Support for macrosubstitutions in the contextMenu > ------------------------------------------------- > > Key: RF-11842 > URL: https://issues.jboss.org/browse/RF-11842 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-menu > Affects Versions: 4.2.0.CR1 > Reporter: Brian Leathem > Fix For: 4.3-Tracking > > > The RichFaces 3 contextMenu supported _macrosubstitutions_, whereby a single instance of the contextMenu will be created and among multiple components. This RichFaces 4 contextMenu should support this feature. > See the [RichFaces 3 showcase|http://livedemo.exadel.com/richfaces-demo/richfaces/contextMenu.jsf] for an example of this behaviour. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 14 15:10:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 14 Mar 2012 15:10:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12029) AbstractTogglePanel should extend UIRepeat, instead of UIOutput In-Reply-To: <1430073926.75557.1331161056577.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <47637563.10164.1331752247407.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12676875#comment-12676875 ] Brian Leathem commented on RF-12029: ------------------------------------ Consider the dynamicly rendered tabs in the facelet: {code} Validation failed:#{facesContext.validationFailed}

Dynamic tab panel

#{person.name} {code} Switching tabs in ajax modes takes two clicks - the tab does not change until the 2nd click. The response on the first click: {code:title="Response after the first click on tab 1 (formatted for clarity)} Validation failed:false]]> {code} the response on the second click: {code:title="Response after the second click on tab 1 (formatted for clarity)} Validation failed:false]]>
Ayn Rand
]]> RichFaces.$('form:tabPanel').onCompleteHandler('Ayn Rand');; {code} Notice how the response content only reflects the tab change in the response of the 2nd click Note: For both the first and second response, the executeIds in the ExtendedPartialViewContext is: {code} form:tabPanel:1:tab form:tabPanel {code} > AbstractTogglePanel should extend UIRepeat, instead of UIOutput > --------------------------------------------------------------- > > Key: RF-12029 > URL: https://issues.jboss.org/browse/RF-12029 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-output > Reporter: Brian Leathem > Assignee: Bernard Labno > > Valid uses exist for dynamically generating rich:tab, rich:togglePanelItem, rich:accordionItem. Current techniques for supporting this use case involve using c:forEach, which is a problem since c: tags are processed too early to nicely support dynamic use cases. > One idea to support this use case, is to have AbstractTogglePanel extend UIRepeat, instead of UIOutput to better dynamic child components. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 14 16:24:47 2012 From: jira-events at lists.jboss.org (Gerald Turner (JIRA)) Date: Wed, 14 Mar 2012 16:24:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12046) JSR303 ConstraintViolation propertyPath support for graphValidator Message-ID: <2053412287.10319.1331756687690.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Gerald Turner created RF-12046: ---------------------------------- Summary: JSR303 ConstraintViolation propertyPath support for graphValidator Key: RF-12046 URL: https://issues.jboss.org/browse/RF-12046 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Components: component-validators Affects Versions: 4.2.0.Final Reporter: Gerald Turner Priority: Optional In JSR303 ? 4.2 ConstraintViolation, there is the following note: "From rootBean and propertyPath, it is possible to rebuild the context of the failure" Perhaps it would be possible for graphValidator to map ConstraintViolation propertyPath to ValueExpressions, then iterate child EditableValueHolder components and assign FacesMessages to clientIds of these components where it finds a match, otherwise fallback on the current behavior of using the clientId of the graphValidator itself (perhaps even adding an the option to use a null clientId for global messages instead). A more thorough example of this use-case is here: http://stackoverflow.com/questions/5639088/cross-field-validation-with-inline-messaging-in-jsf-with-jsr-303 Comments at stackoverflow suggest MyFaces ExtVal Bean Validation can do the trick, however I went down that road, their framework ignores ConstraintViolation propertyPath as well (see: http://old.nabble.com/Re%3A-ExtVal-BV-question-to33455513.html) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 14 16:24:47 2012 From: jira-events at lists.jboss.org (Jean ANDRE (JIRA)) Date: Wed, 14 Mar 2012 16:24:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11763) javascript error : item is undefined on nested tabPanel with switchType='ajax' In-Reply-To: <984864127.56421.1322674601141.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1057499702.10324.1331756687929.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean ANDRE updated RF-11763: ---------------------------- Attachment: RF-11763_ScreenShot_malformedXML.png This screen show an malformedXML - An object can not be found: "During update: tabbedForm:j_idt13:j_idt17 not found" > javascript error : item is undefined on nested tabPanel with switchType='ajax' > ------------------------------------------------------------------------------ > > Key: RF-11763 > URL: https://issues.jboss.org/browse/RF-11763 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.1.0.CR1 > Environment: Websphere 8 - RAD 8 - JSF Mojorra 2.1.4 - Spring 3.0.6 Final - Use @Inject @Named @SessionScoped as annotations - Firefox 7.0.1 - Windows 7 (6.1 sp1) - AspectJ 1.6.12 / AJDT > Reporter: Jean ANDRE > Priority: Blocker > Fix For: 4.Future > > Attachments: RF-11763_ScreenShot.png, RF-11763_ScreenShot_malformedXML.png, RF-11763_ScreenShot_Undefined.png, screenshot-1.jpg > > > See also RF-11750 for the context. > Briefly, we have nested tabPanel - The firs tabPanel is made of static and dynamic tabPanel. One tabPanel contains the search form. When the user performs a search and for each search we open a new tab that contains the result list. When the user click on an item, we update the tab with the detailed information. > The detailed information is made of 6 tabs - There are like a subtabs from the parent tabs. When we set the switchType to 'client' the tab performs well. But as we want that the same tab serves as form to edit and view the detailed information, we want to refresh the tab to display the inputText instead of the outputText. This is the edit mode. > Then, we need to refresh the tab and we decided to pass in ajax switchType for theses subTab. Owener, switching to the 'ajax' triggers a javascript error that blocks the UI. None tab is selectable, user cannot switch from a tab to another tab. Moreover we failed to refresh the tab but the reason is still unknown. > Javascript error is : > {code} > item is undefined - [Stopper sur une erreur] if (!item.disabled && item.getName() === itemName) { > toggle...chfaces (ligne 363) > http://localhost:12000/crm/javax.faces.resource/togglePanel.js.jsf?ln=org.richfaces > {code} > The involved code is (where >>>> is): > {code} > /** > * @private > * */ > __getItemIndex : function (itemName) { > var item; > for (var i = 0; i < this.items.length; i++) { > item = this.items[i]; > >>>>>> if (!item.disabled && item.getName() === itemName) { > return i; > } > } > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 14 16:26:47 2012 From: jira-events at lists.jboss.org (Jean ANDRE (JIRA)) Date: Wed, 14 Mar 2012 16:26:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11763) javascript error : item is undefined on nested tabPanel with switchType='ajax' In-Reply-To: <984864127.56421.1322674601141.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <454569790.10328.1331756807339.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12676890#comment-12676890 ] Jean ANDRE commented on RF-11763: --------------------------------- The screen shows we got an error because an object id is not found. The id is the update id. "During update: tabbedForm:j_idt13:j_idt17 not found" - See the xml partial response > javascript error : item is undefined on nested tabPanel with switchType='ajax' > ------------------------------------------------------------------------------ > > Key: RF-11763 > URL: https://issues.jboss.org/browse/RF-11763 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.1.0.CR1 > Environment: Websphere 8 - RAD 8 - JSF Mojorra 2.1.4 - Spring 3.0.6 Final - Use @Inject @Named @SessionScoped as annotations - Firefox 7.0.1 - Windows 7 (6.1 sp1) - AspectJ 1.6.12 / AJDT > Reporter: Jean ANDRE > Priority: Blocker > Fix For: 4.Future > > Attachments: RF-11763_ScreenShot.png, RF-11763_ScreenShot_malformedXML.png, RF-11763_ScreenShot_Undefined.png, screenshot-1.jpg > > > See also RF-11750 for the context. > Briefly, we have nested tabPanel - The firs tabPanel is made of static and dynamic tabPanel. One tabPanel contains the search form. When the user performs a search and for each search we open a new tab that contains the result list. When the user click on an item, we update the tab with the detailed information. > The detailed information is made of 6 tabs - There are like a subtabs from the parent tabs. When we set the switchType to 'client' the tab performs well. But as we want that the same tab serves as form to edit and view the detailed information, we want to refresh the tab to display the inputText instead of the outputText. This is the edit mode. > Then, we need to refresh the tab and we decided to pass in ajax switchType for theses subTab. Owener, switching to the 'ajax' triggers a javascript error that blocks the UI. None tab is selectable, user cannot switch from a tab to another tab. Moreover we failed to refresh the tab but the reason is still unknown. > Javascript error is : > {code} > item is undefined - [Stopper sur une erreur] if (!item.disabled && item.getName() === itemName) { > toggle...chfaces (ligne 363) > http://localhost:12000/crm/javax.faces.resource/togglePanel.js.jsf?ln=org.richfaces > {code} > The involved code is (where >>>> is): > {code} > /** > * @private > * */ > __getItemIndex : function (itemName) { > var item; > for (var i = 0; i < this.items.length; i++) { > item = this.items[i]; > >>>>>> if (!item.disabled && item.getName() === itemName) { > return i; > } > } > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 14 16:30:47 2012 From: jira-events at lists.jboss.org (Jean ANDRE (JIRA)) Date: Wed, 14 Mar 2012 16:30:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11763) javascript error : item is undefined on nested tabPanel with switchType='ajax' In-Reply-To: <984864127.56421.1322674601141.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <261927020.10332.1331757047588.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean ANDRE updated RF-11763: ---------------------------- Attachment: RF-11763_ScreenShot_malformedXML.xml The xml partial response. > javascript error : item is undefined on nested tabPanel with switchType='ajax' > ------------------------------------------------------------------------------ > > Key: RF-11763 > URL: https://issues.jboss.org/browse/RF-11763 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.1.0.CR1 > Environment: Websphere 8 - RAD 8 - JSF Mojorra 2.1.4 - Spring 3.0.6 Final - Use @Inject @Named @SessionScoped as annotations - Firefox 7.0.1 - Windows 7 (6.1 sp1) - AspectJ 1.6.12 / AJDT > Reporter: Jean ANDRE > Priority: Blocker > Fix For: 4.Future > > Attachments: RF-11763_ScreenShot.png, RF-11763_ScreenShot_malformedXML.png, RF-11763_ScreenShot_malformedXML.xml, RF-11763_ScreenShot_Undefined.png, screenshot-1.jpg > > > See also RF-11750 for the context. > Briefly, we have nested tabPanel - The firs tabPanel is made of static and dynamic tabPanel. One tabPanel contains the search form. When the user performs a search and for each search we open a new tab that contains the result list. When the user click on an item, we update the tab with the detailed information. > The detailed information is made of 6 tabs - There are like a subtabs from the parent tabs. When we set the switchType to 'client' the tab performs well. But as we want that the same tab serves as form to edit and view the detailed information, we want to refresh the tab to display the inputText instead of the outputText. This is the edit mode. > Then, we need to refresh the tab and we decided to pass in ajax switchType for theses subTab. Owener, switching to the 'ajax' triggers a javascript error that blocks the UI. None tab is selectable, user cannot switch from a tab to another tab. Moreover we failed to refresh the tab but the reason is still unknown. > Javascript error is : > {code} > item is undefined - [Stopper sur une erreur] if (!item.disabled && item.getName() === itemName) { > toggle...chfaces (ligne 363) > http://localhost:12000/crm/javax.faces.resource/togglePanel.js.jsf?ln=org.richfaces > {code} > The involved code is (where >>>> is): > {code} > /** > * @private > * */ > __getItemIndex : function (itemName) { > var item; > for (var i = 0; i < this.items.length; i++) { > item = this.items[i]; > >>>>>> if (!item.disabled && item.getName() === itemName) { > return i; > } > } > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 14 16:34:47 2012 From: jira-events at lists.jboss.org (Gerald Turner (JIRA)) Date: Wed, 14 Mar 2012 16:34:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12047) Add "global" attribute to graphValidator Message-ID: <1530502986.10336.1331757287488.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Gerald Turner created RF-12047: ---------------------------------- Summary: Add "global" attribute to graphValidator Key: RF-12047 URL: https://issues.jboss.org/browse/RF-12047 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Components: component-validators Affects Versions: 4.2.0.Final Reporter: Gerald Turner Priority: Trivial graphValidator appends FacesMessages to the FacesContext with clientId set to the clientId of the graphValidator component, naturally, however I have a use-case for not assigning a clientId to those FacesMessages at all (null, global messages). The following example exhibits how graphValidator currently works: What I'm asking for is the following: (Conversely I could wishlist PrimeFaces to add a 'for' attribute to their 'messages' component, something like 'for="@global gv"', so no harm in closing this report ;-) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 14 16:49:47 2012 From: jira-events at lists.jboss.org (Jean ANDRE (JIRA)) Date: Wed, 14 Mar 2012 16:49:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11763) javascript error : item is undefined on nested tabPanel with switchType='ajax' In-Reply-To: <984864127.56421.1322674601141.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <261313891.10353.1331758187387.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12676893#comment-12676893 ] Jean ANDRE commented on RF-11763: --------------------------------- It is clear that there is an undefined object which is bring back to the list of items but I cannot answer why. So, here is the smallest application that we can offer you to help in debugging the case. You can probably also use the this application for the bug RF-11985. Thank you very much. *Note 1:* I've reduce the application to only 4 xhmtl file. The index page, the search, the list and the detailed view. All the xhtml have been reduced to the minimum content. *Note 2:* It is clear that there is problem of resource downloading. To see the case, use an a4j:command button inside the file searchClient.xhtml and a4j:commandLink into listClient instead of JSF tag. I've left the attribute render for easy change. I've also removed the lib from the WEB-INF/lib for a smaller zip. Lbraries are: - annotations-4.2.0.Final - commons-lang-2.4 - commons-logging-1.1.1 - cssparser-0.9.6 - guava-11.0.1 - hibernate-validator-4.2.0.Final - javax.faces.jar - log4j-1.2.16 - org.springframework.asm-3.0.6.RELEASE - org.springframework.beans-3.0.6.RELEASE - org.springframework.context-3.0.6.RELEASE - org.springframework.core-3.0.6.RELEASE - org.springframework.expression-3.0.6.RELEASE - org.springframework.web-3.0.6.RELEASE - richfaces-components-api-4.2.0.Final - richfaces-components-ui-4.2.0.Final - richfaces-core-api-4.2.0.Final - richfaces-core-impl-4.2.0.Final - sac-1.3 - slf4j-api-1.6.1 - slf4j-log4j12-1.6.1 > javascript error : item is undefined on nested tabPanel with switchType='ajax' > ------------------------------------------------------------------------------ > > Key: RF-11763 > URL: https://issues.jboss.org/browse/RF-11763 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.1.0.CR1 > Environment: Websphere 8 - RAD 8 - JSF Mojorra 2.1.4 - Spring 3.0.6 Final - Use @Inject @Named @SessionScoped as annotations - Firefox 7.0.1 - Windows 7 (6.1 sp1) - AspectJ 1.6.12 / AJDT > Reporter: Jean ANDRE > Priority: Blocker > Fix For: 4.Future > > Attachments: RF-11763_ScreenShot.png, RF-11763_ScreenShot_malformedXML.png, RF-11763_ScreenShot_malformedXML.xml, RF-11763_ScreenShot_Undefined.png, screenshot-1.jpg > > > See also RF-11750 for the context. > Briefly, we have nested tabPanel - The firs tabPanel is made of static and dynamic tabPanel. One tabPanel contains the search form. When the user performs a search and for each search we open a new tab that contains the result list. When the user click on an item, we update the tab with the detailed information. > The detailed information is made of 6 tabs - There are like a subtabs from the parent tabs. When we set the switchType to 'client' the tab performs well. But as we want that the same tab serves as form to edit and view the detailed information, we want to refresh the tab to display the inputText instead of the outputText. This is the edit mode. > Then, we need to refresh the tab and we decided to pass in ajax switchType for theses subTab. Owener, switching to the 'ajax' triggers a javascript error that blocks the UI. None tab is selectable, user cannot switch from a tab to another tab. Moreover we failed to refresh the tab but the reason is still unknown. > Javascript error is : > {code} > item is undefined - [Stopper sur une erreur] if (!item.disabled && item.getName() === itemName) { > toggle...chfaces (ligne 363) > http://localhost:12000/crm/javax.faces.resource/togglePanel.js.jsf?ln=org.richfaces > {code} > The involved code is (where >>>> is): > {code} > /** > * @private > * */ > __getItemIndex : function (itemName) { > var item; > for (var i = 0; i < this.items.length; i++) { > item = this.items[i]; > >>>>>> if (!item.disabled && item.getName() === itemName) { > return i; > } > } > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 14 16:53:47 2012 From: jira-events at lists.jboss.org (Jean ANDRE (JIRA)) Date: Wed, 14 Mar 2012 16:53:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11763) javascript error : item is undefined on nested tabPanel with switchType='ajax' In-Reply-To: <984864127.56421.1322674601141.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1924127389.10369.1331758427664.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12676893#comment-12676893 ] Jean ANDRE edited comment on RF-11763 at 3/14/12 4:51 PM: ---------------------------------------------------------- It is clear that there is an undefined object which is bring back to the list of items but I cannot answer why. So, here is the smallest application that we can offer you to help in debugging the case. You can probably also use the this application for the bug RF-11985. Thank you very much. *Note 1:* I've reduce the application to only 4 xhmtl file. The index page, the search, the list and the detailed view. All the xhtml have been reduced to the minimum content. *Note 2:* It is clear that there is problem of resource downloading. To see the case, use an a4j:command button inside the file searchClient.xhtml and a4j:commandLink into listClient instead of JSF tag. I've left the attribute render for easy change. I've also removed the lib from the WEB-INF/lib for a smaller zip. Lbraries are: - annotations-4.2.0.Final - commons-lang-2.4 - commons-logging-1.1.1 - cssparser-0.9.6 - guava-11.0.1 - hibernate-validator-4.2.0.Final - javax.faces.jar - log4j-1.2.16 - org.springframework.asm-3.0.6.RELEASE - org.springframework.beans-3.0.6.RELEASE - org.springframework.context-3.0.6.RELEASE - org.springframework.core-3.0.6.RELEASE - org.springframework.expression-3.0.6.RELEASE - org.springframework.web-3.0.6.RELEASE - richfaces-components-api-4.2.0.Final - richfaces-components-ui-4.2.0.Final - richfaces-core-api-4.2.0.Final - richfaces-core-impl-4.2.0.Final - sac-1.3 - slf4j-api-1.6.1 - slf4j-log4j12-1.6.1 Please, let me know if your are able to reproduce the bug with the application sent. Sincerely, was (Author: jorelia64): It is clear that there is an undefined object which is bring back to the list of items but I cannot answer why. So, here is the smallest application that we can offer you to help in debugging the case. You can probably also use the this application for the bug RF-11985. Thank you very much. *Note 1:* I've reduce the application to only 4 xhmtl file. The index page, the search, the list and the detailed view. All the xhtml have been reduced to the minimum content. *Note 2:* It is clear that there is problem of resource downloading. To see the case, use an a4j:command button inside the file searchClient.xhtml and a4j:commandLink into listClient instead of JSF tag. I've left the attribute render for easy change. I've also removed the lib from the WEB-INF/lib for a smaller zip. Lbraries are: - annotations-4.2.0.Final - commons-lang-2.4 - commons-logging-1.1.1 - cssparser-0.9.6 - guava-11.0.1 - hibernate-validator-4.2.0.Final - javax.faces.jar - log4j-1.2.16 - org.springframework.asm-3.0.6.RELEASE - org.springframework.beans-3.0.6.RELEASE - org.springframework.context-3.0.6.RELEASE - org.springframework.core-3.0.6.RELEASE - org.springframework.expression-3.0.6.RELEASE - org.springframework.web-3.0.6.RELEASE - richfaces-components-api-4.2.0.Final - richfaces-components-ui-4.2.0.Final - richfaces-core-api-4.2.0.Final - richfaces-core-impl-4.2.0.Final - sac-1.3 - slf4j-api-1.6.1 - slf4j-log4j12-1.6.1 > javascript error : item is undefined on nested tabPanel with switchType='ajax' > ------------------------------------------------------------------------------ > > Key: RF-11763 > URL: https://issues.jboss.org/browse/RF-11763 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.1.0.CR1 > Environment: Websphere 8 - RAD 8 - JSF Mojorra 2.1.4 - Spring 3.0.6 Final - Use @Inject @Named @SessionScoped as annotations - Firefox 7.0.1 - Windows 7 (6.1 sp1) - AspectJ 1.6.12 / AJDT > Reporter: Jean ANDRE > Priority: Blocker > Fix For: 4.Future > > Attachments: RF-11763_ScreenShot.png, RF-11763_ScreenShot_malformedXML.png, RF-11763_ScreenShot_malformedXML.xml, RF-11763_ScreenShot_Undefined.png, screenshot-1.jpg > > > See also RF-11750 for the context. > Briefly, we have nested tabPanel - The firs tabPanel is made of static and dynamic tabPanel. One tabPanel contains the search form. When the user performs a search and for each search we open a new tab that contains the result list. When the user click on an item, we update the tab with the detailed information. > The detailed information is made of 6 tabs - There are like a subtabs from the parent tabs. When we set the switchType to 'client' the tab performs well. But as we want that the same tab serves as form to edit and view the detailed information, we want to refresh the tab to display the inputText instead of the outputText. This is the edit mode. > Then, we need to refresh the tab and we decided to pass in ajax switchType for theses subTab. Owener, switching to the 'ajax' triggers a javascript error that blocks the UI. None tab is selectable, user cannot switch from a tab to another tab. Moreover we failed to refresh the tab but the reason is still unknown. > Javascript error is : > {code} > item is undefined - [Stopper sur une erreur] if (!item.disabled && item.getName() === itemName) { > toggle...chfaces (ligne 363) > http://localhost:12000/crm/javax.faces.resource/togglePanel.js.jsf?ln=org.richfaces > {code} > The involved code is (where >>>> is): > {code} > /** > * @private > * */ > __getItemIndex : function (itemName) { > var item; > for (var i = 0; i < this.items.length; i++) { > item = this.items[i]; > >>>>>> if (!item.disabled && item.getName() === itemName) { > return i; > } > } > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 14 16:59:47 2012 From: jira-events at lists.jboss.org (Jean ANDRE (JIRA)) Date: Wed, 14 Mar 2012 16:59:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11763) javascript error : item is undefined on nested tabPanel with switchType='ajax' In-Reply-To: <984864127.56421.1322674601141.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <564073256.10383.1331758787414.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean ANDRE updated RF-11763: ---------------------------- Attachment: RF-11763Web.zip Let me know if you need more material, more explaination or if we doing something wrong. The following file is a manually ziped files. Libraries have been removed from the WEB-INF/lib. This a WebSphere project, then I did not removed specific files in case you want to test the appl with the community edition of WAS. > javascript error : item is undefined on nested tabPanel with switchType='ajax' > ------------------------------------------------------------------------------ > > Key: RF-11763 > URL: https://issues.jboss.org/browse/RF-11763 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.1.0.CR1 > Environment: Websphere 8 - RAD 8 - JSF Mojorra 2.1.4 - Spring 3.0.6 Final - Use @Inject @Named @SessionScoped as annotations - Firefox 7.0.1 - Windows 7 (6.1 sp1) - AspectJ 1.6.12 / AJDT > Reporter: Jean ANDRE > Priority: Blocker > Fix For: 4.Future > > Attachments: RF-11763Web.zip, RF-11763_ScreenShot.png, RF-11763_ScreenShot_malformedXML.png, RF-11763_ScreenShot_malformedXML.xml, RF-11763_ScreenShot_Undefined.png, screenshot-1.jpg > > > See also RF-11750 for the context. > Briefly, we have nested tabPanel - The firs tabPanel is made of static and dynamic tabPanel. One tabPanel contains the search form. When the user performs a search and for each search we open a new tab that contains the result list. When the user click on an item, we update the tab with the detailed information. > The detailed information is made of 6 tabs - There are like a subtabs from the parent tabs. When we set the switchType to 'client' the tab performs well. But as we want that the same tab serves as form to edit and view the detailed information, we want to refresh the tab to display the inputText instead of the outputText. This is the edit mode. > Then, we need to refresh the tab and we decided to pass in ajax switchType for theses subTab. Owener, switching to the 'ajax' triggers a javascript error that blocks the UI. None tab is selectable, user cannot switch from a tab to another tab. Moreover we failed to refresh the tab but the reason is still unknown. > Javascript error is : > {code} > item is undefined - [Stopper sur une erreur] if (!item.disabled && item.getName() === itemName) { > toggle...chfaces (ligne 363) > http://localhost:12000/crm/javax.faces.resource/togglePanel.js.jsf?ln=org.richfaces > {code} > The involved code is (where >>>> is): > {code} > /** > * @private > * */ > __getItemIndex : function (itemName) { > var item; > for (var i = 0; i < this.items.length; i++) { > item = this.items[i]; > >>>>>> if (!item.disabled && item.getName() === itemName) { > return i; > } > } > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 14 17:02:47 2012 From: jira-events at lists.jboss.org (Jean ANDRE (JIRA)) Date: Wed, 14 Mar 2012 17:02:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11763) javascript error : item is undefined on nested tabPanel with switchType='ajax' In-Reply-To: <984864127.56421.1322674601141.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1977239731.10388.1331758967537.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12676893#comment-12676893 ] Jean ANDRE edited comment on RF-11763 at 3/14/12 5:01 PM: ---------------------------------------------------------- It is clear that there is an undefined object which is bring back to the list of items but I cannot answer why. So, here is the smallest application that we can offer you to help in debugging the case. You can probably also use the this application for the bug RF-11985. Thank you very much. *Note 1:* I've reduce the application to only 4 xhmtl files. The index page, the search, the list and the detailed view. All the xhtml have been reduced to their minimum content. *Note 2:* It is clear that there is a problem of resources downloading. To see the case, use an a4j:command button inside the file searchClient.xhtml and a4j:commandLink into listClient instead of JSF tag. I've left the attribute render for easy change. I've also removed the lib from the WEB-INF/lib for a smaller zip. Lbraries are: - annotations-4.2.0.Final - commons-lang-2.4 - commons-logging-1.1.1 - cssparser-0.9.6 - guava-11.0.1 - hibernate-validator-4.2.0.Final - javax.faces.jar - log4j-1.2.16 - org.springframework.asm-3.0.6.RELEASE - org.springframework.beans-3.0.6.RELEASE - org.springframework.context-3.0.6.RELEASE - org.springframework.core-3.0.6.RELEASE - org.springframework.expression-3.0.6.RELEASE - org.springframework.web-3.0.6.RELEASE - richfaces-components-api-4.2.0.Final - richfaces-components-ui-4.2.0.Final - richfaces-core-api-4.2.0.Final - richfaces-core-impl-4.2.0.Final - sac-1.3 - slf4j-api-1.6.1 - slf4j-log4j12-1.6.1 Please, let me know if your are able to reproduce the bug with the application sent. Sincerely, was (Author: jorelia64): It is clear that there is an undefined object which is bring back to the list of items but I cannot answer why. So, here is the smallest application that we can offer you to help in debugging the case. You can probably also use the this application for the bug RF-11985. Thank you very much. *Note 1:* I've reduce the application to only 4 xhmtl file. The index page, the search, the list and the detailed view. All the xhtml have been reduced to the minimum content. *Note 2:* It is clear that there is problem of resource downloading. To see the case, use an a4j:command button inside the file searchClient.xhtml and a4j:commandLink into listClient instead of JSF tag. I've left the attribute render for easy change. I've also removed the lib from the WEB-INF/lib for a smaller zip. Lbraries are: - annotations-4.2.0.Final - commons-lang-2.4 - commons-logging-1.1.1 - cssparser-0.9.6 - guava-11.0.1 - hibernate-validator-4.2.0.Final - javax.faces.jar - log4j-1.2.16 - org.springframework.asm-3.0.6.RELEASE - org.springframework.beans-3.0.6.RELEASE - org.springframework.context-3.0.6.RELEASE - org.springframework.core-3.0.6.RELEASE - org.springframework.expression-3.0.6.RELEASE - org.springframework.web-3.0.6.RELEASE - richfaces-components-api-4.2.0.Final - richfaces-components-ui-4.2.0.Final - richfaces-core-api-4.2.0.Final - richfaces-core-impl-4.2.0.Final - sac-1.3 - slf4j-api-1.6.1 - slf4j-log4j12-1.6.1 Please, let me know if your are able to reproduce the bug with the application sent. Sincerely, > javascript error : item is undefined on nested tabPanel with switchType='ajax' > ------------------------------------------------------------------------------ > > Key: RF-11763 > URL: https://issues.jboss.org/browse/RF-11763 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.1.0.CR1 > Environment: Websphere 8 - RAD 8 - JSF Mojorra 2.1.4 - Spring 3.0.6 Final - Use @Inject @Named @SessionScoped as annotations - Firefox 7.0.1 - Windows 7 (6.1 sp1) - AspectJ 1.6.12 / AJDT > Reporter: Jean ANDRE > Priority: Blocker > Fix For: 4.Future > > Attachments: RF-11763Web.zip, RF-11763_ScreenShot.png, RF-11763_ScreenShot_malformedXML.png, RF-11763_ScreenShot_malformedXML.xml, RF-11763_ScreenShot_Undefined.png, screenshot-1.jpg > > > See also RF-11750 for the context. > Briefly, we have nested tabPanel - The firs tabPanel is made of static and dynamic tabPanel. One tabPanel contains the search form. When the user performs a search and for each search we open a new tab that contains the result list. When the user click on an item, we update the tab with the detailed information. > The detailed information is made of 6 tabs - There are like a subtabs from the parent tabs. When we set the switchType to 'client' the tab performs well. But as we want that the same tab serves as form to edit and view the detailed information, we want to refresh the tab to display the inputText instead of the outputText. This is the edit mode. > Then, we need to refresh the tab and we decided to pass in ajax switchType for theses subTab. Owener, switching to the 'ajax' triggers a javascript error that blocks the UI. None tab is selectable, user cannot switch from a tab to another tab. Moreover we failed to refresh the tab but the reason is still unknown. > Javascript error is : > {code} > item is undefined - [Stopper sur une erreur] if (!item.disabled && item.getName() === itemName) { > toggle...chfaces (ligne 363) > http://localhost:12000/crm/javax.faces.resource/togglePanel.js.jsf?ln=org.richfaces > {code} > The involved code is (where >>>> is): > {code} > /** > * @private > * */ > __getItemIndex : function (itemName) { > var item; > for (var i = 0; i < this.items.length; i++) { > item = this.items[i]; > >>>>>> if (!item.disabled && item.getName() === itemName) { > return i; > } > } > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 14 17:04:47 2012 From: jira-events at lists.jboss.org (Jean ANDRE (JIRA)) Date: Wed, 14 Mar 2012 17:04:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11763) javascript error : item is undefined on nested tabPanel with switchType='ajax' In-Reply-To: <984864127.56421.1322674601141.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <882419460.10398.1331759087993.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12676900#comment-12676900 ] Jean ANDRE edited comment on RF-11763 at 3/14/12 5:03 PM: ---------------------------------------------------------- Let me know if you need more material, more explanation or if we're doing something wrong. The following file is a manually zipped files. Libraries have been removed from the WEB-INF/lib. This a WebSphere project, then I did not removed specific files in case you want to test the appl with the community edition of WAS. was (Author: jorelia64): Let me know if you need more material, more explaination or if we doing something wrong. The following file is a manually ziped files. Libraries have been removed from the WEB-INF/lib. This a WebSphere project, then I did not removed specific files in case you want to test the appl with the community edition of WAS. > javascript error : item is undefined on nested tabPanel with switchType='ajax' > ------------------------------------------------------------------------------ > > Key: RF-11763 > URL: https://issues.jboss.org/browse/RF-11763 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.1.0.CR1 > Environment: Websphere 8 - RAD 8 - JSF Mojorra 2.1.4 - Spring 3.0.6 Final - Use @Inject @Named @SessionScoped as annotations - Firefox 7.0.1 - Windows 7 (6.1 sp1) - AspectJ 1.6.12 / AJDT > Reporter: Jean ANDRE > Priority: Blocker > Fix For: 4.Future > > Attachments: RF-11763Web.zip, RF-11763_ScreenShot.png, RF-11763_ScreenShot_malformedXML.png, RF-11763_ScreenShot_malformedXML.xml, RF-11763_ScreenShot_Undefined.png, screenshot-1.jpg > > > See also RF-11750 for the context. > Briefly, we have nested tabPanel - The firs tabPanel is made of static and dynamic tabPanel. One tabPanel contains the search form. When the user performs a search and for each search we open a new tab that contains the result list. When the user click on an item, we update the tab with the detailed information. > The detailed information is made of 6 tabs - There are like a subtabs from the parent tabs. When we set the switchType to 'client' the tab performs well. But as we want that the same tab serves as form to edit and view the detailed information, we want to refresh the tab to display the inputText instead of the outputText. This is the edit mode. > Then, we need to refresh the tab and we decided to pass in ajax switchType for theses subTab. Owener, switching to the 'ajax' triggers a javascript error that blocks the UI. None tab is selectable, user cannot switch from a tab to another tab. Moreover we failed to refresh the tab but the reason is still unknown. > Javascript error is : > {code} > item is undefined - [Stopper sur une erreur] if (!item.disabled && item.getName() === itemName) { > toggle...chfaces (ligne 363) > http://localhost:12000/crm/javax.faces.resource/togglePanel.js.jsf?ln=org.richfaces > {code} > The involved code is (where >>>> is): > {code} > /** > * @private > * */ > __getItemIndex : function (itemName) { > var item; > for (var i = 0; i < this.items.length; i++) { > item = this.items[i]; > >>>>>> if (!item.disabled && item.getName() === itemName) { > return i; > } > } > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 14 17:28:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 14 Mar 2012 17:28:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11884) Multiple Errors with IE8/9 In-Reply-To: <1562607854.56099.1326530722497.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1611688222.10437.1331760527583.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? reassigned RF-11884: ------------------------------- Assignee: Luk?? Fry? > Multiple Errors with IE8/9 > -------------------------- > > Key: RF-11884 > URL: https://issues.jboss.org/browse/RF-11884 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes, component-tables, component-tree > Environment: Windows 7 64, Tomcat 7.0.23, Mojarra 2.1.3, IE8/9 (all errors), Chrome 16.09 (one problem), PrimesFaces 2.2.1 (ChartGraphics only, problems still persist when PF is removed) > Reporter: Friedhelm Kuehn > Assignee: Luk?? Fry? > Priority: Critical > Fix For: 4.2.1.CR1 > > Attachments: ProgramVariable_Table.xhtml, Richfaces_4.1_Problems.pdf, Richfaces_4.1_Problems_Konfiguration.pdf, Test.war > > > Problem 1: Shaded TabbedPane Tabs, not changing color when tabbing. Big spacing area below tabs (height about 20 px, should be 2px). > Problem 2: Content of not-popped-up Popup-Panel is not visible, but an area is claimed on screen. > Problem 3: with icon: Icon is surrounded by dark border > Problem 4: No Horzontal-Scroller in ExtendDatatable (with Chrome also). > Problem 5: Use of IconCollapsed/..Expanded creates double Icons in TreeNode > Problem 6: Javascript Error in ExtendedDataTable.js > Biggest Problem: We have to deliver our application in a few weeks. Support for IE8/9 is hard customer requirement. > I have a made a documentation for each problem, but don't find a way to attach a PDF to this issue - ?? > Please help ! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 14 17:28:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 14 Mar 2012 17:28:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11971) rich:menuItem onclick return value ignored In-Reply-To: <900498702.34279.1328801928475.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1264977989.10441.1331760527755.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? reassigned RF-11971: ------------------------------- Assignee: Luk?? Fry? > rich:menuItem onclick return value ignored > ------------------------------------------ > > Key: RF-11971 > URL: https://issues.jboss.org/browse/RF-11971 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-menu > Affects Versions: 4.2.0.Final > Environment: Chrome / glassfish 3.1.1 / mojarra 2.1.6 > Reporter: Brendan Healey > Assignee: Luk?? Fry? > Fix For: 4.2.1.CR1 > > > My expectation was that using rich:menuItem onclick="if(!confirm('#{msgs.playerConfirmDelete}')) return false;" > (and selecting cancel) would prevent any action routines being called, as is common > with components such as h:commandButton. As it stands the return value is ignored and > processing continues with return true or return false. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 14 17:47:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 14 Mar 2012 17:47:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12013) Deadlock in push component In-Reply-To: <654291399.48838.1330441536575.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <740520718.10457.1331761667283.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12676911#comment-12676911 ] Luk?? Fry? commented on RF-12013: --------------------------------- Hi Stian, thanks for the report, there is really the deadlock caused by initiating shutdown (destroying push SessionImpl) in time when session tries to post messages. > Deadlock in push component > -------------------------- > > Key: RF-12013 > URL: https://issues.jboss.org/browse/RF-12013 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Affects Versions: 4.2.0.Final > Reporter: Stian Thorgersen > Assignee: Luk?? Fry? > > Deadlocked threads in the push component prevented server from stopping. Not sure whether or not this happened when I initiated shutdown or if these where hanging around for a while. > Relevant output from jstack: > {code} > Found one Java-level deadlock: > ============================= > "push-publish-thread-1": > waiting to lock monitor 0x0000000042650238 (object 0x00000000e5ed5a50, a org.richfaces.application.push.impl.RequestImpl), > which is held by "Atmosphere-AsyncWrite-0" > "Atmosphere-AsyncWrite-0": > waiting to lock monitor 0x00000000427d9ec0 (object 0x00000000e5ed59a0, a org.richfaces.application.push.impl.SessionImpl), > which is held by "push-publish-thread-1" > Java stack information for the threads listed above: > =================================================== > "push-publish-thread-1": > at org.richfaces.application.push.impl.RequestImpl.postMessages(RequestImpl.java:85) > - waiting to lock <0x00000000e5ed5a50> (a org.richfaces.application.push.impl.RequestImpl) > at org.richfaces.application.push.impl.SessionImpl.push(SessionImpl.java:237) > - locked <0x00000000e5ed59a0> (a org.richfaces.application.push.impl.SessionImpl) > at org.richfaces.application.push.impl.TopicImpl$TopicContext.publishMessages(TopicImpl.java:88) > at org.richfaces.application.push.impl.TopicImpl$PublishTask.run(TopicImpl.java:53) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:662) > "Atmosphere-AsyncWrite-0": > at org.richfaces.application.push.impl.SessionImpl.disconnect(SessionImpl.java:117) > - waiting to lock <0x00000000e5ed59a0> (a org.richfaces.application.push.impl.SessionImpl) > at org.richfaces.application.push.impl.RequestImpl.disconnect(RequestImpl.java:107) > at org.richfaces.application.push.impl.RequestImpl.onResume(RequestImpl.java:115) > at org.atmosphere.cpr.AtmosphereResourceImpl.onResume(AtmosphereResourceImpl.java:651) > at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:600) > at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:584) > at org.atmosphere.cpr.AtmosphereResourceImpl.resume(AtmosphereResourceImpl.java:185) > - locked <0x00000000e5ee3380> (a org.atmosphere.cpr.AtmosphereResourceEventImpl) > at org.richfaces.application.push.impl.RequestImpl.onBroadcast(RequestImpl.java:129) > - locked <0x00000000e5ed5a50> (a org.richfaces.application.push.impl.RequestImpl) > at org.atmosphere.cpr.AtmosphereResourceImpl.onBroadcast(AtmosphereResourceImpl.java:663) > at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:608) > at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:584) > at org.atmosphere.cpr.DefaultBroadcaster.executeAsyncWrite(DefaultBroadcaster.java:713) > at org.atmosphere.cpr.DefaultBroadcaster$3.run(DefaultBroadcaster.java:747) > - locked <0x00000000e5ed5a88> (a org.atmosphere.cpr.AtmosphereResourceImpl) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:662) > Found 1 deadlock. > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 14 17:49:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 14 Mar 2012 17:49:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12013) Deadlock in push component In-Reply-To: <654291399.48838.1330441536575.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1305408086.10461.1331761787476.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated RF-12013: ---------------------------- Fix Version/s: 4.2.1.CR1 > Deadlock in push component > -------------------------- > > Key: RF-12013 > URL: https://issues.jboss.org/browse/RF-12013 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Affects Versions: 4.2.0.Final > Reporter: Stian Thorgersen > Assignee: Luk?? Fry? > Fix For: 4.2.1.CR1 > > > Deadlocked threads in the push component prevented server from stopping. Not sure whether or not this happened when I initiated shutdown or if these where hanging around for a while. > Relevant output from jstack: > {code} > Found one Java-level deadlock: > ============================= > "push-publish-thread-1": > waiting to lock monitor 0x0000000042650238 (object 0x00000000e5ed5a50, a org.richfaces.application.push.impl.RequestImpl), > which is held by "Atmosphere-AsyncWrite-0" > "Atmosphere-AsyncWrite-0": > waiting to lock monitor 0x00000000427d9ec0 (object 0x00000000e5ed59a0, a org.richfaces.application.push.impl.SessionImpl), > which is held by "push-publish-thread-1" > Java stack information for the threads listed above: > =================================================== > "push-publish-thread-1": > at org.richfaces.application.push.impl.RequestImpl.postMessages(RequestImpl.java:85) > - waiting to lock <0x00000000e5ed5a50> (a org.richfaces.application.push.impl.RequestImpl) > at org.richfaces.application.push.impl.SessionImpl.push(SessionImpl.java:237) > - locked <0x00000000e5ed59a0> (a org.richfaces.application.push.impl.SessionImpl) > at org.richfaces.application.push.impl.TopicImpl$TopicContext.publishMessages(TopicImpl.java:88) > at org.richfaces.application.push.impl.TopicImpl$PublishTask.run(TopicImpl.java:53) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:662) > "Atmosphere-AsyncWrite-0": > at org.richfaces.application.push.impl.SessionImpl.disconnect(SessionImpl.java:117) > - waiting to lock <0x00000000e5ed59a0> (a org.richfaces.application.push.impl.SessionImpl) > at org.richfaces.application.push.impl.RequestImpl.disconnect(RequestImpl.java:107) > at org.richfaces.application.push.impl.RequestImpl.onResume(RequestImpl.java:115) > at org.atmosphere.cpr.AtmosphereResourceImpl.onResume(AtmosphereResourceImpl.java:651) > at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:600) > at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:584) > at org.atmosphere.cpr.AtmosphereResourceImpl.resume(AtmosphereResourceImpl.java:185) > - locked <0x00000000e5ee3380> (a org.atmosphere.cpr.AtmosphereResourceEventImpl) > at org.richfaces.application.push.impl.RequestImpl.onBroadcast(RequestImpl.java:129) > - locked <0x00000000e5ed5a50> (a org.richfaces.application.push.impl.RequestImpl) > at org.atmosphere.cpr.AtmosphereResourceImpl.onBroadcast(AtmosphereResourceImpl.java:663) > at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:608) > at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:584) > at org.atmosphere.cpr.DefaultBroadcaster.executeAsyncWrite(DefaultBroadcaster.java:713) > at org.atmosphere.cpr.DefaultBroadcaster$3.run(DefaultBroadcaster.java:747) > - locked <0x00000000e5ed5a88> (a org.atmosphere.cpr.AtmosphereResourceImpl) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:662) > Found 1 deadlock. > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 14 18:17:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 14 Mar 2012 18:17:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12048) Change the password for JMS guest connection Message-ID: <1881089286.10479.1331763467304.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Luk?? Fry? created RF-12048: ------------------------------- Summary: Change the password for JMS guest connection Key: RF-12048 URL: https://issues.jboss.org/browse/RF-12048 Project: RichFaces Issue Type: Enhancement Security Level: Public (Everyone can see) Components: component-push/poll Affects Versions: 4.2.0.Final Reporter: Luk?? Fry? [Originally request|https://issues.jboss.org/browse/RF-11983?focusedCommentId=12676716&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12676716] by Karel Piwko: AS7 doesn't allow to add user with same name and password, that's why having {{guest:guest}} credentials [1] does not make sense. We can change the credentials to {{guest:password}} - I have verified the actual content does not have any influence on functionality on AS7.0 and will improve usability on AS7.1. [1] https://github.com/richfaces/showcase/blob/4.2.0.20120215-Final/src/main/webapp-jbas7/WEB-INF/web.xml#L78 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 14 18:17:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 14 Mar 2012 18:17:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11983) Showcase: push sample doesn't work In-Reply-To: <1110785355.5085.1329395076292.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <121801375.10480.1331763467493.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12676915#comment-12676915 ] Luk?? Fry? commented on RF-11983: --------------------------------- Hi Karel, it does make sense, I have opened RF-12048. > Showcase: push sample doesn't work > ---------------------------------- > > Key: RF-11983 > URL: https://issues.jboss.org/browse/RF-11983 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Environment: JBoos AS 7.0.2.Final (in default configuration) / JBoss AS 7.1.0.Final and Firefox 8.0 > Reporter: Jan Papousek > Assignee: Luk?? Fry? > Fix For: 4.3-Tracking > > > {code:title=JBoss AS 7.1.0.Final} > 13:13:03,702 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/showcase].[Faces Servlet]] (http--127.0.0.1-8080-1) Servlet.service() for servlet Faces Servlet threw exception: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:397) [guava-10.0.1.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl.createTopic(JMSTopicsContextImpl.java:281) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.TopicsContext.getOrCreateTopic(TopicsContext.java:48) [richfaces-core-api-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.SessionImpl.createSubscriptions(SessionImpl.java:182) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.SessionImpl.subscribe(SessionImpl.java:177) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.resource.PushResource.encode(PushResource.java:88) [richfaces-components-ui-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.resource.UserResourceWrapperImpl.encode(UserResourceWrapperImpl.java:188) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.resource.ResourceHandlerImpl.handleResourceRequest(ResourceHandlerImpl.java:222) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:591) [jboss-jsf-api_2.1_spec-2.0.0.Final.jar:2.0.0.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.10.Final.jar:] > at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:62) [weld-core-1.1.5.AS71.Final.jar:2012-02-10 15:31] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.10.Final.jar:] > at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.1.0.Final.jar:7.1.0.Final] > at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:154) [jboss-as-web-7.1.0.Final.jar:7.1.0.Final] > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.10.Final.jar:] > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.10.Final.jar:] > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.10.Final.jar:] > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.10.Final.jar:] > at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_22] > Caused by: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:207) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:195) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingValueReference.compute(ComputingConcurrentHashMap.java:355) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.compute(ComputingConcurrentHashMap.java:184) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.getOrCompute(ComputingConcurrentHashMap.java:153) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap.getOrCompute(ComputingConcurrentHashMap.java:69) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:393) [guava-10.0.1.jar:] > ... 25 more > Caused by: javax.naming.NameNotFoundException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:97) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:177) > at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:113) > at javax.naming.InitialContext.lookup(InitialContext.java:396) [rt.jar:1.6.0_22] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.createConnection(JMSTopicsContextImpl.java:98) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.start(JMSTopicsContextImpl.java:123) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:199) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > ... 31 more > 13:13:04,263 SEVERE [org.richfaces.demo.push.MessageProducerRunnable] (MessageProducerThread) javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:397) [guava-10.0.1.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl.createTopic(JMSTopicsContextImpl.java:281) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.TopicsContext.getOrCreateTopic(TopicsContext.java:48) [richfaces-core-api-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.TopicsContext.publish(TopicsContext.java:69) [richfaces-core-api-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.demo.push.TopicsContextMessageProducer.sendMessage(TopicsContextMessageProducer.java:46) [classes:] > at org.richfaces.demo.push.MessageProducerRunnable.run(MessageProducerRunnable.java:57) [classes:] > at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_22] > Caused by: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:207) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:195) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingValueReference.compute(ComputingConcurrentHashMap.java:355) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.compute(ComputingConcurrentHashMap.java:184) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.getOrCompute(ComputingConcurrentHashMap.java:153) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap.getOrCompute(ComputingConcurrentHashMap.java:69) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:393) [guava-10.0.1.jar:] > ... 6 more > Caused by: javax.naming.NameNotFoundException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:97) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:177) > at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:113) > at javax.naming.InitialContext.lookup(InitialContext.java:396) [rt.jar:1.6.0_22] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.createConnection(JMSTopicsContextImpl.java:98) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.start(JMSTopicsContextImpl.java:123) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:199) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > ... 12 more > {code} > {code:title=JBoss AS 7.0.2.Final using default configuration} > 13:16:26,372 WARNING [javax.enterprise.resource.webcontainer.jsf.lifecycle] (http--0%3A0%3A0%3A0%3A0%3A0%3A0%3A0-8080-5) #{pushBean.sendMessage}: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory: javax.faces.FacesException: #{pushBean.sendMessage}: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:118) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > at javax.faces.component.UICommand.broadcast(UICommand.java:315) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:794) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:1259) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:81) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > at org.richfaces.demo.arrangeablemodel.PersistenceLifecycle.execute(PersistenceLifecycle.java:58) [classes:] > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:593) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:67) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:139) [jboss-as-web-7.0.2.Final.jar:7.0.2.Final] > at org.jboss.as.web.NamingValve.invoke(NamingValve.java:57) [jboss-as-web-7.0.2.Final.jar:7.0.2.Final] > at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:49) [jboss-as-jpa-7.0.2.Final.jar:7.0.2.Final] > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:154) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:667) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:952) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at java.lang.Thread.run(Thread.java:662) [:1.6.0_22] > Caused by: javax.faces.el.EvaluationException: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:102) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:102) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > ... 26 more > Caused by: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:397) [guava-10.0.1.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl.createTopic(JMSTopicsContextImpl.java:281) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.TopicsContext.getOrCreateTopic(TopicsContext.java:48) [richfaces-core-api-4.2.0.Final.jar:] > at org.richfaces.application.push.TopicsContext.publish(TopicsContext.java:69) [richfaces-core-api-4.2.0.Final.jar:] > at org.richfaces.application.push.TopicsContext$Proxy$_$$_WeldClientProxy.publish(TopicsContext$Proxy$_$$_WeldClientProxy.java) [richfaces-core-api-4.2.0.Final.jar:] > at org.richfaces.cdi.push.PushCDIExtension$PushObserverMethod.notify(PushCDIExtension.java:144) [richfaces-core-impl-4.2.0.Final.jar:] > at org.jboss.weld.manager.BeanManagerImpl.notifyObservers(BeanManagerImpl.java:635) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:628) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.jboss.weld.event.EventImpl.fire(EventImpl.java:75) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.richfaces.demo.push.PushBean.sendMessage(PushBean.java:65) [classes:] > at org.richfaces.demo.push.PushBean$Proxy$_$$_WeldClientProxy.sendMessage(PushBean$Proxy$_$$_WeldClientProxy.java) [classes:] > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_22] > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_22] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_22] > at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_22] > at org.apache.el.parser.AstValue.invoke(AstValue.java:196) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:276) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.jboss.weld.util.el.ForwardingMethodExpression.invoke(ForwardingMethodExpression.java:43) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.jboss.weld.el.WeldMethodExpression.invoke(WeldMethodExpression.java:56) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at com.sun.faces.facelets.el.TagMethodExpression.invoke(TagMethodExpression.java:105) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:88) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > ... 27 more > Caused by: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:207) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:195) [richfaces-core-impl-4.2.0.Final.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingValueReference.compute(ComputingConcurrentHashMap.java:355) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.compute(ComputingConcurrentHashMap.java:184) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.getOrCompute(ComputingConcurrentHashMap.java:153) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap.getOrCompute(ComputingConcurrentHashMap.java:69) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:393) [guava-10.0.1.jar:] > ... 47 more > Caused by: javax.naming.NameNotFoundException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:87) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:173) > at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:47) > at javax.naming.InitialContext.lookup(InitialContext.java:396) [:1.6.0_22] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.createConnection(JMSTopicsContextImpl.java:98) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.start(JMSTopicsContextImpl.java:123) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:199) [richfaces-core-impl-4.2.0.Final.jar:] > ... 53 more > 13:16:28,949 SEVERE [org.richfaces.demo.push.MessageProducerRunnable] (MessageProducerThread) javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:397) [guava-10.0.1.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl.createTopic(JMSTopicsContextImpl.java:281) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.TopicsContext.getOrCreateTopic(TopicsContext.java:48) [richfaces-core-api-4.2.0.Final.jar:] > at org.richfaces.application.push.TopicsContext.publish(TopicsContext.java:69) [richfaces-core-api-4.2.0.Final.jar:] > at org.richfaces.demo.push.TopicsContextMessageProducer.sendMessage(TopicsContextMessageProducer.java:46) [classes:] > at org.richfaces.demo.push.MessageProducerRunnable.run(MessageProducerRunnable.java:57) [classes:] > at java.lang.Thread.run(Thread.java:662) [:1.6.0_22] > Caused by: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:207) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:195) [richfaces-core-impl-4.2.0.Final.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingValueReference.compute(ComputingConcurrentHashMap.java:355) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.compute(ComputingConcurrentHashMap.java:184) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.getOrCompute(ComputingConcurrentHashMap.java:153) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap.getOrCompute(ComputingConcurrentHashMap.java:69) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:393) [guava-10.0.1.jar:] > ... 6 more > Caused by: javax.naming.NameNotFoundException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:87) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:173) > at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:47) > at javax.naming.InitialContext.lookup(InitialContext.java:396) [:1.6.0_22] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.createConnection(JMSTopicsContextImpl.java:98) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.start(JMSTopicsContextImpl.java:123) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:199) [richfaces-core-impl-4.2.0.Final.jar:] > ... 12 more > {code} > ---- > - Showcase on Openshift Express is working (yeah, there is a really big delay, but it's working). > - Sample in Metamer is also working. > - When the JBoss AS 7.0.2.Final is running with "--server-config standalone-preview.xml", the CDI push demo works correctly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 14 18:19:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 14 Mar 2012 18:19:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11983) Showcase: push sample doesn't work In-Reply-To: <1110785355.5085.1329395076292.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1446321900.10487.1331763587398.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12676916#comment-12676916 ] Luk?? Fry? commented on RF-11983: --------------------------------- Additionally we can try to workaround this issue - to make the example deployable without any configuration out-of-the-box. > Showcase: push sample doesn't work > ---------------------------------- > > Key: RF-11983 > URL: https://issues.jboss.org/browse/RF-11983 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Environment: JBoos AS 7.0.2.Final (in default configuration) / JBoss AS 7.1.0.Final and Firefox 8.0 > Reporter: Jan Papousek > Assignee: Luk?? Fry? > Fix For: 4.3-Tracking > > > {code:title=JBoss AS 7.1.0.Final} > 13:13:03,702 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/showcase].[Faces Servlet]] (http--127.0.0.1-8080-1) Servlet.service() for servlet Faces Servlet threw exception: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:397) [guava-10.0.1.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl.createTopic(JMSTopicsContextImpl.java:281) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.TopicsContext.getOrCreateTopic(TopicsContext.java:48) [richfaces-core-api-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.SessionImpl.createSubscriptions(SessionImpl.java:182) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.SessionImpl.subscribe(SessionImpl.java:177) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.resource.PushResource.encode(PushResource.java:88) [richfaces-components-ui-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.resource.UserResourceWrapperImpl.encode(UserResourceWrapperImpl.java:188) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.resource.ResourceHandlerImpl.handleResourceRequest(ResourceHandlerImpl.java:222) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:591) [jboss-jsf-api_2.1_spec-2.0.0.Final.jar:2.0.0.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.10.Final.jar:] > at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:62) [weld-core-1.1.5.AS71.Final.jar:2012-02-10 15:31] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.10.Final.jar:] > at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.1.0.Final.jar:7.1.0.Final] > at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:154) [jboss-as-web-7.1.0.Final.jar:7.1.0.Final] > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.10.Final.jar:] > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.10.Final.jar:] > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.10.Final.jar:] > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.10.Final.jar:] > at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_22] > Caused by: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:207) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:195) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingValueReference.compute(ComputingConcurrentHashMap.java:355) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.compute(ComputingConcurrentHashMap.java:184) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.getOrCompute(ComputingConcurrentHashMap.java:153) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap.getOrCompute(ComputingConcurrentHashMap.java:69) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:393) [guava-10.0.1.jar:] > ... 25 more > Caused by: javax.naming.NameNotFoundException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:97) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:177) > at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:113) > at javax.naming.InitialContext.lookup(InitialContext.java:396) [rt.jar:1.6.0_22] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.createConnection(JMSTopicsContextImpl.java:98) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.start(JMSTopicsContextImpl.java:123) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:199) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > ... 31 more > 13:13:04,263 SEVERE [org.richfaces.demo.push.MessageProducerRunnable] (MessageProducerThread) javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:397) [guava-10.0.1.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl.createTopic(JMSTopicsContextImpl.java:281) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.TopicsContext.getOrCreateTopic(TopicsContext.java:48) [richfaces-core-api-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.TopicsContext.publish(TopicsContext.java:69) [richfaces-core-api-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.demo.push.TopicsContextMessageProducer.sendMessage(TopicsContextMessageProducer.java:46) [classes:] > at org.richfaces.demo.push.MessageProducerRunnable.run(MessageProducerRunnable.java:57) [classes:] > at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_22] > Caused by: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:207) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:195) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingValueReference.compute(ComputingConcurrentHashMap.java:355) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.compute(ComputingConcurrentHashMap.java:184) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.getOrCompute(ComputingConcurrentHashMap.java:153) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap.getOrCompute(ComputingConcurrentHashMap.java:69) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:393) [guava-10.0.1.jar:] > ... 6 more > Caused by: javax.naming.NameNotFoundException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:97) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:177) > at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:113) > at javax.naming.InitialContext.lookup(InitialContext.java:396) [rt.jar:1.6.0_22] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.createConnection(JMSTopicsContextImpl.java:98) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.start(JMSTopicsContextImpl.java:123) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:199) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > ... 12 more > {code} > {code:title=JBoss AS 7.0.2.Final using default configuration} > 13:16:26,372 WARNING [javax.enterprise.resource.webcontainer.jsf.lifecycle] (http--0%3A0%3A0%3A0%3A0%3A0%3A0%3A0-8080-5) #{pushBean.sendMessage}: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory: javax.faces.FacesException: #{pushBean.sendMessage}: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:118) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > at javax.faces.component.UICommand.broadcast(UICommand.java:315) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:794) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:1259) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:81) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > at org.richfaces.demo.arrangeablemodel.PersistenceLifecycle.execute(PersistenceLifecycle.java:58) [classes:] > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:593) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:67) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:139) [jboss-as-web-7.0.2.Final.jar:7.0.2.Final] > at org.jboss.as.web.NamingValve.invoke(NamingValve.java:57) [jboss-as-web-7.0.2.Final.jar:7.0.2.Final] > at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:49) [jboss-as-jpa-7.0.2.Final.jar:7.0.2.Final] > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:154) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:667) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:952) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at java.lang.Thread.run(Thread.java:662) [:1.6.0_22] > Caused by: javax.faces.el.EvaluationException: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:102) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:102) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > ... 26 more > Caused by: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:397) [guava-10.0.1.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl.createTopic(JMSTopicsContextImpl.java:281) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.TopicsContext.getOrCreateTopic(TopicsContext.java:48) [richfaces-core-api-4.2.0.Final.jar:] > at org.richfaces.application.push.TopicsContext.publish(TopicsContext.java:69) [richfaces-core-api-4.2.0.Final.jar:] > at org.richfaces.application.push.TopicsContext$Proxy$_$$_WeldClientProxy.publish(TopicsContext$Proxy$_$$_WeldClientProxy.java) [richfaces-core-api-4.2.0.Final.jar:] > at org.richfaces.cdi.push.PushCDIExtension$PushObserverMethod.notify(PushCDIExtension.java:144) [richfaces-core-impl-4.2.0.Final.jar:] > at org.jboss.weld.manager.BeanManagerImpl.notifyObservers(BeanManagerImpl.java:635) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:628) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.jboss.weld.event.EventImpl.fire(EventImpl.java:75) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.richfaces.demo.push.PushBean.sendMessage(PushBean.java:65) [classes:] > at org.richfaces.demo.push.PushBean$Proxy$_$$_WeldClientProxy.sendMessage(PushBean$Proxy$_$$_WeldClientProxy.java) [classes:] > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_22] > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_22] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_22] > at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_22] > at org.apache.el.parser.AstValue.invoke(AstValue.java:196) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:276) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.jboss.weld.util.el.ForwardingMethodExpression.invoke(ForwardingMethodExpression.java:43) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.jboss.weld.el.WeldMethodExpression.invoke(WeldMethodExpression.java:56) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at com.sun.faces.facelets.el.TagMethodExpression.invoke(TagMethodExpression.java:105) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:88) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > ... 27 more > Caused by: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:207) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:195) [richfaces-core-impl-4.2.0.Final.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingValueReference.compute(ComputingConcurrentHashMap.java:355) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.compute(ComputingConcurrentHashMap.java:184) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.getOrCompute(ComputingConcurrentHashMap.java:153) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap.getOrCompute(ComputingConcurrentHashMap.java:69) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:393) [guava-10.0.1.jar:] > ... 47 more > Caused by: javax.naming.NameNotFoundException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:87) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:173) > at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:47) > at javax.naming.InitialContext.lookup(InitialContext.java:396) [:1.6.0_22] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.createConnection(JMSTopicsContextImpl.java:98) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.start(JMSTopicsContextImpl.java:123) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:199) [richfaces-core-impl-4.2.0.Final.jar:] > ... 53 more > 13:16:28,949 SEVERE [org.richfaces.demo.push.MessageProducerRunnable] (MessageProducerThread) javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:397) [guava-10.0.1.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl.createTopic(JMSTopicsContextImpl.java:281) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.TopicsContext.getOrCreateTopic(TopicsContext.java:48) [richfaces-core-api-4.2.0.Final.jar:] > at org.richfaces.application.push.TopicsContext.publish(TopicsContext.java:69) [richfaces-core-api-4.2.0.Final.jar:] > at org.richfaces.demo.push.TopicsContextMessageProducer.sendMessage(TopicsContextMessageProducer.java:46) [classes:] > at org.richfaces.demo.push.MessageProducerRunnable.run(MessageProducerRunnable.java:57) [classes:] > at java.lang.Thread.run(Thread.java:662) [:1.6.0_22] > Caused by: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:207) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:195) [richfaces-core-impl-4.2.0.Final.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingValueReference.compute(ComputingConcurrentHashMap.java:355) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.compute(ComputingConcurrentHashMap.java:184) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.getOrCompute(ComputingConcurrentHashMap.java:153) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap.getOrCompute(ComputingConcurrentHashMap.java:69) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:393) [guava-10.0.1.jar:] > ... 6 more > Caused by: javax.naming.NameNotFoundException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:87) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:173) > at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:47) > at javax.naming.InitialContext.lookup(InitialContext.java:396) [:1.6.0_22] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.createConnection(JMSTopicsContextImpl.java:98) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.start(JMSTopicsContextImpl.java:123) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:199) [richfaces-core-impl-4.2.0.Final.jar:] > ... 12 more > {code} > ---- > - Showcase on Openshift Express is working (yeah, there is a really big delay, but it's working). > - Sample in Metamer is also working. > - When the JBoss AS 7.0.2.Final is running with "--server-config standalone-preview.xml", the CDI push demo works correctly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 14 18:21:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 14 Mar 2012 18:21:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11983) Showcase: push sample doesn't work In-Reply-To: <1110785355.5085.1329395076292.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <664820652.10494.1331763707575.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12676916#comment-12676916 ] Luk?? Fry? edited comment on RF-11983 at 3/14/12 6:20 PM: ---------------------------------------------------------- Additionally we can try to workaround this issue - to make the example deployable without any configuration out-of-the-box. We can achieve it by configuring the JMS (adding user) using DMR interface. was (Author: lfryc): Additionally we can try to workaround this issue - to make the example deployable without any configuration out-of-the-box. > Showcase: push sample doesn't work > ---------------------------------- > > Key: RF-11983 > URL: https://issues.jboss.org/browse/RF-11983 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Environment: JBoos AS 7.0.2.Final (in default configuration) / JBoss AS 7.1.0.Final and Firefox 8.0 > Reporter: Jan Papousek > Assignee: Luk?? Fry? > Fix For: 4.3-Tracking > > > {code:title=JBoss AS 7.1.0.Final} > 13:13:03,702 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/showcase].[Faces Servlet]] (http--127.0.0.1-8080-1) Servlet.service() for servlet Faces Servlet threw exception: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:397) [guava-10.0.1.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl.createTopic(JMSTopicsContextImpl.java:281) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.TopicsContext.getOrCreateTopic(TopicsContext.java:48) [richfaces-core-api-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.SessionImpl.createSubscriptions(SessionImpl.java:182) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.SessionImpl.subscribe(SessionImpl.java:177) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.resource.PushResource.encode(PushResource.java:88) [richfaces-components-ui-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.resource.UserResourceWrapperImpl.encode(UserResourceWrapperImpl.java:188) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.resource.ResourceHandlerImpl.handleResourceRequest(ResourceHandlerImpl.java:222) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:591) [jboss-jsf-api_2.1_spec-2.0.0.Final.jar:2.0.0.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.10.Final.jar:] > at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:62) [weld-core-1.1.5.AS71.Final.jar:2012-02-10 15:31] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.10.Final.jar:] > at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.1.0.Final.jar:7.1.0.Final] > at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:154) [jboss-as-web-7.1.0.Final.jar:7.1.0.Final] > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.10.Final.jar:] > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.10.Final.jar:] > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.10.Final.jar:] > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.10.Final.jar:] > at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_22] > Caused by: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:207) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:195) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingValueReference.compute(ComputingConcurrentHashMap.java:355) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.compute(ComputingConcurrentHashMap.java:184) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.getOrCompute(ComputingConcurrentHashMap.java:153) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap.getOrCompute(ComputingConcurrentHashMap.java:69) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:393) [guava-10.0.1.jar:] > ... 25 more > Caused by: javax.naming.NameNotFoundException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:97) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:177) > at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:113) > at javax.naming.InitialContext.lookup(InitialContext.java:396) [rt.jar:1.6.0_22] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.createConnection(JMSTopicsContextImpl.java:98) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.start(JMSTopicsContextImpl.java:123) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:199) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > ... 31 more > 13:13:04,263 SEVERE [org.richfaces.demo.push.MessageProducerRunnable] (MessageProducerThread) javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:397) [guava-10.0.1.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl.createTopic(JMSTopicsContextImpl.java:281) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.TopicsContext.getOrCreateTopic(TopicsContext.java:48) [richfaces-core-api-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.TopicsContext.publish(TopicsContext.java:69) [richfaces-core-api-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.demo.push.TopicsContextMessageProducer.sendMessage(TopicsContextMessageProducer.java:46) [classes:] > at org.richfaces.demo.push.MessageProducerRunnable.run(MessageProducerRunnable.java:57) [classes:] > at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_22] > Caused by: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:207) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:195) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingValueReference.compute(ComputingConcurrentHashMap.java:355) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.compute(ComputingConcurrentHashMap.java:184) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.getOrCompute(ComputingConcurrentHashMap.java:153) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap.getOrCompute(ComputingConcurrentHashMap.java:69) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:393) [guava-10.0.1.jar:] > ... 6 more > Caused by: javax.naming.NameNotFoundException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:97) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:177) > at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:113) > at javax.naming.InitialContext.lookup(InitialContext.java:396) [rt.jar:1.6.0_22] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.createConnection(JMSTopicsContextImpl.java:98) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.start(JMSTopicsContextImpl.java:123) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:199) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > ... 12 more > {code} > {code:title=JBoss AS 7.0.2.Final using default configuration} > 13:16:26,372 WARNING [javax.enterprise.resource.webcontainer.jsf.lifecycle] (http--0%3A0%3A0%3A0%3A0%3A0%3A0%3A0-8080-5) #{pushBean.sendMessage}: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory: javax.faces.FacesException: #{pushBean.sendMessage}: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:118) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > at javax.faces.component.UICommand.broadcast(UICommand.java:315) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:794) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:1259) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:81) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > at org.richfaces.demo.arrangeablemodel.PersistenceLifecycle.execute(PersistenceLifecycle.java:58) [classes:] > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:593) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:67) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:139) [jboss-as-web-7.0.2.Final.jar:7.0.2.Final] > at org.jboss.as.web.NamingValve.invoke(NamingValve.java:57) [jboss-as-web-7.0.2.Final.jar:7.0.2.Final] > at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:49) [jboss-as-jpa-7.0.2.Final.jar:7.0.2.Final] > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:154) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:667) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:952) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at java.lang.Thread.run(Thread.java:662) [:1.6.0_22] > Caused by: javax.faces.el.EvaluationException: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:102) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:102) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > ... 26 more > Caused by: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:397) [guava-10.0.1.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl.createTopic(JMSTopicsContextImpl.java:281) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.TopicsContext.getOrCreateTopic(TopicsContext.java:48) [richfaces-core-api-4.2.0.Final.jar:] > at org.richfaces.application.push.TopicsContext.publish(TopicsContext.java:69) [richfaces-core-api-4.2.0.Final.jar:] > at org.richfaces.application.push.TopicsContext$Proxy$_$$_WeldClientProxy.publish(TopicsContext$Proxy$_$$_WeldClientProxy.java) [richfaces-core-api-4.2.0.Final.jar:] > at org.richfaces.cdi.push.PushCDIExtension$PushObserverMethod.notify(PushCDIExtension.java:144) [richfaces-core-impl-4.2.0.Final.jar:] > at org.jboss.weld.manager.BeanManagerImpl.notifyObservers(BeanManagerImpl.java:635) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:628) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.jboss.weld.event.EventImpl.fire(EventImpl.java:75) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.richfaces.demo.push.PushBean.sendMessage(PushBean.java:65) [classes:] > at org.richfaces.demo.push.PushBean$Proxy$_$$_WeldClientProxy.sendMessage(PushBean$Proxy$_$$_WeldClientProxy.java) [classes:] > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_22] > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_22] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_22] > at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_22] > at org.apache.el.parser.AstValue.invoke(AstValue.java:196) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:276) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.jboss.weld.util.el.ForwardingMethodExpression.invoke(ForwardingMethodExpression.java:43) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.jboss.weld.el.WeldMethodExpression.invoke(WeldMethodExpression.java:56) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at com.sun.faces.facelets.el.TagMethodExpression.invoke(TagMethodExpression.java:105) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:88) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > ... 27 more > Caused by: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:207) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:195) [richfaces-core-impl-4.2.0.Final.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingValueReference.compute(ComputingConcurrentHashMap.java:355) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.compute(ComputingConcurrentHashMap.java:184) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.getOrCompute(ComputingConcurrentHashMap.java:153) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap.getOrCompute(ComputingConcurrentHashMap.java:69) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:393) [guava-10.0.1.jar:] > ... 47 more > Caused by: javax.naming.NameNotFoundException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:87) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:173) > at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:47) > at javax.naming.InitialContext.lookup(InitialContext.java:396) [:1.6.0_22] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.createConnection(JMSTopicsContextImpl.java:98) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.start(JMSTopicsContextImpl.java:123) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:199) [richfaces-core-impl-4.2.0.Final.jar:] > ... 53 more > 13:16:28,949 SEVERE [org.richfaces.demo.push.MessageProducerRunnable] (MessageProducerThread) javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:397) [guava-10.0.1.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl.createTopic(JMSTopicsContextImpl.java:281) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.TopicsContext.getOrCreateTopic(TopicsContext.java:48) [richfaces-core-api-4.2.0.Final.jar:] > at org.richfaces.application.push.TopicsContext.publish(TopicsContext.java:69) [richfaces-core-api-4.2.0.Final.jar:] > at org.richfaces.demo.push.TopicsContextMessageProducer.sendMessage(TopicsContextMessageProducer.java:46) [classes:] > at org.richfaces.demo.push.MessageProducerRunnable.run(MessageProducerRunnable.java:57) [classes:] > at java.lang.Thread.run(Thread.java:662) [:1.6.0_22] > Caused by: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:207) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:195) [richfaces-core-impl-4.2.0.Final.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingValueReference.compute(ComputingConcurrentHashMap.java:355) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.compute(ComputingConcurrentHashMap.java:184) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.getOrCompute(ComputingConcurrentHashMap.java:153) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap.getOrCompute(ComputingConcurrentHashMap.java:69) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:393) [guava-10.0.1.jar:] > ... 6 more > Caused by: javax.naming.NameNotFoundException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:87) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:173) > at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:47) > at javax.naming.InitialContext.lookup(InitialContext.java:396) [:1.6.0_22] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.createConnection(JMSTopicsContextImpl.java:98) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.start(JMSTopicsContextImpl.java:123) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:199) [richfaces-core-impl-4.2.0.Final.jar:] > ... 12 more > {code} > ---- > - Showcase on Openshift Express is working (yeah, there is a really big delay, but it's working). > - Sample in Metamer is also working. > - When the JBoss AS 7.0.2.Final is running with "--server-config standalone-preview.xml", the CDI push demo works correctly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 14 18:21:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 14 Mar 2012 18:21:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11983) Showcase: push sample doesn't work In-Reply-To: <1110785355.5085.1329395076292.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <573601840.10499.1331763707820.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12676916#comment-12676916 ] Luk?? Fry? edited comment on RF-11983 at 3/14/12 6:20 PM: ---------------------------------------------------------- Additionally we can try to workaround this issue - to make the example deployable without any configuration out-of-the-box. We can achieve it by configuring the JMS (adding user) using DMR interface (the same already used for topic creation). was (Author: lfryc): Additionally we can try to workaround this issue - to make the example deployable without any configuration out-of-the-box. We can achieve it by configuring the JMS (adding user) using DMR interface. > Showcase: push sample doesn't work > ---------------------------------- > > Key: RF-11983 > URL: https://issues.jboss.org/browse/RF-11983 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Environment: JBoos AS 7.0.2.Final (in default configuration) / JBoss AS 7.1.0.Final and Firefox 8.0 > Reporter: Jan Papousek > Assignee: Luk?? Fry? > Fix For: 4.3-Tracking > > > {code:title=JBoss AS 7.1.0.Final} > 13:13:03,702 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/showcase].[Faces Servlet]] (http--127.0.0.1-8080-1) Servlet.service() for servlet Faces Servlet threw exception: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:397) [guava-10.0.1.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl.createTopic(JMSTopicsContextImpl.java:281) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.TopicsContext.getOrCreateTopic(TopicsContext.java:48) [richfaces-core-api-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.SessionImpl.createSubscriptions(SessionImpl.java:182) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.SessionImpl.subscribe(SessionImpl.java:177) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.resource.PushResource.encode(PushResource.java:88) [richfaces-components-ui-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.resource.UserResourceWrapperImpl.encode(UserResourceWrapperImpl.java:188) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.resource.ResourceHandlerImpl.handleResourceRequest(ResourceHandlerImpl.java:222) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:591) [jboss-jsf-api_2.1_spec-2.0.0.Final.jar:2.0.0.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.10.Final.jar:] > at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:62) [weld-core-1.1.5.AS71.Final.jar:2012-02-10 15:31] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.10.Final.jar:] > at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.1.0.Final.jar:7.1.0.Final] > at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:154) [jboss-as-web-7.1.0.Final.jar:7.1.0.Final] > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.10.Final.jar:] > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.10.Final.jar:] > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.10.Final.jar:] > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.10.Final.jar:] > at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_22] > Caused by: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:207) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:195) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingValueReference.compute(ComputingConcurrentHashMap.java:355) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.compute(ComputingConcurrentHashMap.java:184) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.getOrCompute(ComputingConcurrentHashMap.java:153) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap.getOrCompute(ComputingConcurrentHashMap.java:69) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:393) [guava-10.0.1.jar:] > ... 25 more > Caused by: javax.naming.NameNotFoundException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:97) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:177) > at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:113) > at javax.naming.InitialContext.lookup(InitialContext.java:396) [rt.jar:1.6.0_22] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.createConnection(JMSTopicsContextImpl.java:98) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.start(JMSTopicsContextImpl.java:123) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:199) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > ... 31 more > 13:13:04,263 SEVERE [org.richfaces.demo.push.MessageProducerRunnable] (MessageProducerThread) javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:397) [guava-10.0.1.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl.createTopic(JMSTopicsContextImpl.java:281) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.TopicsContext.getOrCreateTopic(TopicsContext.java:48) [richfaces-core-api-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.TopicsContext.publish(TopicsContext.java:69) [richfaces-core-api-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.demo.push.TopicsContextMessageProducer.sendMessage(TopicsContextMessageProducer.java:46) [classes:] > at org.richfaces.demo.push.MessageProducerRunnable.run(MessageProducerRunnable.java:57) [classes:] > at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_22] > Caused by: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:207) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:195) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingValueReference.compute(ComputingConcurrentHashMap.java:355) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.compute(ComputingConcurrentHashMap.java:184) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.getOrCompute(ComputingConcurrentHashMap.java:153) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap.getOrCompute(ComputingConcurrentHashMap.java:69) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:393) [guava-10.0.1.jar:] > ... 6 more > Caused by: javax.naming.NameNotFoundException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:97) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:177) > at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:113) > at javax.naming.InitialContext.lookup(InitialContext.java:396) [rt.jar:1.6.0_22] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.createConnection(JMSTopicsContextImpl.java:98) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.start(JMSTopicsContextImpl.java:123) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:199) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > ... 12 more > {code} > {code:title=JBoss AS 7.0.2.Final using default configuration} > 13:16:26,372 WARNING [javax.enterprise.resource.webcontainer.jsf.lifecycle] (http--0%3A0%3A0%3A0%3A0%3A0%3A0%3A0-8080-5) #{pushBean.sendMessage}: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory: javax.faces.FacesException: #{pushBean.sendMessage}: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:118) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > at javax.faces.component.UICommand.broadcast(UICommand.java:315) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:794) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:1259) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:81) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > at org.richfaces.demo.arrangeablemodel.PersistenceLifecycle.execute(PersistenceLifecycle.java:58) [classes:] > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:593) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:67) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:139) [jboss-as-web-7.0.2.Final.jar:7.0.2.Final] > at org.jboss.as.web.NamingValve.invoke(NamingValve.java:57) [jboss-as-web-7.0.2.Final.jar:7.0.2.Final] > at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:49) [jboss-as-jpa-7.0.2.Final.jar:7.0.2.Final] > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:154) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:667) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:952) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at java.lang.Thread.run(Thread.java:662) [:1.6.0_22] > Caused by: javax.faces.el.EvaluationException: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:102) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:102) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > ... 26 more > Caused by: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:397) [guava-10.0.1.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl.createTopic(JMSTopicsContextImpl.java:281) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.TopicsContext.getOrCreateTopic(TopicsContext.java:48) [richfaces-core-api-4.2.0.Final.jar:] > at org.richfaces.application.push.TopicsContext.publish(TopicsContext.java:69) [richfaces-core-api-4.2.0.Final.jar:] > at org.richfaces.application.push.TopicsContext$Proxy$_$$_WeldClientProxy.publish(TopicsContext$Proxy$_$$_WeldClientProxy.java) [richfaces-core-api-4.2.0.Final.jar:] > at org.richfaces.cdi.push.PushCDIExtension$PushObserverMethod.notify(PushCDIExtension.java:144) [richfaces-core-impl-4.2.0.Final.jar:] > at org.jboss.weld.manager.BeanManagerImpl.notifyObservers(BeanManagerImpl.java:635) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:628) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.jboss.weld.event.EventImpl.fire(EventImpl.java:75) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.richfaces.demo.push.PushBean.sendMessage(PushBean.java:65) [classes:] > at org.richfaces.demo.push.PushBean$Proxy$_$$_WeldClientProxy.sendMessage(PushBean$Proxy$_$$_WeldClientProxy.java) [classes:] > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_22] > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_22] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_22] > at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_22] > at org.apache.el.parser.AstValue.invoke(AstValue.java:196) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:276) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.jboss.weld.util.el.ForwardingMethodExpression.invoke(ForwardingMethodExpression.java:43) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.jboss.weld.el.WeldMethodExpression.invoke(WeldMethodExpression.java:56) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at com.sun.faces.facelets.el.TagMethodExpression.invoke(TagMethodExpression.java:105) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:88) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > ... 27 more > Caused by: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:207) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:195) [richfaces-core-impl-4.2.0.Final.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingValueReference.compute(ComputingConcurrentHashMap.java:355) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.compute(ComputingConcurrentHashMap.java:184) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.getOrCompute(ComputingConcurrentHashMap.java:153) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap.getOrCompute(ComputingConcurrentHashMap.java:69) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:393) [guava-10.0.1.jar:] > ... 47 more > Caused by: javax.naming.NameNotFoundException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:87) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:173) > at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:47) > at javax.naming.InitialContext.lookup(InitialContext.java:396) [:1.6.0_22] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.createConnection(JMSTopicsContextImpl.java:98) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.start(JMSTopicsContextImpl.java:123) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:199) [richfaces-core-impl-4.2.0.Final.jar:] > ... 53 more > 13:16:28,949 SEVERE [org.richfaces.demo.push.MessageProducerRunnable] (MessageProducerThread) javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:397) [guava-10.0.1.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl.createTopic(JMSTopicsContextImpl.java:281) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.TopicsContext.getOrCreateTopic(TopicsContext.java:48) [richfaces-core-api-4.2.0.Final.jar:] > at org.richfaces.application.push.TopicsContext.publish(TopicsContext.java:69) [richfaces-core-api-4.2.0.Final.jar:] > at org.richfaces.demo.push.TopicsContextMessageProducer.sendMessage(TopicsContextMessageProducer.java:46) [classes:] > at org.richfaces.demo.push.MessageProducerRunnable.run(MessageProducerRunnable.java:57) [classes:] > at java.lang.Thread.run(Thread.java:662) [:1.6.0_22] > Caused by: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:207) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:195) [richfaces-core-impl-4.2.0.Final.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingValueReference.compute(ComputingConcurrentHashMap.java:355) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.compute(ComputingConcurrentHashMap.java:184) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.getOrCompute(ComputingConcurrentHashMap.java:153) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap.getOrCompute(ComputingConcurrentHashMap.java:69) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:393) [guava-10.0.1.jar:] > ... 6 more > Caused by: javax.naming.NameNotFoundException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:87) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:173) > at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:47) > at javax.naming.InitialContext.lookup(InitialContext.java:396) [:1.6.0_22] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.createConnection(JMSTopicsContextImpl.java:98) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.start(JMSTopicsContextImpl.java:123) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:199) [richfaces-core-impl-4.2.0.Final.jar:] > ... 12 more > {code} > ---- > - Showcase on Openshift Express is working (yeah, there is a really big delay, but it's working). > - Sample in Metamer is also working. > - When the JBoss AS 7.0.2.Final is running with "--server-config standalone-preview.xml", the CDI push demo works correctly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 14 18:21:49 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 14 Mar 2012 18:21:49 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11983) Showcase: can't connect to JMS on AS7.1 since it is secured In-Reply-To: <1110785355.5085.1329395076292.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <142499144.10503.1331763709155.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated RF-11983: ---------------------------- Summary: Showcase: can't connect to JMS on AS7.1 since it is secured (was: Showcase: push sample doesn't work) Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=802444 (was: https://bugzilla.redhat.com/show_bug.cgi?id=802444) > Showcase: can't connect to JMS on AS7.1 since it is secured > ----------------------------------------------------------- > > Key: RF-11983 > URL: https://issues.jboss.org/browse/RF-11983 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Environment: JBoos AS 7.0.2.Final (in default configuration) / JBoss AS 7.1.0.Final and Firefox 8.0 > Reporter: Jan Papousek > Assignee: Luk?? Fry? > Fix For: 4.3-Tracking > > > {code:title=JBoss AS 7.1.0.Final} > 13:13:03,702 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/showcase].[Faces Servlet]] (http--127.0.0.1-8080-1) Servlet.service() for servlet Faces Servlet threw exception: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:397) [guava-10.0.1.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl.createTopic(JMSTopicsContextImpl.java:281) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.TopicsContext.getOrCreateTopic(TopicsContext.java:48) [richfaces-core-api-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.SessionImpl.createSubscriptions(SessionImpl.java:182) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.SessionImpl.subscribe(SessionImpl.java:177) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.resource.PushResource.encode(PushResource.java:88) [richfaces-components-ui-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.resource.UserResourceWrapperImpl.encode(UserResourceWrapperImpl.java:188) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.resource.ResourceHandlerImpl.handleResourceRequest(ResourceHandlerImpl.java:222) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:591) [jboss-jsf-api_2.1_spec-2.0.0.Final.jar:2.0.0.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.10.Final.jar:] > at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:62) [weld-core-1.1.5.AS71.Final.jar:2012-02-10 15:31] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.10.Final.jar:] > at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.1.0.Final.jar:7.1.0.Final] > at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:154) [jboss-as-web-7.1.0.Final.jar:7.1.0.Final] > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.10.Final.jar:] > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.10.Final.jar:] > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.10.Final.jar:] > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.10.Final.jar:] > at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_22] > Caused by: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:207) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:195) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingValueReference.compute(ComputingConcurrentHashMap.java:355) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.compute(ComputingConcurrentHashMap.java:184) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.getOrCompute(ComputingConcurrentHashMap.java:153) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap.getOrCompute(ComputingConcurrentHashMap.java:69) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:393) [guava-10.0.1.jar:] > ... 25 more > Caused by: javax.naming.NameNotFoundException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:97) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:177) > at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:113) > at javax.naming.InitialContext.lookup(InitialContext.java:396) [rt.jar:1.6.0_22] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.createConnection(JMSTopicsContextImpl.java:98) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.start(JMSTopicsContextImpl.java:123) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:199) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > ... 31 more > 13:13:04,263 SEVERE [org.richfaces.demo.push.MessageProducerRunnable] (MessageProducerThread) javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:397) [guava-10.0.1.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl.createTopic(JMSTopicsContextImpl.java:281) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.TopicsContext.getOrCreateTopic(TopicsContext.java:48) [richfaces-core-api-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.TopicsContext.publish(TopicsContext.java:69) [richfaces-core-api-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.demo.push.TopicsContextMessageProducer.sendMessage(TopicsContextMessageProducer.java:46) [classes:] > at org.richfaces.demo.push.MessageProducerRunnable.run(MessageProducerRunnable.java:57) [classes:] > at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_22] > Caused by: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:207) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:195) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingValueReference.compute(ComputingConcurrentHashMap.java:355) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.compute(ComputingConcurrentHashMap.java:184) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.getOrCompute(ComputingConcurrentHashMap.java:153) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap.getOrCompute(ComputingConcurrentHashMap.java:69) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:393) [guava-10.0.1.jar:] > ... 6 more > Caused by: javax.naming.NameNotFoundException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:97) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:177) > at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:113) > at javax.naming.InitialContext.lookup(InitialContext.java:396) [rt.jar:1.6.0_22] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.createConnection(JMSTopicsContextImpl.java:98) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.start(JMSTopicsContextImpl.java:123) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:199) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > ... 12 more > {code} > {code:title=JBoss AS 7.0.2.Final using default configuration} > 13:16:26,372 WARNING [javax.enterprise.resource.webcontainer.jsf.lifecycle] (http--0%3A0%3A0%3A0%3A0%3A0%3A0%3A0-8080-5) #{pushBean.sendMessage}: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory: javax.faces.FacesException: #{pushBean.sendMessage}: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:118) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > at javax.faces.component.UICommand.broadcast(UICommand.java:315) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:794) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:1259) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:81) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > at org.richfaces.demo.arrangeablemodel.PersistenceLifecycle.execute(PersistenceLifecycle.java:58) [classes:] > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:593) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:67) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:139) [jboss-as-web-7.0.2.Final.jar:7.0.2.Final] > at org.jboss.as.web.NamingValve.invoke(NamingValve.java:57) [jboss-as-web-7.0.2.Final.jar:7.0.2.Final] > at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:49) [jboss-as-jpa-7.0.2.Final.jar:7.0.2.Final] > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:154) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:667) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:952) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at java.lang.Thread.run(Thread.java:662) [:1.6.0_22] > Caused by: javax.faces.el.EvaluationException: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:102) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:102) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > ... 26 more > Caused by: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:397) [guava-10.0.1.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl.createTopic(JMSTopicsContextImpl.java:281) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.TopicsContext.getOrCreateTopic(TopicsContext.java:48) [richfaces-core-api-4.2.0.Final.jar:] > at org.richfaces.application.push.TopicsContext.publish(TopicsContext.java:69) [richfaces-core-api-4.2.0.Final.jar:] > at org.richfaces.application.push.TopicsContext$Proxy$_$$_WeldClientProxy.publish(TopicsContext$Proxy$_$$_WeldClientProxy.java) [richfaces-core-api-4.2.0.Final.jar:] > at org.richfaces.cdi.push.PushCDIExtension$PushObserverMethod.notify(PushCDIExtension.java:144) [richfaces-core-impl-4.2.0.Final.jar:] > at org.jboss.weld.manager.BeanManagerImpl.notifyObservers(BeanManagerImpl.java:635) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:628) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.jboss.weld.event.EventImpl.fire(EventImpl.java:75) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.richfaces.demo.push.PushBean.sendMessage(PushBean.java:65) [classes:] > at org.richfaces.demo.push.PushBean$Proxy$_$$_WeldClientProxy.sendMessage(PushBean$Proxy$_$$_WeldClientProxy.java) [classes:] > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_22] > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_22] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_22] > at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_22] > at org.apache.el.parser.AstValue.invoke(AstValue.java:196) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:276) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.jboss.weld.util.el.ForwardingMethodExpression.invoke(ForwardingMethodExpression.java:43) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.jboss.weld.el.WeldMethodExpression.invoke(WeldMethodExpression.java:56) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at com.sun.faces.facelets.el.TagMethodExpression.invoke(TagMethodExpression.java:105) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:88) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > ... 27 more > Caused by: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:207) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:195) [richfaces-core-impl-4.2.0.Final.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingValueReference.compute(ComputingConcurrentHashMap.java:355) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.compute(ComputingConcurrentHashMap.java:184) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.getOrCompute(ComputingConcurrentHashMap.java:153) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap.getOrCompute(ComputingConcurrentHashMap.java:69) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:393) [guava-10.0.1.jar:] > ... 47 more > Caused by: javax.naming.NameNotFoundException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:87) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:173) > at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:47) > at javax.naming.InitialContext.lookup(InitialContext.java:396) [:1.6.0_22] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.createConnection(JMSTopicsContextImpl.java:98) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.start(JMSTopicsContextImpl.java:123) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:199) [richfaces-core-impl-4.2.0.Final.jar:] > ... 53 more > 13:16:28,949 SEVERE [org.richfaces.demo.push.MessageProducerRunnable] (MessageProducerThread) javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:397) [guava-10.0.1.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl.createTopic(JMSTopicsContextImpl.java:281) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.TopicsContext.getOrCreateTopic(TopicsContext.java:48) [richfaces-core-api-4.2.0.Final.jar:] > at org.richfaces.application.push.TopicsContext.publish(TopicsContext.java:69) [richfaces-core-api-4.2.0.Final.jar:] > at org.richfaces.demo.push.TopicsContextMessageProducer.sendMessage(TopicsContextMessageProducer.java:46) [classes:] > at org.richfaces.demo.push.MessageProducerRunnable.run(MessageProducerRunnable.java:57) [classes:] > at java.lang.Thread.run(Thread.java:662) [:1.6.0_22] > Caused by: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:207) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:195) [richfaces-core-impl-4.2.0.Final.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingValueReference.compute(ComputingConcurrentHashMap.java:355) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.compute(ComputingConcurrentHashMap.java:184) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.getOrCompute(ComputingConcurrentHashMap.java:153) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap.getOrCompute(ComputingConcurrentHashMap.java:69) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:393) [guava-10.0.1.jar:] > ... 6 more > Caused by: javax.naming.NameNotFoundException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:87) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:173) > at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:47) > at javax.naming.InitialContext.lookup(InitialContext.java:396) [:1.6.0_22] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.createConnection(JMSTopicsContextImpl.java:98) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.start(JMSTopicsContextImpl.java:123) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:199) [richfaces-core-impl-4.2.0.Final.jar:] > ... 12 more > {code} > ---- > - Showcase on Openshift Express is working (yeah, there is a really big delay, but it's working). > - Sample in Metamer is also working. > - When the JBoss AS 7.0.2.Final is running with "--server-config standalone-preview.xml", the CDI push demo works correctly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 14 18:23:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 14 Mar 2012 18:23:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12048) Change the password for JMS guest connection In-Reply-To: <1881089286.10479.1331763467304.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1614144391.10506.1331763827388.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12676917#comment-12676917 ] Luk?? Fry? commented on RF-12048: --------------------------------- Consider addition to {{4.2.1.CR1}}. > Change the password for JMS guest connection > -------------------------------------------- > > Key: RF-12048 > URL: https://issues.jboss.org/browse/RF-12048 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-push/poll > Affects Versions: 4.2.0.Final > Reporter: Luk?? Fry? > > [Originally request|https://issues.jboss.org/browse/RF-11983?focusedCommentId=12676716&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12676716] by Karel Piwko: > AS7 doesn't allow to add user with same name and password, that's why having {{guest:guest}} credentials [1] does not make sense. > We can change the credentials to {{guest:password}} - I have verified the actual content does not have any influence on functionality on AS7.0 and will improve usability on AS7.1. > [1] https://github.com/richfaces/showcase/blob/4.2.0.20120215-Final/src/main/webapp-jbas7/WEB-INF/web.xml#L78 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 14 18:23:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 14 Mar 2012 18:23:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12048) Showcase: Change the password for JMS guest connection In-Reply-To: <1881089286.10479.1331763467304.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <2131631902.10508.1331763827548.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated RF-12048: ---------------------------- Summary: Showcase: Change the password for JMS guest connection (was: Change the password for JMS guest connection) > Showcase: Change the password for JMS guest connection > ------------------------------------------------------ > > Key: RF-12048 > URL: https://issues.jboss.org/browse/RF-12048 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-push/poll > Affects Versions: 4.2.0.Final > Reporter: Luk?? Fry? > > [Originally request|https://issues.jboss.org/browse/RF-11983?focusedCommentId=12676716&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12676716] by Karel Piwko: > AS7 doesn't allow to add user with same name and password, that's why having {{guest:guest}} credentials [1] does not make sense. > We can change the credentials to {{guest:password}} - I have verified the actual content does not have any influence on functionality on AS7.0 and will improve usability on AS7.1. > [1] https://github.com/richfaces/showcase/blob/4.2.0.20120215-Final/src/main/webapp-jbas7/WEB-INF/web.xml#L78 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 14 21:39:47 2012 From: jira-events at lists.jboss.org (Burr Sutter (JIRA)) Date: Wed, 14 Mar 2012 21:39:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12049) Richfaces Kitchensink Archetype Message-ID: <298774079.10572.1331775587398.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Burr Sutter created RF-12049: -------------------------------- Summary: Richfaces Kitchensink Archetype Key: RF-12049 URL: https://issues.jboss.org/browse/RF-12049 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Environment: JBDS 5 Beta 1 Reporter: Burr Sutter The currently generated RichFaces-based kitchensink project "richfaces-webapp" throws the following exception when Run As JUnit Test is used. 21:36:27,147 ERROR [org.jboss.ejb3.invocation] (http-localhost-127.0.0.1-8080-7) JBAS014134: EJB Invocation failed on component MemberRegistration for method public void org.jboss.tools.examples.controller.MemberRegistration.register() throws java.lang.Exception: javax.ejb.EJBException: org.jboss.weld.exceptions.IllegalProductException: WELD-000052 Cannot return null from a non-dependent producer method: [method] @Produces @RequestScoped public org.jboss.tools.examples.util.Resources.produceFacesContext() at org.jboss.as.ejb3.tx.CMTTxInterceptor.handleExceptionInOurTx(CMTTxInterceptor.java:166) [jboss-as-ejb3-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1] at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:230) [jboss-as-ejb3-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1] at org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:304) [jboss-as-ejb3-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1] at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:190) [jboss-as-ejb3-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 14 21:41:47 2012 From: jira-events at lists.jboss.org (Burr Sutter (JIRA)) Date: Wed, 14 Mar 2012 21:41:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12049) Richfaces Kitchensink Archetype In-Reply-To: <298774079.10572.1331775587398.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <10456223.10575.1331775707284.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burr Sutter updated RF-12049: ----------------------------- Attachment: richfaces_junit_failure.png > Richfaces Kitchensink Archetype > ------------------------------- > > Key: RF-12049 > URL: https://issues.jboss.org/browse/RF-12049 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Environment: JBDS 5 Beta 1 > Reporter: Burr Sutter > Attachments: richfaces_junit_failure.png > > > The currently generated RichFaces-based kitchensink project "richfaces-webapp" throws the following exception when Run As JUnit Test is used. > 21:36:27,147 ERROR [org.jboss.ejb3.invocation] (http-localhost-127.0.0.1-8080-7) JBAS014134: EJB Invocation failed on component MemberRegistration for method public void org.jboss.tools.examples.controller.MemberRegistration.register() throws java.lang.Exception: javax.ejb.EJBException: org.jboss.weld.exceptions.IllegalProductException: WELD-000052 Cannot return null from a non-dependent producer method: [method] @Produces @RequestScoped public org.jboss.tools.examples.util.Resources.produceFacesContext() > at org.jboss.as.ejb3.tx.CMTTxInterceptor.handleExceptionInOurTx(CMTTxInterceptor.java:166) [jboss-as-ejb3-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1] > at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:230) [jboss-as-ejb3-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1] > at org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:304) [jboss-as-ejb3-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1] > at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:190) [jboss-as-ejb3-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 14 21:58:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 14 Mar 2012 21:58:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12029) AbstractTogglePanel should extend UIRepeat, instead of UIOutput In-Reply-To: <1430073926.75557.1331161056577.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1888648196.10613.1331776727313.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12676931#comment-12676931 ] Brian Leathem commented on RF-12029: ------------------------------------ The TogglePanelRenderer#doDecode method calls the TabPanelRenderer#isSubmitted method before adding the panel renderId to the PartialViewContext#renderIds. On the first tab submit, TabPanelRenderer#isSubmitted returns false, because the call: {code:title=TabPanelRenderer, line:90} panel.getItem(panel.getSubmittedActiveItem()) {code} Does not return a panel item that corresponds to the parameter. The method/visitor that retrieves the tab panels by number needs to be looked at more closely, and corrected. > AbstractTogglePanel should extend UIRepeat, instead of UIOutput > --------------------------------------------------------------- > > Key: RF-12029 > URL: https://issues.jboss.org/browse/RF-12029 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-output > Reporter: Brian Leathem > Assignee: Bernard Labno > > Valid uses exist for dynamically generating rich:tab, rich:togglePanelItem, rich:accordionItem. Current techniques for supporting this use case involve using c:forEach, which is a problem since c: tags are processed too early to nicely support dynamic use cases. > One idea to support this use case, is to have AbstractTogglePanel extend UIRepeat, instead of UIOutput to better dynamic child components. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 15 06:11:48 2012 From: jira-events at lists.jboss.org (Navdeep Thakur (JIRA)) Date: Thu, 15 Mar 2012 06:11:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-5765) ExtendedDataTable: Drag and Drop for columns does not work if column id contain '-' symbol. In-Reply-To: <19172308.1232104144307.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <1832594552.11155.1331806308152.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-5765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12676981#comment-12676981 ] Navdeep Thakur commented on RF-5765: ------------------------------------ i have denied some values to all columns, but still its not working. > ExtendedDataTable: Drag and Drop for columns does not work if column id contain '-' symbol. > ------------------------------------------------------------------------------------------- > > Key: RF-5765 > URL: https://issues.jboss.org/browse/RF-5765 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 3.3.0 > Environment: RF 3.3.0 > Reporter: Andrei Markavtsov > Priority: Minor > Fix For: 3.Future > > > > > sortBy="#{row[ind]}" > sortOrder="#{column.ordering}" > filterBy="#{row[ind]}" > filterValue="#{column.filterValue}" > id="column-#{column.name}" > value="#{test3.columns}" > label="#{column.name}" > var="column" > index="ind"> > > > > > > > > Erroneus code: AbstractExtendedTableRenderer.doDecode(1239). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 15 08:09:48 2012 From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA)) Date: Thu, 15 Mar 2012 08:09:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11312) Output panel: ajaxRendered doesn't work with MyFaces In-Reply-To: <695776633.814.1313497097629.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <928392730.11400.1331813388544.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677007#comment-12677007 ] Pavol Pitonak commented on RF-11312: ------------------------------------ Works in the following configuration: {quote} RichFaces 4.2.1-SNAPSHOT Metamer 4.2.1-SNAPSHOT Apache MyFaces JSF-2.1 Core Impl 2.1.5 JBoss AS 7.1.1.Final OpenJDK Runtime Environment 1.6.0_24-b24 @ Linux Firefox 10.0.1 @ Linux x86_64 {quote} > Output panel: ajaxRendered doesn't work with MyFaces > ---------------------------------------------------- > > Key: RF-11312 > URL: https://issues.jboss.org/browse/RF-11312 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: compatibility > Affects Versions: 4.1.0.Milestone1 > Environment: RichFaces 4.1.0-SNAPSHOT r.d0f9c11eb0dacc1444c0a3182b12567e28aef6bc > Metamer 4.1.0-SNAPSHOT r.22629 > Apache MyFaces JSF-2.1 Core Impl 2.1.1 > Apache Tomcat 6.0.32 > OpenJDK Runtime Environment 1.6.0_22-b22 @Linux > Chrome 13.0.782.112 @ Linux i686 > Reporter: Pavol Pitonak > Labels: ci_issue > Fix For: 4.3-Tracking > > > # deploy Metamer with MyFaces to Tomcat 6.x > # open http://localhost:8080/metamer/faces/components/a4jOutputPanel/simple.xhtml > # click "Increase counter" button > result: > counter is not increased even if ajaxRendered=true, works fine with Mojarra -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 15 08:28:48 2012 From: jira-events at lists.jboss.org (Jean ANDRE (JIRA)) Date: Thu, 15 Mar 2012 08:28:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11763) javascript error : item is undefined on nested tabPanel with switchType='ajax' In-Reply-To: <984864127.56421.1322674601141.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1603447882.11426.1331814528414.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677011#comment-12677011 ] Jean ANDRE commented on RF-11763: --------------------------------- Hell guys, We have the pleasure to announce you that we have found the root cause of the problem early this morning. The problem is caused by the tag inside the searchClient.xhtml file. {code}

{code} To make the story short, the search screen was developed first, later we have implemented the nested tabs but the tabPanel did not work at all since the beginning. Then we thought it was a bug from the tabPanel and we reported the bug several months ago without testing the tapPanel outside our application (time constraint). Few days ago, we took thetime to test the tabPanel outside the application (see the workbench application) and we saw that nested tabPanel is running pretty well. Base on this fact, we decided to go deeper for trapping the bug by pruning unnecessary element, because this bug was a show stopper for us. Thank you to keep us inform about the real reason about this situation. Why a have an impact on tab switching. *Note 1:* replace by a works but we have to customized the layout. Best regards, > javascript error : item is undefined on nested tabPanel with switchType='ajax' > ------------------------------------------------------------------------------ > > Key: RF-11763 > URL: https://issues.jboss.org/browse/RF-11763 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.1.0.CR1 > Environment: Websphere 8 - RAD 8 - JSF Mojorra 2.1.4 - Spring 3.0.6 Final - Use @Inject @Named @SessionScoped as annotations - Firefox 7.0.1 - Windows 7 (6.1 sp1) - AspectJ 1.6.12 / AJDT > Reporter: Jean ANDRE > Priority: Blocker > Fix For: 4.Future > > Attachments: RF-11763Web.zip, RF-11763_ScreenShot.png, RF-11763_ScreenShot_malformedXML.png, RF-11763_ScreenShot_malformedXML.xml, RF-11763_ScreenShot_Undefined.png, screenshot-1.jpg > > > See also RF-11750 for the context. > Briefly, we have nested tabPanel - The firs tabPanel is made of static and dynamic tabPanel. One tabPanel contains the search form. When the user performs a search and for each search we open a new tab that contains the result list. When the user click on an item, we update the tab with the detailed information. > The detailed information is made of 6 tabs - There are like a subtabs from the parent tabs. When we set the switchType to 'client' the tab performs well. But as we want that the same tab serves as form to edit and view the detailed information, we want to refresh the tab to display the inputText instead of the outputText. This is the edit mode. > Then, we need to refresh the tab and we decided to pass in ajax switchType for theses subTab. Owener, switching to the 'ajax' triggers a javascript error that blocks the UI. None tab is selectable, user cannot switch from a tab to another tab. Moreover we failed to refresh the tab but the reason is still unknown. > Javascript error is : > {code} > item is undefined - [Stopper sur une erreur] if (!item.disabled && item.getName() === itemName) { > toggle...chfaces (ligne 363) > http://localhost:12000/crm/javax.faces.resource/togglePanel.js.jsf?ln=org.richfaces > {code} > The involved code is (where >>>> is): > {code} > /** > * @private > * */ > __getItemIndex : function (itemName) { > var item; > for (var i = 0; i < this.items.length; i++) { > item = this.items[i]; > >>>>>> if (!item.disabled && item.getName() === itemName) { > return i; > } > } > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 15 10:39:48 2012 From: jira-events at lists.jboss.org (Rene O (JIRA)) Date: Thu, 15 Mar 2012 10:39:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11763) javascript error : item is undefined on nested tabPanel with switchType='ajax' In-Reply-To: <984864127.56421.1322674601141.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1775506042.11697.1331822388112.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677053#comment-12677053 ] Rene O commented on RF-11763: ----------------------------- RF-12030 deals with a similar problem where rich:message is involved > javascript error : item is undefined on nested tabPanel with switchType='ajax' > ------------------------------------------------------------------------------ > > Key: RF-11763 > URL: https://issues.jboss.org/browse/RF-11763 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.1.0.CR1 > Environment: Websphere 8 - RAD 8 - JSF Mojorra 2.1.4 - Spring 3.0.6 Final - Use @Inject @Named @SessionScoped as annotations - Firefox 7.0.1 - Windows 7 (6.1 sp1) - AspectJ 1.6.12 / AJDT > Reporter: Jean ANDRE > Priority: Blocker > Fix For: 4.Future > > Attachments: RF-11763Web.zip, RF-11763_ScreenShot.png, RF-11763_ScreenShot_malformedXML.png, RF-11763_ScreenShot_malformedXML.xml, RF-11763_ScreenShot_Undefined.png, screenshot-1.jpg > > > See also RF-11750 for the context. > Briefly, we have nested tabPanel - The firs tabPanel is made of static and dynamic tabPanel. One tabPanel contains the search form. When the user performs a search and for each search we open a new tab that contains the result list. When the user click on an item, we update the tab with the detailed information. > The detailed information is made of 6 tabs - There are like a subtabs from the parent tabs. When we set the switchType to 'client' the tab performs well. But as we want that the same tab serves as form to edit and view the detailed information, we want to refresh the tab to display the inputText instead of the outputText. This is the edit mode. > Then, we need to refresh the tab and we decided to pass in ajax switchType for theses subTab. Owener, switching to the 'ajax' triggers a javascript error that blocks the UI. None tab is selectable, user cannot switch from a tab to another tab. Moreover we failed to refresh the tab but the reason is still unknown. > Javascript error is : > {code} > item is undefined - [Stopper sur une erreur] if (!item.disabled && item.getName() === itemName) { > toggle...chfaces (ligne 363) > http://localhost:12000/crm/javax.faces.resource/togglePanel.js.jsf?ln=org.richfaces > {code} > The involved code is (where >>>> is): > {code} > /** > * @private > * */ > __getItemIndex : function (itemName) { > var item; > for (var i = 0; i < this.items.length; i++) { > item = this.items[i]; > >>>>>> if (!item.disabled && item.getName() === itemName) { > return i; > } > } > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 15 10:48:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 15 Mar 2012 10:48:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11965) showcase - a4j:push - error thrown after creating topic for pushCdi In-Reply-To: <1869426390.30466.1328703648739.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <206025981.11719.1331822927679.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated RF-11965: ---------------------------- Fix Version/s: 4.2.1.CR1 > showcase - a4j:push - error thrown after creating topic for pushCdi > ------------------------------------------------------------------- > > Key: RF-11965 > URL: https://issues.jboss.org/browse/RF-11965 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll, showcase > Affects Versions: 4.2.0.Final > Environment: container: JBoss AS 7.1.0.CR1b > Reporter: Juraj Huska > Assignee: Luk?? Fry? > Priority: Minor > Fix For: 4.2.1.CR1 > > > When deploying showcase 4.2.0.CR1 then after pushCdi topic created an error is thrown: > {code} > 18:13:42,211 INFO [org.richfaces.demo.push.JMSInitializer] (MSC service thread 1-2) initializing > 18:13:42,219 INFO [org.richfaces.demo.push.JMSInitializer] (MSC service thread 1-2) AS7MessagingProviderManagement initialized > 18:13:42,219 INFO [org.richfaces.demo.push.JMSInitializer] (MSC service thread 1-2) creating topic pushJms > 18:13:42,761 INFO [org.richfaces.demo.push.JMSInitializer] (MSC service thread 1-2) creating topic pushTopicsContext > 18:13:42,802 INFO [org.richfaces.demo.push.JMSInitializer] (MSC service thread 1-2) creating topic pushCdi > 18:13:42,972 SEVERE [org.richfaces.demo.push.MessageProducerRunnable] (MessageProducerThread) javax.faces.FacesException: topic/pushTopicsContext -- service jboss.naming.context.java.topic.$ > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:397) [guava-10.0.1.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl.createTopic(JMSTopicsContextImpl.java:281) [richfaces-core-impl-4.2.0.CR1.jar:] > at org.richfaces.application.push.TopicsContext.getOrCreateTopic(TopicsContext.java:48) [richfaces-core-api-4.2.0.CR1.jar:] > at org.richfaces.application.push.TopicsContext.publish(TopicsContext.java:69) [richfaces-core-api-4.2.0.CR1.jar:] > at org.richfaces.demo.push.TopicsContextMessageProducer.sendMessage(TopicsContextMessageProducer.java:46) [classes:] > at org.richfaces.demo.push.MessageProducerRunnable.run(MessageProducerRunnable.java:57) [classes:] > at java.lang.Thread.run(Thread.java:662) [:1.6.0_22] > Caused by: javax.faces.FacesException: topic/pushTopicsContext -- service jboss.naming.context.java.topic.pushTopicsContext > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:207) [richfaces-core-impl-4.2.0.CR1.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:195) [richfaces-core-impl-4.2.0.CR1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingValueReference.compute(ComputingConcurrentHashMap.java:355) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.compute(ComputingConcurrentHashMap.java:184) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.getOrCompute(ComputingConcurrentHashMap.java:153) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap.getOrCompute(ComputingConcurrentHashMap.java:69) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:393) [guava-10.0.1.jar:] > ... 6 more > Caused by: javax.naming.NameNotFoundException: topic/pushTopicsContext -- service jboss.naming.context.java.topic.pushTopicsContext > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:92) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:177) > at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:87) > at javax.naming.InitialContext.lookup(InitialContext.java:396) [:1.6.0_22] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.lookupTopic(JMSTopicsContextImpl.java:94) [richfaces-core-impl-4.2.0-20120130.140419-26.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.start(JMSTopicsContextImpl.java:125) [richfaces-core-impl-4.2.0-20120130.140419-26.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:199) [richfaces-core-impl-4.2.0-20120130.140419-26.jar:] > ... 12 more > {code} > The functionality of push demos is fine, just the tests are not passing on Hudson, which I have to investigate whether it is caused by this one. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 15 10:52:50 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 15 Mar 2012 10:52:50 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11965) showcase - a4j:push - error thrown after creating topic for pushCdi In-Reply-To: <1869426390.30466.1328703648739.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1457553822.11743.1331823170179.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677064#comment-12677064 ] Luk?? Fry? commented on RF-11965: --------------------------------- We should do this: * provide only warning "the JMS is not available yet" * check if debug is enabled in logger - then show the exception > showcase - a4j:push - error thrown after creating topic for pushCdi > ------------------------------------------------------------------- > > Key: RF-11965 > URL: https://issues.jboss.org/browse/RF-11965 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll, showcase > Affects Versions: 4.2.0.Final > Environment: container: JBoss AS 7.1.0.CR1b > Reporter: Juraj Huska > Assignee: Luk?? Fry? > Priority: Minor > Fix For: 4.2.1.CR1 > > > When deploying showcase 4.2.0.CR1 then after pushCdi topic created an error is thrown: > {code} > 18:13:42,211 INFO [org.richfaces.demo.push.JMSInitializer] (MSC service thread 1-2) initializing > 18:13:42,219 INFO [org.richfaces.demo.push.JMSInitializer] (MSC service thread 1-2) AS7MessagingProviderManagement initialized > 18:13:42,219 INFO [org.richfaces.demo.push.JMSInitializer] (MSC service thread 1-2) creating topic pushJms > 18:13:42,761 INFO [org.richfaces.demo.push.JMSInitializer] (MSC service thread 1-2) creating topic pushTopicsContext > 18:13:42,802 INFO [org.richfaces.demo.push.JMSInitializer] (MSC service thread 1-2) creating topic pushCdi > 18:13:42,972 SEVERE [org.richfaces.demo.push.MessageProducerRunnable] (MessageProducerThread) javax.faces.FacesException: topic/pushTopicsContext -- service jboss.naming.context.java.topic.$ > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:397) [guava-10.0.1.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl.createTopic(JMSTopicsContextImpl.java:281) [richfaces-core-impl-4.2.0.CR1.jar:] > at org.richfaces.application.push.TopicsContext.getOrCreateTopic(TopicsContext.java:48) [richfaces-core-api-4.2.0.CR1.jar:] > at org.richfaces.application.push.TopicsContext.publish(TopicsContext.java:69) [richfaces-core-api-4.2.0.CR1.jar:] > at org.richfaces.demo.push.TopicsContextMessageProducer.sendMessage(TopicsContextMessageProducer.java:46) [classes:] > at org.richfaces.demo.push.MessageProducerRunnable.run(MessageProducerRunnable.java:57) [classes:] > at java.lang.Thread.run(Thread.java:662) [:1.6.0_22] > Caused by: javax.faces.FacesException: topic/pushTopicsContext -- service jboss.naming.context.java.topic.pushTopicsContext > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:207) [richfaces-core-impl-4.2.0.CR1.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:195) [richfaces-core-impl-4.2.0.CR1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingValueReference.compute(ComputingConcurrentHashMap.java:355) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.compute(ComputingConcurrentHashMap.java:184) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.getOrCompute(ComputingConcurrentHashMap.java:153) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap.getOrCompute(ComputingConcurrentHashMap.java:69) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:393) [guava-10.0.1.jar:] > ... 6 more > Caused by: javax.naming.NameNotFoundException: topic/pushTopicsContext -- service jboss.naming.context.java.topic.pushTopicsContext > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:92) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:177) > at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:87) > at javax.naming.InitialContext.lookup(InitialContext.java:396) [:1.6.0_22] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.lookupTopic(JMSTopicsContextImpl.java:94) [richfaces-core-impl-4.2.0-20120130.140419-26.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.start(JMSTopicsContextImpl.java:125) [richfaces-core-impl-4.2.0-20120130.140419-26.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:199) [richfaces-core-impl-4.2.0-20120130.140419-26.jar:] > ... 12 more > {code} > The functionality of push demos is fine, just the tests are not passing on Hudson, which I have to investigate whether it is caused by this one. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 15 11:02:47 2012 From: jira-events at lists.jboss.org (Jean ANDRE (JIRA)) Date: Thu, 15 Mar 2012 11:02:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11763) javascript error : item is undefined on nested tabPanel with switchType='ajax' In-Reply-To: <984864127.56421.1322674601141.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1879852129.11762.1331823767363.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677067#comment-12677067 ] Jean ANDRE commented on RF-11763: --------------------------------- *Note 1:* Where ever is the inside the search form, the error is triggered during the tab switching. If you put a calendar with a we reproduce the error: {code} {code} replaced by: {code} {code} *Note 2:* If the rich:message is inside the tabPanel, it does not trigger the error (at least the same error) because we got a new message when we closing the sub-tabs since there are in ajax mode. This new message did not appear when the sub-tabs are in server or client mode. If it is comfirmed, he will probably open a new bug report. > javascript error : item is undefined on nested tabPanel with switchType='ajax' > ------------------------------------------------------------------------------ > > Key: RF-11763 > URL: https://issues.jboss.org/browse/RF-11763 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.1.0.CR1 > Environment: Websphere 8 - RAD 8 - JSF Mojorra 2.1.4 - Spring 3.0.6 Final - Use @Inject @Named @SessionScoped as annotations - Firefox 7.0.1 - Windows 7 (6.1 sp1) - AspectJ 1.6.12 / AJDT > Reporter: Jean ANDRE > Priority: Blocker > Fix For: 4.Future > > Attachments: RF-11763Web.zip, RF-11763_ScreenShot.png, RF-11763_ScreenShot_malformedXML.png, RF-11763_ScreenShot_malformedXML.xml, RF-11763_ScreenShot_Undefined.png, screenshot-1.jpg > > > See also RF-11750 for the context. > Briefly, we have nested tabPanel - The firs tabPanel is made of static and dynamic tabPanel. One tabPanel contains the search form. When the user performs a search and for each search we open a new tab that contains the result list. When the user click on an item, we update the tab with the detailed information. > The detailed information is made of 6 tabs - There are like a subtabs from the parent tabs. When we set the switchType to 'client' the tab performs well. But as we want that the same tab serves as form to edit and view the detailed information, we want to refresh the tab to display the inputText instead of the outputText. This is the edit mode. > Then, we need to refresh the tab and we decided to pass in ajax switchType for theses subTab. Owener, switching to the 'ajax' triggers a javascript error that blocks the UI. None tab is selectable, user cannot switch from a tab to another tab. Moreover we failed to refresh the tab but the reason is still unknown. > Javascript error is : > {code} > item is undefined - [Stopper sur une erreur] if (!item.disabled && item.getName() === itemName) { > toggle...chfaces (ligne 363) > http://localhost:12000/crm/javax.faces.resource/togglePanel.js.jsf?ln=org.richfaces > {code} > The involved code is (where >>>> is): > {code} > /** > * @private > * */ > __getItemIndex : function (itemName) { > var item; > for (var i = 0; i < this.items.length; i++) { > item = this.items[i]; > >>>>>> if (!item.disabled && item.getName() === itemName) { > return i; > } > } > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 15 11:17:47 2012 From: jira-events at lists.jboss.org (Jean ANDRE (JIRA)) Date: Thu, 15 Mar 2012 11:17:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11763) javascript error : item is undefined on nested tabPanel with switchType='ajax' In-Reply-To: <984864127.56421.1322674601141.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <999256985.11778.1331824667721.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677011#comment-12677011 ] Jean ANDRE edited comment on RF-11763 at 3/15/12 11:16 AM: ----------------------------------------------------------- Hell guys, We have the pleasure to announce you that we have found the root cause of the problem early this morning. The problem is caused by the tag inside the searchClient.xhtml file. {code}

{code} To make the story short, the search screen was developed first, later we have implemented the nested tabs but the tabPanel did not work at all since the beginning. Then we thought it was a bug from the tabPanel and we reported the bug several months ago without testing the tapPanel outside our application (time constraint). Few days ago, we took thetime to test the tabPanel outside the application (see the workbench application) and we saw that nested tabPanel is running pretty well. Based on this fact, we decided to go deeper for trapping the bug by pruning unnecessary element, because this bug was a show stopper for us at this point of time of the project. Thank you to keep us inform about the real reason about this situation. Why a have an impact on tab switching. *Note 1:* replace by a works but we have to customized the layout. Best regards, was (Author: jorelia64): Hell guys, We have the pleasure to announce you that we have found the root cause of the problem early this morning. The problem is caused by the tag inside the searchClient.xhtml file. {code}

{code} To make the story short, the search screen was developed first, later we have implemented the nested tabs but the tabPanel did not work at all since the beginning. Then we thought it was a bug from the tabPanel and we reported the bug several months ago without testing the tapPanel outside our application (time constraint). Few days ago, we took thetime to test the tabPanel outside the application (see the workbench application) and we saw that nested tabPanel is running pretty well. Base on this fact, we decided to go deeper for trapping the bug by pruning unnecessary element, because this bug was a show stopper for us. Thank you to keep us inform about the real reason about this situation. Why a have an impact on tab switching. *Note 1:* replace by a works but we have to customized the layout. Best regards, > javascript error : item is undefined on nested tabPanel with switchType='ajax' > ------------------------------------------------------------------------------ > > Key: RF-11763 > URL: https://issues.jboss.org/browse/RF-11763 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.1.0.CR1 > Environment: Websphere 8 - RAD 8 - JSF Mojorra 2.1.4 - Spring 3.0.6 Final - Use @Inject @Named @SessionScoped as annotations - Firefox 7.0.1 - Windows 7 (6.1 sp1) - AspectJ 1.6.12 / AJDT > Reporter: Jean ANDRE > Priority: Blocker > Fix For: 4.Future > > Attachments: RF-11763Web.zip, RF-11763_ScreenShot.png, RF-11763_ScreenShot_malformedXML.png, RF-11763_ScreenShot_malformedXML.xml, RF-11763_ScreenShot_Undefined.png, screenshot-1.jpg > > > See also RF-11750 for the context. > Briefly, we have nested tabPanel - The firs tabPanel is made of static and dynamic tabPanel. One tabPanel contains the search form. When the user performs a search and for each search we open a new tab that contains the result list. When the user click on an item, we update the tab with the detailed information. > The detailed information is made of 6 tabs - There are like a subtabs from the parent tabs. When we set the switchType to 'client' the tab performs well. But as we want that the same tab serves as form to edit and view the detailed information, we want to refresh the tab to display the inputText instead of the outputText. This is the edit mode. > Then, we need to refresh the tab and we decided to pass in ajax switchType for theses subTab. Owener, switching to the 'ajax' triggers a javascript error that blocks the UI. None tab is selectable, user cannot switch from a tab to another tab. Moreover we failed to refresh the tab but the reason is still unknown. > Javascript error is : > {code} > item is undefined - [Stopper sur une erreur] if (!item.disabled && item.getName() === itemName) { > toggle...chfaces (ligne 363) > http://localhost:12000/crm/javax.faces.resource/togglePanel.js.jsf?ln=org.richfaces > {code} > The involved code is (where >>>> is): > {code} > /** > * @private > * */ > __getItemIndex : function (itemName) { > var item; > for (var i = 0; i < this.items.length; i++) { > item = this.items[i]; > >>>>>> if (!item.disabled && item.getName() === itemName) { > return i; > } > } > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 15 11:19:47 2012 From: jira-events at lists.jboss.org (Jean ANDRE (JIRA)) Date: Thu, 15 Mar 2012 11:19:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12030) rich:dataScroller doesn't work if a rich:message exists inside of a collapsed rich:collapsiblePanel with switchType='ajax' In-Reply-To: <474795285.76394.1331197237559.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1857540314.11786.1331824787316.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677071#comment-12677071 ] Jean ANDRE commented on RF-12030: --------------------------------- Link to RF-11763 for another similar case - Thank you very much Rene as we are not alone ! ;) > rich:dataScroller doesn't work if a rich:message exists inside of a collapsed rich:collapsiblePanel with switchType='ajax' > -------------------------------------------------------------------------------------------------------------------------- > > Key: RF-12030 > URL: https://issues.jboss.org/browse/RF-12030 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.2.0.Final > Environment: tomcat 7, richfaces-4.2.0.Final, myfaces-2.1.6 > Reporter: Rene O > > rich:dataScroller doesn't work if a rich:message exists inside of a collapsed rich:collapsiblePanel with switchType='ajax' > Steps to reproduce this issue: > 1. use dataScroller to switch table-pages. you can see, that this works. > 2. collaps collapsiblePanel > 3. if collapsiblePanel is collapsed, the dataScroller doesn't react anymore. > 4. if you use switchType='client' everything works correct > {code:title=examplepage.xhtml} > > xmlns:h="http://java.sun.com/jsf/html" > xmlns:f="http://java.sun.com/jsf/core" > xmlns:ui="http://java.sun.com/jsf/facelets" > xmlns:a4j="http://richfaces.org/a4j" > xmlns:rich="http://richfaces.org/rich" > > > > JSF Test > > > > > > > > if rich:message doesn't exists, everything works... > > > > var="item" value="#{model.tableList}" > rows="5" style="width:350px;"> > > > > > > ColA > > #{item.itemA} > > > > > > > > > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 15 11:39:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 15 Mar 2012 11:39:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12029) AbstractTogglePanel should extend UIRepeat, instead of UIOutput In-Reply-To: <1430073926.75557.1331161056577.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <663398414.11832.1331825987608.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677078#comment-12677078 ] Luk?? Fry? commented on RF-12029: --------------------------------- There is feature request for very similar concept: RF-9443 from forum reference: {quote} {code} #{category.value} {code} {quote} The proposed API seems better, since it * allows to combine static and dynamic tabs * separates the iteration and switchable panel logic > AbstractTogglePanel should extend UIRepeat, instead of UIOutput > --------------------------------------------------------------- > > Key: RF-12029 > URL: https://issues.jboss.org/browse/RF-12029 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-output > Reporter: Brian Leathem > Assignee: Bernard Labno > > Valid uses exist for dynamically generating rich:tab, rich:togglePanelItem, rich:accordionItem. Current techniques for supporting this use case involve using c:forEach, which is a problem since c: tags are processed too early to nicely support dynamic use cases. > One idea to support this use case, is to have AbstractTogglePanel extend UIRepeat, instead of UIOutput to better dynamic child components. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 15 11:39:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 15 Mar 2012 11:39:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12029) AbstractTogglePanel should extend UIRepeat, instead of UIOutput In-Reply-To: <1430073926.75557.1331161056577.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <175942638.11835.1331825987751.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677078#comment-12677078 ] Luk?? Fry? edited comment on RF-12029 at 3/15/12 11:39 AM: ----------------------------------------------------------- There is feature request for very similar concept: RF-9443 from forum reference: {quote} {code} #{category.value} {code} {quote} The proposed API seems better, since it * allows to combine static and dynamic tabs * separates the iteration and switchable panel logic (we can discuss the other approach in RF-9443) was (Author: lfryc): There is feature request for very similar concept: RF-9443 from forum reference: {quote} {code} #{category.value} {code} {quote} The proposed API seems better, since it * allows to combine static and dynamic tabs * separates the iteration and switchable panel logic > AbstractTogglePanel should extend UIRepeat, instead of UIOutput > --------------------------------------------------------------- > > Key: RF-12029 > URL: https://issues.jboss.org/browse/RF-12029 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-output > Reporter: Brian Leathem > Assignee: Bernard Labno > > Valid uses exist for dynamically generating rich:tab, rich:togglePanelItem, rich:accordionItem. Current techniques for supporting this use case involve using c:forEach, which is a problem since c: tags are processed too early to nicely support dynamic use cases. > One idea to support this use case, is to have AbstractTogglePanel extend UIRepeat, instead of UIOutput to better dynamic child components. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 15 12:56:48 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 15 Mar 2012 12:56:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12050) a4j:push - rename address attribute to topic to match with the TopicKey class Message-ID: <1897165669.12129.1331830608725.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Luk?? Fry? created RF-12050: ------------------------------- Summary: a4j:push - rename address attribute to topic to match with the TopicKey class Key: RF-12050 URL: https://issues.jboss.org/browse/RF-12050 Project: RichFaces Issue Type: Enhancement Security Level: Public (Everyone can see) Components: component-push/poll Affects Versions: 4.2.0.Final Reporter: Luk?? Fry? Priority: Minor {{a4j:push}} has currently attribute {{address}}, which does not match the name in Java implementation: {{TopicKey}} and {{@Push(topic=...)}}. It would be nice to provide new attribute {{topic}}. To make it backward compatible, we can use alias of the attribute. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 15 12:58:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 15 Mar 2012 12:58:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12050) a4j:push - rename address attribute to topic to match with the TopicKey class In-Reply-To: <1897165669.12129.1331830608725.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1593182074.12132.1331830727846.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated RF-12050: ---------------------------- Fix Version/s: 4.3-Tracking > a4j:push - rename address attribute to topic to match with the TopicKey class > ----------------------------------------------------------------------------- > > Key: RF-12050 > URL: https://issues.jboss.org/browse/RF-12050 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-push/poll > Affects Versions: 4.2.0.Final > Reporter: Luk?? Fry? > Priority: Minor > Fix For: 4.3-Tracking > > > {{a4j:push}} has currently attribute {{address}}, which does not match the name in Java implementation: {{TopicKey}} and {{@Push(topic=...)}}. > It would be nice to provide new attribute {{topic}}. > To make it backward compatible, we can use alias of the attribute. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 15 13:00:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 15 Mar 2012 13:00:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12051) Showcase: simplified Push CDI sample which wouldn't use subtopics In-Reply-To: <1777587358.12158.1331830847464.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1895426656.12159.1331830847501.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated RF-12051: ---------------------------- Description: Push CDI sample in Showcase is currently quite complex and people run into issues when starting to use it, because there is usage of subtopics. There are two alternative ways how to address it: 1. simplify current sample 2. provide new sample as alternative to this one was: Push CDI sample in Showcase is currently quite complex and people run into issues when starting to use it, there are two alternative ways how to address it: 1. simplify current sample 2. provide new sample as alternative to this one > Showcase: simplified Push CDI sample which wouldn't use subtopics > ----------------------------------------------------------------- > > Key: RF-12051 > URL: https://issues.jboss.org/browse/RF-12051 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: showcase > Affects Versions: 4.2.0.Final > Reporter: Luk?? Fry? > > Push CDI sample in Showcase is currently quite complex and people run into issues when starting to use it, > because there is usage of subtopics. > There are two alternative ways how to address it: > 1. simplify current sample > 2. provide new sample as alternative to this one -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 15 13:00:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 15 Mar 2012 13:00:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12051) Showcase: simplified Push CDI sample which wouldn't use subtopics Message-ID: <1777587358.12158.1331830847464.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Luk?? Fry? created RF-12051: ------------------------------- Summary: Showcase: simplified Push CDI sample which wouldn't use subtopics Key: RF-12051 URL: https://issues.jboss.org/browse/RF-12051 Project: RichFaces Issue Type: Enhancement Security Level: Public (Everyone can see) Components: showcase Affects Versions: 4.2.0.Final Reporter: Luk?? Fry? Push CDI sample in Showcase is currently quite complex and people run into issues when starting to use it, there are two alternative ways how to address it: 1. simplify current sample 2. provide new sample as alternative to this one -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 15 13:16:50 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 15 Mar 2012 13:16:50 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12007) AbstractPanelMenuGroup.getChangeExpandListener is not used In-Reply-To: <1007334631.44779.1330344037133.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1380959155.12230.1331831810038.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? reassigned RF-12007: ------------------------------- Assignee: Luk?? Fry? > AbstractPanelMenuGroup.getChangeExpandListener is not used > ---------------------------------------------------------- > > Key: RF-12007 > URL: https://issues.jboss.org/browse/RF-12007 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.2.0.Final > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Priority: Minor > Fix For: 4.2.1.CR1 > > > There is no such listener/event defined in the project. > I suggest to remove this attribute in 4.2.x. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 15 14:47:47 2012 From: jira-events at lists.jboss.org (Jean ANDRE (JIRA)) Date: Thu, 15 Mar 2012 14:47:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12052) rich:TabPanel - HTML comments should be supported inside the tabPanel Message-ID: <1018200636.12395.1331837267498.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Jean ANDRE created RF-12052: ------------------------------- Summary: rich:TabPanel - HTML comments should be supported inside the tabPanel Key: RF-12052 URL: https://issues.jboss.org/browse/RF-12052 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Jean ANDRE Is it possible to support HTML comment inside a tabPanel. Because it causes this error if we but comments as shown below. The error is: E org.richfaces.context.ExtendedPartialViewContextImpl processPartialExecutePhase java.lang.IllegalArgumentException at org.richfaces.component.AbstractTogglePanel.getChildName(AbstractTogglePanel.java:490) {code} {code} Thank you. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 15 15:24:47 2012 From: jira-events at lists.jboss.org (Andrew Cheung (JIRA)) Date: Thu, 15 Mar 2012 15:24:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12053) Picklist : valueChangeListener does not work when user moves items between left and right sides Message-ID: <1447430929.12435.1331839487826.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Andrew Cheung created RF-12053: ---------------------------------- Summary: Picklist : valueChangeListener does not work when user moves items between left and right sides Key: RF-12053 URL: https://issues.jboss.org/browse/RF-12053 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-selects Affects Versions: 3.3.3.Final Environment: RichFaces 3.3.3Final JBOSS EPP5.1.1 browsers : Firefox 10.0.2 and IE8 Reporter: Andrew Cheung The valueChangeListener for picklist does not fire when a user moves items between the left and right hand sides of the picklist. Code as follows: index.xhtml: ----------------- In the bean (myBean.java): private List selectedAuxOffices = null; //for picklist right hand side private ArrayList auxOffices = null; public List getSelectedAuxOffices() { return selectedAuxOffices; } public void setSelectedAuxOffices(List selectedAuxOffices) { this.selectedAuxOffices = selectedAuxOffices; } public ArrayList getAuxOffices() { return auxOffices; } public void setAuxOffices(ArrayList auxOffices) { this.auxOffices = auxOffices; } public UA() throws java.lang.Exception { initializeMyBean(); } private void initializeMyBean() throws java.lang.Exception { .... auxOffices = demo.createSIList(...); //retrieves the list of available offices from the database //get selected attribute values on the right side of the picklist List userSelectedAuxOffices = createSIBeanList(...); //retrieves the list of selected offices from the database if (selectedAuxOffices == null) { selectedAuxOffices = new ArrayList(); } if (auxOffices == null) { auxOffices = new ArrayList(); } selectedAuxOffices = userSelectedAuxOffices; } public void markOfficesModified(ValueChangeEvent event) { ArrayList auxOfficesBeanChanged = (ArrayList)event.getNewValue(); String[] auxOfficesChanged = new String[auxOfficesBeanChanged.size()]; int i = 0; for (SIBean sib : auxOfficesBeanChanged) { auxOfficesChanged[i] = sib.getValue(); _Logger.error("DEBUGXXX : auxOfficesChanged = " + auxOfficesChanged[i]); i++; } } ------------------- Code in SIBean.java : import org.apache.commons.lang.builder.EqualsBuilder; import org.apache.log4j.Logger; public class SIBean { private String label; private String value; public SIBean(String newlabel, String newvalue){ label = newlabel; value = newvalue; } public SIBean(){ label = ""; value = ""; } public String getLabel() { return label; } public void setLabel(String label) { this.label = label; } public String getValue() { return value; } public void setValue(String value) { this.value = value; } public boolean equals(Object obj) { if (obj == null) return false; if (obj == this) return true; if (obj.getClass() != getClass()) return false; SIBean rib = (SIBean) obj; return new EqualsBuilder(). append(value, rib.value). isEquals(); } } -------------- Code in converter : import javax.faces.component.UIComponent; import javax.faces.context.FacesContext; import javax.faces.convert.Converter; import org.apache.log4j.Logger; import demo.SIBean; public class SIBeanConverter implements Converter { @Override public Object getAsObject(FacesContext arg0, UIComponent arg1, String arg2) { // TODO Auto-generated method stub int index = arg2.indexOf(':'); if (index == -1) { return new SIBean(arg2,arg2); //workaround for index out of range issue (arg2 should contain "label:value"; but sometimes it only contain "value" due to the bug reported in JIRA) } else { return new SIBean(arg2.substring(0, index), arg2.substring(index + 1)); } } @Override public String getAsString(FacesContext arg0, UIComponent arg1, Object arg2) { // TODO Auto-generated method stub if (arg2 instanceof SIBean) { return ((SIBean)arg2).getLabel() + ":" + ((SIBean)arg2).getValue(); } else { return arg2.toString(); } } } ---------------------- faces-config.xml : sibcvtr demo.SIBeanConverter myBean myBean demo.myBean session ------------------------- -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 15 15:30:47 2012 From: jira-events at lists.jboss.org (Jean ANDRE (JIRA)) Date: Thu, 15 Mar 2012 15:30:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12052) rich:TabPanel - HTML comments should be supported inside the tabPanel In-Reply-To: <1018200636.12395.1331837267498.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <256258410.12449.1331839847402.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean ANDRE updated RF-12052: ---------------------------- Description: Is it possible to support HTML comment inside a tabPanel. Because it causes this error if we but comments as shown below. The error is: E org.richfaces.context.ExtendedPartialViewContextImpl processPartialExecutePhase java.lang.IllegalArgumentException at org.richfaces.component.AbstractTogglePanel.getChildName(AbstractTogglePanel.java:490) {code} {code} Or at least, give us a clear error message as we did for tabPanel and the form tag. Thank you. was: Is it possible to support HTML comment inside a tabPanel. Because it causes this error if we but comments as shown below. The error is: E org.richfaces.context.ExtendedPartialViewContextImpl processPartialExecutePhase java.lang.IllegalArgumentException at org.richfaces.component.AbstractTogglePanel.getChildName(AbstractTogglePanel.java:490) {code} {code} Thank you. > rich:TabPanel - HTML comments should be supported inside the tabPanel > --------------------------------------------------------------------- > > Key: RF-12052 > URL: https://issues.jboss.org/browse/RF-12052 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Jean ANDRE > > Is it possible to support HTML comment inside a tabPanel. Because it causes this error if we but comments as shown below. The error is: > E org.richfaces.context.ExtendedPartialViewContextImpl processPartialExecutePhase > java.lang.IllegalArgumentException > at org.richfaces.component.AbstractTogglePanel.getChildName(AbstractTogglePanel.java:490) > {code} > switchType="ajax" > headerPosition="top" > itemChangeListener="#{viewItemController.doItemChangeListener}" > activeItem="#{viewItemController.activeTab}" > immediate="true"> > > > > > > {code} > Or at least, give us a clear error message as we did for tabPanel and the form tag. > Thank you. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 15 17:06:47 2012 From: jira-events at lists.jboss.org (Andrew Cheung (JIRA)) Date: Thu, 15 Mar 2012 17:06:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12053) Picklist : valueChangeListener does not work when user moves items between left and right sides In-Reply-To: <1447430929.12435.1331839487826.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1791510741.12533.1331845607424.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Cheung updated RF-12053: ------------------------------- Forum Reference: https://community.jboss.org/message/628865#628865 (was: https://community.jboss.org/message/628865#628865) I found an explanation to the behaviour: Moving items between the left and right hand side are client side and therefore the event is not triggered. The event is triggered on submit. To the administrator of bug reports : Please cancel this bug report. Thanks. > Picklist : valueChangeListener does not work when user moves items between left and right sides > ----------------------------------------------------------------------------------------------- > > Key: RF-12053 > URL: https://issues.jboss.org/browse/RF-12053 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 3.3.3.Final > Environment: RichFaces 3.3.3Final > JBOSS EPP5.1.1 > browsers : Firefox 10.0.2 and IE8 > Reporter: Andrew Cheung > Labels: picklist, valueChangeListener > > The valueChangeListener for picklist does not fire when a user moves items between the left and right hand sides of the picklist. > Code as follows: > index.xhtml: > > > > > > > > ----------------- > In the bean (myBean.java): > private List selectedAuxOffices = null; //for picklist right hand side > private ArrayList auxOffices = null; > public List getSelectedAuxOffices() { > return selectedAuxOffices; > } > public void setSelectedAuxOffices(List selectedAuxOffices) { > this.selectedAuxOffices = selectedAuxOffices; > } > > public ArrayList getAuxOffices() { > return auxOffices; > } > public void setAuxOffices(ArrayList auxOffices) { > this.auxOffices = auxOffices; > } > public UA() throws java.lang.Exception { > initializeMyBean(); > > > } > private void initializeMyBean() throws java.lang.Exception { > .... > auxOffices = demo.createSIList(...); //retrieves the list of available offices from the database > > //get selected attribute values on the right side of the picklist > List userSelectedAuxOffices = createSIBeanList(...); //retrieves the list of selected offices from the database > if (selectedAuxOffices == null) { > selectedAuxOffices = new ArrayList(); > } > > if (auxOffices == null) { > auxOffices = new ArrayList(); > } > > selectedAuxOffices = userSelectedAuxOffices; > } > public void markOfficesModified(ValueChangeEvent event) { > ArrayList auxOfficesBeanChanged = (ArrayList)event.getNewValue(); > String[] auxOfficesChanged = new String[auxOfficesBeanChanged.size()]; > int i = 0; > for (SIBean sib : auxOfficesBeanChanged) { > auxOfficesChanged[i] = sib.getValue(); > _Logger.error("DEBUGXXX : auxOfficesChanged = " + auxOfficesChanged[i]); > i++; > } > > } > > ------------------- > Code in SIBean.java : > > import org.apache.commons.lang.builder.EqualsBuilder; > import org.apache.log4j.Logger; > > > public class SIBean { > > private String label; > private String value; > > public SIBean(String newlabel, String newvalue){ > label = newlabel; > value = newvalue; > } > public SIBean(){ > label = ""; > value = ""; > } > > public String getLabel() { > return label; > } > public void setLabel(String label) { > this.label = label; > } > public String getValue() { > return value; > } > public void setValue(String value) { > this.value = value; > } > > public boolean equals(Object obj) { > > if (obj == null) > return false; > if (obj == this) > return true; > if (obj.getClass() != getClass()) > return false; > > SIBean rib = (SIBean) obj; > > return new EqualsBuilder(). > append(value, rib.value). > isEquals(); > > > } > > } > -------------- > Code in converter : > import javax.faces.component.UIComponent; > import javax.faces.context.FacesContext; > import javax.faces.convert.Converter; > > import org.apache.log4j.Logger; > > > import demo.SIBean; > > public class SIBeanConverter implements Converter { > > > @Override > public Object getAsObject(FacesContext arg0, UIComponent arg1, String arg2) { > // TODO Auto-generated method stub > > > int index = arg2.indexOf(':'); > if (index == -1) { > return new SIBean(arg2,arg2); //workaround for index out of range issue (arg2 should contain "label:value"; but sometimes it only contain "value" due to the bug reported in JIRA) > } > else { > return new SIBean(arg2.substring(0, index), arg2.substring(index + 1)); > } > > > } > > @Override > public String getAsString(FacesContext arg0, UIComponent arg1, Object arg2) { > // TODO Auto-generated method stub > if (arg2 instanceof SIBean) { > return ((SIBean)arg2).getLabel() + ":" + ((SIBean)arg2).getValue(); > } > else { > return arg2.toString(); > } > } > > } > ---------------------- > faces-config.xml : > > sibcvtr > demo.SIBeanConverter > > > myBean > myBean > demo.myBean > session > > ------------------------- -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 15 17:08:47 2012 From: jira-events at lists.jboss.org (Andrew Cheung (JIRA)) Date: Thu, 15 Mar 2012 17:08:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12053) Picklist : valueChangeListener does not work when user moves items between left and right sides In-Reply-To: <1447430929.12435.1331839487826.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <273708621.12536.1331845727955.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Cheung closed RF-12053. ------------------------------ Resolution: Rejected Not a bug. It was due to the user's misunderstanding of the behaviour. > Picklist : valueChangeListener does not work when user moves items between left and right sides > ----------------------------------------------------------------------------------------------- > > Key: RF-12053 > URL: https://issues.jboss.org/browse/RF-12053 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 3.3.3.Final > Environment: RichFaces 3.3.3Final > JBOSS EPP5.1.1 > browsers : Firefox 10.0.2 and IE8 > Reporter: Andrew Cheung > Labels: picklist, valueChangeListener > > The valueChangeListener for picklist does not fire when a user moves items between the left and right hand sides of the picklist. > Code as follows: > index.xhtml: > > > > > > > > ----------------- > In the bean (myBean.java): > private List selectedAuxOffices = null; //for picklist right hand side > private ArrayList auxOffices = null; > public List getSelectedAuxOffices() { > return selectedAuxOffices; > } > public void setSelectedAuxOffices(List selectedAuxOffices) { > this.selectedAuxOffices = selectedAuxOffices; > } > > public ArrayList getAuxOffices() { > return auxOffices; > } > public void setAuxOffices(ArrayList auxOffices) { > this.auxOffices = auxOffices; > } > public UA() throws java.lang.Exception { > initializeMyBean(); > > > } > private void initializeMyBean() throws java.lang.Exception { > .... > auxOffices = demo.createSIList(...); //retrieves the list of available offices from the database > > //get selected attribute values on the right side of the picklist > List userSelectedAuxOffices = createSIBeanList(...); //retrieves the list of selected offices from the database > if (selectedAuxOffices == null) { > selectedAuxOffices = new ArrayList(); > } > > if (auxOffices == null) { > auxOffices = new ArrayList(); > } > > selectedAuxOffices = userSelectedAuxOffices; > } > public void markOfficesModified(ValueChangeEvent event) { > ArrayList auxOfficesBeanChanged = (ArrayList)event.getNewValue(); > String[] auxOfficesChanged = new String[auxOfficesBeanChanged.size()]; > int i = 0; > for (SIBean sib : auxOfficesBeanChanged) { > auxOfficesChanged[i] = sib.getValue(); > _Logger.error("DEBUGXXX : auxOfficesChanged = " + auxOfficesChanged[i]); > i++; > } > > } > > ------------------- > Code in SIBean.java : > > import org.apache.commons.lang.builder.EqualsBuilder; > import org.apache.log4j.Logger; > > > public class SIBean { > > private String label; > private String value; > > public SIBean(String newlabel, String newvalue){ > label = newlabel; > value = newvalue; > } > public SIBean(){ > label = ""; > value = ""; > } > > public String getLabel() { > return label; > } > public void setLabel(String label) { > this.label = label; > } > public String getValue() { > return value; > } > public void setValue(String value) { > this.value = value; > } > > public boolean equals(Object obj) { > > if (obj == null) > return false; > if (obj == this) > return true; > if (obj.getClass() != getClass()) > return false; > > SIBean rib = (SIBean) obj; > > return new EqualsBuilder(). > append(value, rib.value). > isEquals(); > > > } > > } > -------------- > Code in converter : > import javax.faces.component.UIComponent; > import javax.faces.context.FacesContext; > import javax.faces.convert.Converter; > > import org.apache.log4j.Logger; > > > import demo.SIBean; > > public class SIBeanConverter implements Converter { > > > @Override > public Object getAsObject(FacesContext arg0, UIComponent arg1, String arg2) { > // TODO Auto-generated method stub > > > int index = arg2.indexOf(':'); > if (index == -1) { > return new SIBean(arg2,arg2); //workaround for index out of range issue (arg2 should contain "label:value"; but sometimes it only contain "value" due to the bug reported in JIRA) > } > else { > return new SIBean(arg2.substring(0, index), arg2.substring(index + 1)); > } > > > } > > @Override > public String getAsString(FacesContext arg0, UIComponent arg1, Object arg2) { > // TODO Auto-generated method stub > if (arg2 instanceof SIBean) { > return ((SIBean)arg2).getLabel() + ":" + ((SIBean)arg2).getValue(); > } > else { > return arg2.toString(); > } > } > > } > ---------------------- > faces-config.xml : > > sibcvtr > demo.SIBeanConverter > > > myBean > myBean > demo.myBean > session > > ------------------------- -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 15 17:32:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Thu, 15 Mar 2012 17:32:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11872) Mobile Showcase and a4j:region demo: submit button doesn't respond on the first click In-Reply-To: <1714655772.52122.1326201429582.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <529298761.12560.1331847167382.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677154#comment-12677154 ] Brian Leathem commented on RF-11872: ------------------------------------ Confirmed with both a Samsung Galaxy S II, and the android emulator (v2.3.3) > Mobile Showcase and a4j:region demo: submit button doesn't respond on the first click > ------------------------------------------------------------------------------------- > > Key: RF-11872 > URL: https://issues.jboss.org/browse/RF-11872 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: mobile, showcase > Affects Versions: 4.2.0.CR1 > Environment: richfaces-showcase-4.1.1-20120106.230242-18 / richfaces-showcase-4.2.0-20120123.231757-13 > JBoss AS 7.0.2.Final / 7.1.0.Beta1 > Firefox 8.0 / Google Chrome 16.0.912.63 / Android 2.2 / iPhone 4.2.1 > Reporter: Jan Papousek > Assignee: Brian Leathem > Fix For: 4.2.1.CR1 > > Attachments: richfaces-showcase-4.2.0-20120123.231757-13-jbas7.war > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 15 19:00:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Thu, 15 Mar 2012 19:00:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11872) Mobile Showcase and a4j:region demo: submit button doesn't respond on the first click In-Reply-To: <1714655772.52122.1326201429582.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <102836158.12659.1331852447543.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677170#comment-12677170 ] Brian Leathem commented on RF-11872: ------------------------------------ Confirmed with Google Chrome 17, on the mobile view of the showcase: http://showcase.richfaces.org/phoneHome.jsf#region:region > Mobile Showcase and a4j:region demo: submit button doesn't respond on the first click > ------------------------------------------------------------------------------------- > > Key: RF-11872 > URL: https://issues.jboss.org/browse/RF-11872 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: mobile, showcase > Affects Versions: 4.2.0.CR1 > Environment: richfaces-showcase-4.1.1-20120106.230242-18 / richfaces-showcase-4.2.0-20120123.231757-13 > JBoss AS 7.0.2.Final / 7.1.0.Beta1 > Firefox 8.0 / Google Chrome 16.0.912.63 / Android 2.2 / iPhone 4.2.1 > Reporter: Jan Papousek > Assignee: Brian Leathem > Fix For: 4.2.1.CR1 > > Attachments: richfaces-showcase-4.2.0-20120123.231757-13-jbas7.war > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 15 19:28:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Thu, 15 Mar 2012 19:28:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11872) Mobile Showcase and a4j:region demo: submit button doesn't respond on the first click In-Reply-To: <1714655772.52122.1326201429582.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1009278335.12712.1331854127328.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677176#comment-12677176 ] Brian Leathem commented on RF-11872: ------------------------------------ This works on the desktop page, and on the 2nd click of the button on the mobile page. Looking at the ajax request/response, comparing what works to what doesn't work, we can see that in the case where the submission does not work, the javax.faces.ViewState is missing from the submitted form data. > Mobile Showcase and a4j:region demo: submit button doesn't respond on the first click > ------------------------------------------------------------------------------------- > > Key: RF-11872 > URL: https://issues.jboss.org/browse/RF-11872 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: mobile, showcase > Affects Versions: 4.2.0.CR1 > Environment: richfaces-showcase-4.1.1-20120106.230242-18 / richfaces-showcase-4.2.0-20120123.231757-13 > JBoss AS 7.0.2.Final / 7.1.0.Beta1 > Firefox 8.0 / Google Chrome 16.0.912.63 / Android 2.2 / iPhone 4.2.1 > Reporter: Jan Papousek > Assignee: Brian Leathem > Fix For: 4.2.1.CR1 > > Attachments: richfaces-showcase-4.2.0-20120123.231757-13-jbas7.war > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 16 03:35:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Przemys=C5=82aw_D=C4=99bski_=28JIRA=29?=) Date: Fri, 16 Mar 2012 03:35:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12054) TabPanel onitemchange of outer tab fired by inner tab Message-ID: <662615629.13006.1331883347434.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Przemys?aw D?bski created RF-12054: -------------------------------------- Summary: TabPanel onitemchange of outer tab fired by inner tab Key: RF-12054 URL: https://issues.jboss.org/browse/RF-12054 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.2.0.Final Reporter: Przemys?aw D?bski When changing outer tab, "onitemchange" event of outer tab is fired and alert with text 'onitemchange' is shown. But when changing inner tab both "onitemchange" event of outer tab and inner tab are fired and two alerts are show, one with text 'onitemchange' and second with 'onitemchange inner'. It's wrong behaviour, because outer tab is not switched and its "onitemchange" event shouldn't be fired. Same situation with "onbeforeitemchange". Page code to reproduce: {code:xml} tab1 tab inner 1 tab inner 2 {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 16 04:36:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 16 Mar 2012 04:36:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12018) Typo in BOM: jsf-api should be jsp-api In-Reply-To: <269810633.51309.1330504476269.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <792704102.13113.1331887007882.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved RF-12018. ----------------------------- Resolution: Done > Typo in BOM: jsf-api should be jsp-api > -------------------------------------- > > Key: RF-12018 > URL: https://issues.jboss.org/browse/RF-12018 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 4.2.0.Final > Reporter: Marek Novotny > Assignee: Luk?? Fry? > Priority: Minor > Fix For: 4.2.1.CR1 > > > This typo is not causing any issue, it is just confusing. > usage of version: > https://github.com/richfaces/build/blob/4.2.0.20120215-Final/bom/pom.xml#L245 > definition of version: > https://github.com/richfaces/build/blob/4.2.0.20120215-Final/bom/pom.xml#L62 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 16 04:52:49 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 16 Mar 2012 04:52:49 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12020) Reduce number of absolute opened files In-Reply-To: <756676139.61444.1330674096251.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1061416507.13204.1331887969617.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677222#comment-12677222 ] Luk?? Fry? commented on RF-12020: --------------------------------- Marek, I have applied your patch - thanks! Still, the preferred way of accepting patches are pull requests, which does add more cycles than extracting patch. > Reduce number of absolute opened files > -------------------------------------- > > Key: RF-12020 > URL: https://issues.jboss.org/browse/RF-12020 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: cdk > Affects Versions: 4.2.0.Final > Environment: linux > Reporter: Marek Novotny > Assignee: Luk?? Fry? > Fix For: 4.2.1.CR1, 4.Future > > Attachments: cdk-generator.patch > > > While RF Components is compiled, it normally over goes under limit for maximum open files. > I did some change which helped a little, but there will be probably bigger effect if the logic is re-factored to not open all files at the same time in generator/src/main/java/org/richfaces/cdk/templatecompiler/RendererClassGenerator.java of render method. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 16 04:54:51 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 16 Mar 2012 04:54:51 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12020) Reduce number of absolute opened files In-Reply-To: <756676139.61444.1330674096251.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <707747072.13230.1331888091783.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677224#comment-12677224 ] Luk?? Fry? commented on RF-12020: --------------------------------- For the second issue with {{RendererClassGenerator}}, I can't see where it opens all the files at once: https://github.com/richfaces/cdk/blob/develop/generator/src/main/java/org/richfaces/cdk/templatecompiler/RendererClassGenerator.java#L111 Please feel free to comment or directly open new issue to address it in future. For now, I'm resolving this issue for {{4.2.0.CR1}}. > Reduce number of absolute opened files > -------------------------------------- > > Key: RF-12020 > URL: https://issues.jboss.org/browse/RF-12020 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: cdk > Affects Versions: 4.2.0.Final > Environment: linux > Reporter: Marek Novotny > Assignee: Luk?? Fry? > Fix For: 4.2.1.CR1, 4.Future > > Attachments: cdk-generator.patch > > > While RF Components is compiled, it normally over goes under limit for maximum open files. > I did some change which helped a little, but there will be probably bigger effect if the logic is re-factored to not open all files at the same time in generator/src/main/java/org/richfaces/cdk/templatecompiler/RendererClassGenerator.java of render method. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 16 04:56:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 16 Mar 2012 04:56:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12020) Reduce number of absolute opened files In-Reply-To: <756676139.61444.1330674096251.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <704671412.13235.1331888207448.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated RF-12020: ---------------------------- Fix Version/s: (was: 4.Future) > Reduce number of absolute opened files > -------------------------------------- > > Key: RF-12020 > URL: https://issues.jboss.org/browse/RF-12020 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: cdk > Affects Versions: 4.2.0.Final > Environment: linux > Reporter: Marek Novotny > Assignee: Luk?? Fry? > Fix For: 4.2.1.CR1 > > Attachments: cdk-generator.patch > > > While RF Components is compiled, it normally over goes under limit for maximum open files. > I did some change which helped a little, but there will be probably bigger effect if the logic is re-factored to not open all files at the same time in generator/src/main/java/org/richfaces/cdk/templatecompiler/RendererClassGenerator.java of render method. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 16 04:56:48 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 16 Mar 2012 04:56:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12020) Reduce number of absolute opened files In-Reply-To: <756676139.61444.1330674096251.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <473640366.13244.1331888208608.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677222#comment-12677222 ] Luk?? Fry? edited comment on RF-12020 at 3/16/12 4:55 AM: ---------------------------------------------------------- Marek, I have applied your patch - thanks! Still, the preferred way of accepting patches are pull requests, which does not add more cycles than extracting patch. was (Author: lfryc): Marek, I have applied your patch - thanks! Still, the preferred way of accepting patches are pull requests, which does add more cycles than extracting patch. > Reduce number of absolute opened files > -------------------------------------- > > Key: RF-12020 > URL: https://issues.jboss.org/browse/RF-12020 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: cdk > Affects Versions: 4.2.0.Final > Environment: linux > Reporter: Marek Novotny > Assignee: Luk?? Fry? > Fix For: 4.2.1.CR1 > > Attachments: cdk-generator.patch > > > While RF Components is compiled, it normally over goes under limit for maximum open files. > I did some change which helped a little, but there will be probably bigger effect if the logic is re-factored to not open all files at the same time in generator/src/main/java/org/richfaces/cdk/templatecompiler/RendererClassGenerator.java of render method. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 16 04:56:48 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 16 Mar 2012 04:56:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12020) Reduce number of absolute opened files In-Reply-To: <756676139.61444.1330674096251.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <2095433392.13249.1331888208783.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved RF-12020. ----------------------------- Resolution: Done > Reduce number of absolute opened files > -------------------------------------- > > Key: RF-12020 > URL: https://issues.jboss.org/browse/RF-12020 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: cdk > Affects Versions: 4.2.0.Final > Environment: linux > Reporter: Marek Novotny > Assignee: Luk?? Fry? > Fix For: 4.2.1.CR1 > > Attachments: cdk-generator.patch > > > While RF Components is compiled, it normally over goes under limit for maximum open files. > I did some change which helped a little, but there will be probably bigger effect if the logic is re-factored to not open all files at the same time in generator/src/main/java/org/richfaces/cdk/templatecompiler/RendererClassGenerator.java of render method. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 16 06:10:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 16 Mar 2012 06:10:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11905) showcase - shutdown of the JBoss AS with showcase deployed throws DB error In-Reply-To: <567082387.11072.1326986119167.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <783785810.13452.1331892647740.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved RF-11905. ----------------------------- Resolution: Done Profile {{jbas71}} was modified in order to provide custom {{webapp}}/{{resources}} which setup own {{DataSource}} using {{showcase-ds.xml}}. This fix is targeting JBoss AS 7.1 and higher. > showcase - shutdown of the JBoss AS with showcase deployed throws DB error > -------------------------------------------------------------------------- > > Key: RF-11905 > URL: https://issues.jboss.org/browse/RF-11905 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: showcase > Affects Versions: 4.1.0.Final > Environment: container: JBoss AS 7.1.0.CR1b, 7.0.2.Final > app: showcase 4.2.0-SNAPSHOT > Reporter: Juraj Huska > Assignee: Luk?? Fry? > Priority: Minor > Fix For: 4.2.1.CR1 > > > When shutting down JBoss AS 7 with showcase deployed, then the DB error is thrown: > {code} > 16:09:52,334 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] HHH000231: Schema export unsuccessful: org.h2.jdbc.JdbcSQLException: Database is already closed (to disable automatic closing at VM shutdown, add ";DB_CLOSE_ON_EXIT=FALSE" to the db URL) [90121-161] > at org.h2.message.DbException.getJdbcSQLException(DbException.java:329) > at org.h2.message.DbException.get(DbException.java:169) > at org.h2.message.DbException.get(DbException.java:146) > at org.h2.message.DbException.get(DbException.java:135) > at org.h2.jdbc.JdbcConnection.checkClosed(JdbcConnection.java:1394) > at org.h2.jdbc.JdbcConnection.checkClosed(JdbcConnection.java:1369) > at org.h2.jdbc.JdbcConnection.createStatement(JdbcConnection.java:191) > at org.jboss.jca.adapters.jdbc.WrappedConnection.createStatement(WrappedConnection.java:301) > at org.hibernate.tool.hbm2ddl.DatabaseExporter.(DatabaseExporter.java:54) [hibernate-core-4.0.0.Final.jar:4.0.0.Final] > at org.hibernate.tool.hbm2ddl.SchemaExport.execute(SchemaExport.java:368) [hibernate-core-4.0.0.Final.jar:4.0.0.Final] > at org.hibernate.tool.hbm2ddl.SchemaExport.drop(SchemaExport.java:319) [hibernate-core-4.0.0.Final.jar:4.0.0.Final] > at org.hibernate.tool.hbm2ddl.SchemaExport.drop(SchemaExport.java:315) [hibernate-core-4.0.0.Final.jar:4.0.0.Final] > at org.hibernate.internal.SessionFactoryImpl.close(SessionFactoryImpl.java:1305) [hibernate-core-4.0.0.Final.jar:4.0.0.Final] > at org.hibernate.ejb.EntityManagerFactoryImpl.close(EntityManagerFactoryImpl.java:126) [hibernate-entitymanager-4.0.0.Final.jar:4.0.0.Final] > at org.richfaces.demo.arrangeablemodel.PersistenceService.destroy(PersistenceService.java:159) [classes:] > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_22] > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_22] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_22] > at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_22] > at org.jboss.as.ee.component.ManagedReferenceLifecycleMethodInterceptorFactory$ManagedReferenceLifecycleMethodInterceptor.processInvocation(ManagedReferenceLifecycleMethodInterceptorFactory.java:130) [jboss-as-ee-7.1.0.CR1b.jar:7.1.0.CR1b] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final] > at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final] > at org.jboss.as.ee.component.ManagedReferenceReleaseInterceptorFactory$ManagedReferenceReleaseInterceptor.processInvocation(ManagedReferenceReleaseInterceptorFactory.java:90) [jboss-as-ee-7.1.0.CR1b.jar:7.1.0.CR1b] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final] > at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final] > at org.jboss.as.ee.component.TCCLInterceptor.processInvocation(TCCLInterceptor.java:45) [jboss-as-ee-7.1.0.CR1b.jar:7.1.0.CR1b] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final] > at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final] > at org.jboss.as.ee.component.BasicComponentInstance.destroy(BasicComponentInstance.java:122) [jboss-as-ee-7.1.0.CR1b.jar:7.1.0.CR1b] > at org.jboss.as.web.deployment.component.WebComponentInstantiator$2.release(WebComponentInstantiator.java:102) [jboss-as-web-7.1.0.CR1b.jar:7.1.0.CR1b] > at org.jboss.as.web.deployment.WebInjectionContainer.destroyInstance(WebInjectionContainer.java:67) [jboss-as-web-7.1.0.CR1b.jar:7.1.0.CR1b] > at org.jboss.as.web.deployment.jsf.JsfInjectionProvider.invokePreDestroy(JsfInjectionProvider.java:56) [jboss-as-web-7.1.0.CR1b.jar:7.1.0.CR1b] > at com.sun.faces.mgbean.BeanBuilder.destroy(BeanBuilder.java:116) [jsf-impl-2.1.5-jbossorg-1.jar:2.1.5-SNAPSHOT] > at com.sun.faces.mgbean.BeanManager.destroy(BeanManager.java:283) [jsf-impl-2.1.5-jbossorg-1.jar:2.1.5-SNAPSHOT] > at com.sun.faces.application.WebappLifecycleListener.handleAttributeEvent(WebappLifecycleListener.java:314) [jsf-impl-2.1.5-jbossorg-1.jar:2.1.5-SNAPSHOT] > at com.sun.faces.application.WebappLifecycleListener.contextDestroyed(WebappLifecycleListener.java:368) [jsf-impl-2.1.5-jbossorg-1.jar:2.1.5-SNAPSHOT] > at com.sun.faces.config.ConfigureListener.contextDestroyed(ConfigureListener.java:308) [jsf-impl-2.1.5-jbossorg-1.jar:2.1.5-SNAPSHOT] > at org.apache.catalina.core.StandardContext.listenerStop(StandardContext.java:3489) [jbossweb-7.0.7.Final.jar:] > at org.apache.catalina.core.StandardContext.stop(StandardContext.java:3999) [jbossweb-7.0.7.Final.jar:] > at org.jboss.as.web.deployment.WebDeploymentService.stop(WebDeploymentService.java:96) [jboss-as-web-7.1.0.CR1b.jar:7.1.0.CR1b] > at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:1909) > at org.jboss.msc.service.ServiceControllerImpl$StopTask.run(ServiceControllerImpl.java:1872) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_22] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_22] > at java.lang.Thread.run(Thread.java:662) [:1.6.0_22] > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 16 06:29:47 2012 From: jira-events at lists.jboss.org (lakshmee n (JIRA)) Date: Fri, 16 Mar 2012 06:29:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12055) horizontal scrollbar is not working properly by using ScrollableDataTable, with one column Message-ID: <1704997765.13478.1331893787300.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> lakshmee n created RF-12055: ------------------------------- Summary: horizontal scrollbar is not working properly by using ScrollableDataTable, with one column Key: RF-12055 URL: https://issues.jboss.org/browse/RF-12055 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Reporter: lakshmee n -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 16 06:43:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 16 Mar 2012 06:43:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11965) showcase - a4j:push - error thrown after creating topic for pushCdi In-Reply-To: <1869426390.30466.1328703648739.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1937763378.13515.1331894627972.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved RF-11965. ----------------------------- Resolution: Done > showcase - a4j:push - error thrown after creating topic for pushCdi > ------------------------------------------------------------------- > > Key: RF-11965 > URL: https://issues.jboss.org/browse/RF-11965 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll, showcase > Affects Versions: 4.2.0.Final > Environment: container: JBoss AS 7.1.0.CR1b > Reporter: Juraj Huska > Assignee: Luk?? Fry? > Priority: Minor > Fix For: 4.2.1.CR1 > > > When deploying showcase 4.2.0.CR1 then after pushCdi topic created an error is thrown: > {code} > 18:13:42,211 INFO [org.richfaces.demo.push.JMSInitializer] (MSC service thread 1-2) initializing > 18:13:42,219 INFO [org.richfaces.demo.push.JMSInitializer] (MSC service thread 1-2) AS7MessagingProviderManagement initialized > 18:13:42,219 INFO [org.richfaces.demo.push.JMSInitializer] (MSC service thread 1-2) creating topic pushJms > 18:13:42,761 INFO [org.richfaces.demo.push.JMSInitializer] (MSC service thread 1-2) creating topic pushTopicsContext > 18:13:42,802 INFO [org.richfaces.demo.push.JMSInitializer] (MSC service thread 1-2) creating topic pushCdi > 18:13:42,972 SEVERE [org.richfaces.demo.push.MessageProducerRunnable] (MessageProducerThread) javax.faces.FacesException: topic/pushTopicsContext -- service jboss.naming.context.java.topic.$ > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:397) [guava-10.0.1.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl.createTopic(JMSTopicsContextImpl.java:281) [richfaces-core-impl-4.2.0.CR1.jar:] > at org.richfaces.application.push.TopicsContext.getOrCreateTopic(TopicsContext.java:48) [richfaces-core-api-4.2.0.CR1.jar:] > at org.richfaces.application.push.TopicsContext.publish(TopicsContext.java:69) [richfaces-core-api-4.2.0.CR1.jar:] > at org.richfaces.demo.push.TopicsContextMessageProducer.sendMessage(TopicsContextMessageProducer.java:46) [classes:] > at org.richfaces.demo.push.MessageProducerRunnable.run(MessageProducerRunnable.java:57) [classes:] > at java.lang.Thread.run(Thread.java:662) [:1.6.0_22] > Caused by: javax.faces.FacesException: topic/pushTopicsContext -- service jboss.naming.context.java.topic.pushTopicsContext > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:207) [richfaces-core-impl-4.2.0.CR1.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:195) [richfaces-core-impl-4.2.0.CR1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingValueReference.compute(ComputingConcurrentHashMap.java:355) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.compute(ComputingConcurrentHashMap.java:184) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.getOrCompute(ComputingConcurrentHashMap.java:153) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap.getOrCompute(ComputingConcurrentHashMap.java:69) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:393) [guava-10.0.1.jar:] > ... 6 more > Caused by: javax.naming.NameNotFoundException: topic/pushTopicsContext -- service jboss.naming.context.java.topic.pushTopicsContext > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:92) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:177) > at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:87) > at javax.naming.InitialContext.lookup(InitialContext.java:396) [:1.6.0_22] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.lookupTopic(JMSTopicsContextImpl.java:94) [richfaces-core-impl-4.2.0-20120130.140419-26.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.start(JMSTopicsContextImpl.java:125) [richfaces-core-impl-4.2.0-20120130.140419-26.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:199) [richfaces-core-impl-4.2.0-20120130.140419-26.jar:] > ... 12 more > {code} > The functionality of push demos is fine, just the tests are not passing on Hudson, which I have to investigate whether it is caused by this one. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 16 06:49:49 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 16 Mar 2012 06:49:49 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12007) AbstractPanelMenuGroup.getChangeExpandListener is not used In-Reply-To: <1007334631.44779.1330344037133.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1524984773.13536.1331894989082.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved RF-12007. ----------------------------- Resolution: Done > AbstractPanelMenuGroup.getChangeExpandListener is not used > ---------------------------------------------------------- > > Key: RF-12007 > URL: https://issues.jboss.org/browse/RF-12007 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.2.0.Final > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Priority: Minor > Fix For: 4.2.1.CR1 > > > There is no such listener/event defined in the project. > I suggest to remove this attribute in 4.2.x. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 16 07:43:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 16 Mar 2012 07:43:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-10941) a4j:command* components misses default behavior event In-Reply-To: <1049007299.42458.1303309173106.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1530524107.13629.1331898227787.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-10941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677262#comment-12677262 ] Luk?? Fry? commented on RF-10941: --------------------------------- In fact, the behavior is marked as default one [1] in referenced {{props.xml}} file [2], thus CDK should use it. [1] https://github.com/richfaces/cdk/blob/develop/attributes/src/main/resources/META-INF/cdk/attributes/command-button-props.xml#L46 [2] https://github.com/richfaces/components/blob/develop/core/ui/src/main/java/org/richfaces/component/AbstractCommandButton.java#L42 For now I suggest to just register default event programmatically. > a4j:command* components misses default behavior event > ----------------------------------------------------- > > Key: RF-10941 > URL: https://issues.jboss.org/browse/RF-10941 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.0.0.Final > Reporter: Ilya Shaikovsky > Assignee: Luk?? Fry? > Fix For: 4.2.1.CR1 > > Attachments: AbstractCommandButtonHierarchy.png > > > Excerpt from the thread: http://community.jboss.org/message/601191#601191\ > {quote} > ClientBehaviorHolder interface implementors supposed to provide default event for behaviors. And some RF components misses it. > {quote} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 16 07:47:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 16 Mar 2012 07:47:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12056) CDK ignores default-behavior value in props.xml file Message-ID: <1322856240.13636.1331898467400.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Luk?? Fry? created RF-12056: ------------------------------- Summary: CDK ignores default-behavior value in props.xml file Key: RF-12056 URL: https://issues.jboss.org/browse/RF-12056 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: cdk Affects Versions: 4.2.0.Final Reporter: Luk?? Fry? Assignee: Luk?? Fry? In the initial issue, the {{defaultEventName}} is not provided. The problem is CDK recognizes default event name from annotation (@Attribute(event=@EventName(defaultEvent=true, ...))}, but not from XML configuration {{true}}. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 16 07:59:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 16 Mar 2012 07:59:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-10941) a4j:command* components misses default behavior event In-Reply-To: <1049007299.42458.1303309173106.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1251375020.13674.1331899187529.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-10941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated RF-10941: ---------------------------- Comment: was deleted (was: In fact, the behavior is marked as default one [1] in referenced {{props.xml}} file [2], thus CDK should use it. [1] https://github.com/richfaces/cdk/blob/develop/attributes/src/main/resources/META-INF/cdk/attributes/command-button-props.xml#L46 [2] https://github.com/richfaces/components/blob/develop/core/ui/src/main/java/org/richfaces/component/AbstractCommandButton.java#L42 For now I suggest to just register default event programmatically.) > a4j:command* components misses default behavior event > ----------------------------------------------------- > > Key: RF-10941 > URL: https://issues.jboss.org/browse/RF-10941 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.0.0.Final > Reporter: Ilya Shaikovsky > Assignee: Luk?? Fry? > Fix For: 4.2.1.CR1 > > Attachments: AbstractCommandButtonHierarchy.png > > > Excerpt from the thread: http://community.jboss.org/message/601191#601191\ > {quote} > ClientBehaviorHolder interface implementors supposed to provide default event for behaviors. And some RF components misses it. > {quote} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 16 07:59:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 16 Mar 2012 07:59:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12056) CDK ignores default-behavior value in props.xml file Message-ID: <1370063126.13671.1331899187441.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? deleted RF-12056: ---------------------------- > CDK ignores default-behavior value in props.xml file > ---------------------------------------------------- > > Key: RF-12056 > URL: https://issues.jboss.org/browse/RF-12056 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > > In the initial issue, the {{defaultEventName}} is not provided. > The problem is CDK recognizes default event name from annotation (@Attribute(event=@EventName(defaultEvent=true, ...))}, but not from XML configuration {{true}}. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 16 07:59:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 16 Mar 2012 07:59:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-10941) a4j:command* components misses default behavior event In-Reply-To: <1049007299.42458.1303309173106.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1993105893.13678.1331899187989.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-10941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677266#comment-12677266 ] Luk?? Fry? commented on RF-10941: --------------------------------- The only was necessary: set {{click}}. Then the {{getDefaultEventName()}} is generated right. was (Author: lfryc): The only was necessary: set {{ (and selecting cancel) would prevent any action routines being called, as is common > with components such as h:commandButton. As it stands the return value is ignored and > processing continues with return true or return false. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 16 11:19:49 2012 From: jira-events at lists.jboss.org (Jan Papousek (JIRA)) Date: Fri, 16 Mar 2012 11:19:49 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11971) rich:menuItem onclick return value ignored In-Reply-To: <900498702.34279.1328801928475.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <362295121.14331.1331911189559.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Papousek closed RF-11971. ----------------------------- Verified. When it's return 'false' from onclick handler, it'll prevent > rich:menuItem onclick return value ignored > ------------------------------------------ > > Key: RF-11971 > URL: https://issues.jboss.org/browse/RF-11971 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-menu > Affects Versions: 4.2.0.Final > Environment: Chrome / glassfish 3.1.1 / mojarra 2.1.6 > Reporter: Brendan Healey > Assignee: Luk?? Fry? > Fix For: 4.2.1.CR1 > > > My expectation was that using rich:menuItem onclick="if(!confirm('#{msgs.playerConfirmDelete}')) return false;" > (and selecting cancel) would prevent any action routines being called, as is common > with components such as h:commandButton. As it stands the return value is ignored and > processing continues with return true or return false. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 16 11:19:49 2012 From: jira-events at lists.jboss.org (Jan Papousek (JIRA)) Date: Fri, 16 Mar 2012 11:19:49 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11971) rich:menuItem onclick return value ignored In-Reply-To: <900498702.34279.1328801928475.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <862971553.14334.1331911189712.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Papousek reopened RF-11971: ------------------------------- > rich:menuItem onclick return value ignored > ------------------------------------------ > > Key: RF-11971 > URL: https://issues.jboss.org/browse/RF-11971 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-menu > Affects Versions: 4.2.0.Final > Environment: Chrome / glassfish 3.1.1 / mojarra 2.1.6 > Reporter: Brendan Healey > Assignee: Luk?? Fry? > Fix For: 4.2.1.CR1 > > > My expectation was that using rich:menuItem onclick="if(!confirm('#{msgs.playerConfirmDelete}')) return false;" > (and selecting cancel) would prevent any action routines being called, as is common > with components such as h:commandButton. As it stands the return value is ignored and > processing continues with return true or return false. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 16 11:23:47 2012 From: jira-events at lists.jboss.org (Jan Papousek (JIRA)) Date: Fri, 16 Mar 2012 11:23:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11971) rich:menuItem onclick return value ignored In-Reply-To: <900498702.34279.1328801928475.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <2053778808.14347.1331911427627.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677330#comment-12677330 ] Jan Papousek edited comment on RF-11971 at 3/16/12 11:22 AM: ------------------------------------------------------------- Verified. When 'false' is returned from onclick handler, it'll prevent action execution. A note: 'null' has no effect. was (Author: jpapouse): Verified. When it's return 'false' from onclick handler, it'll prevent > rich:menuItem onclick return value ignored > ------------------------------------------ > > Key: RF-11971 > URL: https://issues.jboss.org/browse/RF-11971 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-menu > Affects Versions: 4.2.0.Final > Environment: Chrome / glassfish 3.1.1 / mojarra 2.1.6 > Reporter: Brendan Healey > Assignee: Luk?? Fry? > Fix For: 4.2.1.CR1 > > > My expectation was that using rich:menuItem onclick="if(!confirm('#{msgs.playerConfirmDelete}')) return false;" > (and selecting cancel) would prevent any action routines being called, as is common > with components such as h:commandButton. As it stands the return value is ignored and > processing continues with return true or return false. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 16 11:23:47 2012 From: jira-events at lists.jboss.org (Jan Papousek (JIRA)) Date: Fri, 16 Mar 2012 11:23:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11971) rich:menuItem onclick return value ignored In-Reply-To: <900498702.34279.1328801928475.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <733928069.14352.1331911427976.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Papousek closed RF-11971. ----------------------------- Resolution: Done > rich:menuItem onclick return value ignored > ------------------------------------------ > > Key: RF-11971 > URL: https://issues.jboss.org/browse/RF-11971 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-menu > Affects Versions: 4.2.0.Final > Environment: Chrome / glassfish 3.1.1 / mojarra 2.1.6 > Reporter: Brendan Healey > Assignee: Luk?? Fry? > Fix For: 4.2.1.CR1 > > > My expectation was that using rich:menuItem onclick="if(!confirm('#{msgs.playerConfirmDelete}')) return false;" > (and selecting cancel) would prevent any action routines being called, as is common > with components such as h:commandButton. As it stands the return value is ignored and > processing continues with return true or return false. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 16 16:04:47 2012 From: jira-events at lists.jboss.org (Gurinder Randhawa (JIRA)) Date: Fri, 16 Mar 2012 16:04:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12057) IE 8 rich:toolTip client side toolTip has problems rendering upon ajax request Message-ID: <470606725.14861.1331928287605.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Gurinder Randhawa created RF-12057: -------------------------------------- Summary: IE 8 rich:toolTip client side toolTip has problems rendering upon ajax request Key: RF-12057 URL: https://issues.jboss.org/browse/RF-12057 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-output Affects Versions: 4.1.0.Final Environment: Windows 7, IE 8 Reporter: Gurinder Randhawa Rich:Tooltip in client mode does not refresh upon an ajax event specifically in IE 8. A large part of external clients utilize IE 8 unfortunately. The tool tip is working correctly in IE 9, chrome and FF 7+. The tool tip is refreshed on next ajax request with "previous" ajax response. TOOL TIP CODE: ===============
AJAX REQUEST CODE, SELECTABLE CHECKBOX WHICH RE-RENDERS TOOLTIP =============================================================== -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Sun Mar 18 07:18:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Sun, 18 Mar 2012 07:18:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12009) Showcase: wrong look of page header in Opera Mobile In-Reply-To: <208215608.44849.1330346556934.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <425403450.15548.1332069527622.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12009: ------------------------------- Fix Version/s: 4.3-Tracking Component/s: showcase > Showcase: wrong look of page header in Opera Mobile > --------------------------------------------------- > > Key: RF-12009 > URL: https://issues.jboss.org/browse/RF-12009 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: mobile, showcase > Affects Versions: 4.2.0.Final > Environment: http://showcase.richfaces.org/ > Opera Mobile v 12.00.ADR-1202131246 > Reporter: Luk?? Fry? > Priority: Minor > Labels: mobile, mobile-opera > Fix For: 4.3-Tracking > > Attachments: Android.jpg, Opera.jpg > > > The header in Opera Mobile does not have the background. > It also means the AJAX status (which is white) is not shown when loading new page. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Sun Mar 18 07:22:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Sun, 18 Mar 2012 07:22:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12026) Javascript error in AjaxRequests on FireFox "invalid 'in' operand event" In-Reply-To: <1447882664.73686.1331126016454.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1640280412.15550.1332069767303.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12026: ------------------------------- Fix Version/s: 4.2.1.CR1 Priority: Minor (was: Major) Assignee: Brian Leathem > Javascript error in AjaxRequests on FireFox "invalid 'in' operand event" > ------------------------------------------------------------------------ > > Key: RF-12026 > URL: https://issues.jboss.org/browse/RF-12026 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 4.2.0.Final > Environment: FireFox 3.6.27 > Reporter: Ulf Almehed > Assignee: Brian Leathem > Priority: Minor > Labels: regression > Fix For: 4.2.1.CR1 > > > Ajax request fails with javascript error "invalid 'in' operand event", richfaces-queue.js line 130. > This was introduced by the fix in RF-11943. Checking for existence of layerX fails if event isn't an Object (but a simple type). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Sun Mar 18 07:24:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Sun, 18 Mar 2012 07:24:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12027) Add a maximum number of selectable elements to rich:pickList In-Reply-To: <102106719.74777.1331141136257.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <813419704.15552.1332069887315.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12027: ------------------------------- Fix Version/s: 4.3-Tracking Component/s: component-selects > Add a maximum number of selectable elements to rich:pickList > ------------------------------------------------------------ > > Key: RF-12027 > URL: https://issues.jboss.org/browse/RF-12027 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-selects > Environment: any > Reporter: Karsten Wutzke > Fix For: 4.3-Tracking > > > Please add a maximum number of selectable elements to rich:pickList via an attribute like maxItems="n" or maxValues="n" -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Sun Mar 18 11:37:47 2012 From: jira-events at lists.jboss.org (Thorsten Nieser (JIRA)) Date: Sun, 18 Mar 2012 11:37:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12058) rich:fileUpload - wrong upload icon if resourceOptimization param is set to true Message-ID: <1723961468.15563.1332085067290.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Thorsten Nieser created RF-12058: ------------------------------------ Summary: rich:fileUpload - wrong upload icon if resourceOptimization param is set to true Key: RF-12058 URL: https://issues.jboss.org/browse/RF-12058 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-input Affects Versions: 4.2.0.Final Environment: Tomcat6.33, Richfaces 4.2.0 FINAL, JDK1.6 Reporter: Thorsten Nieser Priority: Minor If the new resource optimization is disabled all icons of the fileUpload element are fine. (http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=fileUpload&skin=blueSky) But if I enabled the optimization by setting the context param to true, the upload button shows the red cross instead of the green check mark. org.richfaces.resourceOptimization.enabled true -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Sun Mar 18 11:39:47 2012 From: jira-events at lists.jboss.org (Thorsten Nieser (JIRA)) Date: Sun, 18 Mar 2012 11:39:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12058) rich:fileUpload - wrong upload icon if resourceOptimization param is set to true In-Reply-To: <1723961468.15563.1332085067290.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1740453345.15566.1332085187282.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thorsten Nieser updated RF-12058: --------------------------------- Attachment: ok.jpg Param value = false > rich:fileUpload - wrong upload icon if resourceOptimization param is set to true > --------------------------------------------------------------------------------- > > Key: RF-12058 > URL: https://issues.jboss.org/browse/RF-12058 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.2.0.Final > Environment: Tomcat6.33, Richfaces 4.2.0 FINAL, JDK1.6 > Reporter: Thorsten Nieser > Priority: Minor > Attachments: ok.jpg > > > If the new resource optimization is disabled all icons of the fileUpload element are fine. > (http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=fileUpload&skin=blueSky) > But if I enabled the optimization by setting the context param to true, the upload button shows the red cross instead of the green check mark. > > org.richfaces.resourceOptimization.enabled > true > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Sun Mar 18 11:41:47 2012 From: jira-events at lists.jboss.org (Thorsten Nieser (JIRA)) Date: Sun, 18 Mar 2012 11:41:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12058) rich:fileUpload - wrong upload icon if resourceOptimization param is set to true In-Reply-To: <1723961468.15563.1332085067290.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <913011888.15570.1332085307343.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thorsten Nieser updated RF-12058: --------------------------------- Attachment: nok.jpg param value = true > rich:fileUpload - wrong upload icon if resourceOptimization param is set to true > --------------------------------------------------------------------------------- > > Key: RF-12058 > URL: https://issues.jboss.org/browse/RF-12058 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.2.0.Final > Environment: Tomcat6.33, Richfaces 4.2.0 FINAL, JDK1.6 > Reporter: Thorsten Nieser > Priority: Minor > Attachments: nok.jpg, ok.jpg > > > If the new resource optimization is disabled all icons of the fileUpload element are fine. > (http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=fileUpload&skin=blueSky) > But if I enabled the optimization by setting the context param to true, the upload button shows the red cross instead of the green check mark. > > org.richfaces.resourceOptimization.enabled > true > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Sun Mar 18 12:02:47 2012 From: jira-events at lists.jboss.org (Thorsten Nieser (JIRA)) Date: Sun, 18 Mar 2012 12:02:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12058) rich:fileUpload - wrong upload icon if resourceOptimization param is set to true In-Reply-To: <1723961468.15563.1332085067290.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <340521597.15573.1332086567338.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thorsten Nieser updated RF-12058: --------------------------------- Attachment: css-snippet.jpg > rich:fileUpload - wrong upload icon if resourceOptimization param is set to true > --------------------------------------------------------------------------------- > > Key: RF-12058 > URL: https://issues.jboss.org/browse/RF-12058 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.2.0.Final > Environment: Tomcat6.33, Richfaces 4.2.0 FINAL, JDK1.6 > Reporter: Thorsten Nieser > Priority: Minor > Attachments: css-snippet.jpg, nok.jpg, ok.jpg > > > If the new resource optimization is disabled all icons of the fileUpload element are fine. > (http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=fileUpload&skin=blueSky) > But if I enabled the optimization by setting the context param to true, the upload button shows the red cross instead of the green check mark. > > org.richfaces.resourceOptimization.enabled > true > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Sun Mar 18 12:13:47 2012 From: jira-events at lists.jboss.org (Thorsten Nieser (JIRA)) Date: Sun, 18 Mar 2012 12:13:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12058) rich:fileUpload - wrong upload icon if resourceOptimization param is set to true In-Reply-To: <1723961468.15563.1332085067290.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <308757105.15575.1332087227349.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677498#comment-12677498 ] Thorsten Nieser edited comment on RF-12058 at 3/18/12 12:13 PM: ---------------------------------------------------------------- A way to solve the problem is to override the default css class by an own one with a reference to another image icon. (I took the original one out if the richfaces ui jar) .rf-fu-btn-cnt-upl { background-image: url("/CMS/javax.faces.resource/graphics/fu-upl.gif.jsf") !important; } was (Author: thorstenn): Param value = false > rich:fileUpload - wrong upload icon if resourceOptimization param is set to true > --------------------------------------------------------------------------------- > > Key: RF-12058 > URL: https://issues.jboss.org/browse/RF-12058 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.2.0.Final > Environment: Tomcat6.33, Richfaces 4.2.0 FINAL, JDK1.6 > Reporter: Thorsten Nieser > Priority: Minor > Attachments: css-snippet.jpg, nok.jpg, ok.jpg > > > If the new resource optimization is disabled all icons of the fileUpload element are fine. > (http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=fileUpload&skin=blueSky) > But if I enabled the optimization by setting the context param to true, the upload button shows the red cross instead of the green check mark. > > org.richfaces.resourceOptimization.enabled > true > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Sun Mar 18 12:13:47 2012 From: jira-events at lists.jboss.org (Thorsten Nieser (JIRA)) Date: Sun, 18 Mar 2012 12:13:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12058) rich:fileUpload - wrong upload icon if resourceOptimization param is set to true In-Reply-To: <1723961468.15563.1332085067290.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1518782066.15579.1332087227494.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677499#comment-12677499 ] Thorsten Nieser edited comment on RF-12058 at 3/18/12 12:13 PM: ---------------------------------------------------------------- - was (Author: thorstenn): param value = true > rich:fileUpload - wrong upload icon if resourceOptimization param is set to true > --------------------------------------------------------------------------------- > > Key: RF-12058 > URL: https://issues.jboss.org/browse/RF-12058 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.2.0.Final > Environment: Tomcat6.33, Richfaces 4.2.0 FINAL, JDK1.6 > Reporter: Thorsten Nieser > Priority: Minor > Attachments: css-snippet.jpg, nok.jpg, ok.jpg > > > If the new resource optimization is disabled all icons of the fileUpload element are fine. > (http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=fileUpload&skin=blueSky) > But if I enabled the optimization by setting the context param to true, the upload button shows the red cross instead of the green check mark. > > org.richfaces.resourceOptimization.enabled > true > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 19 04:40:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 19 Mar 2012 04:40:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11991) NPE in ...push.impl.RequestImpl.onBroadcast() In-Reply-To: <332746981.25417.1329502476234.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <852821461.16131.1332146447624.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677539#comment-12677539 ] Luk?? Fry? commented on RF-11991: --------------------------------- Hey Juergen, is this issue intermittent or does it happen regularly? Any chance to try with RF {{4.2.0.Final}} bits? > NPE in ...push.impl.RequestImpl.onBroadcast() > --------------------------------------------- > > Key: RF-11991 > URL: https://issues.jboss.org/browse/RF-11991 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Affects Versions: 4.2.0.CR1 > Environment: JBossAS 7.1.0 Web Profile > Reporter: Juergen Zimmermann > Assignee: Luk?? Fry? > Labels: waiting_on_user > > I'm using JBossAS 7.1 (Web Profile) via standalone (not domain). When there is no push event I'm getting a NPE (see stacktrace below). > These JARs are in WEB-INF/lib: > atmosphere-compat-jbossweb-0.8.4.jar > atmosphere-compat-jetty-0.8.4.jar > atmosphere-compat-tomcat-0.8.4.jar > atmosphere-compat-tomcat7-0.8.4.jar > atmosphere-compat-weblogic-0.8.4.jar > atmosphere-runtime-0.8.4.jar > web.xml is configured as follows: > > org.atmosphere.useBlocking > true > > Stacktrace: > {code} > 18:50:47,754 Schwerwiegend [org.richfaces.log.Application] (http-localhost-127.0.0.1-8080-5) null: java.lang.NullPointerException > at org.richfaces.application.push.impl.RequestImpl.onBroadcast(RequestImpl.java:124) [richfaces-core-impl-4.2.0.CR1.jar:4.2.0.CR1] > at org.atmosphere.cpr.AtmosphereResourceImpl.onBroadcast(AtmosphereResourceImpl.java:663) [atmosphere-runtime-0.8.4.jar:0.8.4] > at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:608) [atmosphere-runtime-0.8.4.jar:0.8.4] > at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:584) [atmosphere-runtime-0.8.4.jar:0.8.4] > at org.atmosphere.cpr.AsynchronousProcessor.timedout(AsynchronousProcessor.java:379) [atmosphere-runtime-0.8.4.jar:0.8.4] > at org.atmosphere.container.BlockingIOCometSupport.suspend(BlockingIOCometSupport.java:148) [atmosphere-runtime-0.8.4.jar:0.8.4] > at org.atmosphere.container.BlockingIOCometSupport.service(BlockingIOCometSupport.java:92) [atmosphere-runtime-0.8.4.jar:0.8.4] > at org.atmosphere.cpr.AtmosphereServlet.doCometSupport(AtmosphereServlet.java:1217) [atmosphere-runtime-0.8.4.jar:0.8.4] > at org.atmosphere.cpr.AtmosphereServlet.doPost(AtmosphereServlet.java:1176) [atmosphere-runtime-0.8.4.jar:0.8.4] > at org.atmosphere.cpr.AtmosphereServlet.doGet(AtmosphereServlet.java:1162) [atmosphere-runtime-0.8.4.jar:0.8.4] > at javax.servlet.http.HttpServlet.service(HttpServlet.java:734) [jboss-servlet-api_3.0_spec-1.0.0.Final.jar:1.0.0.Final] > at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.0.Final.jar:1.0.0.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.10.Final.jar:] > at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:62) [weld-core-1.1.5.AS71.Final.jar:2012-02-10 15:31] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.10.Final.jar:] > at org.jboss.solder.servlet.exception.CatchExceptionFilter.doFilter(CatchExceptionFilter.java:65) [solder-impl-3.1.0.Final.jar:3.1.0.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.10.Final.jar:] > at org.jboss.solder.servlet.event.ServletEventBridgeFilter.doFilter(ServletEventBridgeFilter.java:74) [solder-impl-3.1.0.Final.jar:3.1.0.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.10.Final.jar:] > at com.ocpsoft.pretty.PrettyFilter.doFilter(PrettyFilter.java:126) [prettyfaces-jsf2-3.3.2.jar:] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:397) [jbossweb-7.0.10.Final.jar:] > at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.1.0.Final.jar:7.1.0.Final] > at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:154) [jboss-as-web-7.1.0.Final.jar:7.1.0.Final] > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.10.Final.jar:] > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.10.Final.jar:] > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.10.Final.jar:] > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.10.Final.jar:] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_03] > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 19 08:14:47 2012 From: jira-events at lists.jboss.org (Jean ANDRE (JIRA)) Date: Mon, 19 Mar 2012 08:14:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12059) RichFaces.ui.Message is not a constructor - Nested Tab Panel - Tab Creation Message-ID: <1031888240.16896.1332159287591.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Jean ANDRE created RF-12059: ------------------------------- Summary: RichFaces.ui.Message is not a constructor - Nested Tab Panel - Tab Creation Key: RF-12059 URL: https://issues.jboss.org/browse/RF-12059 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.2.0.Final Environment: Websphere 8.0.0.2 - RAD 8 - JSF Mojorra 2.1.6 - Spring 3.0.6 Final - Firefox 10.0.2 - Windows 7 (6.1 sp1) - AspectJ 1.6.12 / AJDT - RichFaces 4.2.0 Final - Hibernate Validator 4.2.0 Final Reporter: Jean ANDRE Priority: Blocker We got the following error message, just after a tab has been created or during its creation: {code} RichFaces.ui.Message is not a constructor > return new Function("event", handlerCode); richfaces.js.jsf (ligne 481) {code} This bug is linked to RF-11763 and RF-12030 but the error message and the context are not the same. The rich:messages is also involved in this bug, the rich:message is attached to a rich:calendar. Removing the rich:message removes the error. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 19 09:03:47 2012 From: jira-events at lists.jboss.org (Jean ANDRE (JIRA)) Date: Mon, 19 Mar 2012 09:03:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12059) RichFaces.ui.Message is not a constructor - Nested Tab Panel - Tab Creation In-Reply-To: <1031888240.16896.1332159287591.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1809385193.17096.1332162227312.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean ANDRE updated RF-12059: ---------------------------- Attachment: NestedWeb_RF-12059.zip Here is the workbench to be able to reproduce the bug. > RichFaces.ui.Message is not a constructor - Nested Tab Panel - Tab Creation > --------------------------------------------------------------------------- > > Key: RF-12059 > URL: https://issues.jboss.org/browse/RF-12059 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.2.0.Final > Environment: Websphere 8.0.0.2 - RAD 8 - JSF Mojorra 2.1.6 - Spring 3.0.6 Final - Firefox 10.0.2 - Windows 7 (6.1 sp1) - AspectJ 1.6.12 / AJDT - RichFaces 4.2.0 Final - Hibernate Validator 4.2.0 Final > Reporter: Jean ANDRE > Priority: Blocker > Attachments: NestedWeb_RF-12059.zip > > > We got the following error message, just after a tab has been created or during its creation: > {code} > RichFaces.ui.Message is not a constructor > > return new Function("event", handlerCode); > richfaces.js.jsf (ligne 481) > {code} > This bug is linked to RF-11763 and RF-12030 but the error message and the context are not the same. > The rich:messages is also involved in this bug, the rich:message is attached to a rich:calendar. Removing the rich:message removes the error. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 19 09:10:47 2012 From: jira-events at lists.jboss.org (Jean ANDRE (JIRA)) Date: Mon, 19 Mar 2012 09:10:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12059) RichFaces.ui.Message is not a constructor - Nested Tab Panel - Tab Creation In-Reply-To: <1031888240.16896.1332159287591.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1725049679.17099.1332162647466.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean ANDRE updated RF-12059: ---------------------------- Steps to Reproduce: 1) Install the workbench and do no hesitate to ask any information, material if necessary 2) Go to the Home page 3) Click on tab "Items Management" 4) Enter a number and "New List" button - It will open a new tab with a number of item according to the number 5) From the list, click open - The content is refreshed to display a nested tab. At the top of the nested tabs, there are 3 links about tasks (1,2,3). 6) Click on Task Three (3) and you will see the error (activates error count on firebug). The task Three contains only a calendar field with a rich:message tag. > RichFaces.ui.Message is not a constructor - Nested Tab Panel - Tab Creation > --------------------------------------------------------------------------- > > Key: RF-12059 > URL: https://issues.jboss.org/browse/RF-12059 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.2.0.Final > Environment: Websphere 8.0.0.2 - RAD 8 - JSF Mojorra 2.1.6 - Spring 3.0.6 Final - Firefox 10.0.2 - Windows 7 (6.1 sp1) - AspectJ 1.6.12 / AJDT - RichFaces 4.2.0 Final - Hibernate Validator 4.2.0 Final > Reporter: Jean ANDRE > Priority: Blocker > Attachments: NestedWeb_RF-12059.zip > > > We got the following error message, just after a tab has been created or during its creation: > {code} > RichFaces.ui.Message is not a constructor > > return new Function("event", handlerCode); > richfaces.js.jsf (ligne 481) > {code} > This bug is linked to RF-11763 and RF-12030 but the error message and the context are not the same. > The rich:messages is also involved in this bug, the rich:message is attached to a rich:calendar. Removing the rich:message removes the error. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 19 09:16:48 2012 From: jira-events at lists.jboss.org (Jean ANDRE (JIRA)) Date: Mon, 19 Mar 2012 09:16:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12059) RichFaces.ui.Message is not a constructor - Nested Tab Panel - Tab Creation In-Reply-To: <1031888240.16896.1332159287591.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <777160196.17119.1332163008714.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean ANDRE updated RF-12059: ---------------------------- Description: We got the following error message, just after a tab has been created or during its creation. After the error, we are not able to use the application. Everything looks like frozen, tabs do not switch anymore. {code} RichFaces.ui.Message is not a constructor > return new Function("event", handlerCode); richfaces.js.jsf (ligne 481) {code} This bug is linked to RF-11763 and RF-12030 but the error message and the context are not the same. The rich:messages is also involved in this bug, the rich:message is attached to a rich:calendar. Removing the rich:message removes the error. was: We got the following error message, just after a tab has been created or during its creation: {code} RichFaces.ui.Message is not a constructor > return new Function("event", handlerCode); richfaces.js.jsf (ligne 481) {code} This bug is linked to RF-11763 and RF-12030 but the error message and the context are not the same. The rich:messages is also involved in this bug, the rich:message is attached to a rich:calendar. Removing the rich:message removes the error. > RichFaces.ui.Message is not a constructor - Nested Tab Panel - Tab Creation > --------------------------------------------------------------------------- > > Key: RF-12059 > URL: https://issues.jboss.org/browse/RF-12059 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.2.0.Final > Environment: Websphere 8.0.0.2 - RAD 8 - JSF Mojorra 2.1.6 - Spring 3.0.6 Final - Firefox 10.0.2 - Windows 7 (6.1 sp1) - AspectJ 1.6.12 / AJDT - RichFaces 4.2.0 Final - Hibernate Validator 4.2.0 Final > Reporter: Jean ANDRE > Priority: Blocker > Attachments: NestedWeb_RF-12059.zip > > > We got the following error message, just after a tab has been created or during its creation. After the error, we are not able to use the application. Everything looks like frozen, tabs do not switch anymore. > {code} > RichFaces.ui.Message is not a constructor > > return new Function("event", handlerCode); > richfaces.js.jsf (ligne 481) > {code} > This bug is linked to RF-11763 and RF-12030 but the error message and the context are not the same. > The rich:messages is also involved in this bug, the rich:message is attached to a rich:calendar. Removing the rich:message removes the error. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 19 09:18:47 2012 From: jira-events at lists.jboss.org (Jean ANDRE (JIRA)) Date: Mon, 19 Mar 2012 09:18:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12059) RichFaces.ui.Message is not a constructor - Nested Tab Panel - Tab Creation In-Reply-To: <1031888240.16896.1332159287591.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1790962761.17134.1332163127944.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677628#comment-12677628 ] Jean ANDRE edited comment on RF-12059 at 3/19/12 9:18 AM: ---------------------------------------------------------- Here is the workbench to be able to reproduce the bug - Edit the page taskThree.xhtml to test and fix the bug by replacing the rich:message by a h:message. was (Author: jorelia64): Here is the workbench to be able to reproduce the bug. > RichFaces.ui.Message is not a constructor - Nested Tab Panel - Tab Creation > --------------------------------------------------------------------------- > > Key: RF-12059 > URL: https://issues.jboss.org/browse/RF-12059 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.2.0.Final > Environment: Websphere 8.0.0.2 - RAD 8 - JSF Mojorra 2.1.6 - Spring 3.0.6 Final - Firefox 10.0.2 - Windows 7 (6.1 sp1) - AspectJ 1.6.12 / AJDT - RichFaces 4.2.0 Final - Hibernate Validator 4.2.0 Final > Reporter: Jean ANDRE > Priority: Blocker > Attachments: NestedWeb_RF-12059.zip > > > We got the following error message, just after a tab has been created or during its creation. After the error, we are not able to use the application. Everything looks like frozen, tabs do not switch anymore. > {code} > RichFaces.ui.Message is not a constructor > > return new Function("event", handlerCode); > richfaces.js.jsf (ligne 481) > {code} > This bug is linked to RF-11763 and RF-12030 but the error message and the context are not the same. > The rich:messages is also involved in this bug, the rich:message is attached to a rich:calendar. Removing the rich:message removes the error. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 19 09:53:49 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 19 Mar 2012 09:53:49 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11833) Label for calendar results in non-valid markup In-Reply-To: <1824573501.21859.1324327990123.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1566709499.17316.1332165229761.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677644#comment-12677644 ] Luk?? Fry? commented on RF-11833: --------------------------------- There is no simple fix, since what JSF do for encoding {{for}} attribute is just taking client ID: {code:title=JSF RI 2.1.5, LabelRenderer:85|Java} String forClientId = null; String forValue = (String) component.getAttributes().get("for"); if (forValue != null) { forValue = augmentIdReference(forValue, component); UIComponent forComponent = getForComponent(context, forValue, component); if (forComponent == null) { // it could that the component hasn't been created yet. So // construct the clientId for component. forClientId = getForComponentClientId(component, context, forValue); } else { forClientId = forComponent.getClientId(context); } } {code} Problem is RichFaces does not decode inputs for components with complex DOM structure, we use {{clientId}} for the root of the component's DOM and then input needs to have ID/name with suffix. > Label for calendar results in non-valid markup > ---------------------------------------------- > > Key: RF-11833 > URL: https://issues.jboss.org/browse/RF-11833 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.1.0.Final > Reporter: Pavol Pitonak > Assignee: Luk?? Fry? > Priority: Trivial > Fix For: 4.2.1.CR1 > > > The code in first code snippet results in markup below which is not valid. The for attribute of the label element must refer to a form control, e.g. the actual input inside calendar (that with ID dateForm:fromDateInputDate). > {code:xml} > > > {code} > {code:xml} > > > > > ... > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 19 09:55:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 19 Mar 2012 09:55:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11833) Label for calendar results in non-valid markup In-Reply-To: <1824573501.21859.1324327990123.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <2496358.17320.1332165347450.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677644#comment-12677644 ] Luk?? Fry? edited comment on RF-11833 at 3/19/12 9:54 AM: ---------------------------------------------------------- There is no simple fix, since what JSF do for encoding {{for}} attribute is just taking client ID: {code:title=JSF RI 2.1.5, LabelRenderer:85|Java} String forClientId = null; String forValue = (String) component.getAttributes().get("for"); if (forValue != null) { forValue = augmentIdReference(forValue, component); UIComponent forComponent = getForComponent(context, forValue, component); if (forComponent == null) { // it could that the component hasn't been created yet. So // construct the clientId for component. forClientId = getForComponentClientId(component, context, forValue); } else { forClientId = forComponent.getClientId(context); } } {code} Problem is RichFaces does not decode inputs for components with complex DOM structure, we use {{clientId}} for the root of the component's DOM and then input then needs to have ID/name with suffix. was (Author: lfryc): There is no simple fix, since what JSF do for encoding {{for}} attribute is just taking client ID: {code:title=JSF RI 2.1.5, LabelRenderer:85|Java} String forClientId = null; String forValue = (String) component.getAttributes().get("for"); if (forValue != null) { forValue = augmentIdReference(forValue, component); UIComponent forComponent = getForComponent(context, forValue, component); if (forComponent == null) { // it could that the component hasn't been created yet. So // construct the clientId for component. forClientId = getForComponentClientId(component, context, forValue); } else { forClientId = forComponent.getClientId(context); } } {code} Problem is RichFaces does not decode inputs for components with complex DOM structure, we use {{clientId}} for the root of the component's DOM and then input needs to have ID/name with suffix. > Label for calendar results in non-valid markup > ---------------------------------------------- > > Key: RF-11833 > URL: https://issues.jboss.org/browse/RF-11833 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.1.0.Final > Reporter: Pavol Pitonak > Assignee: Luk?? Fry? > Priority: Trivial > Fix For: 4.2.1.CR1 > > > The code in first code snippet results in markup below which is not valid. The for attribute of the label element must refer to a form control, e.g. the actual input inside calendar (that with ID dateForm:fromDateInputDate). > {code:xml} > > > {code} > {code:xml} > > > > > ... > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 19 09:57:48 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 19 Mar 2012 09:57:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11833) Label for calendar results in non-valid markup In-Reply-To: <1824573501.21859.1324327990123.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1235086820.17336.1332165468994.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677644#comment-12677644 ] Luk?? Fry? edited comment on RF-11833 at 3/19/12 9:57 AM: ---------------------------------------------------------- There is no simple fix, since what JSF do for encoding {{for}} attribute is just taking client ID: {code:title=JSF RI 2.1.5, LabelRenderer:85|Java} String forClientId = null; String forValue = (String) component.getAttributes().get("for"); if (forValue != null) { forValue = augmentIdReference(forValue, component); UIComponent forComponent = getForComponent(context, forValue, component); if (forComponent == null) { // it could that the component hasn't been created yet. So // construct the clientId for component. forClientId = getForComponentClientId(component, context, forValue); } else { forClientId = forComponent.getClientId(context); } } {code} When we encode inputs for components with complex DOM structure, we use {{clientId}} for the root of the component's DOM and then input then needs to have ID/name with suffix, which is expected behavior. was (Author: lfryc): There is no simple fix, since what JSF do for encoding {{for}} attribute is just taking client ID: {code:title=JSF RI 2.1.5, LabelRenderer:85|Java} String forClientId = null; String forValue = (String) component.getAttributes().get("for"); if (forValue != null) { forValue = augmentIdReference(forValue, component); UIComponent forComponent = getForComponent(context, forValue, component); if (forComponent == null) { // it could that the component hasn't been created yet. So // construct the clientId for component. forClientId = getForComponentClientId(component, context, forValue); } else { forClientId = forComponent.getClientId(context); } } {code} Problem is RichFaces does not decode inputs for components with complex DOM structure, we use {{clientId}} for the root of the component's DOM and then input then needs to have ID/name with suffix. > Label for calendar results in non-valid markup > ---------------------------------------------- > > Key: RF-11833 > URL: https://issues.jboss.org/browse/RF-11833 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.1.0.Final > Reporter: Pavol Pitonak > Assignee: Luk?? Fry? > Priority: Trivial > Fix For: 4.2.1.CR1 > > > The code in first code snippet results in markup below which is not valid. The for attribute of the label element must refer to a form control, e.g. the actual input inside calendar (that with ID dateForm:fromDateInputDate). > {code:xml} > > > {code} > {code:xml} > > > > > ... > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 19 09:59:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 19 Mar 2012 09:59:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11833) Label for calendar results in non-valid markup In-Reply-To: <1824573501.21859.1324327990123.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1520334.17339.1332165587892.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677646#comment-12677646 ] Luk?? Fry? commented on RF-11833: --------------------------------- I don't think this issue can be fixed on our side - it even can't be fixed without introducing additional logic for all input fields, like {{UIInput#getInputClientId()}}. > Label for calendar results in non-valid markup > ---------------------------------------------- > > Key: RF-11833 > URL: https://issues.jboss.org/browse/RF-11833 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.1.0.Final > Reporter: Pavol Pitonak > Assignee: Luk?? Fry? > Priority: Trivial > Fix For: 4.2.1.CR1 > > > The code in first code snippet results in markup below which is not valid. The for attribute of the label element must refer to a form control, e.g. the actual input inside calendar (that with ID dateForm:fromDateInputDate). > {code:xml} > > > {code} > {code:xml} > > > > > ... > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 19 10:01:48 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 19 Mar 2012 10:01:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11833) Label for calendar results in non-valid markup In-Reply-To: <1824573501.21859.1324327990123.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1016187997.17357.1332165708217.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677644#comment-12677644 ] Luk?? Fry? edited comment on RF-11833 at 3/19/12 10:01 AM: ----------------------------------------------------------- There is no simple fix, since what JSF do for encoding {{for}} attribute is just taking client ID: {code:title=JSF RI 2.1.5, LabelRenderer:85|Java} String forClientId = null; String forValue = (String) component.getAttributes().get("for"); if (forValue != null) { forValue = augmentIdReference(forValue, component); UIComponent forComponent = getForComponent(context, forValue, component); if (forComponent == null) { // it could that the component hasn't been created yet. So // construct the clientId for component. forClientId = getForComponentClientId(component, context, forValue); } else { forClientId = forComponent.getClientId(context); } } {code} When we encode inputs for components with complex DOM structure, we use {{clientId}} for the root of the component's DOM and then input then needs to have ID/name with suffix, which is expected behavior. Then using {{clientId}} for input [1] would lead to incompatibility with AJAX, which expects having {{clientId}} on the root of the component's DOM. [1] https://github.com/richfaces/components/blob/develop/input/ui/src/main/templates/calendar.template.xml#L30 was (Author: lfryc): There is no simple fix, since what JSF do for encoding {{for}} attribute is just taking client ID: {code:title=JSF RI 2.1.5, LabelRenderer:85|Java} String forClientId = null; String forValue = (String) component.getAttributes().get("for"); if (forValue != null) { forValue = augmentIdReference(forValue, component); UIComponent forComponent = getForComponent(context, forValue, component); if (forComponent == null) { // it could that the component hasn't been created yet. So // construct the clientId for component. forClientId = getForComponentClientId(component, context, forValue); } else { forClientId = forComponent.getClientId(context); } } {code} When we encode inputs for components with complex DOM structure, we use {{clientId}} for the root of the component's DOM and then input then needs to have ID/name with suffix, which is expected behavior. > Label for calendar results in non-valid markup > ---------------------------------------------- > > Key: RF-11833 > URL: https://issues.jboss.org/browse/RF-11833 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.1.0.Final > Reporter: Pavol Pitonak > Assignee: Luk?? Fry? > Priority: Trivial > Fix For: 4.2.1.CR1 > > > The code in first code snippet results in markup below which is not valid. The for attribute of the label element must refer to a form control, e.g. the actual input inside calendar (that with ID dateForm:fromDateInputDate). > {code:xml} > > > {code} > {code:xml} > > > > > ... > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 19 10:05:48 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 19 Mar 2012 10:05:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11833) Label for calendar results in non-valid markup In-Reply-To: <1824573501.21859.1324327990123.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1211577201.17378.1332165948772.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? reassigned RF-11833: ------------------------------- Assignee: Brian Leathem (was: Luk?? Fry?) Hi Brian, could you please review the issue as I think this can't be fixed on our side? I would consider reporting this to the JSF SPEC issue tracker. I did preliminary scan through SPEC/RI issues and didn't find such issue. > Label for calendar results in non-valid markup > ---------------------------------------------- > > Key: RF-11833 > URL: https://issues.jboss.org/browse/RF-11833 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.1.0.Final > Reporter: Pavol Pitonak > Assignee: Brian Leathem > Priority: Trivial > Fix For: 4.2.1.CR1 > > > The code in first code snippet results in markup below which is not valid. The for attribute of the label element must refer to a form control, e.g. the actual input inside calendar (that with ID dateForm:fromDateInputDate). > {code:xml} > > > {code} > {code:xml} > > > > > ... > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 19 10:24:48 2012 From: jira-events at lists.jboss.org (Jean ANDRE (JIRA)) Date: Mon, 19 Mar 2012 10:24:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12060) element is null message when closing tab from an event click Message-ID: <1849991598.17427.1332167088202.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Jean ANDRE created RF-12060: ------------------------------- Summary: element is null message when closing tab from an event click Key: RF-12060 URL: https://issues.jboss.org/browse/RF-12060 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.2.0.Final Environment: Websphere 8.0.0.2 - RAD 8 - JSF Mojorra 2.1.6 - Spring 3.0.6 Final - Firefox 10.0.2 - Windows 7 (6.1 sp1) - AspectJ 1.6.12 / AJDT - RichFaces 4.2.0 Final - Hibernate Validator 4.2.0 Final Reporter: Jean ANDRE There is a link to RF-11950. We got the message "element is null" when we send a click event for closing a tab. To retrieve the id of the close button (an image), we use the function getElementById (because of RF-11950). The click function calls a javascript function declared by a4j:jsFunction (see index.hxtml file - close task). This is the only information we have from firebug. When we close the tab directly by clicking on the close button/image, it works perfectly. *Note :* Moreover, there is also a strange behavior related to generated id on close button/image. When we specified a fix id on the h:graphicImage, the first id is correct but there is no id on other close button/image from other tabs!???. Having a fix id should trigger a duplicate ID but as the ids are not generated on other tabs, it does not. {code}     {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 19 10:30:48 2012 From: jira-events at lists.jboss.org (Jean ANDRE (JIRA)) Date: Mon, 19 Mar 2012 10:30:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12060) element is null message when closing tab from an event click In-Reply-To: <1849991598.17427.1332167088202.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <292947504.17462.1332167448282.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean ANDRE updated RF-12060: ---------------------------- Steps to Reproduce: 1) Install the workbench and do no hesitate to ask any information, material if necessary 1.1) See the readme.txt file enclosed in the zip file 2) Go to the Home page 3) Click on tab "Items Management" 4) Enter a number and "New List" button - It will open a new tab with a number of items according to the number 5) From the list, click open - The content is refreshed to display a nested tab. At the top of the nested tabs, there are 3 links about tasks (1,2,3). 6) Click on any task link, it will open a new tab (dynamic tabs have a close button) 7) Then click on the close button labelled "Close by getElementbyID" and you will see the error. was: 1) Install the workbench and do no hesitate to ask any information, material if necessary 2) Go to the Home page 3) Click on tab "Items Management" 4) Enter a number and "New List" button - It will open a new tab with a number of items according to the number 5) From the list, click open - The content is refreshed to display a nested tab. At the top of the nested tabs, there are 3 links about tasks (1,2,3). 6) Click on any task link, it will open a new tab (dynamic tabs have a close button) 7) Then click on the close button labelled "Close by getElementbyID" and you will see the error. > element is null message when closing tab from an event click > ------------------------------------------------------------ > > Key: RF-12060 > URL: https://issues.jboss.org/browse/RF-12060 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.2.0.Final > Environment: Websphere 8.0.0.2 - RAD 8 - JSF Mojorra 2.1.6 - Spring 3.0.6 Final - Firefox 10.0.2 - Windows 7 (6.1 sp1) - AspectJ 1.6.12 / AJDT - RichFaces 4.2.0 Final - Hibernate Validator 4.2.0 Final > Reporter: Jean ANDRE > Attachments: NestedWeb_RF-12060.zip > > > There is a link to RF-11950. > We got the message "element is null" when we send a click event for closing a tab. To retrieve the id of the close button (an image), we use the function getElementById (because of RF-11950). The click function calls a javascript function declared by a4j:jsFunction (see index.hxtml file - close task). > This is the only information we have from firebug. When we close the tab directly by clicking on the close button/image, it works perfectly. > *Note :* Moreover, there is also a strange behavior related to generated id on close button/image. When we specified a fix id on the h:graphicImage, the first id is correct but there is no id on other close button/image from other tabs!???. Having a fix id should trigger a duplicate ID but as the ids are not generated on other tabs, it does not. > {code} > >   title="#{msg[task.uiActivity.headerKey]}" /> >   styleClass="closeButton" > onclick="closeTask('#{task.id}');event.stopPropagation();" /> > > > > > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 19 10:44:48 2012 From: jira-events at lists.jboss.org (Ibrahim Abu Ghosh (JIRA)) Date: Mon, 19 Mar 2012 10:44:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12061) pickList direction Message-ID: <138392524.17532.1332168288239.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Ibrahim Abu Ghosh created RF-12061: -------------------------------------- Summary: pickList direction Key: RF-12061 URL: https://issues.jboss.org/browse/RF-12061 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-selects Affects Versions: 4.1.0.Final Environment: RF 4.1, JSF 2 Mojarra 2.0.8 Reporter: Ibrahim Abu Ghosh when i set the body direction to "rtl" and click or do any action on pickList the whole page shift to left. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 19 10:44:48 2012 From: jira-events at lists.jboss.org (Bernard Labno (JIRA)) Date: Mon, 19 Mar 2012 10:44:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12029) AbstractTogglePanel should extend UIRepeat, instead of UIOutput In-Reply-To: <1430073926.75557.1331161056577.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <902809892.17539.1332168288981.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677669#comment-12677669 ] Bernard Labno commented on RF-12029: ------------------------------------ Lukas, Which API seems better, the one with built in value/var or with nested ui:repeat? > AbstractTogglePanel should extend UIRepeat, instead of UIOutput > --------------------------------------------------------------- > > Key: RF-12029 > URL: https://issues.jboss.org/browse/RF-12029 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-output > Reporter: Brian Leathem > Assignee: Bernard Labno > > Valid uses exist for dynamically generating rich:tab, rich:togglePanelItem, rich:accordionItem. Current techniques for supporting this use case involve using c:forEach, which is a problem since c: tags are processed too early to nicely support dynamic use cases. > One idea to support this use case, is to have AbstractTogglePanel extend UIRepeat, instead of UIOutput to better dynamic child components. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 19 12:55:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 19 Mar 2012 12:55:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12013) Deadlock in push component In-Reply-To: <654291399.48838.1330441536575.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <917806789.17999.1332176147379.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12676911#comment-12676911 ] Luk?? Fry? edited comment on RF-12013 at 3/19/12 12:54 PM: ----------------------------------------------------------- Hi Stian, thanks for the report, there is really the race condition caused by initiating shutdown (destroying push SessionImpl) in time when session tries to post messages. was (Author: lfryc): Hi Stian, thanks for the report, there is really the deadlock caused by initiating shutdown (destroying push SessionImpl) in time when session tries to post messages. > Deadlock in push component > -------------------------- > > Key: RF-12013 > URL: https://issues.jboss.org/browse/RF-12013 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Affects Versions: 4.2.0.Final > Reporter: Stian Thorgersen > Assignee: Luk?? Fry? > Fix For: 4.2.1.CR1 > > > Deadlocked threads in the push component prevented server from stopping. Not sure whether or not this happened when I initiated shutdown or if these where hanging around for a while. > Relevant output from jstack: > {code} > Found one Java-level deadlock: > ============================= > "push-publish-thread-1": > waiting to lock monitor 0x0000000042650238 (object 0x00000000e5ed5a50, a org.richfaces.application.push.impl.RequestImpl), > which is held by "Atmosphere-AsyncWrite-0" > "Atmosphere-AsyncWrite-0": > waiting to lock monitor 0x00000000427d9ec0 (object 0x00000000e5ed59a0, a org.richfaces.application.push.impl.SessionImpl), > which is held by "push-publish-thread-1" > Java stack information for the threads listed above: > =================================================== > "push-publish-thread-1": > at org.richfaces.application.push.impl.RequestImpl.postMessages(RequestImpl.java:85) > - waiting to lock <0x00000000e5ed5a50> (a org.richfaces.application.push.impl.RequestImpl) > at org.richfaces.application.push.impl.SessionImpl.push(SessionImpl.java:237) > - locked <0x00000000e5ed59a0> (a org.richfaces.application.push.impl.SessionImpl) > at org.richfaces.application.push.impl.TopicImpl$TopicContext.publishMessages(TopicImpl.java:88) > at org.richfaces.application.push.impl.TopicImpl$PublishTask.run(TopicImpl.java:53) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:662) > "Atmosphere-AsyncWrite-0": > at org.richfaces.application.push.impl.SessionImpl.disconnect(SessionImpl.java:117) > - waiting to lock <0x00000000e5ed59a0> (a org.richfaces.application.push.impl.SessionImpl) > at org.richfaces.application.push.impl.RequestImpl.disconnect(RequestImpl.java:107) > at org.richfaces.application.push.impl.RequestImpl.onResume(RequestImpl.java:115) > at org.atmosphere.cpr.AtmosphereResourceImpl.onResume(AtmosphereResourceImpl.java:651) > at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:600) > at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:584) > at org.atmosphere.cpr.AtmosphereResourceImpl.resume(AtmosphereResourceImpl.java:185) > - locked <0x00000000e5ee3380> (a org.atmosphere.cpr.AtmosphereResourceEventImpl) > at org.richfaces.application.push.impl.RequestImpl.onBroadcast(RequestImpl.java:129) > - locked <0x00000000e5ed5a50> (a org.richfaces.application.push.impl.RequestImpl) > at org.atmosphere.cpr.AtmosphereResourceImpl.onBroadcast(AtmosphereResourceImpl.java:663) > at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:608) > at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:584) > at org.atmosphere.cpr.DefaultBroadcaster.executeAsyncWrite(DefaultBroadcaster.java:713) > at org.atmosphere.cpr.DefaultBroadcaster$3.run(DefaultBroadcaster.java:747) > - locked <0x00000000e5ed5a88> (a org.atmosphere.cpr.AtmosphereResourceImpl) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:662) > Found 1 deadlock. > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 19 13:07:47 2012 From: jira-events at lists.jboss.org (Toni Neubert (JIRA)) Date: Mon, 19 Mar 2012 13:07:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12062) a4j:outputMedia does not reRender in Firefox 11 Message-ID: <1235192300.18015.1332176867445.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Toni Neubert created RF-12062: --------------------------------- Summary: a4j:outputMedia does not reRender in Firefox 11 Key: RF-12062 URL: https://issues.jboss.org/browse/RF-12062 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-output Affects Versions: 3.3.3.Final Environment: JBoss AS 6 Reporter: Toni Neubert a4j:outputMedia does not reRender in Firefox 11. The following error appears: ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/BPM-Process].[default]] Servlet.service() for servlet default threw exception: javax.faces.FacesException: Error decode resource data at org.ajax4jsf.resource.ResourceBuilderImpl.decrypt(ResourceBuilderImpl.java:627) [:3.3.3.Final] at org.ajax4jsf.resource.ResourceBuilderImpl.getResourceDataForKey(ResourceBuilderImpl.java:371) [:3.3.3.Final] at org.ajax4jsf.resource.InternetResourceService.serviceResource(InternetResourceService.java:156) [:3.3.3.Final] at org.ajax4jsf.resource.InternetResourceService.serviceResource(InternetResourceService.java:141) [:3.3.3.Final] at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:508) [:3.3.3.Final] at org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:56) [:2.2.2.Final] at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) [:2.2.2.Final] at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:60) [:2.2.2.Final] at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) [:2.2.2.Final] at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:73) [:2.2.2.Final] at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) [:2.2.2.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:274) [:6.1.0.Final] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242) [:6.1.0.Final] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [:6.1.0.Final] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [:6.1.0.Final] at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:181) [:6.1.0.Final] at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:501) [:6.1.0.Final] at org.jboss.modcluster.catalina.CatalinaContext$RequestListenerValve.event(CatalinaContext.java:285) [:1.1.0.Final] at org.jboss.modcluster.catalina.CatalinaContext$RequestListenerValve.invoke(CatalinaContext.java:261) [:1.1.0.Final] at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:88) [:6.1.0.Final] at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:100) [:6.1.0.Final] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:159) [:6.1.0.Final] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [:6.1.0.Final] at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) [:6.1.0.Final] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [:6.1.0.Final] at org.jboss.web.tomcat.service.request.ActiveRequestResponseCacheValve.invoke(ActiveRequestResponseCacheValve.java:53) [:6.1.0.Final] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) [:6.1.0.Final] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [:6.1.0.Final] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:654) [:6.1.0.Final] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:951) [:6.1.0.Final] at java.lang.Thread.run(Unknown Source) [:1.6.0_31] Caused by: java.util.zip.DataFormatException: invalid bit length repeat at java.util.zip.Inflater.inflateBytes(Native Method) [:1.6.0_31] at java.util.zip.Inflater.inflate(Unknown Source) [:1.6.0_31] at java.util.zip.Inflater.inflate(Unknown Source) [:1.6.0_31] at org.ajax4jsf.resource.ResourceBuilderImpl.decrypt(ResourceBuilderImpl.java:621) [:3.3.3.Final] ... 30 more The picture is not visible. But if you refresh the site with f5, there is no error and all works great. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 19 13:09:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 19 Mar 2012 13:09:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12013) Deadlock in push component In-Reply-To: <654291399.48838.1330441536575.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1405904575.18029.1332176987371.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677731#comment-12677731 ] Luk?? Fry? commented on RF-12013: --------------------------------- There are several resources which needs to be locked in {{SessionImpl}} (or maybe more): {{boolean active}} and {{Request request}}. On the other hand, there is only resource in {{RequestImpl}} in the race condition: {{hasActiveBroadcaster}}. ---- I propose to use {{AtomicBoolean}} instead of synchronization to lock broadcasting process - we will ensure that there is no race condition on {{RequestImpl}} and thus no circular dependency. > Deadlock in push component > -------------------------- > > Key: RF-12013 > URL: https://issues.jboss.org/browse/RF-12013 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Affects Versions: 4.2.0.Final > Reporter: Stian Thorgersen > Assignee: Luk?? Fry? > Fix For: 4.2.1.CR1 > > > Deadlocked threads in the push component prevented server from stopping. Not sure whether or not this happened when I initiated shutdown or if these where hanging around for a while. > Relevant output from jstack: > {code} > Found one Java-level deadlock: > ============================= > "push-publish-thread-1": > waiting to lock monitor 0x0000000042650238 (object 0x00000000e5ed5a50, a org.richfaces.application.push.impl.RequestImpl), > which is held by "Atmosphere-AsyncWrite-0" > "Atmosphere-AsyncWrite-0": > waiting to lock monitor 0x00000000427d9ec0 (object 0x00000000e5ed59a0, a org.richfaces.application.push.impl.SessionImpl), > which is held by "push-publish-thread-1" > Java stack information for the threads listed above: > =================================================== > "push-publish-thread-1": > at org.richfaces.application.push.impl.RequestImpl.postMessages(RequestImpl.java:85) > - waiting to lock <0x00000000e5ed5a50> (a org.richfaces.application.push.impl.RequestImpl) > at org.richfaces.application.push.impl.SessionImpl.push(SessionImpl.java:237) > - locked <0x00000000e5ed59a0> (a org.richfaces.application.push.impl.SessionImpl) > at org.richfaces.application.push.impl.TopicImpl$TopicContext.publishMessages(TopicImpl.java:88) > at org.richfaces.application.push.impl.TopicImpl$PublishTask.run(TopicImpl.java:53) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:662) > "Atmosphere-AsyncWrite-0": > at org.richfaces.application.push.impl.SessionImpl.disconnect(SessionImpl.java:117) > - waiting to lock <0x00000000e5ed59a0> (a org.richfaces.application.push.impl.SessionImpl) > at org.richfaces.application.push.impl.RequestImpl.disconnect(RequestImpl.java:107) > at org.richfaces.application.push.impl.RequestImpl.onResume(RequestImpl.java:115) > at org.atmosphere.cpr.AtmosphereResourceImpl.onResume(AtmosphereResourceImpl.java:651) > at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:600) > at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:584) > at org.atmosphere.cpr.AtmosphereResourceImpl.resume(AtmosphereResourceImpl.java:185) > - locked <0x00000000e5ee3380> (a org.atmosphere.cpr.AtmosphereResourceEventImpl) > at org.richfaces.application.push.impl.RequestImpl.onBroadcast(RequestImpl.java:129) > - locked <0x00000000e5ed5a50> (a org.richfaces.application.push.impl.RequestImpl) > at org.atmosphere.cpr.AtmosphereResourceImpl.onBroadcast(AtmosphereResourceImpl.java:663) > at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:608) > at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:584) > at org.atmosphere.cpr.DefaultBroadcaster.executeAsyncWrite(DefaultBroadcaster.java:713) > at org.atmosphere.cpr.DefaultBroadcaster$3.run(DefaultBroadcaster.java:747) > - locked <0x00000000e5ed5a88> (a org.atmosphere.cpr.AtmosphereResourceImpl) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:662) > Found 1 deadlock. > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 19 13:28:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 19 Mar 2012 13:28:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12013) Deadlock in push component In-Reply-To: <654291399.48838.1330441536575.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1013110061.18083.1332178127434.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677739#comment-12677739 ] Luk?? Fry? commented on RF-12013: --------------------------------- Sent pull request and tested on Showcase. Stian, it would be great if you could grab the source and build {{richfaces-core-impl}} and try in your project. > Deadlock in push component > -------------------------- > > Key: RF-12013 > URL: https://issues.jboss.org/browse/RF-12013 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Affects Versions: 4.2.0.Final > Reporter: Stian Thorgersen > Assignee: Luk?? Fry? > Fix For: 4.2.1.CR1 > > > Deadlocked threads in the push component prevented server from stopping. Not sure whether or not this happened when I initiated shutdown or if these where hanging around for a while. > Relevant output from jstack: > {code} > Found one Java-level deadlock: > ============================= > "push-publish-thread-1": > waiting to lock monitor 0x0000000042650238 (object 0x00000000e5ed5a50, a org.richfaces.application.push.impl.RequestImpl), > which is held by "Atmosphere-AsyncWrite-0" > "Atmosphere-AsyncWrite-0": > waiting to lock monitor 0x00000000427d9ec0 (object 0x00000000e5ed59a0, a org.richfaces.application.push.impl.SessionImpl), > which is held by "push-publish-thread-1" > Java stack information for the threads listed above: > =================================================== > "push-publish-thread-1": > at org.richfaces.application.push.impl.RequestImpl.postMessages(RequestImpl.java:85) > - waiting to lock <0x00000000e5ed5a50> (a org.richfaces.application.push.impl.RequestImpl) > at org.richfaces.application.push.impl.SessionImpl.push(SessionImpl.java:237) > - locked <0x00000000e5ed59a0> (a org.richfaces.application.push.impl.SessionImpl) > at org.richfaces.application.push.impl.TopicImpl$TopicContext.publishMessages(TopicImpl.java:88) > at org.richfaces.application.push.impl.TopicImpl$PublishTask.run(TopicImpl.java:53) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:662) > "Atmosphere-AsyncWrite-0": > at org.richfaces.application.push.impl.SessionImpl.disconnect(SessionImpl.java:117) > - waiting to lock <0x00000000e5ed59a0> (a org.richfaces.application.push.impl.SessionImpl) > at org.richfaces.application.push.impl.RequestImpl.disconnect(RequestImpl.java:107) > at org.richfaces.application.push.impl.RequestImpl.onResume(RequestImpl.java:115) > at org.atmosphere.cpr.AtmosphereResourceImpl.onResume(AtmosphereResourceImpl.java:651) > at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:600) > at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:584) > at org.atmosphere.cpr.AtmosphereResourceImpl.resume(AtmosphereResourceImpl.java:185) > - locked <0x00000000e5ee3380> (a org.atmosphere.cpr.AtmosphereResourceEventImpl) > at org.richfaces.application.push.impl.RequestImpl.onBroadcast(RequestImpl.java:129) > - locked <0x00000000e5ed5a50> (a org.richfaces.application.push.impl.RequestImpl) > at org.atmosphere.cpr.AtmosphereResourceImpl.onBroadcast(AtmosphereResourceImpl.java:663) > at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:608) > at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:584) > at org.atmosphere.cpr.DefaultBroadcaster.executeAsyncWrite(DefaultBroadcaster.java:713) > at org.atmosphere.cpr.DefaultBroadcaster$3.run(DefaultBroadcaster.java:747) > - locked <0x00000000e5ed5a88> (a org.atmosphere.cpr.AtmosphereResourceImpl) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:662) > Found 1 deadlock. > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 19 13:28:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 19 Mar 2012 13:28:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12013) Deadlock in push component In-Reply-To: <654291399.48838.1330441536575.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1867511886.18094.1332178127945.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677739#comment-12677739 ] Luk?? Fry? edited comment on RF-12013 at 3/19/12 1:28 PM: ---------------------------------------------------------- Sent pull request and tested on Showcase. Stian, it would be great if you could grab the source and build {{richfaces-core-impl}} and try in your project. Let me know if you would like to test that and I could offer you any assistance. was (Author: lfryc): Sent pull request and tested on Showcase. Stian, it would be great if you could grab the source and build {{richfaces-core-impl}} and try in your project. > Deadlock in push component > -------------------------- > > Key: RF-12013 > URL: https://issues.jboss.org/browse/RF-12013 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Affects Versions: 4.2.0.Final > Reporter: Stian Thorgersen > Assignee: Luk?? Fry? > Fix For: 4.2.1.CR1 > > > Deadlocked threads in the push component prevented server from stopping. Not sure whether or not this happened when I initiated shutdown or if these where hanging around for a while. > Relevant output from jstack: > {code} > Found one Java-level deadlock: > ============================= > "push-publish-thread-1": > waiting to lock monitor 0x0000000042650238 (object 0x00000000e5ed5a50, a org.richfaces.application.push.impl.RequestImpl), > which is held by "Atmosphere-AsyncWrite-0" > "Atmosphere-AsyncWrite-0": > waiting to lock monitor 0x00000000427d9ec0 (object 0x00000000e5ed59a0, a org.richfaces.application.push.impl.SessionImpl), > which is held by "push-publish-thread-1" > Java stack information for the threads listed above: > =================================================== > "push-publish-thread-1": > at org.richfaces.application.push.impl.RequestImpl.postMessages(RequestImpl.java:85) > - waiting to lock <0x00000000e5ed5a50> (a org.richfaces.application.push.impl.RequestImpl) > at org.richfaces.application.push.impl.SessionImpl.push(SessionImpl.java:237) > - locked <0x00000000e5ed59a0> (a org.richfaces.application.push.impl.SessionImpl) > at org.richfaces.application.push.impl.TopicImpl$TopicContext.publishMessages(TopicImpl.java:88) > at org.richfaces.application.push.impl.TopicImpl$PublishTask.run(TopicImpl.java:53) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:662) > "Atmosphere-AsyncWrite-0": > at org.richfaces.application.push.impl.SessionImpl.disconnect(SessionImpl.java:117) > - waiting to lock <0x00000000e5ed59a0> (a org.richfaces.application.push.impl.SessionImpl) > at org.richfaces.application.push.impl.RequestImpl.disconnect(RequestImpl.java:107) > at org.richfaces.application.push.impl.RequestImpl.onResume(RequestImpl.java:115) > at org.atmosphere.cpr.AtmosphereResourceImpl.onResume(AtmosphereResourceImpl.java:651) > at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:600) > at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:584) > at org.atmosphere.cpr.AtmosphereResourceImpl.resume(AtmosphereResourceImpl.java:185) > - locked <0x00000000e5ee3380> (a org.atmosphere.cpr.AtmosphereResourceEventImpl) > at org.richfaces.application.push.impl.RequestImpl.onBroadcast(RequestImpl.java:129) > - locked <0x00000000e5ed5a50> (a org.richfaces.application.push.impl.RequestImpl) > at org.atmosphere.cpr.AtmosphereResourceImpl.onBroadcast(AtmosphereResourceImpl.java:663) > at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:608) > at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:584) > at org.atmosphere.cpr.DefaultBroadcaster.executeAsyncWrite(DefaultBroadcaster.java:713) > at org.atmosphere.cpr.DefaultBroadcaster$3.run(DefaultBroadcaster.java:747) > - locked <0x00000000e5ed5a88> (a org.atmosphere.cpr.AtmosphereResourceImpl) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:662) > Found 1 deadlock. > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 19 13:40:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 19 Mar 2012 13:40:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12029) AbstractTogglePanel should extend UIRepeat, instead of UIOutput In-Reply-To: <1430073926.75557.1331161056577.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <965379661.18135.1332178847607.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677748#comment-12677748 ] Luk?? Fry? commented on RF-12029: --------------------------------- I consider the one with nested {{ui:repeat}} better since it's more flexible - allows to use combination of dynamic/static tabs. > AbstractTogglePanel should extend UIRepeat, instead of UIOutput > --------------------------------------------------------------- > > Key: RF-12029 > URL: https://issues.jboss.org/browse/RF-12029 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-output > Reporter: Brian Leathem > Assignee: Bernard Labno > > Valid uses exist for dynamically generating rich:tab, rich:togglePanelItem, rich:accordionItem. Current techniques for supporting this use case involve using c:forEach, which is a problem since c: tags are processed too early to nicely support dynamic use cases. > One idea to support this use case, is to have AbstractTogglePanel extend UIRepeat, instead of UIOutput to better dynamic child components. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 19 14:10:47 2012 From: jira-events at lists.jboss.org (Brendan Healey (JIRA)) Date: Mon, 19 Mar 2012 14:10:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12063) rich:notifyMessages not displaying error from valueChangeListener Message-ID: <71281469.18246.1332180647276.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Brendan Healey created RF-12063: ----------------------------------- Summary: rich:notifyMessages not displaying error from valueChangeListener Key: RF-12063 URL: https://issues.jboss.org/browse/RF-12063 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Components: component-output Affects Versions: 4.2.0.Final Environment: Mojarra 2.1.7, RF 4.2.0.Final, Windows 7, Glassfish 3.1.2, Chrome browser. Reporter: Brendan Healey I have a global notifyMessages in a template . I log a global error in the usual way from a value change listener (process validations phase): FacesMessage message = getFacesMessage(errKey); message.setSeverity(FacesMessage.SEVERITY_ERROR); FacesContext.getCurrentInstance().addMessage(null, message); but the error never appears. If I have an h:messages on the page which is ajax rendered the message appears ok. Regards, Brendan. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 19 14:12:47 2012 From: jira-events at lists.jboss.org (Brendan Healey (JIRA)) Date: Mon, 19 Mar 2012 14:12:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12063) rich:notifyMessages not displaying error from valueChangeListener In-Reply-To: <71281469.18246.1332180647276.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1291271954.18253.1332180767449.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677764#comment-12677764 ] Brendan Healey commented on RF-12063: ------------------------------------- p.s. I also had the same problem in a validator= method. > rich:notifyMessages not displaying error from valueChangeListener > ----------------------------------------------------------------- > > Key: RF-12063 > URL: https://issues.jboss.org/browse/RF-12063 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.2.0.Final > Environment: Mojarra 2.1.7, RF 4.2.0.Final, Windows 7, Glassfish 3.1.2, Chrome browser. > Reporter: Brendan Healey > > I have a global notifyMessages in a template . > I log a global error in the usual way from a value change listener (process validations > phase): > FacesMessage message = getFacesMessage(errKey); > message.setSeverity(FacesMessage.SEVERITY_ERROR); > FacesContext.getCurrentInstance().addMessage(null, message); > but the error never appears. If I have an h:messages on the page which is ajax > rendered the message appears ok. > Regards, > Brendan. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 19 17:53:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 19 Mar 2012 17:53:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12013) Deadlock in push component In-Reply-To: <654291399.48838.1330441536575.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1783184862.18856.1332194027530.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated RF-12013: ---------------------------- Fix Version/s: 4.3.0.Milestone1 (was: 4.2.1.CR1) Git Pull Request: https://github.com/richfaces/core/pull/8 (was: https://github.com/richfaces/core/pull/8) > Deadlock in push component > -------------------------- > > Key: RF-12013 > URL: https://issues.jboss.org/browse/RF-12013 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Affects Versions: 4.2.0.Final > Reporter: Stian Thorgersen > Assignee: Luk?? Fry? > Fix For: 4.3.0.Milestone1 > > > Deadlocked threads in the push component prevented server from stopping. Not sure whether or not this happened when I initiated shutdown or if these where hanging around for a while. > Relevant output from jstack: > {code} > Found one Java-level deadlock: > ============================= > "push-publish-thread-1": > waiting to lock monitor 0x0000000042650238 (object 0x00000000e5ed5a50, a org.richfaces.application.push.impl.RequestImpl), > which is held by "Atmosphere-AsyncWrite-0" > "Atmosphere-AsyncWrite-0": > waiting to lock monitor 0x00000000427d9ec0 (object 0x00000000e5ed59a0, a org.richfaces.application.push.impl.SessionImpl), > which is held by "push-publish-thread-1" > Java stack information for the threads listed above: > =================================================== > "push-publish-thread-1": > at org.richfaces.application.push.impl.RequestImpl.postMessages(RequestImpl.java:85) > - waiting to lock <0x00000000e5ed5a50> (a org.richfaces.application.push.impl.RequestImpl) > at org.richfaces.application.push.impl.SessionImpl.push(SessionImpl.java:237) > - locked <0x00000000e5ed59a0> (a org.richfaces.application.push.impl.SessionImpl) > at org.richfaces.application.push.impl.TopicImpl$TopicContext.publishMessages(TopicImpl.java:88) > at org.richfaces.application.push.impl.TopicImpl$PublishTask.run(TopicImpl.java:53) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:662) > "Atmosphere-AsyncWrite-0": > at org.richfaces.application.push.impl.SessionImpl.disconnect(SessionImpl.java:117) > - waiting to lock <0x00000000e5ed59a0> (a org.richfaces.application.push.impl.SessionImpl) > at org.richfaces.application.push.impl.RequestImpl.disconnect(RequestImpl.java:107) > at org.richfaces.application.push.impl.RequestImpl.onResume(RequestImpl.java:115) > at org.atmosphere.cpr.AtmosphereResourceImpl.onResume(AtmosphereResourceImpl.java:651) > at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:600) > at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:584) > at org.atmosphere.cpr.AtmosphereResourceImpl.resume(AtmosphereResourceImpl.java:185) > - locked <0x00000000e5ee3380> (a org.atmosphere.cpr.AtmosphereResourceEventImpl) > at org.richfaces.application.push.impl.RequestImpl.onBroadcast(RequestImpl.java:129) > - locked <0x00000000e5ed5a50> (a org.richfaces.application.push.impl.RequestImpl) > at org.atmosphere.cpr.AtmosphereResourceImpl.onBroadcast(AtmosphereResourceImpl.java:663) > at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:608) > at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:584) > at org.atmosphere.cpr.DefaultBroadcaster.executeAsyncWrite(DefaultBroadcaster.java:713) > at org.atmosphere.cpr.DefaultBroadcaster$3.run(DefaultBroadcaster.java:747) > - locked <0x00000000e5ed5a88> (a org.atmosphere.cpr.AtmosphereResourceImpl) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:662) > Found 1 deadlock. > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 19 19:50:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 19 Mar 2012 19:50:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12064) Remove the superfluous versions from the generated pom in the kitchensink archetype Message-ID: <1846737024.18946.1332201047228.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Brian Leathem created RF-12064: ---------------------------------- Summary: Remove the superfluous versions from the generated pom in the kitchensink archetype Key: RF-12064 URL: https://issues.jboss.org/browse/RF-12064 Project: RichFaces Issue Type: Task Security Level: Public (Everyone can see) Components: archetype, build/distribution Reporter: Brian Leathem Priority: Minor Fix For: 4.2.1.CR1 The kitchensink archetype unnecessarily specifies version for it's dependencies. The dependency version that are already specified in the BOM should be removed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 20 06:30:52 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 20 Mar 2012 06:30:52 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-7351) Regression: "messages: globalOnly does not work properly" In-Reply-To: <11790963.1244614376426.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <1193392615.19679.1332239452091.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-7351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677921#comment-12677921 ] Luk?? Fry? commented on RF-7351: -------------------------------- I have run into the same issue with following sample: https://github.com/lfryc/quickstart/tree/quickstart-28/richfaces-validation The issue occurs when using {{}}. > Regression: "messages: globalOnly does not work properly" > --------------------------------------------------------- > > Key: RF-7351 > URL: https://issues.jboss.org/browse/RF-7351 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output, regression > Affects Versions: 3.3.1, 4.0.0.Final > Environment: Windows / JBoss 4.2.2.GA / Seam 2.1.1.GA / RichFaces 3.3.1.GA > Reporter: Joseph Miller > Labels: waiting_on_user > Fix For: 4.3-Tracking > > Attachments: example-globalOnly-bug.zip, example-globalOnly-bug.zip, Screen shot 2011-04-22 at 16.22.11.png, Screen shot 2011-04-27 at 08.51.26.png, Screen shot 2011-04-27 at 08.52.49.png > > Time Spent: 4 hours > Remaining Estimate: 0 minutes > > Looks like a regression of RF-615... I've upgraded my Seam project to sue RF 3.3.1, in order to fix a number of other bugs, but now messages intended for a single UI component (via the for= ) are appearing in the global messages list at the top of my page. > My page template has: > > ... > > and the controls have: > > ... > > I can switch the rich:messages to h:messages, and it behaves as it should. Also reverting back to the RichFaces 3.2.2.SR1 jars makes the problem go away, but I get the other older bugs back :( -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 20 06:32:48 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 20 Mar 2012 06:32:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-7351) Regression: "messages: globalOnly does not work properly" In-Reply-To: <11790963.1244614376426.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <294202006.19712.1332239568537.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-7351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated RF-7351: --------------------------- Fix Version/s: (was: 4.3-Tracking) > Regression: "messages: globalOnly does not work properly" > --------------------------------------------------------- > > Key: RF-7351 > URL: https://issues.jboss.org/browse/RF-7351 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output, regression > Affects Versions: 3.3.1, 4.0.0.Final > Environment: Windows / JBoss 4.2.2.GA / Seam 2.1.1.GA / RichFaces 3.3.1.GA > Reporter: Joseph Miller > Attachments: example-globalOnly-bug.zip, example-globalOnly-bug.zip, Screen shot 2011-04-22 at 16.22.11.png, Screen shot 2011-04-27 at 08.51.26.png, Screen shot 2011-04-27 at 08.52.49.png > > Time Spent: 4 hours > Remaining Estimate: 0 minutes > > Looks like a regression of RF-615... I've upgraded my Seam project to sue RF 3.3.1, in order to fix a number of other bugs, but now messages intended for a single UI component (via the for= ) are appearing in the global messages list at the top of my page. > My page template has: > > ... > > and the controls have: > > ... > > I can switch the rich:messages to h:messages, and it behaves as it should. Also reverting back to the RichFaces 3.2.2.SR1 jars makes the problem go away, but I get the other older bugs back :( -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 20 06:38:49 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 20 Mar 2012 06:38:49 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-7351) Regression: "messages: globalOnly does not work properly" In-Reply-To: <11790963.1244614376426.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <1347597766.19743.1332239929423.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-7351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677921#comment-12677921 ] Luk?? Fry? edited comment on RF-7351 at 3/20/12 6:38 AM: --------------------------------------------------------- I have run into the same issue with following sample: https://github.com/lfryc/quickstart/tree/quickstart-28/richfaces-validation The issue occurs when using {{}}, it means it can be reproduced only when using Client-Side Validation. was (Author: lfryc): I have run into the same issue with following sample: https://github.com/lfryc/quickstart/tree/quickstart-28/richfaces-validation The issue occurs when using {{}}. > Regression: "messages: globalOnly does not work properly" > --------------------------------------------------------- > > Key: RF-7351 > URL: https://issues.jboss.org/browse/RF-7351 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output, regression > Affects Versions: 3.3.1, 4.0.0.Final > Environment: Windows / JBoss 4.2.2.GA / Seam 2.1.1.GA / RichFaces 3.3.1.GA > Reporter: Joseph Miller > Attachments: example-globalOnly-bug.zip, example-globalOnly-bug.zip, Screen shot 2011-04-22 at 16.22.11.png, Screen shot 2011-04-27 at 08.51.26.png, Screen shot 2011-04-27 at 08.52.49.png > > Time Spent: 4 hours > Remaining Estimate: 0 minutes > > Looks like a regression of RF-615... I've upgraded my Seam project to sue RF 3.3.1, in order to fix a number of other bugs, but now messages intended for a single UI component (via the for= ) are appearing in the global messages list at the top of my page. > My page template has: > > ... > > and the controls have: > > ... > > I can switch the rich:messages to h:messages, and it behaves as it should. Also reverting back to the RichFaces 3.2.2.SR1 jars makes the problem go away, but I get the other older bugs back :( -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 20 07:07:47 2012 From: jira-events at lists.jboss.org (Benjamin Riefenstahl (JIRA)) Date: Tue, 20 Mar 2012 07:07:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12062) a4j:outputMedia does not reRender in Firefox 11 In-Reply-To: <1235192300.18015.1332176867445.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <39927929.19810.1332241667693.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677932#comment-12677932 ] Benjamin Riefenstahl commented on RF-12062: ------------------------------------------- ResourceBuilderImpl.decrypt seems to get its parameter from a URL that was created in the browser in JavaScript. This URL parameter than comes via classes InternetResourceService and WebXml to ResourceBuilderImpl.decrypt. Tracing into ResourceBuilderImpl.decrypt shows that FF11 gives us strings where the exclamation point "!" is encoded as "%21". IOW there is a call to URLDecoder.decode missing somewhere. For a quick fix put that call into WebXml.java where the data is extracted from the URL. I'm attaching a patch that does that. > a4j:outputMedia does not reRender in Firefox 11 > ------------------------------------------------ > > Key: RF-12062 > URL: https://issues.jboss.org/browse/RF-12062 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 3.3.3.Final > Environment: JBoss AS 6 > Reporter: Toni Neubert > Labels: a4j, outputmedia, richfaces > Attachments: WebXml.patch > > > a4j:outputMedia does not reRender in Firefox 11. The following error appears: > ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/BPM-Process].[default]] Servlet.service() for servlet default threw exception: javax.faces.FacesException: Error decode resource data > at org.ajax4jsf.resource.ResourceBuilderImpl.decrypt(ResourceBuilderImpl.java:627) [:3.3.3.Final] > at org.ajax4jsf.resource.ResourceBuilderImpl.getResourceDataForKey(ResourceBuilderImpl.java:371) [:3.3.3.Final] > at org.ajax4jsf.resource.InternetResourceService.serviceResource(InternetResourceService.java:156) [:3.3.3.Final] > at org.ajax4jsf.resource.InternetResourceService.serviceResource(InternetResourceService.java:141) [:3.3.3.Final] > at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:508) [:3.3.3.Final] > at org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:56) [:2.2.2.Final] > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) [:2.2.2.Final] > at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:60) [:2.2.2.Final] > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) [:2.2.2.Final] > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:73) [:2.2.2.Final] > at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) [:2.2.2.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:274) [:6.1.0.Final] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242) [:6.1.0.Final] > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [:6.1.0.Final] > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [:6.1.0.Final] > at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:181) [:6.1.0.Final] > at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:501) [:6.1.0.Final] > at org.jboss.modcluster.catalina.CatalinaContext$RequestListenerValve.event(CatalinaContext.java:285) [:1.1.0.Final] > at org.jboss.modcluster.catalina.CatalinaContext$RequestListenerValve.invoke(CatalinaContext.java:261) [:1.1.0.Final] > at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:88) [:6.1.0.Final] > at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:100) [:6.1.0.Final] > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:159) [:6.1.0.Final] > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [:6.1.0.Final] > at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) [:6.1.0.Final] > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [:6.1.0.Final] > at org.jboss.web.tomcat.service.request.ActiveRequestResponseCacheValve.invoke(ActiveRequestResponseCacheValve.java:53) [:6.1.0.Final] > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) [:6.1.0.Final] > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [:6.1.0.Final] > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:654) [:6.1.0.Final] > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:951) [:6.1.0.Final] > at java.lang.Thread.run(Unknown Source) [:1.6.0_31] > Caused by: java.util.zip.DataFormatException: invalid bit length repeat > at java.util.zip.Inflater.inflateBytes(Native Method) [:1.6.0_31] > at java.util.zip.Inflater.inflate(Unknown Source) [:1.6.0_31] > at java.util.zip.Inflater.inflate(Unknown Source) [:1.6.0_31] > at org.ajax4jsf.resource.ResourceBuilderImpl.decrypt(ResourceBuilderImpl.java:621) [:3.3.3.Final] > ... 30 more > The picture is not visible. But if you refresh the site with f5, there is no error and all works great. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 20 07:07:48 2012 From: jira-events at lists.jboss.org (Benjamin Riefenstahl (JIRA)) Date: Tue, 20 Mar 2012 07:07:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12062) a4j:outputMedia does not reRender in Firefox 11 In-Reply-To: <1235192300.18015.1332176867445.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1484785868.19826.1332241668475.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Riefenstahl updated RF-12062: -------------------------------------- Attachment: WebXml.patch > a4j:outputMedia does not reRender in Firefox 11 > ------------------------------------------------ > > Key: RF-12062 > URL: https://issues.jboss.org/browse/RF-12062 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 3.3.3.Final > Environment: JBoss AS 6 > Reporter: Toni Neubert > Labels: a4j, outputmedia, richfaces > Attachments: WebXml.patch > > > a4j:outputMedia does not reRender in Firefox 11. The following error appears: > ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/BPM-Process].[default]] Servlet.service() for servlet default threw exception: javax.faces.FacesException: Error decode resource data > at org.ajax4jsf.resource.ResourceBuilderImpl.decrypt(ResourceBuilderImpl.java:627) [:3.3.3.Final] > at org.ajax4jsf.resource.ResourceBuilderImpl.getResourceDataForKey(ResourceBuilderImpl.java:371) [:3.3.3.Final] > at org.ajax4jsf.resource.InternetResourceService.serviceResource(InternetResourceService.java:156) [:3.3.3.Final] > at org.ajax4jsf.resource.InternetResourceService.serviceResource(InternetResourceService.java:141) [:3.3.3.Final] > at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:508) [:3.3.3.Final] > at org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:56) [:2.2.2.Final] > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) [:2.2.2.Final] > at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:60) [:2.2.2.Final] > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) [:2.2.2.Final] > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:73) [:2.2.2.Final] > at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) [:2.2.2.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:274) [:6.1.0.Final] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242) [:6.1.0.Final] > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [:6.1.0.Final] > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [:6.1.0.Final] > at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:181) [:6.1.0.Final] > at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:501) [:6.1.0.Final] > at org.jboss.modcluster.catalina.CatalinaContext$RequestListenerValve.event(CatalinaContext.java:285) [:1.1.0.Final] > at org.jboss.modcluster.catalina.CatalinaContext$RequestListenerValve.invoke(CatalinaContext.java:261) [:1.1.0.Final] > at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:88) [:6.1.0.Final] > at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:100) [:6.1.0.Final] > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:159) [:6.1.0.Final] > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [:6.1.0.Final] > at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) [:6.1.0.Final] > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [:6.1.0.Final] > at org.jboss.web.tomcat.service.request.ActiveRequestResponseCacheValve.invoke(ActiveRequestResponseCacheValve.java:53) [:6.1.0.Final] > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) [:6.1.0.Final] > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [:6.1.0.Final] > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:654) [:6.1.0.Final] > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:951) [:6.1.0.Final] > at java.lang.Thread.run(Unknown Source) [:1.6.0_31] > Caused by: java.util.zip.DataFormatException: invalid bit length repeat > at java.util.zip.Inflater.inflateBytes(Native Method) [:1.6.0_31] > at java.util.zip.Inflater.inflate(Unknown Source) [:1.6.0_31] > at java.util.zip.Inflater.inflate(Unknown Source) [:1.6.0_31] > at org.ajax4jsf.resource.ResourceBuilderImpl.decrypt(ResourceBuilderImpl.java:621) [:3.3.3.Final] > ... 30 more > The picture is not visible. But if you refresh the site with f5, there is no error and all works great. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 20 07:09:48 2012 From: jira-events at lists.jboss.org (Benjamin Riefenstahl (JIRA)) Date: Tue, 20 Mar 2012 07:09:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12062) a4j:outputMedia does not reRender in Firefox 11 In-Reply-To: <1235192300.18015.1332176867445.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <774584931.19837.1332241788271.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677932#comment-12677932 ] Benjamin Riefenstahl edited comment on RF-12062 at 3/20/12 7:09 AM: -------------------------------------------------------------------- ResourceBuilderImpl.decrypt seems to get its parameter from a URL that was created in the browser in JavaScript. This URL parameter than comes via classes InternetResourceService and WebXml to ResourceBuilderImpl.decrypt. Tracing into ResourceBuilderImpl.decrypt shows that FF11 gives us strings where the exclamation point "!" is encoded as "%21". IOW there is a call to URLDecoder.decode missing somewhere. For a quick fix we put that call into WebXml.java where the data is extracted from the URL. I'm attaching a patch that does that. was (Author: cc_benny): ResourceBuilderImpl.decrypt seems to get its parameter from a URL that was created in the browser in JavaScript. This URL parameter than comes via classes InternetResourceService and WebXml to ResourceBuilderImpl.decrypt. Tracing into ResourceBuilderImpl.decrypt shows that FF11 gives us strings where the exclamation point "!" is encoded as "%21". IOW there is a call to URLDecoder.decode missing somewhere. For a quick fix put that call into WebXml.java where the data is extracted from the URL. I'm attaching a patch that does that. > a4j:outputMedia does not reRender in Firefox 11 > ------------------------------------------------ > > Key: RF-12062 > URL: https://issues.jboss.org/browse/RF-12062 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 3.3.3.Final > Environment: JBoss AS 6 > Reporter: Toni Neubert > Labels: a4j, outputmedia, richfaces > Attachments: WebXml.patch > > > a4j:outputMedia does not reRender in Firefox 11. The following error appears: > ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/BPM-Process].[default]] Servlet.service() for servlet default threw exception: javax.faces.FacesException: Error decode resource data > at org.ajax4jsf.resource.ResourceBuilderImpl.decrypt(ResourceBuilderImpl.java:627) [:3.3.3.Final] > at org.ajax4jsf.resource.ResourceBuilderImpl.getResourceDataForKey(ResourceBuilderImpl.java:371) [:3.3.3.Final] > at org.ajax4jsf.resource.InternetResourceService.serviceResource(InternetResourceService.java:156) [:3.3.3.Final] > at org.ajax4jsf.resource.InternetResourceService.serviceResource(InternetResourceService.java:141) [:3.3.3.Final] > at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:508) [:3.3.3.Final] > at org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:56) [:2.2.2.Final] > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) [:2.2.2.Final] > at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:60) [:2.2.2.Final] > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) [:2.2.2.Final] > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:73) [:2.2.2.Final] > at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) [:2.2.2.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:274) [:6.1.0.Final] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242) [:6.1.0.Final] > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [:6.1.0.Final] > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [:6.1.0.Final] > at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:181) [:6.1.0.Final] > at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:501) [:6.1.0.Final] > at org.jboss.modcluster.catalina.CatalinaContext$RequestListenerValve.event(CatalinaContext.java:285) [:1.1.0.Final] > at org.jboss.modcluster.catalina.CatalinaContext$RequestListenerValve.invoke(CatalinaContext.java:261) [:1.1.0.Final] > at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:88) [:6.1.0.Final] > at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:100) [:6.1.0.Final] > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:159) [:6.1.0.Final] > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [:6.1.0.Final] > at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) [:6.1.0.Final] > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [:6.1.0.Final] > at org.jboss.web.tomcat.service.request.ActiveRequestResponseCacheValve.invoke(ActiveRequestResponseCacheValve.java:53) [:6.1.0.Final] > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) [:6.1.0.Final] > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [:6.1.0.Final] > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:654) [:6.1.0.Final] > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:951) [:6.1.0.Final] > at java.lang.Thread.run(Unknown Source) [:1.6.0_31] > Caused by: java.util.zip.DataFormatException: invalid bit length repeat > at java.util.zip.Inflater.inflateBytes(Native Method) [:1.6.0_31] > at java.util.zip.Inflater.inflate(Unknown Source) [:1.6.0_31] > at java.util.zip.Inflater.inflate(Unknown Source) [:1.6.0_31] > at org.ajax4jsf.resource.ResourceBuilderImpl.decrypt(ResourceBuilderImpl.java:621) [:3.3.3.Final] > ... 30 more > The picture is not visible. But if you refresh the site with f5, there is no error and all works great. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 20 07:31:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Nicholas_Oxh=C3=B8j_=28JIRA=29?=) Date: Tue, 20 Mar 2012 07:31:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12065) Continuous event polling in available.js Message-ID: <289191080.19891.1332243107446.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Nicholas Oxh?j created RF-12065: ----------------------------------- Summary: Continuous event polling in available.js Key: RF-12065 URL: https://issues.jboss.org/browse/RF-12065 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 3.3.3.Final Reporter: Nicholas Oxh?j Priority: Minor In available.js there is two functions activatePolling() and stopPolling(), used to wait for a specific DOM element becoming available. But while activatePolling() starts observing the events "*mousemove*", "focus", and "focusin", stopPolling() stops observing the events "*mouseover*", "focus", and "focusin" - which means that it will _keep_ calling onEvent() on every "mousemove", even when the relevant element has already been found... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 20 07:33:48 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Nicholas_Oxh=C3=B8j_=28JIRA=29?=) Date: Tue, 20 Mar 2012 07:33:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12065) Continuous event polling in available.js In-Reply-To: <289191080.19891.1332243107446.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <262681704.19903.1332243228230.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicholas Oxh?j updated RF-12065: -------------------------------- Description: In available.js there are two functions activatePolling() and stopPolling(), used to wait for a specific DOM element becoming available. But while activatePolling() starts observing the events "*mousemove*", "focus", and "focusin", stopPolling() stops observing the events "*mouseover*", "focus", and "focusin" - which means that it will _keep_ calling onEvent() on every "mousemove", even when the relevant element has already been found... was: In available.js there is two functions activatePolling() and stopPolling(), used to wait for a specific DOM element becoming available. But while activatePolling() starts observing the events "*mousemove*", "focus", and "focusin", stopPolling() stops observing the events "*mouseover*", "focus", and "focusin" - which means that it will _keep_ calling onEvent() on every "mousemove", even when the relevant element has already been found... > Continuous event polling in available.js > ---------------------------------------- > > Key: RF-12065 > URL: https://issues.jboss.org/browse/RF-12065 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 3.3.3.Final > Reporter: Nicholas Oxh?j > Priority: Minor > > In available.js there are two functions activatePolling() and stopPolling(), used to wait for a specific DOM element becoming available. > But while activatePolling() starts observing the events "*mousemove*", "focus", and "focusin", stopPolling() stops observing the events "*mouseover*", "focus", and "focusin" - which means that it will _keep_ calling onEvent() on every "mousemove", even when the relevant element has already been found... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 20 07:40:48 2012 From: jira-events at lists.jboss.org (Drew McLaughlin (JIRA)) Date: Tue, 20 Mar 2012 07:40:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-10442) extendedDataTable: add state saving functionality In-Reply-To: <1245105000.22571.1297083759998.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <707686278.19926.1332243648325.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-10442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677939#comment-12677939 ] Drew McLaughlin commented on RF-10442: -------------------------------------- Any update on when this fix is going into a final release? I'm upgrading to RF 4.2 from 3.3 and it's causing quite a few issues. > extendedDataTable: add state saving functionality > ------------------------------------------------- > > Key: RF-10442 > URL: https://issues.jboss.org/browse/RF-10442 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.0.0.Milestone5 > Reporter: Ilya Shaikovsky > Fix For: 4.Future > > > developer should be able to store column width'es, order and so on between requests. > TO discuss: use tableState as before or maybe create set of specific attributes for every required properties set. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 20 08:31:47 2012 From: jira-events at lists.jboss.org (Juraj Huska (JIRA)) Date: Tue, 20 Mar 2012 08:31:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12066) Kitchensink archetype is not listed in the modules of the parent pom Message-ID: <1702434883.20113.1332246707300.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Juraj Huska created RF-12066: -------------------------------- Summary: Kitchensink archetype is not listed in the modules of the parent pom Key: RF-12066 URL: https://issues.jboss.org/browse/RF-12066 Project: RichFaces Issue Type: Enhancement Security Level: Public (Everyone can see) Components: archetype Affects Versions: 4.2.0.Final Reporter: Juraj Huska Priority: Trivial The maven module `richfaces-archetype-kitchensink` is not listed in the parent pom.xml in the modules section. Therefore, can not be installed from the parent pom. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 20 08:33:47 2012 From: jira-events at lists.jboss.org (Juraj Huska (JIRA)) Date: Tue, 20 Mar 2012 08:33:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12066) Kitchensink archetype is not listed in the modules of the parent pom In-Reply-To: <1702434883.20113.1332246707300.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <192750289.20120.1332246827597.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj Huska updated RF-12066: ----------------------------- Description: The maven module _richfaces-archetype-kitchensink_ is not listed in the parent pom.xml in the modules section. Therefore, can not be installed from the parent pom. was: The maven module `richfaces-archetype-kitchensink` is not listed in the parent pom.xml in the modules section. Therefore, can not be installed from the parent pom. > Kitchensink archetype is not listed in the modules of the parent pom > -------------------------------------------------------------------- > > Key: RF-12066 > URL: https://issues.jboss.org/browse/RF-12066 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: archetype > Affects Versions: 4.2.0.Final > Reporter: Juraj Huska > Priority: Trivial > > The maven module _richfaces-archetype-kitchensink_ is not listed in the parent pom.xml in the modules section. > Therefore, can not be installed from the parent pom. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 20 09:01:50 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Nicholas_Oxh=C3=B8j_=28JIRA=29?=) Date: Tue, 20 Mar 2012 09:01:50 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12067) Load order of external JavaScript files referenced in AJAX responses Message-ID: <1604731307.20138.1332248510243.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Nicholas Oxh?j created RF-12067: ----------------------------------- Summary: Load order of external JavaScript files referenced in AJAX responses Key: RF-12067 URL: https://issues.jboss.org/browse/RF-12067 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 3.3.3.Final Reporter: Nicholas Oxh?j Hi, I think there is a problem with the way that RichFaces loads external JavaScript files, referenced in AJAX responses. The way it is done at the moment, the files are loaded *and parsed* asynchronously/in parallel. This is a problem if the files depend on being loaded in the correct order. As an example, I have a page with an OpenFaces DataTable which is not initially rendered, but can be later rendered using the "reRender" attribute of an AJAX action. The Openfaces DataTable requires two OpenFaces JavaScript files, util.js & ajaxUtil.js, where the second depends on the first being loaded first. These files are included in the section of the AJAX response, in the correct order. But since they are then loaded asynchronously, things will break if ajaxUtil.js finishes loading first. I think you need to ensure, that the files are parsed in the same order as they appear in the response. The problem is mainly in the function _appendNewElements() in AJAX.js. For HTML5 capable browsers, you should just be able to add set the "async" property to "false" on the script element, before appending it to head as described here: [HTML5 Async Scripts|http://ie.microsoft.com/testdrive/Performance/AsyncScripts/Default.html] For non-HTML5 browsers, the only solution would probably be to modify the functionality a bit, such that you would only generate and insert a new script tag, when the previous script finished loading. Since appendNewHeadElements() already uses the scripts "onload" and "onreadystatechange" to find out when _all_ scripts have loaded, I suspect that it should be a relatively minor change to initially just insert the _first_ script tag and then use these functions to insert the _next_ script tag when the first has finished loading. For an in-depth discussion of the problems and different solution strategies, see WHATWGs [Dynamic Script Execution Order|http://wiki.whatwg.org/wiki/Dynamic_Script_Execution_Order] Regards, Nicholas Oxh?j -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 20 09:01:50 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Nicholas_Oxh=C3=B8j_=28JIRA=29?=) Date: Tue, 20 Mar 2012 09:01:50 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12067) Load order of external JavaScript files referenced in AJAX responses In-Reply-To: <1604731307.20138.1332248510243.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1378088277.20140.1332248510331.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicholas Oxh?j updated RF-12067: -------------------------------- Description: Hi, I think there is a problem with the way that RichFaces loads external JavaScript files, referenced in AJAX responses. The way it is done at the moment, the files are loaded *and parsed* asynchronously. This is a problem if the files depend on being loaded in the correct order. As an example, I have a page with an OpenFaces DataTable which is not initially rendered, but can be later rendered using the "reRender" attribute of an AJAX action. The Openfaces DataTable requires two OpenFaces JavaScript files, util.js & ajaxUtil.js, where the second depends on the first being loaded first. These files are included in the section of the AJAX response, in the correct order. But since they are then loaded asynchronously, things will break if ajaxUtil.js finishes loading first. I think you need to ensure, that the files are parsed in the same order as they appear in the response. The problem is mainly in the function _appendNewElements() in AJAX.js. For HTML5 capable browsers, you should just be able to add set the "async" property to "false" on the script element, before appending it to head as described here: [HTML5 Async Scripts|http://ie.microsoft.com/testdrive/Performance/AsyncScripts/Default.html] For non-HTML5 browsers, the only solution would probably be to modify the functionality a bit, such that you would only generate and insert a new script tag, when the previous script finished loading. Since appendNewHeadElements() already uses the scripts "onload" and "onreadystatechange" to find out when _all_ scripts have loaded, I suspect that it should be a relatively minor change to initially just insert the _first_ script tag and then use these functions to insert the _next_ script tag when the first has finished loading. For an in-depth discussion of the problems and different solution strategies, see WHATWGs [Dynamic Script Execution Order|http://wiki.whatwg.org/wiki/Dynamic_Script_Execution_Order] Regards, Nicholas Oxh?j was: Hi, I think there is a problem with the way that RichFaces loads external JavaScript files, referenced in AJAX responses. The way it is done at the moment, the files are loaded *and parsed* asynchronously/in parallel. This is a problem if the files depend on being loaded in the correct order. As an example, I have a page with an OpenFaces DataTable which is not initially rendered, but can be later rendered using the "reRender" attribute of an AJAX action. The Openfaces DataTable requires two OpenFaces JavaScript files, util.js & ajaxUtil.js, where the second depends on the first being loaded first. These files are included in the section of the AJAX response, in the correct order. But since they are then loaded asynchronously, things will break if ajaxUtil.js finishes loading first. I think you need to ensure, that the files are parsed in the same order as they appear in the response. The problem is mainly in the function _appendNewElements() in AJAX.js. For HTML5 capable browsers, you should just be able to add set the "async" property to "false" on the script element, before appending it to head as described here: [HTML5 Async Scripts|http://ie.microsoft.com/testdrive/Performance/AsyncScripts/Default.html] For non-HTML5 browsers, the only solution would probably be to modify the functionality a bit, such that you would only generate and insert a new script tag, when the previous script finished loading. Since appendNewHeadElements() already uses the scripts "onload" and "onreadystatechange" to find out when _all_ scripts have loaded, I suspect that it should be a relatively minor change to initially just insert the _first_ script tag and then use these functions to insert the _next_ script tag when the first has finished loading. For an in-depth discussion of the problems and different solution strategies, see WHATWGs [Dynamic Script Execution Order|http://wiki.whatwg.org/wiki/Dynamic_Script_Execution_Order] Regards, Nicholas Oxh?j > Load order of external JavaScript files referenced in AJAX responses > -------------------------------------------------------------------- > > Key: RF-12067 > URL: https://issues.jboss.org/browse/RF-12067 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 3.3.3.Final > Reporter: Nicholas Oxh?j > > Hi, > I think there is a problem with the way that RichFaces loads external JavaScript files, referenced in AJAX responses. The way it is done at the moment, the files are loaded *and parsed* asynchronously. This is a problem if the files depend on being loaded in the correct order. > As an example, I have a page with an OpenFaces DataTable which is not initially rendered, but can be later rendered using the "reRender" attribute of an AJAX action. The Openfaces DataTable requires two OpenFaces JavaScript files, util.js & ajaxUtil.js, where the second depends on the first being loaded first. These files are included in the section of the AJAX response, in the correct order. But since they are then loaded asynchronously, things will break if ajaxUtil.js finishes loading first. > I think you need to ensure, that the files are parsed in the same order as they appear in the response. > The problem is mainly in the function _appendNewElements() in AJAX.js. > For HTML5 capable browsers, you should just be able to add set the "async" property to "false" on the script element, before appending it to head as described here: [HTML5 Async Scripts|http://ie.microsoft.com/testdrive/Performance/AsyncScripts/Default.html] > For non-HTML5 browsers, the only solution would probably be to modify the functionality a bit, such that you would only generate and insert a new script tag, when the previous script finished loading. Since appendNewHeadElements() already uses the scripts "onload" and "onreadystatechange" to find out when _all_ scripts have loaded, I suspect that it should be a relatively minor change to initially just insert the _first_ script tag and then use these functions to insert the _next_ script tag when the first has finished loading. > For an in-depth discussion of the problems and different solution strategies, see WHATWGs [Dynamic Script Execution Order|http://wiki.whatwg.org/wiki/Dynamic_Script_Execution_Order] > Regards, > Nicholas Oxh?j -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 20 10:16:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 20 Mar 2012 10:16:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12068) rich:toggleControl: can't use immediate=true Message-ID: <1358714521.20262.1332253007498.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Luk?? Fry? created RF-12068: ------------------------------- Summary: rich:toggleControl: can't use immediate=true Key: RF-12068 URL: https://issues.jboss.org/browse/RF-12068 Project: RichFaces Issue Type: Enhancement Security Level: Public (Everyone can see) Components: component-panels-layout-themes Affects Versions: 4.2.0.Final Reporter: Luk?? Fry? The wizard can be created with {{togglePanel}} and {{toggleControl}}. It can use validation mechanism and Ajax to switch between wizard windows. ---- But when validation fails, you can't use {{toggleControl}} to switch to another panel like in the sample of Back button - there is no possibility to request {{immediate}} response (shortened lifecycle skipping validation phase). ---- The scenario can be seen in the sample of Showcase - togglePanel - Wizard [1], and in the QuickStart {{richfaces-validation}} [2]. [1] http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=togglePanel&sample=wizard&skin=blueSky [2] https://github.com/lfryc/quickstart/tree/quickstart-28 ---- Sample code: {code} {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 20 10:24:49 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 20 Mar 2012 10:24:49 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-7351) Regression: "messages: globalOnly does not work properly" In-Reply-To: <11790963.1244614376426.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <2140029421.20328.1332253489539.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-7351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated RF-7351: --------------------------- Fix Version/s: 4.2.1.CR1 > Regression: "messages: globalOnly does not work properly" > --------------------------------------------------------- > > Key: RF-7351 > URL: https://issues.jboss.org/browse/RF-7351 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output, regression > Affects Versions: 3.3.1, 4.0.0.Final > Environment: Windows / JBoss 4.2.2.GA / Seam 2.1.1.GA / RichFaces 3.3.1.GA > Reporter: Joseph Miller > Fix For: 4.2.1.CR1 > > Attachments: example-globalOnly-bug.zip, example-globalOnly-bug.zip, Screen shot 2011-04-22 at 16.22.11.png, Screen shot 2011-04-27 at 08.51.26.png, Screen shot 2011-04-27 at 08.52.49.png > > Time Spent: 4 hours > Remaining Estimate: 0 minutes > > Looks like a regression of RF-615... I've upgraded my Seam project to sue RF 3.3.1, in order to fix a number of other bugs, but now messages intended for a single UI component (via the for= ) are appearing in the global messages list at the top of my page. > My page template has: > > ... > > and the controls have: > > ... > > I can switch the rich:messages to h:messages, and it behaves as it should. Also reverting back to the RichFaces 3.2.2.SR1 jars makes the problem go away, but I get the other older bugs back :( -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 20 10:24:50 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 20 Mar 2012 10:24:50 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-7351) Regression: "messages: globalOnly does not work properly" In-Reply-To: <11790963.1244614376426.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <1042110381.20342.1332253490513.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-7351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? reassigned RF-7351: ------------------------------ Assignee: Luk?? Fry? > Regression: "messages: globalOnly does not work properly" > --------------------------------------------------------- > > Key: RF-7351 > URL: https://issues.jboss.org/browse/RF-7351 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output, regression > Affects Versions: 3.3.1, 4.0.0.Final > Environment: Windows / JBoss 4.2.2.GA / Seam 2.1.1.GA / RichFaces 3.3.1.GA > Reporter: Joseph Miller > Assignee: Luk?? Fry? > Fix For: 4.2.1.CR1 > > Attachments: example-globalOnly-bug.zip, example-globalOnly-bug.zip, Screen shot 2011-04-22 at 16.22.11.png, Screen shot 2011-04-27 at 08.51.26.png, Screen shot 2011-04-27 at 08.52.49.png > > Time Spent: 4 hours > Remaining Estimate: 0 minutes > > Looks like a regression of RF-615... I've upgraded my Seam project to sue RF 3.3.1, in order to fix a number of other bugs, but now messages intended for a single UI component (via the for= ) are appearing in the global messages list at the top of my page. > My page template has: > > ... > > and the controls have: > > ... > > I can switch the rich:messages to h:messages, and it behaves as it should. Also reverting back to the RichFaces 3.2.2.SR1 jars makes the problem go away, but I get the other older bugs back :( -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 20 11:15:48 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Sandro_Br=C3=A4ndli_=28JIRA=29?=) Date: Tue, 20 Mar 2012 11:15:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12069) Use of $(document).ready instead of jQuery(document).ready in org.richfaces.renderkit.html.ScriptsRenderer Message-ID: <1707537090.20595.1332256548101.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Sandro Br?ndli created RF-12069: ----------------------------------- Summary: Use of $(document).ready instead of jQuery(document).ready in org.richfaces.renderkit.html.ScriptsRenderer Key: RF-12069 URL: https://issues.jboss.org/browse/RF-12069 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: core Affects Versions: 4.1.0.Final Reporter: Sandro Br?ndli As stated in the summary ScriptsRenderer uses the $-sign instead of jQuery. This causes problems when using a JavaScript library that overrides the $-sign. In my case it breaks DnD when including Prototype. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 20 12:52:47 2012 From: jira-events at lists.jboss.org (Juraj Huska (JIRA)) Date: Tue, 20 Mar 2012 12:52:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12070) Kitschensink archetype - broken formatting of comments in generated pom.xml Message-ID: <561043984.20917.1332262367501.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Juraj Huska created RF-12070: -------------------------------- Summary: Kitschensink archetype - broken formatting of comments in generated pom.xml Key: RF-12070 URL: https://issues.jboss.org/browse/RF-12070 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: archetype Affects Versions: 4.2.0.Final Reporter: Juraj Huska Priority: Trivial Comments in generated pom.xml from Kitschensink maven archetype have broken formatting. Please see the attachment. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 20 12:54:48 2012 From: jira-events at lists.jboss.org (Juraj Huska (JIRA)) Date: Tue, 20 Mar 2012 12:54:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12070) Kitschensink archetype - broken formatting of comments in generated pom.xml In-Reply-To: <561043984.20917.1332262367501.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <383296189.20927.1332262488434.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678066#comment-12678066 ] Juraj Huska commented on RF-12070: ---------------------------------- Or see the broken formatting [here|https://github.com/richfaces/archetypes/blob/develop/kitchensink/src/main/resources/archetype-resources/pom.xml#L24] > Kitschensink archetype - broken formatting of comments in generated pom.xml > --------------------------------------------------------------------------- > > Key: RF-12070 > URL: https://issues.jboss.org/browse/RF-12070 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: archetype > Affects Versions: 4.2.0.Final > Reporter: Juraj Huska > Priority: Trivial > Attachments: brokenFormatting.png > > > Comments in generated pom.xml from Kitschensink maven archetype have broken formatting. Please see the attachment. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 20 12:54:48 2012 From: jira-events at lists.jboss.org (Juraj Huska (JIRA)) Date: Tue, 20 Mar 2012 12:54:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12070) Kitschensink archetype - broken formatting of comments in generated pom.xml In-Reply-To: <561043984.20917.1332262367501.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <727660299.20926.1332262488368.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj Huska updated RF-12070: ----------------------------- Attachment: brokenFormatting.png > Kitschensink archetype - broken formatting of comments in generated pom.xml > --------------------------------------------------------------------------- > > Key: RF-12070 > URL: https://issues.jboss.org/browse/RF-12070 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: archetype > Affects Versions: 4.2.0.Final > Reporter: Juraj Huska > Priority: Trivial > Attachments: brokenFormatting.png > > > Comments in generated pom.xml from Kitschensink maven archetype have broken formatting. Please see the attachment. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 20 14:05:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Tue, 20 Mar 2012 14:05:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12048) Showcase: Change the password for JMS guest connection In-Reply-To: <1881089286.10479.1331763467304.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <802335470.21091.1332266747297.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12048: ------------------------------- Fix Version/s: 4.2.1.CR1 Priority: Minor (was: Major) > Showcase: Change the password for JMS guest connection > ------------------------------------------------------ > > Key: RF-12048 > URL: https://issues.jboss.org/browse/RF-12048 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-push/poll > Affects Versions: 4.2.0.Final > Reporter: Luk?? Fry? > Priority: Minor > Fix For: 4.2.1.CR1 > > > [Originally request|https://issues.jboss.org/browse/RF-11983?focusedCommentId=12676716&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12676716] by Karel Piwko: > AS7 doesn't allow to add user with same name and password, that's why having {{guest:guest}} credentials [1] does not make sense. > We can change the credentials to {{guest:password}} - I have verified the actual content does not have any influence on functionality on AS7.0 and will improve usability on AS7.1. > [1] https://github.com/richfaces/showcase/blob/4.2.0.20120215-Final/src/main/webapp-jbas7/WEB-INF/web.xml#L78 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 20 14:07:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Tue, 20 Mar 2012 14:07:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12048) Showcase: Change the password for JMS guest connection In-Reply-To: <1881089286.10479.1331763467304.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <832218482.21093.1332266867359.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678093#comment-12678093 ] Brian Leathem commented on RF-12048: ------------------------------------ Let's make this change for 4.2.1.CR1. When we discussed this before, we got sidetracked by looking for a more elegant fall back. In the mean time, we should be sure to provide a username/password that works, with appropriate instructions in the showcase README. > Showcase: Change the password for JMS guest connection > ------------------------------------------------------ > > Key: RF-12048 > URL: https://issues.jboss.org/browse/RF-12048 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-push/poll > Affects Versions: 4.2.0.Final > Reporter: Luk?? Fry? > Priority: Minor > Fix For: 4.2.1.CR1 > > > [Originally request|https://issues.jboss.org/browse/RF-11983?focusedCommentId=12676716&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12676716] by Karel Piwko: > AS7 doesn't allow to add user with same name and password, that's why having {{guest:guest}} credentials [1] does not make sense. > We can change the credentials to {{guest:password}} - I have verified the actual content does not have any influence on functionality on AS7.0 and will improve usability on AS7.1. > [1] https://github.com/richfaces/showcase/blob/4.2.0.20120215-Final/src/main/webapp-jbas7/WEB-INF/web.xml#L78 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 20 14:07:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Tue, 20 Mar 2012 14:07:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12048) Showcase: Change the password for JMS guest connection In-Reply-To: <1881089286.10479.1331763467304.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1632026839.21095.1332266867457.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem reassigned RF-12048: ---------------------------------- Assignee: Brian Leathem > Showcase: Change the password for JMS guest connection > ------------------------------------------------------ > > Key: RF-12048 > URL: https://issues.jboss.org/browse/RF-12048 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-push/poll > Affects Versions: 4.2.0.Final > Reporter: Luk?? Fry? > Assignee: Brian Leathem > Priority: Minor > Fix For: 4.2.1.CR1 > > > [Originally request|https://issues.jboss.org/browse/RF-11983?focusedCommentId=12676716&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12676716] by Karel Piwko: > AS7 doesn't allow to add user with same name and password, that's why having {{guest:guest}} credentials [1] does not make sense. > We can change the credentials to {{guest:password}} - I have verified the actual content does not have any influence on functionality on AS7.0 and will improve usability on AS7.1. > [1] https://github.com/richfaces/showcase/blob/4.2.0.20120215-Final/src/main/webapp-jbas7/WEB-INF/web.xml#L78 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 20 14:49:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Tue, 20 Mar 2012 14:49:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12048) Showcase: Change the password for JMS guest connection In-Reply-To: <1881089286.10479.1331763467304.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <898241960.21157.1332269387295.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-12048. -------------------------------- Resolution: Done Changed the default JMS password to "password" > Showcase: Change the password for JMS guest connection > ------------------------------------------------------ > > Key: RF-12048 > URL: https://issues.jboss.org/browse/RF-12048 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-push/poll > Affects Versions: 4.2.0.Final > Reporter: Luk?? Fry? > Assignee: Brian Leathem > Priority: Minor > Fix For: 4.2.1.CR1 > > > [Originally request|https://issues.jboss.org/browse/RF-11983?focusedCommentId=12676716&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12676716] by Karel Piwko: > AS7 doesn't allow to add user with same name and password, that's why having {{guest:guest}} credentials [1] does not make sense. > We can change the credentials to {{guest:password}} - I have verified the actual content does not have any influence on functionality on AS7.0 and will improve usability on AS7.1. > [1] https://github.com/richfaces/showcase/blob/4.2.0.20120215-Final/src/main/webapp-jbas7/WEB-INF/web.xml#L78 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 20 18:27:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Tue, 20 Mar 2012 18:27:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11872) Mobile Showcase and a4j:region demo: submit button doesn't respond on the first click In-Reply-To: <1714655772.52122.1326201429582.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1960066757.21720.1332282467516.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678169#comment-12678169 ] Brian Leathem commented on RF-11872: ------------------------------------ This is the simplest possible example I could come up with to replicate this behaviour (note, it does not require a4j:region) {code}
User Name:
Entered name:
{code} Notice the pair of nested forms. If I remove the first nested form (the empty one) the problem goes away. Similarly if I switch the order of the nested components. > Mobile Showcase and a4j:region demo: submit button doesn't respond on the first click > ------------------------------------------------------------------------------------- > > Key: RF-11872 > URL: https://issues.jboss.org/browse/RF-11872 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: mobile, showcase > Affects Versions: 4.2.0.CR1 > Environment: richfaces-showcase-4.1.1-20120106.230242-18 / richfaces-showcase-4.2.0-20120123.231757-13 > JBoss AS 7.0.2.Final / 7.1.0.Beta1 > Firefox 8.0 / Google Chrome 16.0.912.63 / Android 2.2 / iPhone 4.2.1 > Reporter: Jan Papousek > Assignee: Brian Leathem > Fix For: 4.2.1.CR1 > > Attachments: richfaces-showcase-4.2.0-20120123.231757-13-jbas7.war > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 20 18:40:48 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Tue, 20 Mar 2012 18:40:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11872) Mobile Showcase and a4j:region demo: submit button doesn't respond on the first click In-Reply-To: <1714655772.52122.1326201429582.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <963441850.21729.1332283248095.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-11872. -------------------------------- Resolution: Done Collapsed the pair fo forms in the included a4j:region sample > Mobile Showcase and a4j:region demo: submit button doesn't respond on the first click > ------------------------------------------------------------------------------------- > > Key: RF-11872 > URL: https://issues.jboss.org/browse/RF-11872 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: mobile, showcase > Affects Versions: 4.2.0.CR1 > Environment: richfaces-showcase-4.1.1-20120106.230242-18 / richfaces-showcase-4.2.0-20120123.231757-13 > JBoss AS 7.0.2.Final / 7.1.0.Beta1 > Firefox 8.0 / Google Chrome 16.0.912.63 / Android 2.2 / iPhone 4.2.1 > Reporter: Jan Papousek > Assignee: Brian Leathem > Fix For: 4.2.1.CR1 > > Attachments: richfaces-showcase-4.2.0-20120123.231757-13-jbas7.war > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 05:58:47 2012 From: jira-events at lists.jboss.org (Jan Papousek (JIRA)) Date: Wed, 21 Mar 2012 05:58:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11872) Mobile Showcase and a4j:region demo: submit button doesn't respond on the first click In-Reply-To: <1714655772.52122.1326201429582.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <806792061.22293.1332323927994.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Papousek closed RF-11872. ----------------------------- Verified on Android 2.2 > Mobile Showcase and a4j:region demo: submit button doesn't respond on the first click > ------------------------------------------------------------------------------------- > > Key: RF-11872 > URL: https://issues.jboss.org/browse/RF-11872 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: mobile, showcase > Affects Versions: 4.2.0.CR1 > Environment: richfaces-showcase-4.1.1-20120106.230242-18 / richfaces-showcase-4.2.0-20120123.231757-13 > JBoss AS 7.0.2.Final / 7.1.0.Beta1 > Firefox 8.0 / Google Chrome 16.0.912.63 / Android 2.2 / iPhone 4.2.1 > Reporter: Jan Papousek > Assignee: Brian Leathem > Fix For: 4.2.1.CR1 > > Attachments: richfaces-showcase-4.2.0-20120123.231757-13-jbas7.war > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 07:59:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Abdullah_=C4=B0lhanl=C4=B1_=28JIRA=29?=) Date: Wed, 21 Mar 2012 07:59:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12071) a4j:outputPanel h:inputText render problem Message-ID: <1254741604.22548.1332331187494.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Abdullah ?lhanl? created RF-12071: ------------------------------------- Summary: a4j:outputPanel h:inputText render problem Key: RF-12071 URL: https://issues.jboss.org/browse/RF-12071 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Abdullah ?lhanl? Create dynamic screen with JSF is so hard and painfull. I used a4j:outputPanel so many times. Today i am trying to create dynamic screen based on combo selected value. When value is for example option1 it generate inputText, otherwise comboBox. But i face to rendered problem son many times. Problem is on submited object value. My problem code like these: Problem detail: Captionvalue is unique in database. When exception is throwed from back end(JPA uniquness error). I pops up error to user. Then user edit captionValue and try to resubmit. But captionValue is not change, even user changed it. When i remove rendered="#{conditionKeyBean.checkable}" problem is solved. rendered is not working correctly i think. How can i solve this problem? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 09:14:48 2012 From: jira-events at lists.jboss.org (Stian Thorgersen (JIRA)) Date: Wed, 21 Mar 2012 09:14:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12072) Lost event in push Message-ID: <1823827590.22721.1332335688298.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Stian Thorgersen created RF-12072: ------------------------------------- Summary: Lost event in push Key: RF-12072 URL: https://issues.jboss.org/browse/RF-12072 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Stian Thorgersen Event can be lost if produced while a response is being prepared. I've attached an example where a push event is used to refresh a count whenever an event is fired. It's using Thread.sleep to simulate an event being produced while the response is being prepared. Note, if the sleep just before returning the count is removed it all works fine, and the page is refreshed every 5 seconds, but without it the event is lost. View: {code} {code} Bean: {code} package com.example; import java.io.Serializable; import java.util.concurrent.atomic.AtomicInteger; import javax.enterprise.context.SessionScoped; import javax.inject.Named; import org.richfaces.application.push.TopicKey; import org.richfaces.application.push.TopicsContext; @Named @SessionScoped public class MyBean implements Serializable { private AtomicInteger count = new AtomicInteger(); public int getCount() { int c = count.get(); new Thread() { public void run() { try { Thread.sleep(5000); count.incrementAndGet(); TopicKey topicKey = new TopicKey("chat"); TopicsContext topicsContext = TopicsContext.lookup(); topicsContext.publish(topicKey, ""); } catch (Exception e) { e.printStackTrace(); } }; }.start(); try { Thread.sleep(10000); } catch (InterruptedException e) { } return c; } } {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 09:25:47 2012 From: jira-events at lists.jboss.org (Stian Thorgersen (JIRA)) Date: Wed, 21 Mar 2012 09:25:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12013) Deadlock in push component In-Reply-To: <654291399.48838.1330441536575.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1357742114.22725.1332336348015.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678322#comment-12678322 ] Stian Thorgersen commented on RF-12013: --------------------------------------- I'm happy to do that, trying out the instructions on https://community.jboss.org/wiki/HowToBuildRichFaces4x at the moment. I'll let you know how I get on, although the problem only happens infrequently so would be hard to guarantee its actually fixed > Deadlock in push component > -------------------------- > > Key: RF-12013 > URL: https://issues.jboss.org/browse/RF-12013 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Affects Versions: 4.2.0.Final > Reporter: Stian Thorgersen > Assignee: Luk?? Fry? > Fix For: 4.3.0.Milestone1 > > > Deadlocked threads in the push component prevented server from stopping. Not sure whether or not this happened when I initiated shutdown or if these where hanging around for a while. > Relevant output from jstack: > {code} > Found one Java-level deadlock: > ============================= > "push-publish-thread-1": > waiting to lock monitor 0x0000000042650238 (object 0x00000000e5ed5a50, a org.richfaces.application.push.impl.RequestImpl), > which is held by "Atmosphere-AsyncWrite-0" > "Atmosphere-AsyncWrite-0": > waiting to lock monitor 0x00000000427d9ec0 (object 0x00000000e5ed59a0, a org.richfaces.application.push.impl.SessionImpl), > which is held by "push-publish-thread-1" > Java stack information for the threads listed above: > =================================================== > "push-publish-thread-1": > at org.richfaces.application.push.impl.RequestImpl.postMessages(RequestImpl.java:85) > - waiting to lock <0x00000000e5ed5a50> (a org.richfaces.application.push.impl.RequestImpl) > at org.richfaces.application.push.impl.SessionImpl.push(SessionImpl.java:237) > - locked <0x00000000e5ed59a0> (a org.richfaces.application.push.impl.SessionImpl) > at org.richfaces.application.push.impl.TopicImpl$TopicContext.publishMessages(TopicImpl.java:88) > at org.richfaces.application.push.impl.TopicImpl$PublishTask.run(TopicImpl.java:53) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:662) > "Atmosphere-AsyncWrite-0": > at org.richfaces.application.push.impl.SessionImpl.disconnect(SessionImpl.java:117) > - waiting to lock <0x00000000e5ed59a0> (a org.richfaces.application.push.impl.SessionImpl) > at org.richfaces.application.push.impl.RequestImpl.disconnect(RequestImpl.java:107) > at org.richfaces.application.push.impl.RequestImpl.onResume(RequestImpl.java:115) > at org.atmosphere.cpr.AtmosphereResourceImpl.onResume(AtmosphereResourceImpl.java:651) > at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:600) > at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:584) > at org.atmosphere.cpr.AtmosphereResourceImpl.resume(AtmosphereResourceImpl.java:185) > - locked <0x00000000e5ee3380> (a org.atmosphere.cpr.AtmosphereResourceEventImpl) > at org.richfaces.application.push.impl.RequestImpl.onBroadcast(RequestImpl.java:129) > - locked <0x00000000e5ed5a50> (a org.richfaces.application.push.impl.RequestImpl) > at org.atmosphere.cpr.AtmosphereResourceImpl.onBroadcast(AtmosphereResourceImpl.java:663) > at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:608) > at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:584) > at org.atmosphere.cpr.DefaultBroadcaster.executeAsyncWrite(DefaultBroadcaster.java:713) > at org.atmosphere.cpr.DefaultBroadcaster$3.run(DefaultBroadcaster.java:747) > - locked <0x00000000e5ed5a88> (a org.atmosphere.cpr.AtmosphereResourceImpl) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:662) > Found 1 deadlock. > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 11:50:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 21 Mar 2012 11:50:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12013) Deadlock in push component In-Reply-To: <654291399.48838.1330441536575.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1689930872.23181.1332345047447.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12013: ------------------------------- Fix Version/s: 4.2.1.CR1 (was: 4.3.0.Milestone1) Git Pull Request: https://github.com/richfaces/core/pull/8 (was: https://github.com/richfaces/core/pull/8) > Deadlock in push component > -------------------------- > > Key: RF-12013 > URL: https://issues.jboss.org/browse/RF-12013 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Affects Versions: 4.2.0.Final > Reporter: Stian Thorgersen > Assignee: Luk?? Fry? > Fix For: 4.2.1.CR1 > > > Deadlocked threads in the push component prevented server from stopping. Not sure whether or not this happened when I initiated shutdown or if these where hanging around for a while. > Relevant output from jstack: > {code} > Found one Java-level deadlock: > ============================= > "push-publish-thread-1": > waiting to lock monitor 0x0000000042650238 (object 0x00000000e5ed5a50, a org.richfaces.application.push.impl.RequestImpl), > which is held by "Atmosphere-AsyncWrite-0" > "Atmosphere-AsyncWrite-0": > waiting to lock monitor 0x00000000427d9ec0 (object 0x00000000e5ed59a0, a org.richfaces.application.push.impl.SessionImpl), > which is held by "push-publish-thread-1" > Java stack information for the threads listed above: > =================================================== > "push-publish-thread-1": > at org.richfaces.application.push.impl.RequestImpl.postMessages(RequestImpl.java:85) > - waiting to lock <0x00000000e5ed5a50> (a org.richfaces.application.push.impl.RequestImpl) > at org.richfaces.application.push.impl.SessionImpl.push(SessionImpl.java:237) > - locked <0x00000000e5ed59a0> (a org.richfaces.application.push.impl.SessionImpl) > at org.richfaces.application.push.impl.TopicImpl$TopicContext.publishMessages(TopicImpl.java:88) > at org.richfaces.application.push.impl.TopicImpl$PublishTask.run(TopicImpl.java:53) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:662) > "Atmosphere-AsyncWrite-0": > at org.richfaces.application.push.impl.SessionImpl.disconnect(SessionImpl.java:117) > - waiting to lock <0x00000000e5ed59a0> (a org.richfaces.application.push.impl.SessionImpl) > at org.richfaces.application.push.impl.RequestImpl.disconnect(RequestImpl.java:107) > at org.richfaces.application.push.impl.RequestImpl.onResume(RequestImpl.java:115) > at org.atmosphere.cpr.AtmosphereResourceImpl.onResume(AtmosphereResourceImpl.java:651) > at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:600) > at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:584) > at org.atmosphere.cpr.AtmosphereResourceImpl.resume(AtmosphereResourceImpl.java:185) > - locked <0x00000000e5ee3380> (a org.atmosphere.cpr.AtmosphereResourceEventImpl) > at org.richfaces.application.push.impl.RequestImpl.onBroadcast(RequestImpl.java:129) > - locked <0x00000000e5ed5a50> (a org.richfaces.application.push.impl.RequestImpl) > at org.atmosphere.cpr.AtmosphereResourceImpl.onBroadcast(AtmosphereResourceImpl.java:663) > at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:608) > at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:584) > at org.atmosphere.cpr.DefaultBroadcaster.executeAsyncWrite(DefaultBroadcaster.java:713) > at org.atmosphere.cpr.DefaultBroadcaster$3.run(DefaultBroadcaster.java:747) > - locked <0x00000000e5ed5a88> (a org.atmosphere.cpr.AtmosphereResourceImpl) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:662) > Found 1 deadlock. > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 11:50:47 2012 From: jira-events at lists.jboss.org (Juraj Huska (JIRA)) Date: Wed, 21 Mar 2012 11:50:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12073) Kitchensink archetype - creating enterprise project requires also community richfaces version Message-ID: <2091208867.23183.1332345047625.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Juraj Huska created RF-12073: -------------------------------- Summary: Kitchensink archetype - creating enterprise project requires also community richfaces version Key: RF-12073 URL: https://issues.jboss.org/browse/RF-12073 Project: RichFaces Issue Type: Enhancement Security Level: Public (Everyone can see) Components: archetype Affects Versions: 4.2.0.Final Reporter: Juraj Huska Priority: Optional When generating enterprise richfaces maven project from kitchensink archetype, it is also prompting for community richfaces version. And then the community version is not used in the generated pom.xml The log from this: {noformat} [INFO] Using property: groupId = bla.bla [INFO] Using property: artifactId = foo_bla Define value for property 'version': 1.0-SNAPSHOT: : [INFO] Using property: package = bla.bla [INFO] Using property: enterprise = n [INFO] Using property: richfaces-enterprise-version = 4.2.0.Final-redhat-1 [INFO] Using property: richfaces-version = 4.3.0-SNAPSHOT Confirm properties configuration: groupId: bla.bla artifactId: foo_bla version: 1.0-SNAPSHOT package: bla.bla enterprise: n richfaces-enterprise-version: 4.2.0.Final-redhat-1 richfaces-version: 4.3.0-SNAPSHOT Y: : N [INFO] Using property: groupId = bla.bla [INFO] Using property: artifactId = foo_bla Define value for property 'version': 1.0-SNAPSHOT: : Define value for property 'package': bla.bla: : Define value for property 'enterprise': n: : y Define value for property 'richfaces-enterprise-version': 4.2.0.Final-redhat-1: : Define value for property 'richfaces-version': 4.3.0-SNAPSHOT: : Confirm properties configuration: groupId: bla.bla artifactId: foo_bla version: 1.0-SNAPSHOT package: bla.bla enterprise: y richfaces-enterprise-version: 4.2.0.Final-redhat-1 richfaces-version: 4.3.0-SNAPSHOT Y: : y [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 54.442s [INFO] Finished at: Wed Mar 21 16:38:02 CET 2012 [INFO] Final Memory: 9M/129M [INFO] ------------------------------------------------------------------------ jhuska at laptop:~/workspace_jbossTools33M5$ {noformat} *Steps to reproduce:* 1. _mvn archetype:generate -DarchetypeGroupId=org.richfaces.archetypes -DarchetypeArtifactId=richfaces-archetype-kitchensink -DarchetypeVersion=4.3.0-SNAPSHOT -DgroupId=bla.bla -DartifactId=foo_bla_ 2. When prompting: ?Define value for property 'version': 1.0-SNAPSHOT:_, press just enter. 3. When prompting for confirming predefined values: type N 4. When prompting for _Define value for property 'version': 1.0-SNAPSHOT: :_ press just enter. 5. _Define value for property 'package': bla.bla: : _ just enter 6. _Define value for property 'enterprise': n: :_ type y 7. _Define value for property 'richfaces-enterprise-version': 4.2.0.Final-redhat-1: :_ just enter 8. now you should be prompted for _Define value for property 'richfaces-version': 4.3.0-SNAPSHOT: :_, which you should not. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 11:55:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 21 Mar 2012 11:55:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12026) Javascript error in AjaxRequests on FireFox "invalid 'in' operand event" In-Reply-To: <1447882664.73686.1331126016454.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <885372347.23198.1332345347442.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678393#comment-12678393 ] Brian Leathem commented on RF-12026: ------------------------------------ Ulf, can you provide some sample code to duplicate this behaviour? > Javascript error in AjaxRequests on FireFox "invalid 'in' operand event" > ------------------------------------------------------------------------ > > Key: RF-12026 > URL: https://issues.jboss.org/browse/RF-12026 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 4.2.0.Final > Environment: FireFox 3.6.27 > Reporter: Ulf Almehed > Assignee: Brian Leathem > Priority: Minor > Labels: regression > Fix For: 4.2.1.CR1 > > > Ajax request fails with javascript error "invalid 'in' operand event", richfaces-queue.js line 130. > This was introduced by the fix in RF-11943. Checking for existence of layerX fails if event isn't an Object (but a simple type). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 12:02:51 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 21 Mar 2012 12:02:51 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12074) Showcase mediaOutput refers to GAE limitations Message-ID: <852769834.23256.1332345771654.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Brian Leathem created RF-12074: ---------------------------------- Summary: Showcase mediaOutput refers to GAE limitations Key: RF-12074 URL: https://issues.jboss.org/browse/RF-12074 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: showcase Reporter: Brian Leathem Fix For: 4.2.1.CR1 {quote} As the Google Application Engine restricts AWT class usage, this example reads the existing image and only performs re-indexing of the palette using colors you selected below. {quote} The example, and the wording should be re-worked to not refer to the GAE limitation. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 12:02:51 2012 From: jira-events at lists.jboss.org (Jean ANDRE (JIRA)) Date: Wed, 21 Mar 2012 12:02:51 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12038) IE8 - Object does not support this property or method - a4j:jsFunction In-Reply-To: <1674243330.3069.1331568048477.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1012475580.23259.1332345771787.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678395#comment-12678395 ] Jean ANDRE commented on RF-12038: --------------------------------- We have found the reason of that. The reason is because the id of the a4j:jsFunction is the same as its name. We made the change and the call to the javascript function is running well. See: http://forum.alsacreations.com/topic-5-862-1-Rsolu-Cet-objet-ne-gre-pas-cette-proprit-ou-cette-mthode.html. Then.... or remove the id as it is not mandatory. {code} {code} > IE8 - Object does not support this property or method - a4j:jsFunction > ---------------------------------------------------------------------- > > Key: RF-12038 > URL: https://issues.jboss.org/browse/RF-12038 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.2.0.Final > Environment: cssparser-0.9.6- guava-11.0.1 - hibernate-validator-4.2.0.Final - JSF/Mojarra 2.1.6 - springframework-3.0.6.RELEASE - sac-1.3 - Windows 7 - IE 8.0.1.7601.17514 > Reporter: Jean ANDRE > Attachments: index.xhtml, NestedWeb.zip > > > Under IE8, IE reports the following error message due to a javascript error. However, the page are well displayed and the application is running ok. > Object doesn't support this property or method line 177 caracter 1 > Object doesn't support this property or method line 177 caracter 99 > Under IE Debugger, the line is: > {code} > closeTab=function(tabId){RichFaces.ajax("closeTab",null,{"incId":"1","parameters":{"tabId":tabId} } )};< > The caracter 99, is..............................................................................| (here) > {code} > This is a code generated by a4j:jsFunction from the XHTML > {code} > > > > > > > {code} > The rendered code is : > {code} > > > > {code} > See also this link as we got almost a similar: https://bugzilla.redhat.com/show_bug.cgi?id=601360. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 12:30:47 2012 From: jira-events at lists.jboss.org (Juraj Huska (JIRA)) Date: Wed, 21 Mar 2012 12:30:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12075) Kitchensink archetype - link for JBoss AS 7 project site is broken Message-ID: <1802298851.23317.1332347447560.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Juraj Huska created RF-12075: -------------------------------- Summary: Kitchensink archetype - link for JBoss AS 7 project site is broken Key: RF-12075 URL: https://issues.jboss.org/browse/RF-12075 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: archetype Affects Versions: 4.2.0.Final Reporter: Juraj Huska Priority: Trivial The link for JBoss AS 7 project site, which is suited in the find out more section is broken, and points to the: {noformat}http://localhost:8080/kitchen-sink-community/jboss.org/jbossas{noformat} It should point to _http://www.jboss.org/jbossas_ It is caused by missing http://www prefix. It is in the facelet page (about.xhtml), particularly line 16: {code:xml}
  • JBoss AS 7 project site
    • {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 12:30:48 2012 From: jira-events at lists.jboss.org (Juraj Huska (JIRA)) Date: Wed, 21 Mar 2012 12:30:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12075) Kitchensink archetype - link for JBoss AS 7 project site is broken In-Reply-To: <1802298851.23317.1332347447560.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1476909414.23331.1332347448085.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj Huska updated RF-12075: ----------------------------- Description: The link for JBoss AS 7 project site, which is suited in the find out more section is broken, and points to the: {noformat}http://localhost:8080/kitchen-sink-community/jboss.org/jbossas{noformat} It should point to http://www.jboss.org/jbossas It is caused by missing http://www prefix. It is in the facelet page (about.xhtml), particularly line 16: {code:xml}
  • JBoss AS 7 project site
    • {code} was: The link for JBoss AS 7 project site, which is suited in the find out more section is broken, and points to the: {noformat}http://localhost:8080/kitchen-sink-community/jboss.org/jbossas{noformat} It should point to _http://www.jboss.org/jbossas_ It is caused by missing http://www prefix. It is in the facelet page (about.xhtml), particularly line 16: {code:xml}
  • JBoss AS 7 project site
    • {code} > Kitchensink archetype - link for JBoss AS 7 project site is broken > ------------------------------------------------------------------ > > Key: RF-12075 > URL: https://issues.jboss.org/browse/RF-12075 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: archetype > Affects Versions: 4.2.0.Final > Reporter: Juraj Huska > Priority: Trivial > > The link for JBoss AS 7 project site, which is suited in the find out more section is broken, and points to the: > {noformat}http://localhost:8080/kitchen-sink-community/jboss.org/jbossas{noformat} > It should point to http://www.jboss.org/jbossas > It is caused by missing http://www prefix. It is in the facelet page (about.xhtml), particularly line 16: > {code:xml} >
  • JBoss AS 7 project site
    • > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 12:40:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 21 Mar 2012 12:40:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12038) IE8 - Object does not support this property or method - a4j:jsFunction In-Reply-To: <1674243330.3069.1331568048477.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1543417886.23357.1332348047294.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12038: ------------------------------- Fix Version/s: 4.2.1.CR1 Component/s: component-a4j-core Thank you for the time you put into identifying the cause, and finding a solution. We'll be sure to include this in the 4.2.1 release. > IE8 - Object does not support this property or method - a4j:jsFunction > ---------------------------------------------------------------------- > > Key: RF-12038 > URL: https://issues.jboss.org/browse/RF-12038 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.2.0.Final > Environment: cssparser-0.9.6- guava-11.0.1 - hibernate-validator-4.2.0.Final - JSF/Mojarra 2.1.6 - springframework-3.0.6.RELEASE - sac-1.3 - Windows 7 - IE 8.0.1.7601.17514 > Reporter: Jean ANDRE > Fix For: 4.2.1.CR1 > > Attachments: index.xhtml, NestedWeb.zip > > > Under IE8, IE reports the following error message due to a javascript error. However, the page are well displayed and the application is running ok. > Object doesn't support this property or method line 177 caracter 1 > Object doesn't support this property or method line 177 caracter 99 > Under IE Debugger, the line is: > {code} > closeTab=function(tabId){RichFaces.ajax("closeTab",null,{"incId":"1","parameters":{"tabId":tabId} } )};< > The caracter 99, is..............................................................................| (here) > {code} > This is a code generated by a4j:jsFunction from the XHTML > {code} > > > > > > > {code} > The rendered code is : > {code} > > > > {code} > See also this link as we got almost a similar: https://bugzilla.redhat.com/show_bug.cgi?id=601360. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 12:42:47 2012 From: jira-events at lists.jboss.org (Stian Thorgersen (JIRA)) Date: Wed, 21 Mar 2012 12:42:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12013) Deadlock in push component In-Reply-To: <654291399.48838.1330441536575.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <655212672.23360.1332348167346.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678406#comment-12678406 ] Stian Thorgersen commented on RF-12013: --------------------------------------- Tried to get the problem to happen, but no luck. So can't actually test the fix properly. > Deadlock in push component > -------------------------- > > Key: RF-12013 > URL: https://issues.jboss.org/browse/RF-12013 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Affects Versions: 4.2.0.Final > Reporter: Stian Thorgersen > Assignee: Luk?? Fry? > Fix For: 4.2.1.CR1 > > > Deadlocked threads in the push component prevented server from stopping. Not sure whether or not this happened when I initiated shutdown or if these where hanging around for a while. > Relevant output from jstack: > {code} > Found one Java-level deadlock: > ============================= > "push-publish-thread-1": > waiting to lock monitor 0x0000000042650238 (object 0x00000000e5ed5a50, a org.richfaces.application.push.impl.RequestImpl), > which is held by "Atmosphere-AsyncWrite-0" > "Atmosphere-AsyncWrite-0": > waiting to lock monitor 0x00000000427d9ec0 (object 0x00000000e5ed59a0, a org.richfaces.application.push.impl.SessionImpl), > which is held by "push-publish-thread-1" > Java stack information for the threads listed above: > =================================================== > "push-publish-thread-1": > at org.richfaces.application.push.impl.RequestImpl.postMessages(RequestImpl.java:85) > - waiting to lock <0x00000000e5ed5a50> (a org.richfaces.application.push.impl.RequestImpl) > at org.richfaces.application.push.impl.SessionImpl.push(SessionImpl.java:237) > - locked <0x00000000e5ed59a0> (a org.richfaces.application.push.impl.SessionImpl) > at org.richfaces.application.push.impl.TopicImpl$TopicContext.publishMessages(TopicImpl.java:88) > at org.richfaces.application.push.impl.TopicImpl$PublishTask.run(TopicImpl.java:53) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:662) > "Atmosphere-AsyncWrite-0": > at org.richfaces.application.push.impl.SessionImpl.disconnect(SessionImpl.java:117) > - waiting to lock <0x00000000e5ed59a0> (a org.richfaces.application.push.impl.SessionImpl) > at org.richfaces.application.push.impl.RequestImpl.disconnect(RequestImpl.java:107) > at org.richfaces.application.push.impl.RequestImpl.onResume(RequestImpl.java:115) > at org.atmosphere.cpr.AtmosphereResourceImpl.onResume(AtmosphereResourceImpl.java:651) > at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:600) > at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:584) > at org.atmosphere.cpr.AtmosphereResourceImpl.resume(AtmosphereResourceImpl.java:185) > - locked <0x00000000e5ee3380> (a org.atmosphere.cpr.AtmosphereResourceEventImpl) > at org.richfaces.application.push.impl.RequestImpl.onBroadcast(RequestImpl.java:129) > - locked <0x00000000e5ed5a50> (a org.richfaces.application.push.impl.RequestImpl) > at org.atmosphere.cpr.AtmosphereResourceImpl.onBroadcast(AtmosphereResourceImpl.java:663) > at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:608) > at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:584) > at org.atmosphere.cpr.DefaultBroadcaster.executeAsyncWrite(DefaultBroadcaster.java:713) > at org.atmosphere.cpr.DefaultBroadcaster$3.run(DefaultBroadcaster.java:747) > - locked <0x00000000e5ed5a88> (a org.atmosphere.cpr.AtmosphereResourceImpl) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:662) > Found 1 deadlock. > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 12:45:47 2012 From: jira-events at lists.jboss.org (Juraj Huska (JIRA)) Date: Wed, 21 Mar 2012 12:45:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12076) Kitchensink archetype - back button does not back to the correct page state Message-ID: <364076515.23363.1332348347607.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Juraj Huska created RF-12076: -------------------------------- Summary: Kitchensink archetype - back button does not back to the correct page state Key: RF-12076 URL: https://issues.jboss.org/browse/RF-12076 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: archetype Affects Versions: 4.2.0.Final Reporter: Juraj Huska Priority: Minor When clicking on the url of the freshly created new member (like /rest/members/0) and backing back from the xml viewing, results in removed freshly added member. After refresh, or AJAX update (clicking on accordion panel), the table is with all members again. This happens only for freshly added members. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 12:47:47 2012 From: jira-events at lists.jboss.org (Juraj Huska (JIRA)) Date: Wed, 21 Mar 2012 12:47:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12076) Kitchensink archetype - back button does not back to the correct page state In-Reply-To: <364076515.23363.1332348347607.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1709651090.23370.1332348467419.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj Huska updated RF-12076: ----------------------------- Description: When clicking on the url of the freshly created new member (like /rest/members/0) and backing back from the xml viewing, results in removed freshly added member. After refresh, or AJAX update (clicking on collapsiblePanel), the table is with all members again. This happens only for freshly added members. was: When clicking on the url of the freshly created new member (like /rest/members/0) and backing back from the xml viewing, results in removed freshly added member. After refresh, or AJAX update (clicking on accordion panel), the table is with all members again. This happens only for freshly added members. > Kitchensink archetype - back button does not back to the correct page state > --------------------------------------------------------------------------- > > Key: RF-12076 > URL: https://issues.jboss.org/browse/RF-12076 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: archetype > Affects Versions: 4.2.0.Final > Reporter: Juraj Huska > Priority: Minor > > When clicking on the url of the freshly created new member (like /rest/members/0) and backing back from the xml viewing, results in removed freshly added member. > After refresh, or AJAX update (clicking on collapsiblePanel), the table is with all members again. > This happens only for freshly added members. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 12:53:47 2012 From: jira-events at lists.jboss.org (Juraj Huska (JIRA)) Date: Wed, 21 Mar 2012 12:53:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12076) Kitchensink archetype - back button does not back to the correct page state In-Reply-To: <364076515.23363.1332348347607.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1802460574.23399.1332348827799.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj Huska updated RF-12076: ----------------------------- Environment: AS: JBoss AS 7.1.1.Final, EAP 6.0.0.ER3 > Kitchensink archetype - back button does not back to the correct page state > --------------------------------------------------------------------------- > > Key: RF-12076 > URL: https://issues.jboss.org/browse/RF-12076 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: archetype > Affects Versions: 4.2.0.Final > Environment: AS: JBoss AS 7.1.1.Final, EAP 6.0.0.ER3 > Reporter: Juraj Huska > Priority: Minor > > When clicking on the url of the freshly created new member (like /rest/members/0) and backing back from the xml viewing, results in removed freshly added member. > After refresh, or AJAX update (clicking on collapsiblePanel), the table is with all members again. > This happens only for freshly added members. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 13:39:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 21 Mar 2012 13:39:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12013) Deadlock in push component In-Reply-To: <654291399.48838.1330441536575.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1124831044.23450.1332351587338.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678413#comment-12678413 ] Luk?? Fry? commented on RF-12013: --------------------------------- Thanks for trying, Stian, I'm pretty sure it's hard to reproduce it. Otherwise Push works as expected? > Deadlock in push component > -------------------------- > > Key: RF-12013 > URL: https://issues.jboss.org/browse/RF-12013 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Affects Versions: 4.2.0.Final > Reporter: Stian Thorgersen > Assignee: Luk?? Fry? > Fix For: 4.2.1.CR1 > > > Deadlocked threads in the push component prevented server from stopping. Not sure whether or not this happened when I initiated shutdown or if these where hanging around for a while. > Relevant output from jstack: > {code} > Found one Java-level deadlock: > ============================= > "push-publish-thread-1": > waiting to lock monitor 0x0000000042650238 (object 0x00000000e5ed5a50, a org.richfaces.application.push.impl.RequestImpl), > which is held by "Atmosphere-AsyncWrite-0" > "Atmosphere-AsyncWrite-0": > waiting to lock monitor 0x00000000427d9ec0 (object 0x00000000e5ed59a0, a org.richfaces.application.push.impl.SessionImpl), > which is held by "push-publish-thread-1" > Java stack information for the threads listed above: > =================================================== > "push-publish-thread-1": > at org.richfaces.application.push.impl.RequestImpl.postMessages(RequestImpl.java:85) > - waiting to lock <0x00000000e5ed5a50> (a org.richfaces.application.push.impl.RequestImpl) > at org.richfaces.application.push.impl.SessionImpl.push(SessionImpl.java:237) > - locked <0x00000000e5ed59a0> (a org.richfaces.application.push.impl.SessionImpl) > at org.richfaces.application.push.impl.TopicImpl$TopicContext.publishMessages(TopicImpl.java:88) > at org.richfaces.application.push.impl.TopicImpl$PublishTask.run(TopicImpl.java:53) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:662) > "Atmosphere-AsyncWrite-0": > at org.richfaces.application.push.impl.SessionImpl.disconnect(SessionImpl.java:117) > - waiting to lock <0x00000000e5ed59a0> (a org.richfaces.application.push.impl.SessionImpl) > at org.richfaces.application.push.impl.RequestImpl.disconnect(RequestImpl.java:107) > at org.richfaces.application.push.impl.RequestImpl.onResume(RequestImpl.java:115) > at org.atmosphere.cpr.AtmosphereResourceImpl.onResume(AtmosphereResourceImpl.java:651) > at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:600) > at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:584) > at org.atmosphere.cpr.AtmosphereResourceImpl.resume(AtmosphereResourceImpl.java:185) > - locked <0x00000000e5ee3380> (a org.atmosphere.cpr.AtmosphereResourceEventImpl) > at org.richfaces.application.push.impl.RequestImpl.onBroadcast(RequestImpl.java:129) > - locked <0x00000000e5ed5a50> (a org.richfaces.application.push.impl.RequestImpl) > at org.atmosphere.cpr.AtmosphereResourceImpl.onBroadcast(AtmosphereResourceImpl.java:663) > at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:608) > at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:584) > at org.atmosphere.cpr.DefaultBroadcaster.executeAsyncWrite(DefaultBroadcaster.java:713) > at org.atmosphere.cpr.DefaultBroadcaster$3.run(DefaultBroadcaster.java:747) > - locked <0x00000000e5ed5a88> (a org.atmosphere.cpr.AtmosphereResourceImpl) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:662) > Found 1 deadlock. > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 13:50:47 2012 From: jira-events at lists.jboss.org (Stian Thorgersen (JIRA)) Date: Wed, 21 Mar 2012 13:50:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12072) Lost event in push In-Reply-To: <1823827590.22721.1332335688298.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1532234996.23469.1332352247479.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stian Thorgersen updated RF-12072: ---------------------------------- Description: Event can be lost if produced while a response is being prepared. I've attached an example where a push event is used to refresh a count whenever an event is fired. It's using Thread.sleep to simulate an event being produced while the response is being prepared. Note, if the sleep just before returning the count is removed it all works fine, and the page is refreshed every 5 seconds, but with the sleep in place the event is lost. View: {code} {code} Bean: {code} package com.example; import java.io.Serializable; import java.util.concurrent.atomic.AtomicInteger; import javax.enterprise.context.SessionScoped; import javax.inject.Named; import org.richfaces.application.push.TopicKey; import org.richfaces.application.push.TopicsContext; @Named @SessionScoped public class MyBean implements Serializable { private AtomicInteger count = new AtomicInteger(); public int getCount() { int c = count.get(); new Thread() { public void run() { try { Thread.sleep(5000); count.incrementAndGet(); TopicKey topicKey = new TopicKey("chat"); TopicsContext topicsContext = TopicsContext.lookup(); topicsContext.publish(topicKey, ""); } catch (Exception e) { e.printStackTrace(); } }; }.start(); try { Thread.sleep(10000); } catch (InterruptedException e) { } return c; } } {code} was: Event can be lost if produced while a response is being prepared. I've attached an example where a push event is used to refresh a count whenever an event is fired. It's using Thread.sleep to simulate an event being produced while the response is being prepared. Note, if the sleep just before returning the count is removed it all works fine, and the page is refreshed every 5 seconds, but with the sleep in place it the event is lost. View: {code} {code} Bean: {code} package com.example; import java.io.Serializable; import java.util.concurrent.atomic.AtomicInteger; import javax.enterprise.context.SessionScoped; import javax.inject.Named; import org.richfaces.application.push.TopicKey; import org.richfaces.application.push.TopicsContext; @Named @SessionScoped public class MyBean implements Serializable { private AtomicInteger count = new AtomicInteger(); public int getCount() { int c = count.get(); new Thread() { public void run() { try { Thread.sleep(5000); count.incrementAndGet(); TopicKey topicKey = new TopicKey("chat"); TopicsContext topicsContext = TopicsContext.lookup(); topicsContext.publish(topicKey, ""); } catch (Exception e) { e.printStackTrace(); } }; }.start(); try { Thread.sleep(10000); } catch (InterruptedException e) { } return c; } } {code} > Lost event in push > ------------------ > > Key: RF-12072 > URL: https://issues.jboss.org/browse/RF-12072 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Stian Thorgersen > > Event can be lost if produced while a response is being prepared. I've attached an example where a push event is used to refresh a count whenever an event is fired. It's using Thread.sleep to simulate an event being produced while the response is being prepared. Note, if the sleep just before returning the count is removed it all works fine, and the page is refreshed every 5 seconds, but with the sleep in place the event is lost. > View: > {code} > > > xmlns:f="http://java.sun.com/jsf/core" > xmlns:h="http://java.sun.com/jsf/html" > xmlns:a4j="http://richfaces.org/a4j" > xmlns:rich="http://richfaces.org/rich"> > > > > > > > > > > > > > {code} > Bean: > {code} > package com.example; > import java.io.Serializable; > import java.util.concurrent.atomic.AtomicInteger; > import javax.enterprise.context.SessionScoped; > import javax.inject.Named; > import org.richfaces.application.push.TopicKey; > import org.richfaces.application.push.TopicsContext; > @Named > @SessionScoped > public class MyBean implements Serializable > { > private AtomicInteger count = new AtomicInteger(); > public int getCount() > { > int c = count.get(); > new Thread() > { > public void run() > { > try > { > Thread.sleep(5000); > count.incrementAndGet(); > TopicKey topicKey = new TopicKey("chat"); > TopicsContext topicsContext = TopicsContext.lookup(); > topicsContext.publish(topicKey, ""); > } > catch (Exception e) > { > e.printStackTrace(); > } > }; > }.start(); > > try > { > Thread.sleep(10000); > } > catch (InterruptedException e) > { > } > return c; > } > } > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 13:50:47 2012 From: jira-events at lists.jboss.org (Stian Thorgersen (JIRA)) Date: Wed, 21 Mar 2012 13:50:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12072) Lost event in push In-Reply-To: <1823827590.22721.1332335688298.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <882946208.23466.1332352247382.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stian Thorgersen updated RF-12072: ---------------------------------- Description: Event can be lost if produced while a response is being prepared. I've attached an example where a push event is used to refresh a count whenever an event is fired. It's using Thread.sleep to simulate an event being produced while the response is being prepared. Note, if the sleep just before returning the count is removed it all works fine, and the page is refreshed every 5 seconds, but with the sleep in place it the event is lost. View: {code} {code} Bean: {code} package com.example; import java.io.Serializable; import java.util.concurrent.atomic.AtomicInteger; import javax.enterprise.context.SessionScoped; import javax.inject.Named; import org.richfaces.application.push.TopicKey; import org.richfaces.application.push.TopicsContext; @Named @SessionScoped public class MyBean implements Serializable { private AtomicInteger count = new AtomicInteger(); public int getCount() { int c = count.get(); new Thread() { public void run() { try { Thread.sleep(5000); count.incrementAndGet(); TopicKey topicKey = new TopicKey("chat"); TopicsContext topicsContext = TopicsContext.lookup(); topicsContext.publish(topicKey, ""); } catch (Exception e) { e.printStackTrace(); } }; }.start(); try { Thread.sleep(10000); } catch (InterruptedException e) { } return c; } } {code} was: Event can be lost if produced while a response is being prepared. I've attached an example where a push event is used to refresh a count whenever an event is fired. It's using Thread.sleep to simulate an event being produced while the response is being prepared. Note, if the sleep just before returning the count is removed it all works fine, and the page is refreshed every 5 seconds, but without it the event is lost. View: {code} {code} Bean: {code} package com.example; import java.io.Serializable; import java.util.concurrent.atomic.AtomicInteger; import javax.enterprise.context.SessionScoped; import javax.inject.Named; import org.richfaces.application.push.TopicKey; import org.richfaces.application.push.TopicsContext; @Named @SessionScoped public class MyBean implements Serializable { private AtomicInteger count = new AtomicInteger(); public int getCount() { int c = count.get(); new Thread() { public void run() { try { Thread.sleep(5000); count.incrementAndGet(); TopicKey topicKey = new TopicKey("chat"); TopicsContext topicsContext = TopicsContext.lookup(); topicsContext.publish(topicKey, ""); } catch (Exception e) { e.printStackTrace(); } }; }.start(); try { Thread.sleep(10000); } catch (InterruptedException e) { } return c; } } {code} > Lost event in push > ------------------ > > Key: RF-12072 > URL: https://issues.jboss.org/browse/RF-12072 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Stian Thorgersen > > Event can be lost if produced while a response is being prepared. I've attached an example where a push event is used to refresh a count whenever an event is fired. It's using Thread.sleep to simulate an event being produced while the response is being prepared. Note, if the sleep just before returning the count is removed it all works fine, and the page is refreshed every 5 seconds, but with the sleep in place it the event is lost. > View: > {code} > > > xmlns:f="http://java.sun.com/jsf/core" > xmlns:h="http://java.sun.com/jsf/html" > xmlns:a4j="http://richfaces.org/a4j" > xmlns:rich="http://richfaces.org/rich"> > > > > > > > > > > > > > {code} > Bean: > {code} > package com.example; > import java.io.Serializable; > import java.util.concurrent.atomic.AtomicInteger; > import javax.enterprise.context.SessionScoped; > import javax.inject.Named; > import org.richfaces.application.push.TopicKey; > import org.richfaces.application.push.TopicsContext; > @Named > @SessionScoped > public class MyBean implements Serializable > { > private AtomicInteger count = new AtomicInteger(); > public int getCount() > { > int c = count.get(); > new Thread() > { > public void run() > { > try > { > Thread.sleep(5000); > count.incrementAndGet(); > TopicKey topicKey = new TopicKey("chat"); > TopicsContext topicsContext = TopicsContext.lookup(); > topicsContext.publish(topicKey, ""); > } > catch (Exception e) > { > e.printStackTrace(); > } > }; > }.start(); > > try > { > Thread.sleep(10000); > } > catch (InterruptedException e) > { > } > return c; > } > } > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 13:56:47 2012 From: jira-events at lists.jboss.org (Jean ANDRE (JIRA)) Date: Wed, 21 Mar 2012 13:56:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12038) IE8 - Object does not support this property or method - a4j:jsFunction In-Reply-To: <1674243330.3069.1331568048477.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1917591157.23485.1332352607479.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678418#comment-12678418 ] Jean ANDRE commented on RF-12038: --------------------------------- The case is also here with tab. IE8 - Object does not support this property or method - a4j:jsFunction > ---------------------------------------------------------------------- > > Key: RF-12038 > URL: https://issues.jboss.org/browse/RF-12038 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.2.0.Final > Environment: cssparser-0.9.6- guava-11.0.1 - hibernate-validator-4.2.0.Final - JSF/Mojarra 2.1.6 - springframework-3.0.6.RELEASE - sac-1.3 - Windows 7 - IE 8.0.1.7601.17514 > Reporter: Jean ANDRE > Fix For: 4.2.1.CR1 > > Attachments: index.xhtml, NestedWeb.zip > > > Under IE8, IE reports the following error message due to a javascript error. However, the page are well displayed and the application is running ok. > Object doesn't support this property or method line 177 caracter 1 > Object doesn't support this property or method line 177 caracter 99 > Under IE Debugger, the line is: > {code} > closeTab=function(tabId){RichFaces.ajax("closeTab",null,{"incId":"1","parameters":{"tabId":tabId} } )};< > The caracter 99, is..............................................................................| (here) > {code} > This is a code generated by a4j:jsFunction from the XHTML > {code} > > > > > > > {code} > The rendered code is : > {code} > > > > {code} > See also this link as we got almost a similar: https://bugzilla.redhat.com/show_bug.cgi?id=601360. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 13:58:47 2012 From: jira-events at lists.jboss.org (Jean ANDRE (JIRA)) Date: Wed, 21 Mar 2012 13:58:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12038) IE8 - Object does not support this property or method - a4j:jsFunction In-Reply-To: <1674243330.3069.1331568048477.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <378410548.23489.1332352727984.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678418#comment-12678418 ] Jean ANDRE edited comment on RF-12038 at 3/21/12 1:57 PM: ---------------------------------------------------------- The case is also here with tab. From our side we must have an id as the id is used by our automated testing tool. was (Author: jorelia64): The case is also here with tab. IE8 - Object does not support this property or method - a4j:jsFunction > ---------------------------------------------------------------------- > > Key: RF-12038 > URL: https://issues.jboss.org/browse/RF-12038 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.2.0.Final > Environment: cssparser-0.9.6- guava-11.0.1 - hibernate-validator-4.2.0.Final - JSF/Mojarra 2.1.6 - springframework-3.0.6.RELEASE - sac-1.3 - Windows 7 - IE 8.0.1.7601.17514 > Reporter: Jean ANDRE > Fix For: 4.2.1.CR1 > > Attachments: index.xhtml, NestedWeb.zip > > > Under IE8, IE reports the following error message due to a javascript error. However, the page are well displayed and the application is running ok. > Object doesn't support this property or method line 177 caracter 1 > Object doesn't support this property or method line 177 caracter 99 > Under IE Debugger, the line is: > {code} > closeTab=function(tabId){RichFaces.ajax("closeTab",null,{"incId":"1","parameters":{"tabId":tabId} } )};< > The caracter 99, is..............................................................................| (here) > {code} > This is a code generated by a4j:jsFunction from the XHTML > {code} > > > > > > > {code} > The rendered code is : > {code} > > > > {code} > See also this link as we got almost a similar: https://bugzilla.redhat.com/show_bug.cgi?id=601360. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 14:02:48 2012 From: jira-events at lists.jboss.org (Stian Thorgersen (JIRA)) Date: Wed, 21 Mar 2012 14:02:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12013) Deadlock in push component In-Reply-To: <654291399.48838.1330441536575.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <472582444.23503.1332352968045.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678421#comment-12678421 ] Stian Thorgersen commented on RF-12013: --------------------------------------- Thanks for the fix, I've built it from GIT and will use that on my dev box. Other than this issue, the push component is mostly working, except for another issue I've recently discovered. I'm loosing events if they are fired between the model is updated and the page is viewed. See https://issues.jboss.org/browse/RF-12072. I'm currently using TopicsContext to publish messages, I tried to use CDI events to see if that made any difference but got an exception with "Service Tracker has not been initialized". > Deadlock in push component > -------------------------- > > Key: RF-12013 > URL: https://issues.jboss.org/browse/RF-12013 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Affects Versions: 4.2.0.Final > Reporter: Stian Thorgersen > Assignee: Luk?? Fry? > Fix For: 4.2.1.CR1 > > > Deadlocked threads in the push component prevented server from stopping. Not sure whether or not this happened when I initiated shutdown or if these where hanging around for a while. > Relevant output from jstack: > {code} > Found one Java-level deadlock: > ============================= > "push-publish-thread-1": > waiting to lock monitor 0x0000000042650238 (object 0x00000000e5ed5a50, a org.richfaces.application.push.impl.RequestImpl), > which is held by "Atmosphere-AsyncWrite-0" > "Atmosphere-AsyncWrite-0": > waiting to lock monitor 0x00000000427d9ec0 (object 0x00000000e5ed59a0, a org.richfaces.application.push.impl.SessionImpl), > which is held by "push-publish-thread-1" > Java stack information for the threads listed above: > =================================================== > "push-publish-thread-1": > at org.richfaces.application.push.impl.RequestImpl.postMessages(RequestImpl.java:85) > - waiting to lock <0x00000000e5ed5a50> (a org.richfaces.application.push.impl.RequestImpl) > at org.richfaces.application.push.impl.SessionImpl.push(SessionImpl.java:237) > - locked <0x00000000e5ed59a0> (a org.richfaces.application.push.impl.SessionImpl) > at org.richfaces.application.push.impl.TopicImpl$TopicContext.publishMessages(TopicImpl.java:88) > at org.richfaces.application.push.impl.TopicImpl$PublishTask.run(TopicImpl.java:53) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:662) > "Atmosphere-AsyncWrite-0": > at org.richfaces.application.push.impl.SessionImpl.disconnect(SessionImpl.java:117) > - waiting to lock <0x00000000e5ed59a0> (a org.richfaces.application.push.impl.SessionImpl) > at org.richfaces.application.push.impl.RequestImpl.disconnect(RequestImpl.java:107) > at org.richfaces.application.push.impl.RequestImpl.onResume(RequestImpl.java:115) > at org.atmosphere.cpr.AtmosphereResourceImpl.onResume(AtmosphereResourceImpl.java:651) > at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:600) > at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:584) > at org.atmosphere.cpr.AtmosphereResourceImpl.resume(AtmosphereResourceImpl.java:185) > - locked <0x00000000e5ee3380> (a org.atmosphere.cpr.AtmosphereResourceEventImpl) > at org.richfaces.application.push.impl.RequestImpl.onBroadcast(RequestImpl.java:129) > - locked <0x00000000e5ed5a50> (a org.richfaces.application.push.impl.RequestImpl) > at org.atmosphere.cpr.AtmosphereResourceImpl.onBroadcast(AtmosphereResourceImpl.java:663) > at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:608) > at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:584) > at org.atmosphere.cpr.DefaultBroadcaster.executeAsyncWrite(DefaultBroadcaster.java:713) > at org.atmosphere.cpr.DefaultBroadcaster$3.run(DefaultBroadcaster.java:747) > - locked <0x00000000e5ed5a88> (a org.atmosphere.cpr.AtmosphereResourceImpl) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:662) > Found 1 deadlock. > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 14:40:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 21 Mar 2012 14:40:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12041) BeanValidator: no way to use BeanValidation with a custom config In-Reply-To: <1809953065.8110.1331715108624.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <891914795.23571.1332355247854.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12041: ------------------------------- Fix Version/s: 3.Future > BeanValidator: no way to use BeanValidation with a custom config > ---------------------------------------------------------------- > > Key: RF-12041 > URL: https://issues.jboss.org/browse/RF-12041 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 3.3.3.Final > Environment: Liferay 5.2.4, Portlet 2.0, JSF 1.2 > Reporter: Markus Staab > Fix For: 3.Future > > > The BeanValidator class bootstraps a whole new BeanValidation context in its constructor: > {code} > BeanValidator() { > // Enforce class to load > ValidatorFactory.class.getName(); > // Check Factory, to avoid instantiation errors > // https://jira.jboss.org/jira/browse/RF-7226 > validatorFactory = Validation > .buildDefaultValidatorFactory(); > validatorContext = validatorFactory.usingContext(); > MessageInterpolator jsfMessageInterpolator = new JsfMessageInterpolator( > validatorFactory.getMessageInterpolator()); > validatorContext.messageInterpolator(jsfMessageInterpolator); > } > {code} > because of this, there is no way to use the programmatic configuration feature of BeanValidation. > I tried to pre-configure a custom MessageInterpolator with > {code} > Configuration config = Validation.byDefaultProvider().configure(); > config.messageInterpolator( new MyInterpolator() ); > {code} > but this configuration change is not taken into account by the BeanValidator of Richfaces. > ATM the only way to achive this sort of customization is to use a META-INF/validation.xml -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 14:40:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 21 Mar 2012 14:40:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12065) Continuous event polling in available.js In-Reply-To: <289191080.19891.1332243107446.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <184415013.23573.1332355247985.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12065: ------------------------------- Fix Version/s: 3.Future > Continuous event polling in available.js > ---------------------------------------- > > Key: RF-12065 > URL: https://issues.jboss.org/browse/RF-12065 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 3.3.3.Final > Reporter: Nicholas Oxh?j > Priority: Minor > Fix For: 3.Future > > > In available.js there are two functions activatePolling() and stopPolling(), used to wait for a specific DOM element becoming available. > But while activatePolling() starts observing the events "*mousemove*", "focus", and "focusin", stopPolling() stops observing the events "*mouseover*", "focus", and "focusin" - which means that it will _keep_ calling onEvent() on every "mousemove", even when the relevant element has already been found... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 14:40:48 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 21 Mar 2012 14:40:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12067) Load order of external JavaScript files referenced in AJAX responses In-Reply-To: <1604731307.20138.1332248510243.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <2004224583.23575.1332355248044.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12067: ------------------------------- Fix Version/s: 3.Future > Load order of external JavaScript files referenced in AJAX responses > -------------------------------------------------------------------- > > Key: RF-12067 > URL: https://issues.jboss.org/browse/RF-12067 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 3.3.3.Final > Reporter: Nicholas Oxh?j > Fix For: 3.Future > > > Hi, > I think there is a problem with the way that RichFaces loads external JavaScript files, referenced in AJAX responses. The way it is done at the moment, the files are loaded *and parsed* asynchronously. This is a problem if the files depend on being loaded in the correct order. > As an example, I have a page with an OpenFaces DataTable which is not initially rendered, but can be later rendered using the "reRender" attribute of an AJAX action. The Openfaces DataTable requires two OpenFaces JavaScript files, util.js & ajaxUtil.js, where the second depends on the first being loaded first. These files are included in the section of the AJAX response, in the correct order. But since they are then loaded asynchronously, things will break if ajaxUtil.js finishes loading first. > I think you need to ensure, that the files are parsed in the same order as they appear in the response. > The problem is mainly in the function _appendNewElements() in AJAX.js. > For HTML5 capable browsers, you should just be able to add set the "async" property to "false" on the script element, before appending it to head as described here: [HTML5 Async Scripts|http://ie.microsoft.com/testdrive/Performance/AsyncScripts/Default.html] > For non-HTML5 browsers, the only solution would probably be to modify the functionality a bit, such that you would only generate and insert a new script tag, when the previous script finished loading. Since appendNewHeadElements() already uses the scripts "onload" and "onreadystatechange" to find out when _all_ scripts have loaded, I suspect that it should be a relatively minor change to initially just insert the _first_ script tag and then use these functions to insert the _next_ script tag when the first has finished loading. > For an in-depth discussion of the problems and different solution strategies, see WHATWGs [Dynamic Script Execution Order|http://wiki.whatwg.org/wiki/Dynamic_Script_Execution_Order] > Regards, > Nicholas Oxh?j -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 14:40:48 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 21 Mar 2012 14:40:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12062) a4j:outputMedia does not reRender in Firefox 11 In-Reply-To: <1235192300.18015.1332176867445.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1104249216.23580.1332355248243.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12062: ------------------------------- Fix Version/s: 3.Future > a4j:outputMedia does not reRender in Firefox 11 > ------------------------------------------------ > > Key: RF-12062 > URL: https://issues.jboss.org/browse/RF-12062 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 3.3.3.Final > Environment: JBoss AS 6 > Reporter: Toni Neubert > Labels: a4j, outputmedia, richfaces > Fix For: 3.Future > > Attachments: WebXml.patch > > > a4j:outputMedia does not reRender in Firefox 11. The following error appears: > ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/BPM-Process].[default]] Servlet.service() for servlet default threw exception: javax.faces.FacesException: Error decode resource data > at org.ajax4jsf.resource.ResourceBuilderImpl.decrypt(ResourceBuilderImpl.java:627) [:3.3.3.Final] > at org.ajax4jsf.resource.ResourceBuilderImpl.getResourceDataForKey(ResourceBuilderImpl.java:371) [:3.3.3.Final] > at org.ajax4jsf.resource.InternetResourceService.serviceResource(InternetResourceService.java:156) [:3.3.3.Final] > at org.ajax4jsf.resource.InternetResourceService.serviceResource(InternetResourceService.java:141) [:3.3.3.Final] > at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:508) [:3.3.3.Final] > at org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:56) [:2.2.2.Final] > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) [:2.2.2.Final] > at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:60) [:2.2.2.Final] > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) [:2.2.2.Final] > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:73) [:2.2.2.Final] > at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) [:2.2.2.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:274) [:6.1.0.Final] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242) [:6.1.0.Final] > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [:6.1.0.Final] > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [:6.1.0.Final] > at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:181) [:6.1.0.Final] > at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:501) [:6.1.0.Final] > at org.jboss.modcluster.catalina.CatalinaContext$RequestListenerValve.event(CatalinaContext.java:285) [:1.1.0.Final] > at org.jboss.modcluster.catalina.CatalinaContext$RequestListenerValve.invoke(CatalinaContext.java:261) [:1.1.0.Final] > at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:88) [:6.1.0.Final] > at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:100) [:6.1.0.Final] > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:159) [:6.1.0.Final] > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [:6.1.0.Final] > at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) [:6.1.0.Final] > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [:6.1.0.Final] > at org.jboss.web.tomcat.service.request.ActiveRequestResponseCacheValve.invoke(ActiveRequestResponseCacheValve.java:53) [:6.1.0.Final] > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) [:6.1.0.Final] > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [:6.1.0.Final] > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:654) [:6.1.0.Final] > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:951) [:6.1.0.Final] > at java.lang.Thread.run(Unknown Source) [:1.6.0_31] > Caused by: java.util.zip.DataFormatException: invalid bit length repeat > at java.util.zip.Inflater.inflateBytes(Native Method) [:1.6.0_31] > at java.util.zip.Inflater.inflate(Unknown Source) [:1.6.0_31] > at java.util.zip.Inflater.inflate(Unknown Source) [:1.6.0_31] > at org.ajax4jsf.resource.ResourceBuilderImpl.decrypt(ResourceBuilderImpl.java:621) [:3.3.3.Final] > ... 30 more > The picture is not visible. But if you refresh the site with f5, there is no error and all works great. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 14:42:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 21 Mar 2012 14:42:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11801) ClientValidatorImpl ClassCastException in restoreState (StateHolderSaver not an Object[]) In-Reply-To: <1599733089.80179.1323286480699.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <883582230.23585.1332355367832.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-11801. -------------------------------- Labels: (was: waiting_on_user) Resolution: Incomplete Description > ClientValidatorImpl ClassCastException in restoreState (StateHolderSaver not an Object[]) > ----------------------------------------------------------------------------------------- > > Key: RF-11801 > URL: https://issues.jboss.org/browse/RF-11801 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-validators > Affects Versions: 4.1.0.CR1 > Reporter: Giovanni Pelosi > Assignee: Jan Papousek > Attachments: abDataTemplate.xhtml, dataform.xhtml, input.xhtml > > > when i do an ajax submit on a form with inputs fields (h:inputText) > (defined in a composite component), i got this exception: > ClassCastException > in org.richfaces.component.behavior.ClientValidatorImpl.restoreState at line 357 > {code} > @Override > public void restoreState(FacesContext context, Object state) { > if (context == null) { > throw new NullPointerException(); > } > if (state != null) { > ==> Object[] values = (Object[]) state; > super.restoreState(context, values[0]); > if (values.length != 1) { > groups = (Class[]) values[1]; > // If we saved state last time, save state again next time. > clearInitialState(); > } > } > } > {code} > because state is an instance of javax.faces.component.StateHolderSaver > RF 4.1CR1 > MOJARRA 2.1.3 > JBoss 7.0.2 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 14:42:48 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 21 Mar 2012 14:42:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11991) NPE in ...push.impl.RequestImpl.onBroadcast() In-Reply-To: <332746981.25417.1329502476234.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <678409467.23599.1332355368510.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-11991. -------------------------------- Resolution: Cannot Reproduce Bug > NPE in ...push.impl.RequestImpl.onBroadcast() > --------------------------------------------- > > Key: RF-11991 > URL: https://issues.jboss.org/browse/RF-11991 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Affects Versions: 4.2.0.CR1 > Environment: JBossAS 7.1.0 Web Profile > Reporter: Juergen Zimmermann > Assignee: Luk?? Fry? > Labels: waiting_on_user > > I'm using JBossAS 7.1 (Web Profile) via standalone (not domain). When there is no push event I'm getting a NPE (see stacktrace below). > These JARs are in WEB-INF/lib: > atmosphere-compat-jbossweb-0.8.4.jar > atmosphere-compat-jetty-0.8.4.jar > atmosphere-compat-tomcat-0.8.4.jar > atmosphere-compat-tomcat7-0.8.4.jar > atmosphere-compat-weblogic-0.8.4.jar > atmosphere-runtime-0.8.4.jar > web.xml is configured as follows: > > org.atmosphere.useBlocking > true > > Stacktrace: > {code} > 18:50:47,754 Schwerwiegend [org.richfaces.log.Application] (http-localhost-127.0.0.1-8080-5) null: java.lang.NullPointerException > at org.richfaces.application.push.impl.RequestImpl.onBroadcast(RequestImpl.java:124) [richfaces-core-impl-4.2.0.CR1.jar:4.2.0.CR1] > at org.atmosphere.cpr.AtmosphereResourceImpl.onBroadcast(AtmosphereResourceImpl.java:663) [atmosphere-runtime-0.8.4.jar:0.8.4] > at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:608) [atmosphere-runtime-0.8.4.jar:0.8.4] > at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:584) [atmosphere-runtime-0.8.4.jar:0.8.4] > at org.atmosphere.cpr.AsynchronousProcessor.timedout(AsynchronousProcessor.java:379) [atmosphere-runtime-0.8.4.jar:0.8.4] > at org.atmosphere.container.BlockingIOCometSupport.suspend(BlockingIOCometSupport.java:148) [atmosphere-runtime-0.8.4.jar:0.8.4] > at org.atmosphere.container.BlockingIOCometSupport.service(BlockingIOCometSupport.java:92) [atmosphere-runtime-0.8.4.jar:0.8.4] > at org.atmosphere.cpr.AtmosphereServlet.doCometSupport(AtmosphereServlet.java:1217) [atmosphere-runtime-0.8.4.jar:0.8.4] > at org.atmosphere.cpr.AtmosphereServlet.doPost(AtmosphereServlet.java:1176) [atmosphere-runtime-0.8.4.jar:0.8.4] > at org.atmosphere.cpr.AtmosphereServlet.doGet(AtmosphereServlet.java:1162) [atmosphere-runtime-0.8.4.jar:0.8.4] > at javax.servlet.http.HttpServlet.service(HttpServlet.java:734) [jboss-servlet-api_3.0_spec-1.0.0.Final.jar:1.0.0.Final] > at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.0.Final.jar:1.0.0.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.10.Final.jar:] > at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:62) [weld-core-1.1.5.AS71.Final.jar:2012-02-10 15:31] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.10.Final.jar:] > at org.jboss.solder.servlet.exception.CatchExceptionFilter.doFilter(CatchExceptionFilter.java:65) [solder-impl-3.1.0.Final.jar:3.1.0.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.10.Final.jar:] > at org.jboss.solder.servlet.event.ServletEventBridgeFilter.doFilter(ServletEventBridgeFilter.java:74) [solder-impl-3.1.0.Final.jar:3.1.0.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.10.Final.jar:] > at com.ocpsoft.pretty.PrettyFilter.doFilter(PrettyFilter.java:126) [prettyfaces-jsf2-3.3.2.jar:] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:397) [jbossweb-7.0.10.Final.jar:] > at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.1.0.Final.jar:7.1.0.Final] > at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:154) [jboss-as-web-7.1.0.Final.jar:7.1.0.Final] > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.10.Final.jar:] > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.10.Final.jar:] > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.10.Final.jar:] > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.10.Final.jar:] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_03] > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 14:44:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 21 Mar 2012 14:44:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11995) autocomplete only displaying select popup on minChars + 1 In-Reply-To: <1491446387.30098.1329818436170.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <737860080.23602.1332355487402.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-11995: ------------------------------- Labels: (was: waiting_on_user) Assignee: Pavol Pitonak QE, please confirm > autocomplete only displaying select popup on minChars + 1 > --------------------------------------------------------- > > Key: RF-11995 > URL: https://issues.jboss.org/browse/RF-11995 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.2.0.CR1 > Environment: Glassfish 3.1.1 / Mojarra 2.1.7 / Chrome browser > Reporter: Brendan Healey > Assignee: Pavol Pitonak > > I'm running the following test with org.richfaces.resourceOptimization.enabled > set to true. > After typing the minChars number of characters (2), I see an ajax request being > sent to the server and a response is successfully returned (observed using chrome > developer tools), but the popup selection list does not appear until minChars + 1 > (3) characters are entered. > Typing the third character causes a get request for combo_list_shadow.png to be > sent. > {code} > mode="cachedAjax" > var="var" > fetchValue="#{var.name}" > minChars="2" > autocompleteMethod="#{bean.doSearch}"> > > > > > {code} > w > I've only just migrated to rich:autocomplete from a self-developed custom component > so I don't know if this behavior existed in any richfaces version prior to 4.2.0.CR1. > I tried this on the showcase example here: > http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=autocomplete&skin=blueSky > (in the first autocomplete on the page) and could not reproduce the behavior. > I tried using mode="ajax" and mode="client" and could not get the popup to show in > either case, although I'd only ever want to use cachedAjax mode normally. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 14:46:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 21 Mar 2012 14:46:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12012) rich:contextMenu re-render problem In-Reply-To: <739413833.48708.1330440217630.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1734009017.23605.1332355607327.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-12012. -------------------------------- Assignee: Brian Leathem Resolution: Duplicate Issue > rich:contextMenu re-render problem > ---------------------------------- > > Key: RF-12012 > URL: https://issues.jboss.org/browse/RF-12012 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-menu > Affects Versions: 4.2.0.Final > Environment: Apache Tomcat/7.0.23 , Mojarra 2.1.5, RichFaces 4.2.0.Final > Reporter: Philip Maes > Assignee: Brian Leathem > Priority: Critical > Labels: waiting_on_user > > I have a extendedDataTable with a contextMenu attached to it. > When the selection changes on the extendedDataTable, a a4j:jsFunction is called. This jsFunction renders the contextMenu. > {quote} > onselectionchange="selChange('dtLivingCosts')" > ... > > ... > action="#{fhIndBean.selectionListener()}" > status="none" render="dtLivingCosts, contextMenu_dtLivingCosts"> > > > ... > attached="true" mode="ajax" > > ... > > {quote} > The problem is that as soon as I right-click, the contextMenu appears, the ajax request is sent and received, the view is partially updated (dtLivingCosts, contextMenu_dtLivingCosts) and then the contextMenu disappears and won't appear anymore. > I noticed that the javascript code generated by RichFaces for the contextMenu is not rerendered as you can see on these two screenshots. The first one shows the code when the page is generated for the first time. The second one, when a right-click has been done on a row in the extendedDataTable: > http://img848.imageshack.us/img848/8876/cm1j.png > http://img19.imageshack.us/img19/5170/cm2c.png > A possible workaround is to refresh only menuItems of the contextMenu (https://issues.jboss.org/browse/RF-11973). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 14:50:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 21 Mar 2012 14:50:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11902) [rich:autocomplete] add attribute queueId In-Reply-To: <1022848615.10266.1326969138391.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <278532798.23630.1332355847878.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-11902: ------------------------------- Fix Version/s: 4.3-Tracking > [rich:autocomplete] add attribute queueId > ----------------------------------------- > > Key: RF-11902 > URL: https://issues.jboss.org/browse/RF-11902 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 4.1.0.Final > Reporter: Rene O > Fix For: 4.3-Tracking > > > It would be nice if rich:autocomplete has an attribute queueId like a4j:ajax component. With this you will have more control over the ajax requests if ajax mode is enabled within autocomplete component. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 14:54:56 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 21 Mar 2012 14:54:56 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12011) Gradient configuration in ecss In-Reply-To: <1705971640.48518.1330438838009.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <801126500.23633.1332356096329.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12011: ------------------------------- Fix Version/s: 4-Tracking > Gradient configuration in ecss > ------------------------------ > > Key: RF-12011 > URL: https://issues.jboss.org/browse/RF-12011 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Dupont Dupont > Fix For: 4-Tracking > > > For the moment, gradients are : > # configured in resource-mappings.properties (i.e. https://github.com/richfaces/components/blob/develop/input/ui/src/main/resources/META-INF/richfaces/resource-mappings.properties) > {noformat} > org.richfaces.images\:autocompleteButtonGradient.png=org.richfaces.renderkit.html.images.AutocompleteGradient\ > {topColorParam=headerGradientColor ,bottomColorParam=headerBackgroundColor} > {noformat} > # and then used in ecss files (i.e. https://github.com/richfaces/components/blob/develop/input/ui/src/main/resources/META-INF/resources/org.richfaces/Autocomplete.ecss). > {noformat} > background-image: "url(#{resource['org.richfaces.images:autocompleteButtonGradient.png']})"; > {noformat} > A simpler solution could be allowing gradient configuration directly in the ecss file, e.g. > {noformat} > background-image:"url(#{resource['org.richfaces.dynamic:org.richfaces.renderkit.html.images.AutocompleteGradient?topColorParam=headerGradientColor&bottomColorParam=headerBackgroundColor']})"; > {noformat} > org.richfaces.dynamic being a special library name telling Richfaces to instantiate AutocompleteGradient and configure it on the fly. > This would enable to get rid of resource-mappings.properties for simple use cases. > N.B. : > * a control must be implemented to control which classes can be dynamically instantiated (i.e. only allow classes implementing Java2DUserResource). > * ecss configuration must allow us to configure the gradient (c.f. topColorParam and bottomColorParam variables in our sample). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 14:54:56 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 21 Mar 2012 14:54:56 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12016) Support for mechanism dynamically choosing skin from inside theme-template.xhtml In-Reply-To: <766495427.49785.1330451796452.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <270531002.23635.1332356096607.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12016: ------------------------------- Fix Version/s: 4-Tracking > Support for mechanism dynamically choosing skin from inside theme-template.xhtml > -------------------------------------------------------------------------------- > > Key: RF-12016 > URL: https://issues.jboss.org/browse/RF-12016 > Project: RichFaces > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: component-misc > Reporter: Dupont Dupont > Fix For: 4-Tracking > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 14:54:56 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 21 Mar 2012 14:54:56 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12017) Template handling In-Reply-To: <1706290983.49800.1330451917163.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <265257164.23637.1332356096714.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12017: ------------------------------- Fix Version/s: 4-Tracking > Template handling > ----------------- > > Key: RF-12017 > URL: https://issues.jboss.org/browse/RF-12017 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Dupont Dupont > Fix For: 4-Tracking > > > This functionnality will enable easily import a theme into it's own application. > It's quite related to template handling in JSF 2.2 [1]. > A template / theme will consist of : > * 1..n : the necessary xhtml file for the site layout. > * 0..n : images. > * 0..n : css files or ecss files. > * 0..n : js files. > * 0..1 : resource-mapping.property > * 1 : skin.properties > Requirements : > * easy installation > adding a template / theme must be just a matter of drag & drop (so all the resources must be a stand alone directory). > * easy modification > the developer must be able to customize the template / theme. > Implies : > ** template/theme resources must be expanded (not zipped or jarred) > ** hot reloading all common theme related resource modification must be hot reloaded. > Proposed organization : > * src/main/webapp/resources/templates/theme1/template.xhtml > * src/main/webapp/resources/templates/theme1/img > * src/main/webapp/resources/templates/theme1/css > * src/main/webapp/resources/templates/theme1/js > * src/main/webapp/resources/templates/theme1/theme1.skin.properties > * src/main/webapp/resources/templates/theme1/resource-mapping.properties > TBD : > * this JIRA must define common names for template parts (i.e. menu, title, content) in order to be able > to use different themes with the same jsf files. > Sample usage (jsf file using a template) : > {code:xml} > xmlns:h="http://java.sun.com/jsf/html" > xmlns:ui="http://java.sun.com/jsf/facelets" > xmlns:f="http://java.sun.com/jsf/core"> > Gallery > > My custom content > > > {code} > [1] > http://weblogs.java.net/blog/lamineba/archive/2011/11/12/multi-templating-system-jsf-22-what-does-it-mean-you > http://weblogs.java.net/blog/lamineba/archive/2011/10/03/conventional-ui-design-facelets-and-jsf-22 > https://svn.java.net/svn/jsf-extensions~svn/branches/SPEC_532_MODULAR_JSF > [2] Discussion on this topic : http://transcripts.jboss.org/channel/irc.freenode.org/%23richfaces/2012/%23richfaces.2012-02-28.log.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 14:54:56 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 21 Mar 2012 14:54:56 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12015) Support for EL-evaluated Less-to-CSS compiler In-Reply-To: <741300267.49776.1330451616677.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1648817491.23641.1332356096861.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12015: ------------------------------- Fix Version/s: 4-Tracking > Support for EL-evaluated Less-to-CSS compiler > --------------------------------------------- > > Key: RF-12015 > URL: https://issues.jboss.org/browse/RF-12015 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: core > Reporter: Dupont Dupont > Fix For: 4-Tracking > > > Suggested approach would be to parse El expression and afterwards execute less processor. > Server-side mechanism must be available for executing less. > Approach 1 : end-user chooses less or ecss but cannot mix the 2 syntax in the same file. > Approach 2 : allow end-user to use less syntax in ecss files > * modify current ecss execution (evaluate EL expression and don't parse CSS anymore) > * add a less compilator afterwards. > Less compilation at build time or runtime ? > For both of these 2 approaches, less compilation can be done built-time or execution time (need to investigate more to choose the right approach). > If build time, richfaces-resources-maven-pluginwould be a candidate to execute El and less compilation. > Full discussion on this topic here : http://transcripts.jboss.org/channel/irc.freenode.org/%23richfaces/2012/%23richfaces.2012-02-28.log.html > Some less plugins / engines : > * http://code.google.com/p/maven-less-plugin/ > * http://www.asual.com/lesscss/ > * https://github.com/achingbrain/less-maven-plugin > * http://code.google.com/p/maven-less-plugin/ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 14:54:56 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 21 Mar 2012 14:54:56 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12014) Support for loading skin.properties and resource-mapping.properties from webapp/resources In-Reply-To: <91341365.49772.1330451616528.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <913146809.23639.1332356096792.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12014: ------------------------------- Fix Version/s: 4-Tracking > Support for loading skin.properties and resource-mapping.properties from webapp/resources > ----------------------------------------------------------------------------------------- > > Key: RF-12014 > URL: https://issues.jboss.org/browse/RF-12014 > Project: RichFaces > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: core > Reporter: Dupont Dupont > Fix For: 4-Tracking > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 14:54:56 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 21 Mar 2012 14:54:56 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12024) rich:dataGrid component and a4j:status don't cooperate together In-Reply-To: <953422806.72367.1331080056746.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1578231264.23643.1332356096933.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12024: ------------------------------- Fix Version/s: 4.Future Component/s: component-a4j-core > rich:dataGrid component and a4j:status don't cooperate together > --------------------------------------------------------------- > > Key: RF-12024 > URL: https://issues.jboss.org/browse/RF-12024 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.1.0.Final, 4.2.0.Final > Environment: JDK1.6, > JBoss 6.0.Final, > richfaces 4.1.0.Final/4.2.0.Final > IE 9 > Reporter: Artur Mioduszewski > Fix For: 4.Future > > > rich:dataGrid component and a4j:status don't cooperate together. > 1. PROBLEM: After clicking a4j:commandLink inside rich:dataGrid, rich:dataGrid behaves properly, but a4j:status component is not able to hide. > 2. When I remove a4j:status component, everything is OK (but rerendering rich:dataGrid is taking a while, so I would like to get a4j:status component functionality on page) > 3. a4j:commandButton present at that page (not shown in below code extract) cooperate to a4j:status correctly > ------------- > (I just have noticed: a4j:status component also does not cooperate correctly to richfaces tabs: durring first tab switching, a4j:status component is not able to hide > After refresh: tabs and a4j:status component start to behave correctly ). > {code:title="XHTML FILE CODE EXTRACT"} > > columns="7" elements="168" styleClass="noPaddings"> > > > > > > > > > > > > > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 14:56:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 21 Mar 2012 14:56:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12025) [rich:tabPanel] Switching tabs doesn't work correctly In-Reply-To: <564356619.72400.1331081680333.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <24609065.23645.1332356207304.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12025: ------------------------------- Fix Version/s: 4.Future > [rich:tabPanel] Switching tabs doesn't work correctly > ----------------------------------------------------- > > Key: RF-12025 > URL: https://issues.jboss.org/browse/RF-12025 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.1.0.Final, 4.2.0.Final > Environment: JDK1.6, > JBoss 6.0.Final, > richfaces 4.1.0.Final/4.2.0.Final > IE 9 > Reporter: Artur Mioduszewski > Fix For: 4.Future > > > Every tab switching caused more (perhaps 2 times more) calling of logger.debug("----preRenderHomeView"); > {code:title=XHTML FILE CODE EXTRACT} > > > > > > > > > > > > > > {code} > {code:title="HomeAction"} > public void preRenderHomeView() { > logger.debug("----preRenderHomeView"); > } > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 14:58:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 21 Mar 2012 14:58:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12028) a4j:outputPanel - Error message enhancement In-Reply-To: <1368665910.75459.1331155416313.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1240935616.23649.1332356327474.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678437#comment-12678437 ] Brian Leathem commented on RF-12028: ------------------------------------ Can you confirm that you get such a detailed message with a mojarra component, when you reference an attribute that does not exist? (this information will tell us if it's an upstream/mojarra bug, or a RichFaces bug) > a4j:outputPanel - Error message enhancement > ------------------------------------------- > > Key: RF-12028 > URL: https://issues.jboss.org/browse/RF-12028 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Environment: JSF / Mojarra 2.1.6 - cssparser-0.9.6 - guava-11.0.1 - hibernate-validator-4.2.0.Final - springframework 3.0.6.RELEASE - richfaces--4.2.0.Final - sac-1.3 - FireFox 10 - WAS 8.0.0.1 / Windows 7 > Reporter: Jean ANDRE > Labels: waiting_on_user > > When we set an non existing attribute on a4j:outputPanel, for eg. "class" because we have converted a div to a a4j:outputPanel, the error message displayed at the user interface does not inform the developer about the faulty component. The message we got is only : > > Error 500: javax.servlet.ServletException: Setter not found for property class > This error message is not very helpful to debug.... ;) > {code} > layout="block" > class="dark-box" > rendered="#{productBean.expanded eq true}"> > {code} > We should have, as usual, the line of the XHTML file or the component name, the line number, well something more accurate that really help to go faster. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 15:02:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 21 Mar 2012 15:02:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12030) rich:dataScroller doesn't work if a rich:message exists inside of a collapsed rich:collapsiblePanel with switchType='ajax' In-Reply-To: <474795285.76394.1331197237559.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1545931930.23656.1332356567580.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12030: ------------------------------- Fix Version/s: 4.3.0.Milestone1 > rich:dataScroller doesn't work if a rich:message exists inside of a collapsed rich:collapsiblePanel with switchType='ajax' > -------------------------------------------------------------------------------------------------------------------------- > > Key: RF-12030 > URL: https://issues.jboss.org/browse/RF-12030 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.2.0.Final > Environment: tomcat 7, richfaces-4.2.0.Final, myfaces-2.1.6 > Reporter: Rene O > Fix For: 4.3.0.Milestone1 > > > rich:dataScroller doesn't work if a rich:message exists inside of a collapsed rich:collapsiblePanel with switchType='ajax' > Steps to reproduce this issue: > 1. use dataScroller to switch table-pages. you can see, that this works. > 2. collaps collapsiblePanel > 3. if collapsiblePanel is collapsed, the dataScroller doesn't react anymore. > 4. if you use switchType='client' everything works correct > {code:title=examplepage.xhtml} > > xmlns:h="http://java.sun.com/jsf/html" > xmlns:f="http://java.sun.com/jsf/core" > xmlns:ui="http://java.sun.com/jsf/facelets" > xmlns:a4j="http://richfaces.org/a4j" > xmlns:rich="http://richfaces.org/rich" > > > > JSF Test > > > > > > > > if rich:message doesn't exists, everything works... > > > > var="item" value="#{model.tableList}" > rows="5" style="width:350px;"> > > > > > > ColA > > #{item.itemA} > > > > > > > > > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 15:04:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 21 Mar 2012 15:04:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12031) rich:validator does not work after re render (ajax) In-Reply-To: <245851677.76479.1331198676205.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <468260014.23659.1332356687429.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem reassigned RF-12031: ---------------------------------- Assignee: Luk?? Fry? > rich:validator does not work after re render (ajax) > --------------------------------------------------- > > Key: RF-12031 > URL: https://issues.jboss.org/browse/RF-12031 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.2.0.Final > Reporter: Andries Ehlers > Assignee: Luk?? Fry? > > When you have a simple inputText component with rich:validator inside, validation works perfectly when you move focus away from the component - validation messages display, e.g: > {code:xml|borderStyle=solid} > > > > > {code} > If the above code resides in a panel, which is conditionally rendered, then ceases to function when you re-render the panel with ajax, eg: > {code:xml|borderStyle=solid} > > > > > > >
    > > > > >     >     > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 15:06:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 21 Mar 2012 15:06:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12032) rich:calendar : Ajax request - Error message enhancement - sql.Date In-Reply-To: <1406650855.77949.1331220940774.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1567301378.23661.1332356807354.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678439#comment-12678439 ] Brian Leathem commented on RF-12032: ------------------------------------ Was there no message logged in your server log? > rich:calendar : Ajax request - Error message enhancement - sql.Date > ------------------------------------------------------------------- > > Key: RF-12032 > URL: https://issues.jboss.org/browse/RF-12032 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Environment: cssparser-0.9.6 - guava-11.0.1 - hibernate-validator-4.2.0.Final - JSF/Mojarra 2.1.6 - springframework-3.0.6.RELEASE - richfaces-4.2.0.Final - sac-1.3.jar - Windows 7, WAS 8.0.0.1, Servlet 2.5 - Java 6. > Reporter: Jean ANDRE > Labels: waiting_on_user > Attachments: rich_calendar_errorMsg_Enhancement.png > > > When a backing-bean have a type of sql.Date which is mapped to a rich:calendar, there is an conversion error due to the rich:calendar component uses util.Date by default. Unfortunately, we do not see any error message at the screen when an ajax request is sent and returned back to us. > What we got, and thanks to Firebug, is the text below as an answer from our Ajax request POST. Nothing is rendered at the screen and the method of the backing bean is not called. > {code} > > class javax.faces.component.UpdateModelException > {code} > Our code looks like this (we remove unecessary field and decoration): > {code} > > > > > value="#{msg['common.command.add.phone']}" > action="#{createClientController.doAddPhone}"> > > > > > > > value="#{phoneBean.effectiveDate}" > popup="true" > showApplyButton="false" > enableManualInput="true" > datePattern="#{msg['client.date.format']}" > inputSize="12" > styleClass="calendar"> > > > > > > > > {code} > Is is possible to have a message returned back to the UI??? or is there a way to handle this error properly? > Other information > ================= > The form is inside a dynamic tab - Fragment are also include dynamically - we use c:if et subView as shown below: > {code} > > > > > > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 15:06:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 21 Mar 2012 15:06:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12033) ExtendedDataTable doesn't show up in tabpanel with switchType="client" In-Reply-To: <1476360638.82467.1331324676272.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1057884691.23667.1332356807538.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12033: ------------------------------- Description: ExtendedDataTable doesn't show up in tabpanel with switchType="client" (was: testcase attached 1. Open test1.xhtml 2. Switch to Tab Two Expected Result: ExtendedDataTable shows up Actual Result: Grey bar shows up Workaround is to set switchType to "ajax" instead of "client" ) Steps to Reproduce: Using the attached testcase 1. Open test1.xhtml 2. Switch to Tab Two Expected Result: ExtendedDataTable shows up Actual Result: Grey bar shows up Workaround Description: Workaround is to set switchType to "ajax" instead of "client" > ExtendedDataTable doesn't show up in tabpanel with switchType="client" > ---------------------------------------------------------------------- > > Key: RF-12033 > URL: https://issues.jboss.org/browse/RF-12033 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.2.0.Final > Environment: FireFox 10.0.2 (works in IE7) > GlassFish 3.1 > Reporter: Josh Hill > Attachments: richfaces-test.zip > > > ExtendedDataTable doesn't show up in tabpanel with switchType="client" -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 15:12:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 21 Mar 2012 15:12:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12033) ExtendedDataTable doesn't show up in tabpanel with switchType="client" In-Reply-To: <1476360638.82467.1331324676272.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1986324783.23669.1332357167349.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12033: ------------------------------- Fix Version/s: 4.3-Tracking Description: ExtendedDataTable doesn't show up in tabpanel with switchType="client" Facelet file from the attached testcase: {code} Test One

    Extended datatable inside tabpanel with switchType "client"

    Tab One Tab One Tab Two Column 1 #{color}     {code} was:ExtendedDataTable doesn't show up in tabpanel with switchType="client" Labels: lazy-loaded (was: ) > ExtendedDataTable doesn't show up in tabpanel with switchType="client" > ---------------------------------------------------------------------- > > Key: RF-12033 > URL: https://issues.jboss.org/browse/RF-12033 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.2.0.Final > Environment: FireFox 10.0.2 (works in IE7) > GlassFish 3.1 > Reporter: Josh Hill > Labels: lazy-loaded > Fix For: 4.3-Tracking > > Attachments: richfaces-test.zip > > > ExtendedDataTable doesn't show up in tabpanel with switchType="client" > Facelet file from the attached testcase: > {code} > > > xmlns:h="http://java.sun.com/jsf/html" > xmlns:rich="http://richfaces.org/rich" > xmlns:f="http://java.sun.com/jsf/core"> > > Test One > > >

    Extended datatable inside tabpanel with switchType "client"

    > > > > > Tab One > > Tab One > > > > Tab Two > > > > > Column 1 > > #{color} > > > > > >     > > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 15:12:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 21 Mar 2012 15:12:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12033) ExtendedDataTable doesn't show up in tabpanel with switchType="client" In-Reply-To: <1476360638.82467.1331324676272.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1906659994.23671.1332357167452.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12033: ------------------------------- Steps to Reproduce: Using the attached testcase # Open test1.xhtml # Switch to Tab Two Expected Result: ExtendedDataTable shows up Actual Result: Grey bar shows up was: Using the attached testcase 1. Open test1.xhtml 2. Switch to Tab Two Expected Result: ExtendedDataTable shows up Actual Result: Grey bar shows up > ExtendedDataTable doesn't show up in tabpanel with switchType="client" > ---------------------------------------------------------------------- > > Key: RF-12033 > URL: https://issues.jboss.org/browse/RF-12033 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.2.0.Final > Environment: FireFox 10.0.2 (works in IE7) > GlassFish 3.1 > Reporter: Josh Hill > Labels: lazy-loaded > Fix For: 4.3-Tracking > > Attachments: richfaces-test.zip > > > ExtendedDataTable doesn't show up in tabpanel with switchType="client" > Facelet file from the attached testcase: > {code} > > > xmlns:h="http://java.sun.com/jsf/html" > xmlns:rich="http://richfaces.org/rich" > xmlns:f="http://java.sun.com/jsf/core"> > > Test One > > >

    Extended datatable inside tabpanel with switchType "client"

    > > > > > Tab One > > Tab One > > > > Tab Two > > > > > Column 1 > > #{color} > > > > > >     > > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 15:14:48 2012 From: jira-events at lists.jboss.org (Jean ANDRE (JIRA)) Date: Wed, 21 Mar 2012 15:14:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12038) IE8 - Object does not support this property or method - a4j:jsFunction In-Reply-To: <1674243330.3069.1331568048477.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <738596240.23674.1332357288311.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678440#comment-12678440 ] Jean ANDRE commented on RF-12038: --------------------------------- There is another issue with with a same message but we cannot pinpoint the exact reason of that. Here is the workbench (setuped) and the steps to reproduce the bug. 1) Install the workbench and read the readme.txt file for additional information 2) Do not hesitate to request any information about it 3) Once the page appears (http://localhost:9080/NestedWeb/pages/index.jsf) or (http://localhost:9080/NestedWeb/index.html 4) Select the tab "Items management" 5) Enter a number and press "New List" button 6) Once a new dynamic tab is created with a list, close the tab by clicking on X image IE reports the following error: Line: 5 Erreur : Cet objet ne g?re pas cette propri?t? ou cette m?thode >Object does not support this property or method Another way to reproduce the case is: 7) From the step 6, click on any item from the list - Open link 8) From the available tasks link, click on task, a new task tab appears 9) Close the tab by clicking on X image IE reports the following error: Line: 8 Erreur : Cet objet ne g?re pas cette propri?t? ou cette m?thode >From the workbench, we removed any id="xzy" name="xyz", then the bug should not come from this case but from another reason. Under FireFox, everything works perfectly. Similar error on the Web of the past... - http://forum.jquery.com/topic/object-doesn-t-support-this-property-or-method-from-jquery-1-4-1-in-ie7-only - > IE8 - Object does not support this property or method - a4j:jsFunction > ---------------------------------------------------------------------- > > Key: RF-12038 > URL: https://issues.jboss.org/browse/RF-12038 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.2.0.Final > Environment: cssparser-0.9.6- guava-11.0.1 - hibernate-validator-4.2.0.Final - JSF/Mojarra 2.1.6 - springframework-3.0.6.RELEASE - sac-1.3 - Windows 7 - IE 8.0.1.7601.17514 > Reporter: Jean ANDRE > Fix For: 4.2.1.CR1 > > Attachments: index.xhtml, NestedWeb.zip > > > Under IE8, IE reports the following error message due to a javascript error. However, the page are well displayed and the application is running ok. > Object doesn't support this property or method line 177 caracter 1 > Object doesn't support this property or method line 177 caracter 99 > Under IE Debugger, the line is: > {code} > closeTab=function(tabId){RichFaces.ajax("closeTab",null,{"incId":"1","parameters":{"tabId":tabId} } )};< > The caracter 99, is..............................................................................| (here) > {code} > This is a code generated by a4j:jsFunction from the XHTML > {code} > > > > > > > {code} > The rendered code is : > {code} > > > > {code} > See also this link as we got almost a similar: https://bugzilla.redhat.com/show_bug.cgi?id=601360. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 15:14:48 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 21 Mar 2012 15:14:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12034) Accepting multiple date format in rich calendar In-Reply-To: <2086963364.234.1331444747307.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1758007078.23676.1332357288382.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12034: ------------------------------- Fix Version/s: 4-Tracking > Accepting multiple date format in rich calendar > ----------------------------------------------- > > Key: RF-12034 > URL: https://issues.jboss.org/browse/RF-12034 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-input > Reporter: Sunil Chauraha > Labels: richfaces > Fix For: 4-Tracking > > > Sometimes it is required to deal with multiple date formats in rich:calendar in both calendar selection and manual input. > But here we can define only one date pattern. > Could it be possible to accept for this component to accept multiple date formats, based on locale or other requirement. > I could write a workaround using javascript but this would be great if we can do it by defining just the date patterns inside the component. > My javascript solution is here : https://community.jboss.org/wiki/AcceptingMultipleDateFormatsInRichcalendar -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 15:14:48 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 21 Mar 2012 15:14:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12035) Switchable panels do not work after rerendering whole page In-Reply-To: <1502418805.1981.1331557787347.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <343171576.23678.1332357288495.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12035: ------------------------------- Fix Version/s: 4.3-Tracking > Switchable panels do not work after rerendering whole page > ---------------------------------------------------------- > > Key: RF-12035 > URL: https://issues.jboss.org/browse/RF-12035 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.2.0.Final > Environment: RichFaces 4.2.1-SNAPSHOT > Metamer 4.2.1-SNAPSHOT > Mojarra 2.1.7-jbossorg-1 > JBoss AS 7.1.1.Final > OpenJDK Runtime Environment 1.6.0_24-b24 @ Linux > Chrome 17.0.963.79 @ Linux i686 > Reporter: Pavol Pitonak > Fix For: 4.3-Tracking > > > # deploy Metamer and open http://localhost:8080/metamer/faces/components/richAccordion/simple.xhtml > # click on panel 3 > # verify that panel 3 is displayed > # click rerender all button (4th button in page header) > # verify that panel 3 is displayed > # click on panel 2 > # click on panel 2 > result: > * accordion is not switched to panel 2 on first click, second click is necessary > * there is the same problem with rich:collapsiblePanel -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 15:16:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 21 Mar 2012 15:16:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12036) showcase - rich:progressBar - client side mode of progressBar halts another progress bar in AJAX mode In-Reply-To: <653082305.2290.1331562647939.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <130304641.23680.1332357407747.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12036: ------------------------------- Fix Version/s: 4-Tracking > showcase - rich:progressBar - client side mode of progressBar halts another progress bar in AJAX mode > ----------------------------------------------------------------------------------------------------- > > Key: RF-12036 > URL: https://issues.jboss.org/browse/RF-12036 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output, showcase > Affects Versions: 4.2.0.Final > Environment: browsers: Firefox 10, Chrome 17 > Reporter: Juraj Huska > Fix For: 4-Tracking > > > When you have open both samples for the rich:progressBar at the same browser(in separated cards), and run Ajax mode one and during of execution of this one also the client mode one, then the Ajax one is halted. > The server updates are still coming for that Ajax one, however the visual state is not updated. It is not restored even when the second one is completed. > This is noticeable on showcase since RF 4.0.0.Final, and reproducible on GAE or OpenShift accounts. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 15:18:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 21 Mar 2012 15:18:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12037) Fileupload:onbegin, oncomplete and onbeforedomupdate does not work In-Reply-To: <59538813.2564.1331564567977.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <196105898.23683.1332357527816.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12037: ------------------------------- Description: Fileupload:onbegin, oncomplete and onbeforedomupdate does not display the alerts specified via the metamer testing application. (was: # Deploy metamer # open http://localhost:8080/metamer/faces/components/richFileUpload/simple.xhtml # Attribute onbegin=alert('1') # Attribute onbeforedomupdate=alert('2') # Attribute oncomplete=alert('3') # Upload file # 3 alerts should show ) Steps to Reproduce: # Deploy metamer # open http://localhost:8080/metamer/faces/components/richFileUpload/simple.xhtml # Attribute onbegin=alert('1') # Attribute onbeforedomupdate=alert('2') # Attribute oncomplete=alert('3') # Upload file # 3 alerts should show > Fileupload:onbegin, oncomplete and onbeforedomupdate does not work > ------------------------------------------------------------------ > > Key: RF-12037 > URL: https://issues.jboss.org/browse/RF-12037 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.2.0.Final > Environment: RichFaces 4.2.1-SNAPSHOT > Metamer 4.2.1-SNAPSHOT > Mojarra 2.1.5-SNAPSHOT > JBoss AS 7.1.0.Final > OpenJDK Runtime Environment 1.6.0_24-b24 @ Linux > Firefox 10.0.1 @ Linux x86_64 > Chrome 17.0.963.56 @ Linux i686 > Reporter: Ji?? ?tefek > Fix For: 4.3-Tracking > > > Fileupload:onbegin, oncomplete and onbeforedomupdate does not display the alerts specified via the metamer testing application. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 15:18:48 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 21 Mar 2012 15:18:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12037) Fileupload:onbegin, oncomplete and onbeforedomupdate does not work In-Reply-To: <59538813.2564.1331564567977.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <2059092147.23686.1332357528319.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12037: ------------------------------- Fix Version/s: 4.3-Tracking > Fileupload:onbegin, oncomplete and onbeforedomupdate does not work > ------------------------------------------------------------------ > > Key: RF-12037 > URL: https://issues.jboss.org/browse/RF-12037 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.2.0.Final > Environment: RichFaces 4.2.1-SNAPSHOT > Metamer 4.2.1-SNAPSHOT > Mojarra 2.1.5-SNAPSHOT > JBoss AS 7.1.0.Final > OpenJDK Runtime Environment 1.6.0_24-b24 @ Linux > Firefox 10.0.1 @ Linux x86_64 > Chrome 17.0.963.56 @ Linux i686 > Reporter: Ji?? ?tefek > Fix For: 4.3-Tracking > > > Fileupload:onbegin, oncomplete and onbeforedomupdate does not display the alerts specified via the metamer testing application. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 15:20:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 21 Mar 2012 15:20:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12039) fileupload: attribute data does not work In-Reply-To: <1594423263.5104.1331625708133.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1889836991.23688.1332357647303.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12039: ------------------------------- Description: The value assigned to the data attribute of the fileupload comopnent is not available via the event object in the oncomplete listener (was: # Deploy metamer # open http://localhost:8080/metamer/faces/components/richFileUpload/simple.xhtml # Set attribute data = 'RichFaces 4' # Set attribute onuploadcomplete = alert(event.data) # Upload file # Alert with "RichFaces 4" should show) Steps to Reproduce: # Deploy metamer # open http://localhost:8080/metamer/faces/components/richFileUpload/simple.xhtml # Set attribute data = 'RichFaces 4' # Set attribute onuploadcomplete = alert(event.data) # Upload file # Alert with "RichFaces 4" should show > fileupload: attribute data does not work > ---------------------------------------- > > Key: RF-12039 > URL: https://issues.jboss.org/browse/RF-12039 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.2.0.Final > Environment: RichFaces 4.2.1-SNAPSHOT > Metamer 4.2.1-SNAPSHOT > Mojarra 2.1.5-SNAPSHOT > JBoss Web 7.0.10.Final > OpenJDK Runtime Environment 1.6.0_24-b24 @ Linux > Firefox 10.0.1 @ Linux x86_64 > Chrome 17.0.963.56 @ Linux i686 > Reporter: Ji?? ?tefek > > The value assigned to the data attribute of the fileupload comopnent is not available via the event object in the oncomplete listener -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 15:22:48 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 21 Mar 2012 15:22:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12039) fileupload: attribute data does not work In-Reply-To: <1594423263.5104.1331625708133.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1715661211.23690.1332357768224.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12039: ------------------------------- Fix Version/s: 4.3-Tracking > fileupload: attribute data does not work > ---------------------------------------- > > Key: RF-12039 > URL: https://issues.jboss.org/browse/RF-12039 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.2.0.Final > Environment: RichFaces 4.2.1-SNAPSHOT > Metamer 4.2.1-SNAPSHOT > Mojarra 2.1.5-SNAPSHOT > JBoss Web 7.0.10.Final > OpenJDK Runtime Environment 1.6.0_24-b24 @ Linux > Firefox 10.0.1 @ Linux x86_64 > Chrome 17.0.963.56 @ Linux i686 > Reporter: Ji?? ?tefek > Fix For: 4.3-Tracking > > > The value assigned to the data attribute of the fileupload comopnent is not available via the event object in the oncomplete listener -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 15:54:48 2012 From: jira-events at lists.jboss.org (Jean ANDRE (JIRA)) Date: Wed, 21 Mar 2012 15:54:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12038) IE8 - Object does not support this property or method - a4j:jsFunction In-Reply-To: <1674243330.3069.1331568048477.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <453934832.23720.1332359688843.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678446#comment-12678446 ] Jean ANDRE commented on RF-12038: --------------------------------- >From the workbench, page index.xhtml, you can remove the form related to the menu and also the form related to the quick search. it does not impact the issue. From the template page, basePage.xhtml, you can also remove the tag related to the bug JAVASERVERFACES-2016/RF-11694, it does not impact the issue. All of that, in order to reduce the scope. After removing this code, it seems that the javacript function to close the tab is involved. See index.xhtml page. IE reports something wrong with event. By removing this piece of code you get something similar to RF-12060 {code}     {code} If you leave the code of the workbench as is, removing only the event.stopPropagation(), you get the following error message. Message?: Objet requis Ligne?: 1 Caract?re?: 22732 Code?: 0 URI?: http://localhost:9080/NestedWeb/javax.faces.resource/jsf.js.jsf?ln=javax.faces > IE8 - Object does not support this property or method - a4j:jsFunction > ---------------------------------------------------------------------- > > Key: RF-12038 > URL: https://issues.jboss.org/browse/RF-12038 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.2.0.Final > Environment: cssparser-0.9.6- guava-11.0.1 - hibernate-validator-4.2.0.Final - JSF/Mojarra 2.1.6 - springframework-3.0.6.RELEASE - sac-1.3 - Windows 7 - IE 8.0.1.7601.17514 > Reporter: Jean ANDRE > Fix For: 4.2.1.CR1 > > Attachments: index.xhtml, NestedWeb.zip, NestedWeb_RF-12038.zip > > > Under IE8, IE reports the following error message due to a javascript error. However, the page are well displayed and the application is running ok. > Object doesn't support this property or method line 177 caracter 1 > Object doesn't support this property or method line 177 caracter 99 > Under IE Debugger, the line is: > {code} > closeTab=function(tabId){RichFaces.ajax("closeTab",null,{"incId":"1","parameters":{"tabId":tabId} } )};< > The caracter 99, is..............................................................................| (here) > {code} > This is a code generated by a4j:jsFunction from the XHTML > {code} > > > > > > > {code} > The rendered code is : > {code} > > > > {code} > See also this link as we got almost a similar: https://bugzilla.redhat.com/show_bug.cgi?id=601360. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 16:02:48 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 21 Mar 2012 16:02:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12040) Multi-form document - command button (submit) does not work after rendering In-Reply-To: <375257168.7025.1331658768095.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1260736197.23735.1332360168915.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12040: ------------------------------- Description: We have one page that contains two forms. The first form contain a menus bar (ajax switchType) while the second contains a tabPanel (also in ajax switchType). When a user select a menu, we select the corresponding tab that contains a submit button. Once the tab is selected, the submit button does not work. We have to click twice for submitting. # If we move the menu bar inside the second forms, it is working. # If we set the menu bar in client switchType, selecting the menu doesn't do anything. # If we set the menu bar in server switchType it's working. As the rendering is well executed, the submit button should works but is not whatever we set as render="@all, or any valid id". We have prepared a small application that demonstrates the case. This is a simple but realistic application. Edit the index.xhtml to play with the menu. Let us know if we doing something wrong. Note also that the JIRA JAVASERVERFACES-2016 was reopened :[JIRA] Reopened: (JAVASERVERFACES-2016) Resources not loaded when using a dynamic ui:inlclude and rendered via ajax [ http://java.net/jira/browse/JAVASERVERFACES-2016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] {code:title=Relevant Facelet markup}

    #1

    {code} was: We have one page that contains two forms. The first form contain a menus bar (ajax switchType) while the second contains a tabPanel (also in ajax switchType). When a user select a menu, we select the corresponding tab that contains a submit button. Once the tab is selected, the submit button does not work. We have to click twice for submitting. 1) If we move the menu bar inside the second forms, it is working. 2) If we set the menu bar in client switchType, selecting the menu doesn't do anything. 3) If we set the menu bar in server switchType it's working. As the rendering is well executed, the submit button should works but is not whatever we set as render="@all, or any valid id". We have prepared a small application that demonstrates the case. This is a simple but realistic application. Edit the index.xhtml to play with the menu. Let us know if we doing something wrong. Note also that the JIRA JAVASERVERFACES-2016 was reopened :[JIRA] Reopened: (JAVASERVERFACES-2016) Resources not loaded when using a dynamic ui:inlclude and rendered via ajax [ http://java.net/jira/browse/JAVASERVERFACES-2016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steps to Reproduce: # Setup the application, read the readme.txt file # Once the index page is displayed, the tab "Items Management" is selected by default # Click one the first static tab "Tab S-#1" # From the menu, select the menu "items management" # Then click on button "New List" 6) A list of item should be displayed But at the step 5, you have to click twice the button or to do F5 that refresh the whole page, it is like restarting the appl. from the beginning. was: 1) Setup the application, read the readme.txt file 2) Once the index page is displayed, the tab "Items Management" is selected by default 3) Click one the first static tab "Tab S-#1" 4) From the menu, select the menu "items management" 5) Then click on button "New List" 6) A list of item should be displayed But at the step 5, you have to click twice the button or to do F5 that refresh the whole page, it is like restarting the appl. from the beginning. In the referenced form, I see the rich:menuItem _#item-management_ from h:form _#MenuForm_ has a render target of _desktopTabs_, with is a rich:tabPanel in the h:form _#desktopForm_. You are attempting to re-render a component in an adjacent form. I believe you are experiencing the behaviour described in this spec issue: http://java.net/jira/browse/JAVASERVERFACES_SPEC_PUBLIC-790 As a workaround, I recommend using a single form, and use a4j:region panels automatically where you would have used _ at form_ otherwise. If you agree this is the problem you are experiencing, I will close this issue as an upstream problem. > Multi-form document - command button (submit) does not work after rendering > --------------------------------------------------------------------------- > > Key: RF-12040 > URL: https://issues.jboss.org/browse/RF-12040 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Environment: cssparser-0.9.6 - guava-11.0.1 - hibernate-validator-4.2.0.Final - JSF/Mojarra 2.1.6 - springframework-3.0.6.RELEASE - sac-1.3 - Windows 7 - FireFox 10 - RichFaces 4.2 Final > Reporter: Jean ANDRE > Labels: waiting_on_user > Attachments: NestedWebWithMenu.zip > > > We have one page that contains two forms. The first form contain a menus bar (ajax switchType) while the second contains a tabPanel (also in ajax switchType). When a user select a menu, we select the corresponding tab that contains a submit button. Once the tab is selected, the submit button does not work. We have to click twice for submitting. > # If we move the menu bar inside the second forms, it is working. > # If we set the menu bar in client switchType, selecting the menu doesn't do anything. > # If we set the menu bar in server switchType it's working. > As the rendering is well executed, the submit button should works but is not whatever we set as render="@all, or any valid id". > We have prepared a small application that demonstrates the case. This is a simple but realistic application. Edit the index.xhtml to play with the menu. Let us know if we doing something wrong. > Note also that the JIRA JAVASERVERFACES-2016 was reopened :[JIRA] Reopened: (JAVASERVERFACES-2016) Resources not loaded when using a dynamic ui:inlclude and rendered via ajax > [ http://java.net/jira/browse/JAVASERVERFACES-2016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] > {code:title=Relevant Facelet markup} > > xmlns:ui="http://java.sun.com/jsf/facelets" > xmlns:h="http://java.sun.com/jsf/html" > xmlns:f="http://java.sun.com/jsf/core" > xmlns:rich="http://richfaces.org/rich" > xmlns:a4j="http://richfaces.org/a4j" > xmlns:c="http://java.sun.com/jsp/jstl/core" > template="/templates/basePage.xhtml"> > > > > > > > > > > > > > > > > > > > > > > > label="#{msg['menu.item.one.items.management']}" > action="#{desktopController.doActivateTabItems}" > render="desktopTabs" /> > > > > >
    >
    > > > > > > > > switchType="ajax" > headerPosition="top" > activeItem="#{desktopController.activeTab}" > itemChangeListener="#{desktopController.doItemChangeListener}" > immediate="true"> > > > > > #1 > > > > > > > > > > value="#{msg[desktopController.togglePanelLabel]}" > actionListener="#{desktopController.doToggleTabContent}" > render="toggleTabContent"> > >
    >
    > > > > > > > > > > > > >     >     > > > > > > > > > styleClass="closeButton" > onclick="closeTab('#{tab.id}');event.stopPropagation();" /> > > > > > > > > > >     >     > > > > > > > > > > > > >     > > > >     > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 16:02:50 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 21 Mar 2012 16:02:50 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12042) Metamer: rich:contextMenu doesn't disappear after clicking out of the menu in IE9 and Google Chrome In-Reply-To: <1422678186.9420.1331737667612.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1449217431.23737.1332360170147.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12042: ------------------------------- Fix Version/s: 4.2.1.CR1 Assignee: Brian Leathem > Metamer: rich:contextMenu doesn't disappear after clicking out of the menu in IE9 and Google Chrome > --------------------------------------------------------------------------------------------------- > > Key: RF-12042 > URL: https://issues.jboss.org/browse/RF-12042 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-menu > Affects Versions: 4.2.0.Final > Environment: ?RichFaces 4.2.1-SNAPSHOT > ?Metamer 4.2.1-SNAPSHOT > ?Mojarra 2.1.5-SNAPSHOT > ?JBoss AS 7.1.0.Final > ?Java(TM) SE Runtime Environment 1.6.0_31-b04 @ Linux > ?Internet Explorer 9.0 @ Win32 > RichFaces 4.2.1-SNAPSHOT > Metamer 4.2.1-SNAPSHOT > Mojarra 2.1.5-SNAPSHOT > JBoss AS 7.1.0.Final > Java(TM) SE Runtime Environment 1.6.0_31-b04 @ Linux > Chrome 17.0.963.78 @ Linux i686 > Reporter: Jan Papousek > Assignee: Brian Leathem > Labels: Chrome, IE9 > Fix For: 4.2.1.CR1 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 16:04:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 21 Mar 2012 16:04:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12043) Metamer: rich:contextMenu isn't rendered correctly in IE 9 compatibility mode In-Reply-To: <714594071.9445.1331737907625.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1810685755.23739.1332360287750.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12043: ------------------------------- Fix Version/s: 4.2.1.CR1 Assignee: Brian Leathem > Metamer: rich:contextMenu isn't rendered correctly in IE 9 compatibility mode > ----------------------------------------------------------------------------- > > Key: RF-12043 > URL: https://issues.jboss.org/browse/RF-12043 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-menu > Affects Versions: 4.2.0.Final > Environment: RichFaces 4.2.1-SNAPSHOT > Metamer 4.2.1-SNAPSHOT > Mojarra 2.1.5-SNAPSHOT > JBoss AS 7.1.0.Final > Java(TM) SE Runtime Environment 1.6.0_31-b04 @ Linux > Internet Explorer 7.0 @ Win32 (this is IE 9 Compatibility Mode) > Reporter: Jan Papousek > Assignee: Brian Leathem > Labels: IE9 > Fix For: 4.2.1.CR1 > > Attachments: metamer-ie-9-rich_contextMenu.png > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 16:04:49 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 21 Mar 2012 16:04:49 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12044) Metamer: @preventDefault attribute of rich:hotKey component doesn't work in IE 9 and Google Chrome In-Reply-To: <283065864.9549.1331739467659.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <389248162.23746.1332360289561.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12044: ------------------------------- Fix Version/s: 4.2.1.CR1 Assignee: Luk?? Fry? > Metamer: @preventDefault attribute of rich:hotKey component doesn't work in IE 9 and Google Chrome > -------------------------------------------------------------------------------------------------- > > Key: RF-12044 > URL: https://issues.jboss.org/browse/RF-12044 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-misc > Affects Versions: 4.2.0.Final > Environment: RichFaces 4.2.1-SNAPSHOT > Metamer 4.2.1-SNAPSHOT > Mojarra 2.1.5-SNAPSHOT > JBoss AS 7.1.0.Final > Java(TM) SE Runtime Environment 1.6.0_31-b04 @ Linux > Chrome 17.0.963.78 @ Linux i686 > ?RichFaces 4.2.1-SNAPSHOT > ?Metamer 4.2.1-SNAPSHOT > ?Mojarra 2.1.5-SNAPSHOT > ?JBoss AS 7.1.0.Final > ?Java(TM) SE Runtime Environment 1.6.0_31-b04 @ Linux > ?Internet Explorer 9.0 @ Win32 > Reporter: Jan Papousek > Assignee: Luk?? Fry? > Labels: Chrome, IE9 > Fix For: 4.2.1.CR1 > > > It's working correctly in Firefox 10. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 16:04:50 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 21 Mar 2012 16:04:50 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12045) Metamer: focusing of rich:inplaceInput behaves in Google Chrome differently than in other browsers In-Reply-To: <645136326.9592.1331740187653.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <2046839613.23752.1332360290780.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12045: ------------------------------- Fix Version/s: 4.Future > Metamer: focusing of rich:inplaceInput behaves in Google Chrome differently than in other browsers > -------------------------------------------------------------------------------------------------- > > Key: RF-12045 > URL: https://issues.jboss.org/browse/RF-12045 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.2.0.Final > Environment: RichFaces 4.2.1-SNAPSHOT > Metamer 4.2.1-SNAPSHOT > Mojarra 2.1.5-SNAPSHOT > JBoss AS 7.1.0.Final > Java(TM) SE Runtime Environment 1.6.0_31-b04 @ Linux > Chrome 17.0.963.78 @ Linux i686 > Reporter: Jan Papousek > Priority: Optional > Labels: Chrome > Fix For: 4.Future > > > After clicking on rich:inplaceInput in Firefox, the cursor is placed in the beginning of the input and nothing is selected. Doing the same in Google Chrome - the text in the input is selected. > EDIT: It happens only after the first click on the input. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 16:04:50 2012 From: jira-events at lists.jboss.org (Jean ANDRE (JIRA)) Date: Wed, 21 Mar 2012 16:04:50 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12028) a4j:outputPanel - Error message enhancement In-Reply-To: <1368665910.75459.1331155416313.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <2048202920.23753.1332360290848.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678449#comment-12678449 ] Jean ANDRE commented on RF-12028: --------------------------------- The component involved is the because the "class" attribute does not exist for this tag. The error appears when you convert a
    tag to an tag without replacing the "class" attribute by the "styleClass". > a4j:outputPanel - Error message enhancement > ------------------------------------------- > > Key: RF-12028 > URL: https://issues.jboss.org/browse/RF-12028 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Environment: JSF / Mojarra 2.1.6 - cssparser-0.9.6 - guava-11.0.1 - hibernate-validator-4.2.0.Final - springframework 3.0.6.RELEASE - richfaces--4.2.0.Final - sac-1.3 - FireFox 10 - WAS 8.0.0.1 / Windows 7 > Reporter: Jean ANDRE > Labels: waiting_on_user > > When we set an non existing attribute on a4j:outputPanel, for eg. "class" because we have converted a div to a a4j:outputPanel, the error message displayed at the user interface does not inform the developer about the faulty component. The message we got is only : > > Error 500: javax.servlet.ServletException: Setter not found for property class > This error message is not very helpful to debug.... ;) > {code} > layout="block" > class="dark-box" > rendered="#{productBean.expanded eq true}"> > {code} > We should have, as usual, the line of the XHTML file or the component name, the line number, well something more accurate that really help to go faster. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 16:06:50 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 21 Mar 2012 16:06:50 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12046) JSR303 ConstraintViolation propertyPath support for graphValidator In-Reply-To: <2053412287.10319.1331756687690.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1867719778.23761.1332360410396.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12046: ------------------------------- Fix Version/s: 4.Future > JSR303 ConstraintViolation propertyPath support for graphValidator > ------------------------------------------------------------------ > > Key: RF-12046 > URL: https://issues.jboss.org/browse/RF-12046 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-validators > Affects Versions: 4.2.0.Final > Reporter: Gerald Turner > Priority: Optional > Fix For: 4.Future > > > In JSR303 ? 4.2 ConstraintViolation, there is the following note: > "From rootBean and propertyPath, it is possible to rebuild the context of the failure" > Perhaps it would be possible for graphValidator to map ConstraintViolation propertyPath to ValueExpressions, then iterate child EditableValueHolder components and assign FacesMessages to clientIds of these components where it finds a match, otherwise fallback on the current behavior of using the clientId of the graphValidator itself (perhaps even adding an the option to use a null clientId for global messages instead). > A more thorough example of this use-case is here: http://stackoverflow.com/questions/5639088/cross-field-validation-with-inline-messaging-in-jsf-with-jsr-303 > Comments at stackoverflow suggest MyFaces ExtVal Bean Validation can do the trick, however I went down that road, their framework ignores ConstraintViolation propertyPath as well (see: http://old.nabble.com/Re%3A-ExtVal-BV-question-to33455513.html) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 16:08:51 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 21 Mar 2012 16:08:51 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12047) Add "global" attribute to graphValidator In-Reply-To: <1530502986.10336.1331757287488.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1699038040.23763.1332360531602.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12047: ------------------------------- Fix Version/s: 4.Future > Add "global" attribute to graphValidator > ---------------------------------------- > > Key: RF-12047 > URL: https://issues.jboss.org/browse/RF-12047 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-validators > Affects Versions: 4.2.0.Final > Reporter: Gerald Turner > Priority: Trivial > Fix For: 4.Future > > > graphValidator appends FacesMessages to the FacesContext with clientId set to the clientId of the graphValidator component, naturally, however I have a use-case for not assigning a clientId to those FacesMessages at all (null, global messages). > The following example exhibits how graphValidator currently works: > > > What I'm asking for is the following: > > > (Conversely I could wishlist PrimeFaces to add a 'for' attribute to their 'messages' component, something like 'for="@global gv"', so no harm in closing this report ;-) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 16:10:48 2012 From: jira-events at lists.jboss.org (RH Bugzilla Integration (JIRA)) Date: Wed, 21 Mar 2012 16:10:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12049) Richfaces Kitchensink Archetype In-Reply-To: <298774079.10572.1331775587398.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1794617574.23766.1332360648680.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] RH Bugzilla Integration updated RF-12049: ----------------------------------------- Bugzilla Update: Perform > Richfaces Kitchensink Archetype > ------------------------------- > > Key: RF-12049 > URL: https://issues.jboss.org/browse/RF-12049 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Environment: JBDS 5 Beta 1 > Reporter: Burr Sutter > Attachments: richfaces_junit_failure.png > > > The currently generated RichFaces-based kitchensink project "richfaces-webapp" throws the following exception when Run As JUnit Test is used. > 21:36:27,147 ERROR [org.jboss.ejb3.invocation] (http-localhost-127.0.0.1-8080-7) JBAS014134: EJB Invocation failed on component MemberRegistration for method public void org.jboss.tools.examples.controller.MemberRegistration.register() throws java.lang.Exception: javax.ejb.EJBException: org.jboss.weld.exceptions.IllegalProductException: WELD-000052 Cannot return null from a non-dependent producer method: [method] @Produces @RequestScoped public org.jboss.tools.examples.util.Resources.produceFacesContext() > at org.jboss.as.ejb3.tx.CMTTxInterceptor.handleExceptionInOurTx(CMTTxInterceptor.java:166) [jboss-as-ejb3-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1] > at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:230) [jboss-as-ejb3-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1] > at org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:304) [jboss-as-ejb3-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1] > at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:190) [jboss-as-ejb3-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 16:10:48 2012 From: jira-events at lists.jboss.org (RH Bugzilla Integration (JIRA)) Date: Wed, 21 Mar 2012 16:10:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12049) Richfaces Kitchensink Archetype In-Reply-To: <298774079.10572.1331775587398.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <181902360.23768.1332360648836.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] RH Bugzilla Integration updated RF-12049: ----------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=802802 > Richfaces Kitchensink Archetype > ------------------------------- > > Key: RF-12049 > URL: https://issues.jboss.org/browse/RF-12049 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Environment: JBDS 5 Beta 1 > Reporter: Burr Sutter > Attachments: richfaces_junit_failure.png > > > The currently generated RichFaces-based kitchensink project "richfaces-webapp" throws the following exception when Run As JUnit Test is used. > 21:36:27,147 ERROR [org.jboss.ejb3.invocation] (http-localhost-127.0.0.1-8080-7) JBAS014134: EJB Invocation failed on component MemberRegistration for method public void org.jboss.tools.examples.controller.MemberRegistration.register() throws java.lang.Exception: javax.ejb.EJBException: org.jboss.weld.exceptions.IllegalProductException: WELD-000052 Cannot return null from a non-dependent producer method: [method] @Produces @RequestScoped public org.jboss.tools.examples.util.Resources.produceFacesContext() > at org.jboss.as.ejb3.tx.CMTTxInterceptor.handleExceptionInOurTx(CMTTxInterceptor.java:166) [jboss-as-ejb3-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1] > at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:230) [jboss-as-ejb3-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1] > at org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:304) [jboss-as-ejb3-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1] > at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:190) [jboss-as-ejb3-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 16:12:47 2012 From: jira-events at lists.jboss.org (Jean ANDRE (JIRA)) Date: Wed, 21 Mar 2012 16:12:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12032) rich:calendar : Ajax request - Error message enhancement - sql.Date In-Reply-To: <1406650855.77949.1331220940774.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1089273508.23771.1332360767927.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678450#comment-12678450 ] Jean ANDRE commented on RF-12032: --------------------------------- I have not checked the server log, in production we do not have access right away to the log files, it is why, it will be more suitable to have: 1) An standard error of conversion displayed at the user screen - The screen shot does not show the problem because in fact, we have no message. More over, the message does not talk about conversion error but about a mandatory value from an another validator @NotNull 2) Or to support both date format according to the date format given by the backing 3) Any message at the user screen instead of having a silent error. > rich:calendar : Ajax request - Error message enhancement - sql.Date > ------------------------------------------------------------------- > > Key: RF-12032 > URL: https://issues.jboss.org/browse/RF-12032 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Environment: cssparser-0.9.6 - guava-11.0.1 - hibernate-validator-4.2.0.Final - JSF/Mojarra 2.1.6 - springframework-3.0.6.RELEASE - richfaces-4.2.0.Final - sac-1.3.jar - Windows 7, WAS 8.0.0.1, Servlet 2.5 - Java 6. > Reporter: Jean ANDRE > Labels: waiting_on_user > Attachments: rich_calendar_errorMsg_Enhancement.png > > > When a backing-bean have a type of sql.Date which is mapped to a rich:calendar, there is an conversion error due to the rich:calendar component uses util.Date by default. Unfortunately, we do not see any error message at the screen when an ajax request is sent and returned back to us. > What we got, and thanks to Firebug, is the text below as an answer from our Ajax request POST. Nothing is rendered at the screen and the method of the backing bean is not called. > {code} > > class javax.faces.component.UpdateModelException > {code} > Our code looks like this (we remove unecessary field and decoration): > {code} > > > > > value="#{msg['common.command.add.phone']}" > action="#{createClientController.doAddPhone}"> > > > > > > > value="#{phoneBean.effectiveDate}" > popup="true" > showApplyButton="false" > enableManualInput="true" > datePattern="#{msg['client.date.format']}" > inputSize="12" > styleClass="calendar"> > > > > > > > > {code} > Is is possible to have a message returned back to the UI??? or is there a way to handle this error properly? > Other information > ================= > The form is inside a dynamic tab - Fragment are also include dynamically - we use c:if et subView as shown below: > {code} > > > > > > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 16:14:48 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 21 Mar 2012 16:14:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12049) Richfaces Kitchensink Archetype In-Reply-To: <298774079.10572.1331775587398.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <150585817.23774.1332360888227.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-12049. -------------------------------- Assignee: Brian Leathem Resolution: Out of Date This has already been fixed in the latest SNAPSHOTS, and will be available with the the 4.2.1.CR1 release of the kitchensink archetype. > Richfaces Kitchensink Archetype > ------------------------------- > > Key: RF-12049 > URL: https://issues.jboss.org/browse/RF-12049 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Environment: JBDS 5 Beta 1 > Reporter: Burr Sutter > Assignee: Brian Leathem > Attachments: richfaces_junit_failure.png > > > The currently generated RichFaces-based kitchensink project "richfaces-webapp" throws the following exception when Run As JUnit Test is used. > 21:36:27,147 ERROR [org.jboss.ejb3.invocation] (http-localhost-127.0.0.1-8080-7) JBAS014134: EJB Invocation failed on component MemberRegistration for method public void org.jboss.tools.examples.controller.MemberRegistration.register() throws java.lang.Exception: javax.ejb.EJBException: org.jboss.weld.exceptions.IllegalProductException: WELD-000052 Cannot return null from a non-dependent producer method: [method] @Produces @RequestScoped public org.jboss.tools.examples.util.Resources.produceFacesContext() > at org.jboss.as.ejb3.tx.CMTTxInterceptor.handleExceptionInOurTx(CMTTxInterceptor.java:166) [jboss-as-ejb3-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1] > at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:230) [jboss-as-ejb3-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1] > at org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:304) [jboss-as-ejb3-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1] > at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:190) [jboss-as-ejb3-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 16:14:48 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 21 Mar 2012 16:14:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12051) Showcase: simplified Push CDI sample which wouldn't use subtopics In-Reply-To: <1777587358.12158.1331830847464.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <225357280.23776.1332360888581.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12051: ------------------------------- Assignee: Luk?? Fry? Fix Version/s: 4.2.1.CR1 Priority: Minor (was: Major) Description: Push CDI sample in Showcase is currently quite complex and people run into issues when starting to use it, because there is usage of subtopics. There are two alternative ways how to address it: # simplify current sample # provide new sample as alternative to this one was: Push CDI sample in Showcase is currently quite complex and people run into issues when starting to use it, because there is usage of subtopics. There are two alternative ways how to address it: 1. simplify current sample 2. provide new sample as alternative to this one Let's go with the simplifying approach. > Showcase: simplified Push CDI sample which wouldn't use subtopics > ----------------------------------------------------------------- > > Key: RF-12051 > URL: https://issues.jboss.org/browse/RF-12051 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: showcase > Affects Versions: 4.2.0.Final > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Priority: Minor > Fix For: 4.2.1.CR1 > > > Push CDI sample in Showcase is currently quite complex and people run into issues when starting to use it, > because there is usage of subtopics. > There are two alternative ways how to address it: > # simplify current sample > # provide new sample as alternative to this one -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 16:16:48 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 21 Mar 2012 16:16:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12052) rich:TabPanel - HTML comments should be supported inside the tabPanel In-Reply-To: <1018200636.12395.1331837267498.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <637163760.23778.1332361008470.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12052: ------------------------------- Assignee: Brian Leathem Fix Version/s: 4.2.1.CR1 Priority: Trivial (was: Major) Component/s: component-output > rich:TabPanel - HTML comments should be supported inside the tabPanel > --------------------------------------------------------------------- > > Key: RF-12052 > URL: https://issues.jboss.org/browse/RF-12052 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-output > Reporter: Jean ANDRE > Assignee: Brian Leathem > Priority: Trivial > Fix For: 4.2.1.CR1 > > > Is it possible to support HTML comment inside a tabPanel. Because it causes this error if we but comments as shown below. The error is: > E org.richfaces.context.ExtendedPartialViewContextImpl processPartialExecutePhase > java.lang.IllegalArgumentException > at org.richfaces.component.AbstractTogglePanel.getChildName(AbstractTogglePanel.java:490) > {code} > switchType="ajax" > headerPosition="top" > itemChangeListener="#{viewItemController.doItemChangeListener}" > activeItem="#{viewItemController.activeTab}" > immediate="true"> > > > > > > {code} > Or at least, give us a clear error message as we did for tabPanel and the form tag. > Thank you. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 16:16:48 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 21 Mar 2012 16:16:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12054) TabPanel onitemchange of outer tab fired by inner tab In-Reply-To: <662615629.13006.1331883347434.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1421245831.23781.1332361008888.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12054: ------------------------------- Fix Version/s: 4.Future Forum Reference: https://community.jboss.org/thread/196901 (was: https://community.jboss.org/thread/196901) > TabPanel onitemchange of outer tab fired by inner tab > ----------------------------------------------------- > > Key: RF-12054 > URL: https://issues.jboss.org/browse/RF-12054 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.2.0.Final > Reporter: Przemys?aw D?bski > Labels: tabpanel > Fix For: 4.Future > > > When changing outer tab, "onitemchange" event of outer tab is fired and alert with text 'onitemchange' is shown. > But when changing inner tab both "onitemchange" event of outer tab and inner tab are fired and two alerts are show, one with text 'onitemchange' and second with 'onitemchange inner'. > It's wrong behaviour, because outer tab is not switched and its "onitemchange" event shouldn't be fired. Same situation with "onbeforeitemchange". > Page code to reproduce: > {code:xml} > xmlns:f="http://java.sun.com/jsf/core" xmlns:rich="http://richfaces.org/rich"> > > > > > tab1 > > > tab inner 1 > tab inner 2 > > > > > > > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 16:16:49 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 21 Mar 2012 16:16:49 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12054) TabPanel onitemchange of outer tab fired by inner tab In-Reply-To: <662615629.13006.1331883347434.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1897659260.23784.1332361009747.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12054: ------------------------------- Component/s: component-panels-layout-themes Forum Reference: https://community.jboss.org/thread/196901 (was: https://community.jboss.org/thread/196901) > TabPanel onitemchange of outer tab fired by inner tab > ----------------------------------------------------- > > Key: RF-12054 > URL: https://issues.jboss.org/browse/RF-12054 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.2.0.Final > Reporter: Przemys?aw D?bski > Labels: tabpanel > Fix For: 4.Future > > > When changing outer tab, "onitemchange" event of outer tab is fired and alert with text 'onitemchange' is shown. > But when changing inner tab both "onitemchange" event of outer tab and inner tab are fired and two alerts are show, one with text 'onitemchange' and second with 'onitemchange inner'. > It's wrong behaviour, because outer tab is not switched and its "onitemchange" event shouldn't be fired. Same situation with "onbeforeitemchange". > Page code to reproduce: > {code:xml} > xmlns:f="http://java.sun.com/jsf/core" xmlns:rich="http://richfaces.org/rich"> > > > > > tab1 > > > tab inner 1 > tab inner 2 > > > > > > > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 16:18:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 21 Mar 2012 16:18:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12055) horizontal scrollbar is not working properly by using ScrollableDataTable, with one column In-Reply-To: <1704997765.13478.1331893787300.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1599502328.23786.1332361127589.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-12055. -------------------------------- Assignee: Brian Leathem Resolution: Incomplete Description Please re-open this issue with a complete description: https://community.jboss.org/wiki/SubmittingEffectiveIssueReports > horizontal scrollbar is not working properly by using ScrollableDataTable, with one column > ------------------------------------------------------------------------------------------- > > Key: RF-12055 > URL: https://issues.jboss.org/browse/RF-12055 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: lakshmee n > Assignee: Brian Leathem > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 16:22:49 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 21 Mar 2012 16:22:49 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12057) IE 8 rich:toolTip client side toolTip has problems rendering upon ajax request In-Reply-To: <470606725.14861.1331928287605.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1935554791.23809.1332361369016.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12057: ------------------------------- Description: Rich:Tooltip in client mode does not refresh upon an ajax event specifically in IE 8. A large part of external clients utilize IE 8 unfortunately. The tool tip is working correctly in IE 9, chrome and FF 7+. The tool tip is refreshed on next ajax request with "previous" ajax response. {code:title=TOOL TIP CODE:}
    {code} {code:title=AJAX REQUEST CODE, SELECTABLE CHECKBOX WHICH RE-RENDERS TOOLTIP} {code} was: Rich:Tooltip in client mode does not refresh upon an ajax event specifically in IE 8. A large part of external clients utilize IE 8 unfortunately. The tool tip is working correctly in IE 9, chrome and FF 7+. The tool tip is refreshed on next ajax request with "previous" ajax response. TOOL TIP CODE: ===============
    AJAX REQUEST CODE, SELECTABLE CHECKBOX WHICH RE-RENDERS TOOLTIP =============================================================== > IE 8 rich:toolTip client side toolTip has problems rendering upon ajax request > ------------------------------------------------------------------------------ > > Key: RF-12057 > URL: https://issues.jboss.org/browse/RF-12057 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.1.0.Final > Environment: Windows 7, IE 8 > Reporter: Gurinder Randhawa > Fix For: 4.3-Tracking > > > Rich:Tooltip in client mode does not refresh upon an ajax event specifically in IE 8. A large part of external clients utilize IE 8 unfortunately. The tool tip is working correctly in IE 9, chrome and FF 7+. > The tool tip is refreshed on next ajax request with "previous" ajax response. > {code:title=TOOL TIP CODE:} > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
    > >
    rendered="#{modifier.calculated}, #{modifier.applied.maximum}" /> > >
    > >
    > >
    > >
    >     > {code} > {code:title=AJAX REQUEST CODE, SELECTABLE CHECKBOX WHICH RE-RENDERS TOOLTIP} > > > > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 16:22:49 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 21 Mar 2012 16:22:49 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12057) IE 8 rich:toolTip client side toolTip has problems rendering upon ajax request In-Reply-To: <470606725.14861.1331928287605.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1070274894.23811.1332361369304.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12057: ------------------------------- Fix Version/s: 4.3-Tracking > IE 8 rich:toolTip client side toolTip has problems rendering upon ajax request > ------------------------------------------------------------------------------ > > Key: RF-12057 > URL: https://issues.jboss.org/browse/RF-12057 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.1.0.Final > Environment: Windows 7, IE 8 > Reporter: Gurinder Randhawa > Fix For: 4.3-Tracking > > > Rich:Tooltip in client mode does not refresh upon an ajax event specifically in IE 8. A large part of external clients utilize IE 8 unfortunately. The tool tip is working correctly in IE 9, chrome and FF 7+. > The tool tip is refreshed on next ajax request with "previous" ajax response. > {code:title=TOOL TIP CODE:} > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
    > >
    rendered="#{modifier.calculated}, #{modifier.applied.maximum}" /> > >
    > >
    > >
    > >
    >     > {code} > {code:title=AJAX REQUEST CODE, SELECTABLE CHECKBOX WHICH RE-RENDERS TOOLTIP} > > > > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 16:24:49 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 21 Mar 2012 16:24:49 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12058) rich:fileUpload - wrong upload icon if resourceOptimization param is set to true In-Reply-To: <1723961468.15563.1332085067290.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <302747040.23823.1332361489761.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12058: ------------------------------- Fix Version/s: 4.2.1.CR1 Assignee: Luk?? Fry? Component/s: resource handling > rich:fileUpload - wrong upload icon if resourceOptimization param is set to true > --------------------------------------------------------------------------------- > > Key: RF-12058 > URL: https://issues.jboss.org/browse/RF-12058 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input, resource handling > Affects Versions: 4.2.0.Final > Environment: Tomcat6.33, Richfaces 4.2.0 FINAL, JDK1.6 > Reporter: Thorsten Nieser > Assignee: Luk?? Fry? > Priority: Minor > Fix For: 4.2.1.CR1 > > Attachments: css-snippet.jpg, nok.jpg, ok.jpg > > > If the new resource optimization is disabled all icons of the fileUpload element are fine. > (http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=fileUpload&skin=blueSky) > But if I enabled the optimization by setting the context param to true, the upload button shows the red cross instead of the green check mark. > > org.richfaces.resourceOptimization.enabled > true > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 16:26:48 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 21 Mar 2012 16:26:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12059) RichFaces.ui.Message is not a constructor - Nested Tab Panel - Tab Creation In-Reply-To: <1031888240.16896.1332159287591.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <127353800.23828.1332361608495.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12059: ------------------------------- Fix Version/s: 4.3-Tracking > RichFaces.ui.Message is not a constructor - Nested Tab Panel - Tab Creation > --------------------------------------------------------------------------- > > Key: RF-12059 > URL: https://issues.jboss.org/browse/RF-12059 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.2.0.Final > Environment: Websphere 8.0.0.2 - RAD 8 - JSF Mojorra 2.1.6 - Spring 3.0.6 Final - Firefox 10.0.2 - Windows 7 (6.1 sp1) - AspectJ 1.6.12 / AJDT - RichFaces 4.2.0 Final - Hibernate Validator 4.2.0 Final > Reporter: Jean ANDRE > Priority: Blocker > Fix For: 4.3-Tracking > > Attachments: NestedWeb_RF-12059.zip > > > We got the following error message, just after a tab has been created or during its creation. After the error, we are not able to use the application. Everything looks like frozen, tabs do not switch anymore. > {code} > RichFaces.ui.Message is not a constructor > > return new Function("event", handlerCode); > richfaces.js.jsf (ligne 481) > {code} > This bug is linked to RF-11763 and RF-12030 but the error message and the context are not the same. > The rich:messages is also involved in this bug, the rich:message is attached to a rich:calendar. Removing the rich:message removes the error. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 16:28:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 21 Mar 2012 16:28:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12060) element is null message when closing tab from an event click In-Reply-To: <1849991598.17427.1332167088202.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1807552930.23830.1332361727900.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12060: ------------------------------- Fix Version/s: 4.Future > element is null message when closing tab from an event click > ------------------------------------------------------------ > > Key: RF-12060 > URL: https://issues.jboss.org/browse/RF-12060 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.2.0.Final > Environment: Websphere 8.0.0.2 - RAD 8 - JSF Mojorra 2.1.6 - Spring 3.0.6 Final - Firefox 10.0.2 - Windows 7 (6.1 sp1) - AspectJ 1.6.12 / AJDT - RichFaces 4.2.0 Final - Hibernate Validator 4.2.0 Final > Reporter: Jean ANDRE > Fix For: 4.Future > > Attachments: NestedWeb_RF-12060.zip > > > There is a link to RF-11950. > We got the message "element is null" when we send a click event for closing a tab. To retrieve the id of the close button (an image), we use the function getElementById (because of RF-11950). The click function calls a javascript function declared by a4j:jsFunction (see index.hxtml file - close task). > This is the only information we have from firebug. When we close the tab directly by clicking on the close button/image, it works perfectly. > *Note :* Moreover, there is also a strange behavior related to generated id on close button/image. When we specified a fix id on the h:graphicImage, the first id is correct but there is no id on other close button/image from other tabs!???. Having a fix id should trigger a duplicate ID but as the ids are not generated on other tabs, it does not. > {code} > >   title="#{msg[task.uiActivity.headerKey]}" /> >   styleClass="closeButton" > onclick="closeTask('#{task.id}');event.stopPropagation();" /> > > > > > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 16:28:48 2012 From: jira-events at lists.jboss.org (Jean ANDRE (JIRA)) Date: Wed, 21 Mar 2012 16:28:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12040) Multi-form document - command button (submit) does not work after rendering In-Reply-To: <375257168.7025.1331658768095.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1601928741.23831.1332361728445.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678456#comment-12678456 ] Jean ANDRE commented on RF-12040: --------------------------------- That's correct, our problem looks like JAVASERVERFACES_SPEC_PUBLIC-790. You can close the issue. In our case, I have to try what your are suggesting because we have also the quick search form between both. If the quick search is part of a single form, when we click the search button of the quick search and if there is any other form with validation inside the desktopTabs form (TabPanel), we trigger also the validation of that form. It is why we put the quick search form outside the other forms. Moreover, put all in one means also more unnecessary fields are sent to the server and dependencies issues. > Multi-form document - command button (submit) does not work after rendering > --------------------------------------------------------------------------- > > Key: RF-12040 > URL: https://issues.jboss.org/browse/RF-12040 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Environment: cssparser-0.9.6 - guava-11.0.1 - hibernate-validator-4.2.0.Final - JSF/Mojarra 2.1.6 - springframework-3.0.6.RELEASE - sac-1.3 - Windows 7 - FireFox 10 - RichFaces 4.2 Final > Reporter: Jean ANDRE > Labels: waiting_on_user > Attachments: NestedWebWithMenu.zip > > > We have one page that contains two forms. The first form contain a menus bar (ajax switchType) while the second contains a tabPanel (also in ajax switchType). When a user select a menu, we select the corresponding tab that contains a submit button. Once the tab is selected, the submit button does not work. We have to click twice for submitting. > # If we move the menu bar inside the second forms, it is working. > # If we set the menu bar in client switchType, selecting the menu doesn't do anything. > # If we set the menu bar in server switchType it's working. > As the rendering is well executed, the submit button should works but is not whatever we set as render="@all, or any valid id". > We have prepared a small application that demonstrates the case. This is a simple but realistic application. Edit the index.xhtml to play with the menu. Let us know if we doing something wrong. > Note also that the JIRA JAVASERVERFACES-2016 was reopened :[JIRA] Reopened: (JAVASERVERFACES-2016) Resources not loaded when using a dynamic ui:inlclude and rendered via ajax > [ http://java.net/jira/browse/JAVASERVERFACES-2016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] > {code:title=Relevant Facelet markup} > > xmlns:ui="http://java.sun.com/jsf/facelets" > xmlns:h="http://java.sun.com/jsf/html" > xmlns:f="http://java.sun.com/jsf/core" > xmlns:rich="http://richfaces.org/rich" > xmlns:a4j="http://richfaces.org/a4j" > xmlns:c="http://java.sun.com/jsp/jstl/core" > template="/templates/basePage.xhtml"> > > > > > > > > > > > > > > > > > > > > > > > label="#{msg['menu.item.one.items.management']}" > action="#{desktopController.doActivateTabItems}" > render="desktopTabs" /> > > > > >
    >
    > > > > > > > > switchType="ajax" > headerPosition="top" > activeItem="#{desktopController.activeTab}" > itemChangeListener="#{desktopController.doItemChangeListener}" > immediate="true"> > > > > > #1 > > > > > > > > > > value="#{msg[desktopController.togglePanelLabel]}" > actionListener="#{desktopController.doToggleTabContent}" > render="toggleTabContent"> > >
    >
    > > > > > > > > > > > > >     >     > > > > > > > > > styleClass="closeButton" > onclick="closeTab('#{tab.id}');event.stopPropagation();" /> > > > > > > > > > >     >     > > > > > > > > > > > > >     > > > >     > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 16:34:48 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 21 Mar 2012 16:34:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12061) pickList direction In-Reply-To: <138392524.17532.1332168288239.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <2134692529.23836.1332362088854.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12061: ------------------------------- Fix Version/s: 4.Future Forum Reference: https://community.jboss.org/message/724610#724610 (was: https://community.jboss.org/message/724610#724610) As a workaround, you can override the CSS style for the pickList component. > pickList direction > ------------------ > > Key: RF-12061 > URL: https://issues.jboss.org/browse/RF-12061 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 4.1.0.Final > Environment: RF 4.1, JSF 2 Mojarra 2.0.8 > Reporter: Ibrahim Abu Ghosh > Labels: pickList > Fix For: 4.Future > > > when i set the body direction to "rtl" and click or do any action on pickList the whole page shift to left. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 16:36:48 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 21 Mar 2012 16:36:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12063) rich:notifyMessages not displaying error from valueChangeListener In-Reply-To: <71281469.18246.1332180647276.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <725312541.23838.1332362208102.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12063: ------------------------------- Labels: waiting_on_user (was: ) Would you please provide some sample code to reproduce this problem? https://community.jboss.org/wiki/SubmittingEffectiveIssueReports > rich:notifyMessages not displaying error from valueChangeListener > ----------------------------------------------------------------- > > Key: RF-12063 > URL: https://issues.jboss.org/browse/RF-12063 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.2.0.Final > Environment: Mojarra 2.1.7, RF 4.2.0.Final, Windows 7, Glassfish 3.1.2, Chrome browser. > Reporter: Brendan Healey > Labels: waiting_on_user > > I have a global notifyMessages in a template . > I log a global error in the usual way from a value change listener (process validations > phase): > FacesMessage message = getFacesMessage(errKey); > message.setSeverity(FacesMessage.SEVERITY_ERROR); > FacesContext.getCurrentInstance().addMessage(null, message); > but the error never appears. If I have an h:messages on the page which is ajax > rendered the message appears ok. > Regards, > Brendan. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 16:36:50 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 21 Mar 2012 16:36:50 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12066) Kitchensink archetype is not listed in the modules of the parent pom In-Reply-To: <1702434883.20113.1332246707300.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1096579975.23852.1332362210811.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12066: ------------------------------- Assignee: Brian Leathem Fix Version/s: 4.2.1.CR1 > Kitchensink archetype is not listed in the modules of the parent pom > -------------------------------------------------------------------- > > Key: RF-12066 > URL: https://issues.jboss.org/browse/RF-12066 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: archetype > Affects Versions: 4.2.0.Final > Reporter: Juraj Huska > Assignee: Brian Leathem > Priority: Trivial > Fix For: 4.2.1.CR1 > > > The maven module _richfaces-archetype-kitchensink_ is not listed in the parent pom.xml in the modules section. > Therefore, can not be installed from the parent pom. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 16:38:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 21 Mar 2012 16:38:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12068) rich:toggleControl: can't use immediate=true In-Reply-To: <1358714521.20262.1332253007498.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1842060028.23854.1332362327858.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12068: ------------------------------- Fix Version/s: 4.3-Tracking > rich:toggleControl: can't use immediate=true > -------------------------------------------- > > Key: RF-12068 > URL: https://issues.jboss.org/browse/RF-12068 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.2.0.Final > Reporter: Luk?? Fry? > Fix For: 4.3-Tracking > > > The wizard can be created with {{togglePanel}} and {{toggleControl}}. > It can use validation mechanism and Ajax to switch between wizard windows. > ---- > But when validation fails, you can't use {{toggleControl}} to switch to another panel > like in the sample of Back button - there is no possibility to request {{immediate}} response (shortened lifecycle skipping validation phase). > ---- > The scenario can be seen in the sample of Showcase - togglePanel - Wizard [1], > and in the QuickStart {{richfaces-validation}} [2]. > [1] http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=togglePanel&sample=wizard&skin=blueSky > [2] https://github.com/lfryc/quickstart/tree/quickstart-28 > ---- > Sample code: > {code} > > > > > > > > > > > > > > > > > > > > > > > > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 16:38:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 21 Mar 2012 16:38:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12069) Use of $(document).ready instead of jQuery(document).ready in org.richfaces.renderkit.html.ScriptsRenderer In-Reply-To: <1707537090.20595.1332256548101.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <4207430.23856.1332362327991.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12069: ------------------------------- Fix Version/s: 4.3-Tracking > Use of $(document).ready instead of jQuery(document).ready in org.richfaces.renderkit.html.ScriptsRenderer > ---------------------------------------------------------------------------------------------------------- > > Key: RF-12069 > URL: https://issues.jboss.org/browse/RF-12069 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 4.1.0.Final > Reporter: Sandro Br?ndli > Fix For: 4.3-Tracking > > > As stated in the summary ScriptsRenderer uses the $-sign instead of jQuery. This causes problems when using a JavaScript library that overrides the $-sign. In my case it breaks DnD when including Prototype. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 16:40:49 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 21 Mar 2012 16:40:49 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12070) Kitschensink archetype - broken formatting of comments in generated pom.xml In-Reply-To: <561043984.20917.1332262367501.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1454653742.23858.1332362449275.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12070: ------------------------------- Fix Version/s: 4.2.1.CR1 Assignee: Brian Leathem > Kitschensink archetype - broken formatting of comments in generated pom.xml > --------------------------------------------------------------------------- > > Key: RF-12070 > URL: https://issues.jboss.org/browse/RF-12070 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: archetype > Affects Versions: 4.2.0.Final > Reporter: Juraj Huska > Assignee: Brian Leathem > Priority: Trivial > Fix For: 4.2.1.CR1 > > Attachments: brokenFormatting.png > > > Comments in generated pom.xml from Kitschensink maven archetype have broken formatting. Please see the attachment. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 16:42:52 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 21 Mar 2012 16:42:52 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12071) a4j:outputPanel h:inputText render problem In-Reply-To: <1254741604.22548.1332331187494.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <549619271.23860.1332362572010.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12071: ------------------------------- Description: Create dynamic screen with JSF is so hard and painfull. I used a4j:outputPanel so many times. Today i am trying to create dynamic screen based on combo selected value. When value is for example option1 it generate inputText, otherwise comboBox. But i face to rendered problem son many times. Problem is on submited object value. My problem code like these: {code} {code} Problem detail: Captionvalue is unique in database. When exception is throwed from back end(JPA uniquness error). I pops up error to user. Then user edit captionValue and try to resubmit. But captionValue is not change, even user changed it. When i remove rendered="#{conditionKeyBean.checkable}" problem is solved. rendered is not working correctly i think. How can i solve this problem? was: Create dynamic screen with JSF is so hard and painfull. I used a4j:outputPanel so many times. Today i am trying to create dynamic screen based on combo selected value. When value is for example option1 it generate inputText, otherwise comboBox. But i face to rendered problem son many times. Problem is on submited object value. My problem code like these: Problem detail: Captionvalue is unique in database. When exception is throwed from back end(JPA uniquness error). I pops up error to user. Then user edit captionValue and try to resubmit. But captionValue is not change, even user changed it. When i remove rendered="#{conditionKeyBean.checkable}" problem is solved. rendered is not working correctly i think. How can i solve this problem? Component/s: component-panels-layout-themes > a4j:outputPanel h:inputText render problem > ------------------------------------------ > > Key: RF-12071 > URL: https://issues.jboss.org/browse/RF-12071 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Reporter: Abdullah ?lhanl? > > Create dynamic screen with JSF is so hard and painfull. > I used a4j:outputPanel so many times. > Today i am trying to create dynamic screen based on combo selected value. When value is for example option1 it generate inputText, otherwise comboBox. > But i face to rendered problem son many times. Problem is on submited object value. > My problem code like these: > {code} > > > valueChangeListener="#{conditionKeyBean.compTypeChanged}"> > > render="checkableLabel,checkableField" /> > > > rendered="#{conditionKeyBean.checkable}" /> > > > > > > > > {code} > Problem detail: > Captionvalue is unique in database. > When exception is throwed from back end(JPA uniquness error). I pops up error to user. Then user edit captionValue and try to resubmit. But captionValue is not change, even user changed it. When i remove rendered="#{conditionKeyBean.checkable}" problem is solved. rendered is not working correctly i think. > How can i solve this problem? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 16:46:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 21 Mar 2012 16:46:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12071) a4j:outputPanel h:inputText render problem In-Reply-To: <1254741604.22548.1332331187494.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <194056472.23862.1332362807373.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678462#comment-12678462 ] Brian Leathem commented on RF-12071: ------------------------------------ Is _conditionKeyBean.checkable_ constant throughout the request lifecycle? If so, you may have better success with the c:if tag. > a4j:outputPanel h:inputText render problem > ------------------------------------------ > > Key: RF-12071 > URL: https://issues.jboss.org/browse/RF-12071 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Reporter: Abdullah ?lhanl? > Labels: waiting_on_user > > Create dynamic screen with JSF is so hard and painfull. > I used a4j:outputPanel so many times. > Today i am trying to create dynamic screen based on combo selected value. When value is for example option1 it generate inputText, otherwise comboBox. > But i face to rendered problem son many times. Problem is on submited object value. > My problem code like these: > {code} > > > valueChangeListener="#{conditionKeyBean.compTypeChanged}"> > > render="checkableLabel,checkableField" /> > > > rendered="#{conditionKeyBean.checkable}" /> > > > > > > > > {code} > Problem detail: > Captionvalue is unique in database. > When exception is throwed from back end(JPA uniquness error). I pops up error to user. Then user edit captionValue and try to resubmit. But captionValue is not change, even user changed it. When i remove rendered="#{conditionKeyBean.checkable}" problem is solved. rendered is not working correctly i think. > How can i solve this problem? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 16:48:49 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 21 Mar 2012 16:48:49 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12072) Lost event in push In-Reply-To: <1823827590.22721.1332335688298.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1550985786.23874.1332362929253.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12072: ------------------------------- Fix Version/s: 4.2.1.CR1 Assignee: Luk?? Fry? Component/s: component-push/poll Lukas, does this problem go away with the recent asynchronous improvements you committed? > Lost event in push > ------------------ > > Key: RF-12072 > URL: https://issues.jboss.org/browse/RF-12072 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Reporter: Stian Thorgersen > Assignee: Luk?? Fry? > Fix For: 4.2.1.CR1 > > > Event can be lost if produced while a response is being prepared. I've attached an example where a push event is used to refresh a count whenever an event is fired. It's using Thread.sleep to simulate an event being produced while the response is being prepared. Note, if the sleep just before returning the count is removed it all works fine, and the page is refreshed every 5 seconds, but with the sleep in place the event is lost. > View: > {code} > > > xmlns:f="http://java.sun.com/jsf/core" > xmlns:h="http://java.sun.com/jsf/html" > xmlns:a4j="http://richfaces.org/a4j" > xmlns:rich="http://richfaces.org/rich"> > > > > > > > > > > > > > {code} > Bean: > {code} > package com.example; > import java.io.Serializable; > import java.util.concurrent.atomic.AtomicInteger; > import javax.enterprise.context.SessionScoped; > import javax.inject.Named; > import org.richfaces.application.push.TopicKey; > import org.richfaces.application.push.TopicsContext; > @Named > @SessionScoped > public class MyBean implements Serializable > { > private AtomicInteger count = new AtomicInteger(); > public int getCount() > { > int c = count.get(); > new Thread() > { > public void run() > { > try > { > Thread.sleep(5000); > count.incrementAndGet(); > TopicKey topicKey = new TopicKey("chat"); > TopicsContext topicsContext = TopicsContext.lookup(); > topicsContext.publish(topicKey, ""); > } > catch (Exception e) > { > e.printStackTrace(); > } > }; > }.start(); > > try > { > Thread.sleep(10000); > } > catch (InterruptedException e) > { > } > return c; > } > } > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 16:48:49 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 21 Mar 2012 16:48:49 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12073) Kitchensink archetype - creating enterprise project requires also community richfaces version In-Reply-To: <2091208867.23183.1332345047625.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1567388522.23877.1332362930039.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12073: ------------------------------- Assignee: Brian Leathem Fix Version/s: 4.2.1.CR1 > Kitchensink archetype - creating enterprise project requires also community richfaces version > --------------------------------------------------------------------------------------------- > > Key: RF-12073 > URL: https://issues.jboss.org/browse/RF-12073 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: archetype > Affects Versions: 4.2.0.Final > Reporter: Juraj Huska > Assignee: Brian Leathem > Priority: Optional > Fix For: 4.2.1.CR1 > > > When generating enterprise richfaces maven project from kitchensink archetype, it is also prompting for community richfaces version. And then the community version is not used in the generated pom.xml > The log from this: > {noformat} > [INFO] Using property: groupId = bla.bla > [INFO] Using property: artifactId = foo_bla > Define value for property 'version': 1.0-SNAPSHOT: : > [INFO] Using property: package = bla.bla > [INFO] Using property: enterprise = n > [INFO] Using property: richfaces-enterprise-version = 4.2.0.Final-redhat-1 > [INFO] Using property: richfaces-version = 4.3.0-SNAPSHOT > Confirm properties configuration: > groupId: bla.bla > artifactId: foo_bla > version: 1.0-SNAPSHOT > package: bla.bla > enterprise: n > richfaces-enterprise-version: 4.2.0.Final-redhat-1 > richfaces-version: 4.3.0-SNAPSHOT > Y: : N > [INFO] Using property: groupId = bla.bla > [INFO] Using property: artifactId = foo_bla > Define value for property 'version': 1.0-SNAPSHOT: : > Define value for property 'package': bla.bla: : > Define value for property 'enterprise': n: : y > Define value for property 'richfaces-enterprise-version': 4.2.0.Final-redhat-1: : > Define value for property 'richfaces-version': 4.3.0-SNAPSHOT: : > Confirm properties configuration: > groupId: bla.bla > artifactId: foo_bla > version: 1.0-SNAPSHOT > package: bla.bla > enterprise: y > richfaces-enterprise-version: 4.2.0.Final-redhat-1 > richfaces-version: 4.3.0-SNAPSHOT > Y: : y > [INFO] ------------------------------------------------------------------------ > [INFO] BUILD SUCCESS > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 54.442s > [INFO] Finished at: Wed Mar 21 16:38:02 CET 2012 > [INFO] Final Memory: 9M/129M > [INFO] ------------------------------------------------------------------------ > jhuska at laptop:~/workspace_jbossTools33M5$ > {noformat} > *Steps to reproduce:* > 1. _mvn archetype:generate -DarchetypeGroupId=org.richfaces.archetypes -DarchetypeArtifactId=richfaces-archetype-kitchensink -DarchetypeVersion=4.3.0-SNAPSHOT -DgroupId=bla.bla -DartifactId=foo_bla_ > 2. When prompting: ?Define value for property 'version': 1.0-SNAPSHOT:_, press just enter. > 3. When prompting for confirming predefined values: type N > 4. When prompting for _Define value for property 'version': 1.0-SNAPSHOT: :_ press just enter. > 5. _Define value for property 'package': bla.bla: : _ just enter > 6. _Define value for property 'enterprise': n: :_ type y > 7. _Define value for property 'richfaces-enterprise-version': 4.2.0.Final-redhat-1: :_ just enter > 8. now you should be prompted for _Define value for property 'richfaces-version': 4.3.0-SNAPSHOT: :_, which you should not. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 16:48:50 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 21 Mar 2012 16:48:50 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12075) Kitchensink archetype - link for JBoss AS 7 project site is broken In-Reply-To: <1802298851.23317.1332347447560.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <581895011.23879.1332362930938.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12075: ------------------------------- Fix Version/s: 4.2.1.CR1 Assignee: Brian Leathem > Kitchensink archetype - link for JBoss AS 7 project site is broken > ------------------------------------------------------------------ > > Key: RF-12075 > URL: https://issues.jboss.org/browse/RF-12075 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: archetype > Affects Versions: 4.2.0.Final > Reporter: Juraj Huska > Assignee: Brian Leathem > Priority: Trivial > Fix For: 4.2.1.CR1 > > > The link for JBoss AS 7 project site, which is suited in the find out more section is broken, and points to the: > {noformat}http://localhost:8080/kitchen-sink-community/jboss.org/jbossas{noformat} > It should point to http://www.jboss.org/jbossas > It is caused by missing http://www prefix. It is in the facelet page (about.xhtml), particularly line 16: > {code:xml} >
  • JBoss AS 7 project site
    • > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 16:52:48 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 21 Mar 2012 16:52:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12076) Kitchensink archetype - back button does not back to the correct page state In-Reply-To: <364076515.23363.1332348347607.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <804820981.23885.1332363168748.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12076: ------------------------------- Fix Version/s: 4.3-Tracking > Kitchensink archetype - back button does not back to the correct page state > --------------------------------------------------------------------------- > > Key: RF-12076 > URL: https://issues.jboss.org/browse/RF-12076 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: archetype > Affects Versions: 4.2.0.Final > Environment: AS: JBoss AS 7.1.1.Final, EAP 6.0.0.ER3 > Reporter: Juraj Huska > Priority: Minor > Fix For: 4.3-Tracking > > > When clicking on the url of the freshly created new member (like /rest/members/0) and backing back from the xml viewing, results in removed freshly added member. > After refresh, or AJAX update (clicking on collapsiblePanel), the table is with all members again. > This happens only for freshly added members. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 16:52:50 2012 From: jira-events at lists.jboss.org (Jean ANDRE (JIRA)) Date: Wed, 21 Mar 2012 16:52:50 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12038) IE8 - Object does not support this property or method - a4j:jsFunction In-Reply-To: <1674243330.3069.1331568048477.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <2120504464.23896.1332363170973.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean ANDRE updated RF-12038: ---------------------------- Attachment: ScreenShot_RF-12038.png This the piece of code involved in this issue when we remove event.stopPropagation(). > IE8 - Object does not support this property or method - a4j:jsFunction > ---------------------------------------------------------------------- > > Key: RF-12038 > URL: https://issues.jboss.org/browse/RF-12038 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.2.0.Final > Environment: cssparser-0.9.6- guava-11.0.1 - hibernate-validator-4.2.0.Final - JSF/Mojarra 2.1.6 - springframework-3.0.6.RELEASE - sac-1.3 - Windows 7 - IE 8.0.1.7601.17514 > Reporter: Jean ANDRE > Fix For: 4.2.1.CR1 > > Attachments: index.xhtml, NestedWeb.zip, NestedWeb_RF-12038.zip, ScreenShot_RF-12038.png > > > Under IE8, IE reports the following error message due to a javascript error. However, the page are well displayed and the application is running ok. > Object doesn't support this property or method line 177 caracter 1 > Object doesn't support this property or method line 177 caracter 99 > Under IE Debugger, the line is: > {code} > closeTab=function(tabId){RichFaces.ajax("closeTab",null,{"incId":"1","parameters":{"tabId":tabId} } )};< > The caracter 99, is..............................................................................| (here) > {code} > This is a code generated by a4j:jsFunction from the XHTML > {code} > > > > > > > {code} > The rendered code is : > {code} > > > > {code} > See also this link as we got almost a similar: https://bugzilla.redhat.com/show_bug.cgi?id=601360. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 17:02:47 2012 From: jira-events at lists.jboss.org (Jean ANDRE (JIRA)) Date: Wed, 21 Mar 2012 17:02:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12038) IE8 - Object does not support this property or method - a4j:jsFunction In-Reply-To: <1674243330.3069.1331568048477.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <445897617.23963.1332363767394.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678476#comment-12678476 ] Jean ANDRE commented on RF-12038: --------------------------------- Question: Is it really legitimate to have this instruction "event.stopPropagation();" because we do not know where the event object comes from? Because the close behavior was taken from this site: http://livedemo.exadel.com/richfaces-demo/richfaces/tabPanel.jsf?tab=delete&cid=276296 (View source), however, Event.stop() does not work as Event is not defined. > IE8 - Object does not support this property or method - a4j:jsFunction > ---------------------------------------------------------------------- > > Key: RF-12038 > URL: https://issues.jboss.org/browse/RF-12038 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.2.0.Final > Environment: cssparser-0.9.6- guava-11.0.1 - hibernate-validator-4.2.0.Final - JSF/Mojarra 2.1.6 - springframework-3.0.6.RELEASE - sac-1.3 - Windows 7 - IE 8.0.1.7601.17514 > Reporter: Jean ANDRE > Fix For: 4.2.1.CR1 > > Attachments: index.xhtml, NestedWeb.zip, NestedWeb_RF-12038.zip, ScreenShot_RF-12038.png > > > Under IE8, IE reports the following error message due to a javascript error. However, the page are well displayed and the application is running ok. > Object doesn't support this property or method line 177 caracter 1 > Object doesn't support this property or method line 177 caracter 99 > Under IE Debugger, the line is: > {code} > closeTab=function(tabId){RichFaces.ajax("closeTab",null,{"incId":"1","parameters":{"tabId":tabId} } )};< > The caracter 99, is..............................................................................| (here) > {code} > This is a code generated by a4j:jsFunction from the XHTML > {code} > > > > > > > {code} > The rendered code is : > {code} > > > > {code} > See also this link as we got almost a similar: https://bugzilla.redhat.com/show_bug.cgi?id=601360. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 17:04:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Abdullah_=C4=B0lhanl=C4=B1_=28JIRA=29?=) Date: Wed, 21 Mar 2012 17:04:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12071) a4j:outputPanel h:inputText render problem In-Reply-To: <1254741604.22548.1332331187494.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <796030819.23974.1332363887418.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678478#comment-12678478 ] Abdullah ?lhanl? commented on RF-12071: --------------------------------------- Thank you Brian. ConditionKeyBean work on view scope. Checkable is boolean value in bean. When combo value is changed, in valueChangeListener, i control which option is selected then set checkable boolean value. c:if i have never used. It is jsp syntax, isnt it?. It can be success, but i think c:if is not standart in JSF, isnt it? > a4j:outputPanel h:inputText render problem > ------------------------------------------ > > Key: RF-12071 > URL: https://issues.jboss.org/browse/RF-12071 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Reporter: Abdullah ?lhanl? > Labels: waiting_on_user > > Create dynamic screen with JSF is so hard and painfull. > I used a4j:outputPanel so many times. > Today i am trying to create dynamic screen based on combo selected value. When value is for example option1 it generate inputText, otherwise comboBox. > But i face to rendered problem son many times. Problem is on submited object value. > My problem code like these: > {code} > > > valueChangeListener="#{conditionKeyBean.compTypeChanged}"> > > render="checkableLabel,checkableField" /> > > > rendered="#{conditionKeyBean.checkable}" /> > > > > > > > > {code} > Problem detail: > Captionvalue is unique in database. > When exception is throwed from back end(JPA uniquness error). I pops up error to user. Then user edit captionValue and try to resubmit. But captionValue is not change, even user changed it. When i remove rendered="#{conditionKeyBean.checkable}" problem is solved. rendered is not working correctly i think. > How can i solve this problem? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 17:47:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 21 Mar 2012 17:47:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12071) a4j:outputPanel h:inputText render problem In-Reply-To: <1254741604.22548.1332331187494.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <924963206.24036.1332366467944.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678489#comment-12678489 ] Brian Leathem commented on RF-12071: ------------------------------------ c:if is perfectly valid JSF, it just executes at a different stage of the lifecycle. If a component is excluded with _c:_ tag, it is omitted from the component tree, as opposed to just not being rendered. This means they should be avoided in cases where the exclusion logic can change throughout the request lifecycle. In fact, appropriate use of _c:_ tags can be a real performance benefit. > a4j:outputPanel h:inputText render problem > ------------------------------------------ > > Key: RF-12071 > URL: https://issues.jboss.org/browse/RF-12071 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Reporter: Abdullah ?lhanl? > Labels: waiting_on_user > > Create dynamic screen with JSF is so hard and painfull. > I used a4j:outputPanel so many times. > Today i am trying to create dynamic screen based on combo selected value. When value is for example option1 it generate inputText, otherwise comboBox. > But i face to rendered problem son many times. Problem is on submited object value. > My problem code like these: > {code} > > > valueChangeListener="#{conditionKeyBean.compTypeChanged}"> > > render="checkableLabel,checkableField" /> > > > rendered="#{conditionKeyBean.checkable}" /> > > > > > > > > {code} > Problem detail: > Captionvalue is unique in database. > When exception is throwed from back end(JPA uniquness error). I pops up error to user. Then user edit captionValue and try to resubmit. But captionValue is not change, even user changed it. When i remove rendered="#{conditionKeyBean.checkable}" problem is solved. rendered is not working correctly i think. > How can i solve this problem? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 17:51:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 21 Mar 2012 17:51:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12066) Kitchensink archetype is not listed in the modules of the parent pom In-Reply-To: <1702434883.20113.1332246707300.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <469662053.24040.1332366707603.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-12066. -------------------------------- Resolution: Done Added the kitchensink archetype to the list of module in the parent pom > Kitchensink archetype is not listed in the modules of the parent pom > -------------------------------------------------------------------- > > Key: RF-12066 > URL: https://issues.jboss.org/browse/RF-12066 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: archetype > Affects Versions: 4.2.0.Final > Reporter: Juraj Huska > Assignee: Brian Leathem > Priority: Trivial > Fix For: 4.2.1.CR1 > > > The maven module _richfaces-archetype-kitchensink_ is not listed in the parent pom.xml in the modules section. > Therefore, can not be installed from the parent pom. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 17:59:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 21 Mar 2012 17:59:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12070) Kitschensink archetype - broken formatting of comments in generated pom.xml In-Reply-To: <561043984.20917.1332262367501.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1355861412.24042.1332367187345.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-12070. -------------------------------- Resolution: Done Reformatted the comments of the generated pom > Kitschensink archetype - broken formatting of comments in generated pom.xml > --------------------------------------------------------------------------- > > Key: RF-12070 > URL: https://issues.jboss.org/browse/RF-12070 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: archetype > Affects Versions: 4.2.0.Final > Reporter: Juraj Huska > Assignee: Brian Leathem > Priority: Trivial > Fix For: 4.2.1.CR1 > > Attachments: brokenFormatting.png > > > Comments in generated pom.xml from Kitschensink maven archetype have broken formatting. Please see the attachment. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 18:03:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 21 Mar 2012 18:03:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12075) Kitchensink archetype - link for JBoss AS 7 project site is broken In-Reply-To: <1802298851.23317.1332347447560.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1185296079.24044.1332367427297.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-12075. -------------------------------- Resolution: Done > Kitchensink archetype - link for JBoss AS 7 project site is broken > ------------------------------------------------------------------ > > Key: RF-12075 > URL: https://issues.jboss.org/browse/RF-12075 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: archetype > Affects Versions: 4.2.0.Final > Reporter: Juraj Huska > Assignee: Brian Leathem > Priority: Trivial > Fix For: 4.2.1.CR1 > > > The link for JBoss AS 7 project site, which is suited in the find out more section is broken, and points to the: > {noformat}http://localhost:8080/kitchen-sink-community/jboss.org/jbossas{noformat} > It should point to http://www.jboss.org/jbossas > It is caused by missing http://www prefix. It is in the facelet page (about.xhtml), particularly line 16: > {code:xml} >
  • JBoss AS 7 project site
    • > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 18:08:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 21 Mar 2012 18:08:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11833) Label for calendar results in non-valid markup In-Reply-To: <1824573501.21859.1324327990123.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1849235180.24047.1332367727889.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-11833: ------------------------------- Priority: Major (was: Trivial) > Label for calendar results in non-valid markup > ---------------------------------------------- > > Key: RF-11833 > URL: https://issues.jboss.org/browse/RF-11833 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.1.0.Final > Reporter: Pavol Pitonak > Assignee: Brian Leathem > Fix For: 4.2.1.CR1 > > > The code in first code snippet results in markup below which is not valid. The for attribute of the label element must refer to a form control, e.g. the actual input inside calendar (that with ID dateForm:fromDateInputDate). > {code:xml} > > > {code} > {code:xml} > > > > > ... > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 18:14:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Abdullah_=C4=B0lhanl=C4=B1_=28JIRA=29?=) Date: Wed, 21 Mar 2012 18:14:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12071) a4j:outputPanel h:inputText render problem In-Reply-To: <1254741604.22548.1332331187494.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1941425204.24050.1332368087305.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678492#comment-12678492 ] Abdullah ?lhanl? commented on RF-12071: --------------------------------------- It is ok. I ll try these as soon as posibble. Then I ll post result on these topic. Thank you so much. > a4j:outputPanel h:inputText render problem > ------------------------------------------ > > Key: RF-12071 > URL: https://issues.jboss.org/browse/RF-12071 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Reporter: Abdullah ?lhanl? > Labels: waiting_on_user > > Create dynamic screen with JSF is so hard and painfull. > I used a4j:outputPanel so many times. > Today i am trying to create dynamic screen based on combo selected value. When value is for example option1 it generate inputText, otherwise comboBox. > But i face to rendered problem son many times. Problem is on submited object value. > My problem code like these: > {code} > > > valueChangeListener="#{conditionKeyBean.compTypeChanged}"> > > render="checkableLabel,checkableField" /> > > > rendered="#{conditionKeyBean.checkable}" /> > > > > > > > > {code} > Problem detail: > Captionvalue is unique in database. > When exception is throwed from back end(JPA uniquness error). I pops up error to user. Then user edit captionValue and try to resubmit. But captionValue is not change, even user changed it. When i remove rendered="#{conditionKeyBean.checkable}" problem is solved. rendered is not working correctly i think. > How can i solve this problem? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 18:14:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Abdullah_=C4=B0lhanl=C4=B1_=28JIRA=29?=) Date: Wed, 21 Mar 2012 18:14:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12071) a4j:outputPanel h:inputText render problem In-Reply-To: <1254741604.22548.1332331187494.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1676158874.24052.1332368087381.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678492#comment-12678492 ] Abdullah ?lhanl? edited comment on RF-12071 at 3/21/12 6:14 PM: ---------------------------------------------------------------- It is ok. I ll try these as soon as posibble. Then I ll post result on this topic. Thank you so much. was (Author: ailhanli): It is ok. I ll try these as soon as posibble. Then I ll post result on these topic. Thank you so much. > a4j:outputPanel h:inputText render problem > ------------------------------------------ > > Key: RF-12071 > URL: https://issues.jboss.org/browse/RF-12071 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Reporter: Abdullah ?lhanl? > Labels: waiting_on_user > > Create dynamic screen with JSF is so hard and painfull. > I used a4j:outputPanel so many times. > Today i am trying to create dynamic screen based on combo selected value. When value is for example option1 it generate inputText, otherwise comboBox. > But i face to rendered problem son many times. Problem is on submited object value. > My problem code like these: > {code} > > > valueChangeListener="#{conditionKeyBean.compTypeChanged}"> > > render="checkableLabel,checkableField" /> > > > rendered="#{conditionKeyBean.checkable}" /> > > > > > > > > {code} > Problem detail: > Captionvalue is unique in database. > When exception is throwed from back end(JPA uniquness error). I pops up error to user. Then user edit captionValue and try to resubmit. But captionValue is not change, even user changed it. When i remove rendered="#{conditionKeyBean.checkable}" problem is solved. rendered is not working correctly i think. > How can i solve this problem? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 21 18:23:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 21 Mar 2012 18:23:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12052) rich:TabPanel - HTML comments should be supported inside the tabPanel In-Reply-To: <1018200636.12395.1331837267498.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <857285707.24055.1332368627266.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-12052. -------------------------------- Resolution: Done Added in instance check to the AbstractTogglePanel#isActiveItem method > rich:TabPanel - HTML comments should be supported inside the tabPanel > --------------------------------------------------------------------- > > Key: RF-12052 > URL: https://issues.jboss.org/browse/RF-12052 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-output > Reporter: Jean ANDRE > Assignee: Brian Leathem > Priority: Trivial > Fix For: 4.2.1.CR1 > > > Is it possible to support HTML comment inside a tabPanel. Because it causes this error if we but comments as shown below. The error is: > E org.richfaces.context.ExtendedPartialViewContextImpl processPartialExecutePhase > java.lang.IllegalArgumentException > at org.richfaces.component.AbstractTogglePanel.getChildName(AbstractTogglePanel.java:490) > {code} > switchType="ajax" > headerPosition="top" > itemChangeListener="#{viewItemController.doItemChangeListener}" > activeItem="#{viewItemController.activeTab}" > immediate="true"> > > > > > > {code} > Or at least, give us a clear error message as we did for tabPanel and the form tag. > Thank you. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 22 03:56:47 2012 From: jira-events at lists.jboss.org (SBS JIRA Integration (JIRA)) Date: Thu, 22 Mar 2012 03:56:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11469) autocomplete method does not resolve bean if ui:included In-Reply-To: <1637048952.14156.1318020615972.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <2062245278.24381.1332403007810.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] SBS JIRA Integration updated RF-11469: -------------------------------------- Forum Reference: https://community.jboss.org/message/593359#593359, http://community.jboss.org/thread/169729?tstart=0 (was: http://community.jboss.org/thread/169729?tstart=0) > autocomplete method does not resolve bean if ui:included > -------------------------------------------------------- > > Key: RF-11469 > URL: https://issues.jboss.org/browse/RF-11469 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.0.0.Final > Reporter: u j > Fix For: 4.3-Tracking > > > A bean parameter in the autocomplete method is not resolved if the rich:autocomplete is part of a ui:include. > {code} > > > > {code} > searchlocation.xhtml contains: > {code} > > {code} > The value binding works, but the binding in the autocompleteMethod gives: > {code} > 15:26:15,809 SEVERE [org.richfaces.log.Renderkit] (ajp-127.0.0.1-127.0.0.1-8009-1) Target Unreachable, identifier 'bean' resolved to null: javax.el.PropertyNotFoundException: Target Unreachable, identifier 'bean' resolved to null > at org.apache.el.parser.AstValue.getTarget(AstValue.java:75) [jbossweb-7.0.1.Final.jar:7.0.1.Final] > at org.apache.el.parser.AstValue.invoke(AstValue.java:183) [jbossweb-7.0.1.Final.jar:7.0.1.Final] > at org.apache.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:276) [jbossweb-7.0.1.Final.jar:7.0.1.Final] > at org.jboss.weld.util.el.ForwardingMethodExpression.invoke(ForwardingMethodExpression.java:43) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.jboss.weld.el.WeldMethodExpression.invoke(WeldMethodExpression.java:56) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.richfaces.renderkit.AutocompleteRendererBase.getItems(AutocompleteRendererBase.java:105) [richfaces-components-ui-4.0.0-20110322.220419-243.jar:] > at org.richfaces.renderkit.AutocompleteRendererBase.encodeItems(AutocompleteRendererBase.java:160) [richfaces-components-ui-4.0.0-20110322.220419-243.jar:] > at org.richfaces.renderkit.AutocompleteRendererBase.encodeMetaComponent(AutocompleteRendererBase.java:271) [richfaces-components-ui-4.0.0-20110322.220419-243.jar:] > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 22 04:12:49 2012 From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA)) Date: Thu, 22 Mar 2012 04:12:49 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11995) autocomplete only displaying select popup on minChars + 1 In-Reply-To: <1491446387.30098.1329818436170.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <2065727938.24415.1332403969075.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavol Pitonak reassigned RF-11995: ---------------------------------- Assignee: Juraj Huska (was: Pavol Pitonak) > autocomplete only displaying select popup on minChars + 1 > --------------------------------------------------------- > > Key: RF-11995 > URL: https://issues.jboss.org/browse/RF-11995 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.2.0.CR1 > Environment: Glassfish 3.1.1 / Mojarra 2.1.7 / Chrome browser > Reporter: Brendan Healey > Assignee: Juraj Huska > > I'm running the following test with org.richfaces.resourceOptimization.enabled > set to true. > After typing the minChars number of characters (2), I see an ajax request being > sent to the server and a response is successfully returned (observed using chrome > developer tools), but the popup selection list does not appear until minChars + 1 > (3) characters are entered. > Typing the third character causes a get request for combo_list_shadow.png to be > sent. > {code} > mode="cachedAjax" > var="var" > fetchValue="#{var.name}" > minChars="2" > autocompleteMethod="#{bean.doSearch}"> > > > > > {code} > w > I've only just migrated to rich:autocomplete from a self-developed custom component > so I don't know if this behavior existed in any richfaces version prior to 4.2.0.CR1. > I tried this on the showcase example here: > http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=autocomplete&skin=blueSky > (in the first autocomplete on the page) and could not reproduce the behavior. > I tried using mode="ajax" and mode="client" and could not get the popup to show in > either case, although I'd only ever want to use cachedAjax mode normally. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 22 04:55:47 2012 From: jira-events at lists.jboss.org (Vladimir Rom (JIRA)) Date: Thu, 22 Mar 2012 04:55:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12077) Selection in extendedDataTable doesn't work in Chrome Message-ID: <2021407965.24539.1332406547698.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Vladimir Rom created RF-12077: --------------------------------- Summary: Selection in extendedDataTable doesn't work in Chrome Key: RF-12077 URL: https://issues.jboss.org/browse/RF-12077 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-tables Affects Versions: 4.2.0.Final Environment: Windows XP. JBoss AS 7 Chrome 17.0.963.83 Reporter: Vladimir Rom Priority: Blocker JavaScript error in console on rendered page with Uncaught TypeError: Cannot read property 'length' of null richfaces.utils.getCSSRule extendedDataTable.js.jsf:40 richfaces.ui.ExtendedDataTable.richfaces.BaseComponent.extendClass.initialize extendedDataTable.js.jsf:362 jQuery.extend.proxy.proxyjquery.js.jsf:814 jQuery.Callbacks.firejquery.js.jsf:1046 jQuery.Callbacks.self.fireWithjquery.js.jsf:1164 jQuery.extend.readyjquery.js.jsf:435 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 22 05:19:48 2012 From: jira-events at lists.jboss.org (Jan Papousek (JIRA)) Date: Thu, 22 Mar 2012 05:19:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11645) Mobile Showcase and rich:orderingList - selecting an item doesn't enable the moving buttons In-Reply-To: <1473358329.50052.1320248685965.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <816422779.24698.1332407988194.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Papousek resolved RF-11645. ------------------------------- Resolution: Cannot Reproduce Bug > Mobile Showcase and rich:orderingList - selecting an item doesn't enable the moving buttons > ------------------------------------------------------------------------------------------- > > Key: RF-11645 > URL: https://issues.jboss.org/browse/RF-11645 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects, mobile, showcase > Affects Versions: 4.1.0.Milestone4, 4.2.0.CR1 > Environment: iPad 4.3.3 (8J3) > iPhone 4.2.1 (8C148) > JBoss AS 7.1.0.CR1b > Reporter: Jan Papousek > Assignee: Jan Papousek > Attachments: ipad-orderingList.png, iPhone-orderingList.png, iphone-orderingList.png, Screen Shot 2011-11-21 at 10.27.21 PM.PNG, Screen Shot 2011-11-21 at 10.27.35 PM.PNG > > > After selecting an item from ordering list, the moving buttons next to the list should be enabled. This doesn't work on iPhone and iPad. > It works on Android. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 22 05:37:48 2012 From: jira-events at lists.jboss.org (Peter Chuang (JIRA)) Date: Thu, 22 Mar 2012 05:37:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-7955) ExtendedDataTable : Only first column correctly resize In-Reply-To: <482767548.1254848329252.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com> Message-ID: <700535752.24777.1332409068153.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-7955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678566#comment-12678566 ] Peter Chuang commented on RF-7955: ---------------------------------- Hi Ilya, Looks like this is still a problem with FF 11 and 12 even with the recommended DocType declaration. In fact, Exadel's LiveDemo site shows the problem. Much appreciated! > ExtendedDataTable : Only first column correctly resize > ------------------------------------------------------ > > Key: RF-7955 > URL: https://issues.jboss.org/browse/RF-7955 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 3.3.2.CR1, 3.3.2.GA > Environment: JSF RI 1.2_13 > Facelets 1.1.14 (with .jspx files) > Glassfish > Jdk 1.6 > Reporter: Nicolas Gaudin > Assignee: Pavel Yaschenko > Labels: EDT, columns, extendedDataTable > Fix For: 3.3.2.GA > > Attachments: EDT columns resizing issue.jpg > > > Hi, > During my test to deliver, I discovered that the columns of all my EDTs would not resize correctly. > More precisely, the first column resizes without any problem but the others resize WITHOUT resizing the header. > I must mention that my EDT use value binding for dynamic column creation. > My actions that generated this issue: > - moved from jsp to facelets (with jspx extension) > - upgraded to JSF 1.2_13 > This affected 3.3.2.CR1, the version I was using. > I then upgraded to 3.3.2.GA to check if this would fix but no luck > Also, I thought that 3.3.2.GA would full scrolling support for EDT (horizontal mainly) > Is that the case? > Could you please confirm? > May thanks in advance -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 22 06:05:47 2012 From: jira-events at lists.jboss.org (Brendan Healey (JIRA)) Date: Thu, 22 Mar 2012 06:05:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12063) rich:notifyMessages not displaying error from valueChangeListener In-Reply-To: <71281469.18246.1332180647276.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <477883507.24801.1332410747476.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678570#comment-12678570 ] Brendan Healey commented on RF-12063: ------------------------------------- Clicking into and out of the input should cause the value change listener to fire, however no message appears on the screen. Simply adding a commandButton, and copying the message generation code from the value change listener into an action= method and clicking the button will cause a notifyMessage to appear on screen. Bean.java --------- @Named @ViewScoped public class Bean implements Serializable { public void testVcl(ValueChangeEvent event) { //Log.log("testVcl"); FacesMessage message = getFacesMessage("helloText"); message.setSeverity(FacesMessage.SEVERITY_ERROR); FacesContext.getCurrentInstance().addMessage(null, message); } public String testAction() { //Log.log("testVcl"); FacesMessage message = getFacesMessage("helloText"); message.setSeverity(FacesMessage.SEVERITY_ERROR); FacesContext.getCurrentInstance().addMessage(null, message); } public static FacesMessage getFacesMessage(String msgKey) { FacesMessage message = Messages.getMessage("messages", msgKey, null); return message; } Messages.java ------------- package uk.co.myproj.test; /** * * @author Brendan Healey * copied from Core JSF Geary/Horstmann p249 */ import java.text.MessageFormat; import java.util.Locale; import java.util.MissingResourceException; import java.util.ResourceBundle; import javax.faces.application.Application; import javax.faces.application.FacesMessage; import javax.faces.component.UIViewRoot; import javax.faces.context.FacesContext; public class Messages { public static FacesMessage getMessage(String bundleName, String resourceId, Object[] params) { FacesContext context = FacesContext.getCurrentInstance(); Application app = context.getApplication(); String appBundle = app.getMessageBundle(); Locale locale = getLocale(context); ClassLoader loader = getClassLoader(); String summary = getString(appBundle, bundleName, resourceId, locale, loader, params); if (summary == null) { summary = "???" + resourceId + "???"; } String detail = getString(appBundle, bundleName, resourceId + "_detail", locale, loader, params); return new FacesMessage(summary, detail); } public static String getString(String bundle, String resourceId, Object[] params) { FacesContext context = FacesContext.getCurrentInstance(); Application app = context.getApplication(); String appBundle = app.getMessageBundle(); Locale locale = getLocale(context); ClassLoader loader = getClassLoader(); return getString(appBundle, bundle, resourceId, locale, loader, params); } public static String getString(String bundle1, String bundle2, String resourceId, Locale locale, ClassLoader loader, Object[] params) { String resource = null; ResourceBundle bundle; if (bundle1 != null) { bundle = ResourceBundle.getBundle(bundle1, locale, loader); if (bundle != null) { try { resource = bundle.getString(resourceId); } catch (MissingResourceException ex) { } } } if (resource == null) { bundle = ResourceBundle.getBundle(bundle2, locale, loader); if (bundle != null) { try { resource = bundle.getString(resourceId); } catch (MissingResourceException ex) { } } } if (resource == null) { return null; // no match } if (params == null) { return resource; } MessageFormat formatter = new MessageFormat(resource, locale); return formatter.format(params); } public static Locale getLocale(FacesContext context) { Locale locale = null; UIViewRoot viewRoot = context.getViewRoot(); if (viewRoot != null) { locale = viewRoot.getLocale(); } if (locale == null) { locale = Locale.getDefault(); } return locale; } public static ClassLoader getClassLoader() { ClassLoader loader = Thread.currentThread().getContextClassLoader(); if (loader == null) { loader = ClassLoader.getSystemClassLoader(); } return loader; } } > rich:notifyMessages not displaying error from valueChangeListener > ----------------------------------------------------------------- > > Key: RF-12063 > URL: https://issues.jboss.org/browse/RF-12063 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.2.0.Final > Environment: Mojarra 2.1.7, RF 4.2.0.Final, Windows 7, Glassfish 3.1.2, Chrome browser. > Reporter: Brendan Healey > Labels: waiting_on_user > > I have a global notifyMessages in a template . > I log a global error in the usual way from a value change listener (process validations > phase): > FacesMessage message = getFacesMessage(errKey); > message.setSeverity(FacesMessage.SEVERITY_ERROR); > FacesContext.getCurrentInstance().addMessage(null, message); > but the error never appears. If I have an h:messages on the page which is ajax > rendered the message appears ok. > Regards, > Brendan. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 22 06:19:48 2012 From: jira-events at lists.jboss.org (roel croonenberghs (JIRA)) Date: Thu, 22 Mar 2012 06:19:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-9345) Richfaces HTTP Header Cache-Control settings, need 'public' In-Reply-To: <1197045230.163.1284232939713.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1990204311.24871.1332411588656.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-9345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678574#comment-12678574 ] roel croonenberghs commented on RF-9345: ---------------------------------------- any news on when this will be fixed? > Richfaces HTTP Header Cache-Control settings, need 'public' > ----------------------------------------------------------- > > Key: RF-9345 > URL: https://issues.jboss.org/browse/RF-9345 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: optimization > Affects Versions: 3.3.1, 3.3.2.CR1, 3.3.2.GA, 3.3.2.SR1, 3.3.3.BETA1, 3.3.3.CR1, 3.3.3.Final > Environment: This issue affect any web browser according to w3c specification > Reporter: igor regis > Assignee: Nick Belaevski > Fix For: 4.Future > > Attachments: RF-9345.patch > > > If an application is running over https the web browser will only cache on disk, the Richfaces resources, if and only if, the Cache-control header (present on http header) has the value "public" on it. Otherwise the web browser will perform in memory cache, so when user restarts the browser the application will need to request all the resources again. > For applications running on corporative network, manipulating sensitive information, it's mandatory the use of a secure connection through https protocol, and form better performance is necessary for Richfaces to provide it's resources with this "public" mark on cache-control tag. > According the w3c specs (http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.9.1) Richfaces resources may be classified as public content with non individual information. > Here (https://community.jboss.org/thread/150732?tstart=0) there is a discussion about this issue, as well as the point on Richfaces source code that need to be changed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 22 06:23:48 2012 From: jira-events at lists.jboss.org (emmanuel dufour (JIRA)) Date: Thu, 22 Mar 2012 06:23:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11592) RichFaces 4.1 Milestone changes for fileUpload component incompatible with Apache MyFaces Orchestra conversation scope In-Reply-To: <1839758620.29810.1319638185453.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <908561709.24903.1332411828106.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678577#comment-12678577 ] emmanuel dufour commented on RF-11592: -------------------------------------- This issue is not strictly related to myfaces, I have the same problem using mojarra 2.1.1 on glassfish 3.x and richfaces 4.1 and 4.2 (4.0 is fine but doesnt have rich:picklist so I cant go back !) {noformat} SEVERE: Exception parsing multipart request: Request prolog cannot be read org.richfaces.exception.FileUploadException: Exception parsing multipart request: Request prolog cannot be read at org.richfaces.request.MultipartRequestParser.parse(MultipartRequestParser.java:156) at org.richfaces.request.MultipartRequest25.parseIfNecessary(MultipartRequest25.java:77) at org.richfaces.request.MultipartRequest25.getParameter(MultipartRequest25.java:114) at com.sun.faces.context.RequestParameterMap.get(RequestParameterMap.java:75) at com.sun.faces.context.RequestParameterMap.get(RequestParameterMap.java:56) at java.util.Collections$UnmodifiableMap.get(Collections.java:1282) at com.sun.faces.application.view.MultiViewHandler.calculateRenderKitId(MultiViewHandler.java:220) at javax.faces.application.ViewHandlerWrapper.calculateRenderKitId(ViewHandlerWrapper.java:155) at com.sun.faces.context.FacesContextImpl.isPostback(FacesContextImpl.java:211) at javax.faces.context.FacesContextWrapper.isPostback(FacesContextWrapper.java:402) at com.sun.faces.lifecycle.RestoreViewPhase.execute(RestoreViewPhase.java:188) at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) at com.sun.faces.lifecycle.RestoreViewPhase.doPhase(RestoreViewPhase.java:116) at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:593) at org.apache.catalina.core.StandardWrapper.service(StandardWrapper.java:1542) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:343) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:217) at entities.util.SecurityFilter.doFilter(SecurityFilter.java:47) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:256) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:217) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:279) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:655) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:595) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:161) at org.apache.catalina.connector.CoyoteAdapter.doService(CoyoteAdapter.java:331) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:231) at com.sun.enterprise.v3.services.impl.ContainerMapper$AdapterCallable.call(ContainerMapper.java:317) at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:195) at com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:849) at com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:746) at com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:1045) at com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:228) at com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:137) at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:104) at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:90) at com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:79) at com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:54) at com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:59) at com.sun.grizzly.ContextTask.run(ContextTask.java:71) at com.sun.grizzly.util.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:532) at com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:513) at java.lang.Thread.run(Thread.java:662) Caused by: java.io.IOException: Request prolog cannot be read at org.richfaces.request.MultipartRequestParser.readProlog(MultipartRequestParser.java:270) at org.richfaces.request.MultipartRequestParser.initialize(MultipartRequestParser.java:172) at org.richfaces.request.MultipartRequestParser.parse(MultipartRequestParser.java:148) ... 43 more {noformat} > RichFaces 4.1 Milestone changes for fileUpload component incompatible with Apache MyFaces Orchestra conversation scope > ---------------------------------------------------------------------------------------------------------------------- > > Key: RF-11592 > URL: https://issues.jboss.org/browse/RF-11592 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.1.0.Milestone1, 4.1.0.Milestone2, 4.1.0.Milestone3 > Environment: Mojarra 2.1.3, JBoss AS 5.0.1, Apache MyFaces Orchestra 1.4, Spring 3.0.4 > Reporter: Joshua Brookes > Labels: fileUpload, multipart/form-data, orchestra, regression, richfaces, richfaces4 > Fix For: 4.3-Tracking > > Attachments: fileUploadWeb.zip, server.log > > > There is a compatibility issue with recent changes in RichFaces 4.1 Milestone 1 and Apache MyFaces Orchestra conversation scope feature. When including the Orchestra jar in the application the fileUpload component stops working. Orchestra bundles a faces-config.xml that enables 2 FacesContext Factories and multiple PhaseListeners. This did not pose a problem with RichFaces 4.0.0.Final. > Here is a stacktrace that shows the error: > {code} > Oct 25, 2011 11:45:01 AM org.richfaces.request.MultipartRequest25 parseIfNecessary > SEVERE: Exception parsing multipart request: Request prolog cannot be read > org.richfaces.exception.FileUploadException: Exception parsing multipart request: Request prolog cannot be read > at org.richfaces.request.MultipartRequestParser.parse(MultipartRequestParser.java:156) > at org.richfaces.request.MultipartRequest25.parseIfNecessary(MultipartRequest25.java:77) > at org.richfaces.request.MultipartRequest25.getParameter(MultipartRequest25.java:114) > at com.sun.faces.context.RequestParameterMap.containsKey(RequestParameterMap.java:99) > at java.util.Collections$UnmodifiableMap.containsKey(Collections.java:1280) > at org.apache.myfaces.orchestra.frameworkAdapter.jsf.JsfFrameworkAdapter.containsRequestParameterAttribute(JsfFrameworkAdapter.java:105) > at org.apache.myfaces.orchestra.conversation.ConversationManager.findConversationContextId(ConversationManager.java:169) > at org.apache.myfaces.orchestra.conversation.ConversationManager.getCurrentRootConversationContext(ConversationManager.java:580) > at org.apache.myfaces.orchestra.lib.jsf.ContextLockRequestHandler.init(ContextLockRequestHandler.java:87) > at org.apache.myfaces.orchestra.lib.jsf.OrchestraFacesContextFactory$1.(OrchestraFacesContextFactory.java:122) > at org.apache.myfaces.orchestra.lib.jsf.OrchestraFacesContextFactory.getFacesContext(OrchestraFacesContextFactory.java:103) > at org.apache.myfaces.orchestra.requestParameterProvider.jsf.RequestParameterFacesContextFactory.getFacesContext(RequestParameterFacesContextFactory.java:93) > at org.richfaces.context.FileUploadFacesContextFactory.getFacesContext(FileUploadFacesContextFactory.java:136) > at com.sun.faces.context.InjectionFacesContextFactory.getFacesContext(InjectionFacesContextFactory.java:121) > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:583) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:638) > at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:446) > at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:382) > at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:310) > at org.apache.catalina.core.StandardHostValve.custom(StandardHostValve.java:416) > at org.apache.catalina.core.StandardHostValve.status(StandardHostValve.java:342) > at org.apache.catalina.core.StandardHostValve.throwable(StandardHostValve.java:286) > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:141) > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) > at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330) > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829) > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:598) > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) > at java.lang.Thread.run(Thread.java:619) > Caused by: java.io.IOException: Request prolog cannot be read > at org.richfaces.request.MultipartRequestParser.readProlog(MultipartRequestParser.java:270) > at org.richfaces.request.MultipartRequestParser.initialize(MultipartRequestParser.java:172) > at org.richfaces.request.MultipartRequestParser.parse(MultipartRequestParser.java:148) > ... 32 more > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 22 06:27:47 2012 From: jira-events at lists.jboss.org (emmanuel dufour (JIRA)) Date: Thu, 22 Mar 2012 06:27:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11592) RichFaces 4.1 Milestone changes for fileUpload component incompatible with Apache MyFaces Orchestra conversation scope In-Reply-To: <1839758620.29810.1319638185453.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <176646360.24930.1332412067570.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678579#comment-12678579 ] emmanuel dufour commented on RF-11592: -------------------------------------- test > RichFaces 4.1 Milestone changes for fileUpload component incompatible with Apache MyFaces Orchestra conversation scope > ---------------------------------------------------------------------------------------------------------------------- > > Key: RF-11592 > URL: https://issues.jboss.org/browse/RF-11592 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.1.0.Milestone1, 4.1.0.Milestone2, 4.1.0.Milestone3 > Environment: Mojarra 2.1.3, JBoss AS 5.0.1, Apache MyFaces Orchestra 1.4, Spring 3.0.4 > Reporter: Joshua Brookes > Labels: fileUpload, multipart/form-data, orchestra, regression, richfaces, richfaces4 > Fix For: 4.3-Tracking > > Attachments: fileUploadWeb.zip, server.log > > > There is a compatibility issue with recent changes in RichFaces 4.1 Milestone 1 and Apache MyFaces Orchestra conversation scope feature. When including the Orchestra jar in the application the fileUpload component stops working. Orchestra bundles a faces-config.xml that enables 2 FacesContext Factories and multiple PhaseListeners. This did not pose a problem with RichFaces 4.0.0.Final. > Here is a stacktrace that shows the error: > {code} > Oct 25, 2011 11:45:01 AM org.richfaces.request.MultipartRequest25 parseIfNecessary > SEVERE: Exception parsing multipart request: Request prolog cannot be read > org.richfaces.exception.FileUploadException: Exception parsing multipart request: Request prolog cannot be read > at org.richfaces.request.MultipartRequestParser.parse(MultipartRequestParser.java:156) > at org.richfaces.request.MultipartRequest25.parseIfNecessary(MultipartRequest25.java:77) > at org.richfaces.request.MultipartRequest25.getParameter(MultipartRequest25.java:114) > at com.sun.faces.context.RequestParameterMap.containsKey(RequestParameterMap.java:99) > at java.util.Collections$UnmodifiableMap.containsKey(Collections.java:1280) > at org.apache.myfaces.orchestra.frameworkAdapter.jsf.JsfFrameworkAdapter.containsRequestParameterAttribute(JsfFrameworkAdapter.java:105) > at org.apache.myfaces.orchestra.conversation.ConversationManager.findConversationContextId(ConversationManager.java:169) > at org.apache.myfaces.orchestra.conversation.ConversationManager.getCurrentRootConversationContext(ConversationManager.java:580) > at org.apache.myfaces.orchestra.lib.jsf.ContextLockRequestHandler.init(ContextLockRequestHandler.java:87) > at org.apache.myfaces.orchestra.lib.jsf.OrchestraFacesContextFactory$1.(OrchestraFacesContextFactory.java:122) > at org.apache.myfaces.orchestra.lib.jsf.OrchestraFacesContextFactory.getFacesContext(OrchestraFacesContextFactory.java:103) > at org.apache.myfaces.orchestra.requestParameterProvider.jsf.RequestParameterFacesContextFactory.getFacesContext(RequestParameterFacesContextFactory.java:93) > at org.richfaces.context.FileUploadFacesContextFactory.getFacesContext(FileUploadFacesContextFactory.java:136) > at com.sun.faces.context.InjectionFacesContextFactory.getFacesContext(InjectionFacesContextFactory.java:121) > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:583) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:638) > at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:446) > at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:382) > at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:310) > at org.apache.catalina.core.StandardHostValve.custom(StandardHostValve.java:416) > at org.apache.catalina.core.StandardHostValve.status(StandardHostValve.java:342) > at org.apache.catalina.core.StandardHostValve.throwable(StandardHostValve.java:286) > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:141) > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) > at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330) > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829) > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:598) > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) > at java.lang.Thread.run(Thread.java:619) > Caused by: java.io.IOException: Request prolog cannot be read > at org.richfaces.request.MultipartRequestParser.readProlog(MultipartRequestParser.java:270) > at org.richfaces.request.MultipartRequestParser.initialize(MultipartRequestParser.java:172) > at org.richfaces.request.MultipartRequestParser.parse(MultipartRequestParser.java:148) > ... 32 more > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 22 06:52:47 2012 From: jira-events at lists.jboss.org (emmanuel dufour (JIRA)) Date: Thu, 22 Mar 2012 06:52:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11592) RichFaces 4.1 Milestone changes for fileUpload component incompatible with Apache MyFaces Orchestra conversation scope In-Reply-To: <1839758620.29810.1319638185453.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1362394958.25022.1332413567696.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678579#comment-12678579 ] emmanuel dufour edited comment on RF-11592 at 3/22/12 6:52 AM: --------------------------------------------------------------- as pointed above, this is a glassfish problem, patch (webcore.jar) and install instruction there : http://java.net/jira/browse/GLASSFISH-18444 was (Author: emmanueldufour): test > RichFaces 4.1 Milestone changes for fileUpload component incompatible with Apache MyFaces Orchestra conversation scope > ---------------------------------------------------------------------------------------------------------------------- > > Key: RF-11592 > URL: https://issues.jboss.org/browse/RF-11592 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.1.0.Milestone1, 4.1.0.Milestone2, 4.1.0.Milestone3 > Environment: Mojarra 2.1.3, JBoss AS 5.0.1, Apache MyFaces Orchestra 1.4, Spring 3.0.4 > Reporter: Joshua Brookes > Labels: fileUpload, multipart/form-data, orchestra, regression, richfaces, richfaces4 > Fix For: 4.3-Tracking > > Attachments: fileUploadWeb.zip, server.log > > > There is a compatibility issue with recent changes in RichFaces 4.1 Milestone 1 and Apache MyFaces Orchestra conversation scope feature. When including the Orchestra jar in the application the fileUpload component stops working. Orchestra bundles a faces-config.xml that enables 2 FacesContext Factories and multiple PhaseListeners. This did not pose a problem with RichFaces 4.0.0.Final. > Here is a stacktrace that shows the error: > {code} > Oct 25, 2011 11:45:01 AM org.richfaces.request.MultipartRequest25 parseIfNecessary > SEVERE: Exception parsing multipart request: Request prolog cannot be read > org.richfaces.exception.FileUploadException: Exception parsing multipart request: Request prolog cannot be read > at org.richfaces.request.MultipartRequestParser.parse(MultipartRequestParser.java:156) > at org.richfaces.request.MultipartRequest25.parseIfNecessary(MultipartRequest25.java:77) > at org.richfaces.request.MultipartRequest25.getParameter(MultipartRequest25.java:114) > at com.sun.faces.context.RequestParameterMap.containsKey(RequestParameterMap.java:99) > at java.util.Collections$UnmodifiableMap.containsKey(Collections.java:1280) > at org.apache.myfaces.orchestra.frameworkAdapter.jsf.JsfFrameworkAdapter.containsRequestParameterAttribute(JsfFrameworkAdapter.java:105) > at org.apache.myfaces.orchestra.conversation.ConversationManager.findConversationContextId(ConversationManager.java:169) > at org.apache.myfaces.orchestra.conversation.ConversationManager.getCurrentRootConversationContext(ConversationManager.java:580) > at org.apache.myfaces.orchestra.lib.jsf.ContextLockRequestHandler.init(ContextLockRequestHandler.java:87) > at org.apache.myfaces.orchestra.lib.jsf.OrchestraFacesContextFactory$1.(OrchestraFacesContextFactory.java:122) > at org.apache.myfaces.orchestra.lib.jsf.OrchestraFacesContextFactory.getFacesContext(OrchestraFacesContextFactory.java:103) > at org.apache.myfaces.orchestra.requestParameterProvider.jsf.RequestParameterFacesContextFactory.getFacesContext(RequestParameterFacesContextFactory.java:93) > at org.richfaces.context.FileUploadFacesContextFactory.getFacesContext(FileUploadFacesContextFactory.java:136) > at com.sun.faces.context.InjectionFacesContextFactory.getFacesContext(InjectionFacesContextFactory.java:121) > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:583) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:638) > at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:446) > at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:382) > at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:310) > at org.apache.catalina.core.StandardHostValve.custom(StandardHostValve.java:416) > at org.apache.catalina.core.StandardHostValve.status(StandardHostValve.java:342) > at org.apache.catalina.core.StandardHostValve.throwable(StandardHostValve.java:286) > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:141) > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) > at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330) > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829) > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:598) > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) > at java.lang.Thread.run(Thread.java:619) > Caused by: java.io.IOException: Request prolog cannot be read > at org.richfaces.request.MultipartRequestParser.readProlog(MultipartRequestParser.java:270) > at org.richfaces.request.MultipartRequestParser.initialize(MultipartRequestParser.java:172) > at org.richfaces.request.MultipartRequestParser.parse(MultipartRequestParser.java:148) > ... 32 more > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 22 07:25:47 2012 From: jira-events at lists.jboss.org (Brendan Healey (JIRA)) Date: Thu, 22 Mar 2012 07:25:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12063) rich:notifyMessages not displaying error from valueChangeListener In-Reply-To: <71281469.18246.1332180647276.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <695269179.25122.1332415547433.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678570#comment-12678570 ] Brendan Healey edited comment on RF-12063 at 3/22/12 7:24 AM: -------------------------------------------------------------- Clicking into and out of the input should cause the value change listener to fire, however no message appears on the screen. Simply adding a commandButton, and copying the message generation code from the value change listener into an action= method and clicking the button will cause a notifyMessage to appear on screen. Bean.java --------- @Named @ViewScoped public class Bean implements Serializable { public void testVcl(ValueChangeEvent event) { //Log.log("testVcl"); FacesMessage message = getFacesMessage("helloText"); message.setSeverity(FacesMessage.SEVERITY_ERROR); FacesContext.getCurrentInstance().addMessage(null, message); } public String testAction() { //Log.log("testVcl"); FacesMessage message = getFacesMessage("helloText"); message.setSeverity(FacesMessage.SEVERITY_ERROR); FacesContext.getCurrentInstance().addMessage(null, message); return null; } public static FacesMessage getFacesMessage(String msgKey) { FacesMessage message = Messages.getMessage("messages", msgKey, null); return message; } Messages.java ------------- package uk.co.myproj.test; /** * * @author Brendan Healey * copied from Core JSF Geary/Horstmann p249 */ import java.text.MessageFormat; import java.util.Locale; import java.util.MissingResourceException; import java.util.ResourceBundle; import javax.faces.application.Application; import javax.faces.application.FacesMessage; import javax.faces.component.UIViewRoot; import javax.faces.context.FacesContext; public class Messages { public static FacesMessage getMessage(String bundleName, String resourceId, Object[] params) { FacesContext context = FacesContext.getCurrentInstance(); Application app = context.getApplication(); String appBundle = app.getMessageBundle(); Locale locale = getLocale(context); ClassLoader loader = getClassLoader(); String summary = getString(appBundle, bundleName, resourceId, locale, loader, params); if (summary == null) { summary = "???" + resourceId + "???"; } String detail = getString(appBundle, bundleName, resourceId + "_detail", locale, loader, params); return new FacesMessage(summary, detail); } public static String getString(String bundle, String resourceId, Object[] params) { FacesContext context = FacesContext.getCurrentInstance(); Application app = context.getApplication(); String appBundle = app.getMessageBundle(); Locale locale = getLocale(context); ClassLoader loader = getClassLoader(); return getString(appBundle, bundle, resourceId, locale, loader, params); } public static String getString(String bundle1, String bundle2, String resourceId, Locale locale, ClassLoader loader, Object[] params) { String resource = null; ResourceBundle bundle; if (bundle1 != null) { bundle = ResourceBundle.getBundle(bundle1, locale, loader); if (bundle != null) { try { resource = bundle.getString(resourceId); } catch (MissingResourceException ex) { } } } if (resource == null) { bundle = ResourceBundle.getBundle(bundle2, locale, loader); if (bundle != null) { try { resource = bundle.getString(resourceId); } catch (MissingResourceException ex) { } } } if (resource == null) { return null; // no match } if (params == null) { return resource; } MessageFormat formatter = new MessageFormat(resource, locale); return formatter.format(params); } public static Locale getLocale(FacesContext context) { Locale locale = null; UIViewRoot viewRoot = context.getViewRoot(); if (viewRoot != null) { locale = viewRoot.getLocale(); } if (locale == null) { locale = Locale.getDefault(); } return locale; } public static ClassLoader getClassLoader() { ClassLoader loader = Thread.currentThread().getContextClassLoader(); if (loader == null) { loader = ClassLoader.getSystemClassLoader(); } return loader; } } was (Author: healeyb): Clicking into and out of the input should cause the value change listener to fire, however no message appears on the screen. Simply adding a commandButton, and copying the message generation code from the value change listener into an action= method and clicking the button will cause a notifyMessage to appear on screen. Bean.java --------- @Named @ViewScoped public class Bean implements Serializable { public void testVcl(ValueChangeEvent event) { //Log.log("testVcl"); FacesMessage message = getFacesMessage("helloText"); message.setSeverity(FacesMessage.SEVERITY_ERROR); FacesContext.getCurrentInstance().addMessage(null, message); } public String testAction() { //Log.log("testVcl"); FacesMessage message = getFacesMessage("helloText"); message.setSeverity(FacesMessage.SEVERITY_ERROR); FacesContext.getCurrentInstance().addMessage(null, message); } public static FacesMessage getFacesMessage(String msgKey) { FacesMessage message = Messages.getMessage("messages", msgKey, null); return message; } Messages.java ------------- package uk.co.myproj.test; /** * * @author Brendan Healey * copied from Core JSF Geary/Horstmann p249 */ import java.text.MessageFormat; import java.util.Locale; import java.util.MissingResourceException; import java.util.ResourceBundle; import javax.faces.application.Application; import javax.faces.application.FacesMessage; import javax.faces.component.UIViewRoot; import javax.faces.context.FacesContext; public class Messages { public static FacesMessage getMessage(String bundleName, String resourceId, Object[] params) { FacesContext context = FacesContext.getCurrentInstance(); Application app = context.getApplication(); String appBundle = app.getMessageBundle(); Locale locale = getLocale(context); ClassLoader loader = getClassLoader(); String summary = getString(appBundle, bundleName, resourceId, locale, loader, params); if (summary == null) { summary = "???" + resourceId + "???"; } String detail = getString(appBundle, bundleName, resourceId + "_detail", locale, loader, params); return new FacesMessage(summary, detail); } public static String getString(String bundle, String resourceId, Object[] params) { FacesContext context = FacesContext.getCurrentInstance(); Application app = context.getApplication(); String appBundle = app.getMessageBundle(); Locale locale = getLocale(context); ClassLoader loader = getClassLoader(); return getString(appBundle, bundle, resourceId, locale, loader, params); } public static String getString(String bundle1, String bundle2, String resourceId, Locale locale, ClassLoader loader, Object[] params) { String resource = null; ResourceBundle bundle; if (bundle1 != null) { bundle = ResourceBundle.getBundle(bundle1, locale, loader); if (bundle != null) { try { resource = bundle.getString(resourceId); } catch (MissingResourceException ex) { } } } if (resource == null) { bundle = ResourceBundle.getBundle(bundle2, locale, loader); if (bundle != null) { try { resource = bundle.getString(resourceId); } catch (MissingResourceException ex) { } } } if (resource == null) { return null; // no match } if (params == null) { return resource; } MessageFormat formatter = new MessageFormat(resource, locale); return formatter.format(params); } public static Locale getLocale(FacesContext context) { Locale locale = null; UIViewRoot viewRoot = context.getViewRoot(); if (viewRoot != null) { locale = viewRoot.getLocale(); } if (locale == null) { locale = Locale.getDefault(); } return locale; } public static ClassLoader getClassLoader() { ClassLoader loader = Thread.currentThread().getContextClassLoader(); if (loader == null) { loader = ClassLoader.getSystemClassLoader(); } return loader; } } > rich:notifyMessages not displaying error from valueChangeListener > ----------------------------------------------------------------- > > Key: RF-12063 > URL: https://issues.jboss.org/browse/RF-12063 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.2.0.Final > Environment: Mojarra 2.1.7, RF 4.2.0.Final, Windows 7, Glassfish 3.1.2, Chrome browser. > Reporter: Brendan Healey > Labels: waiting_on_user > > I have a global notifyMessages in a template . > I log a global error in the usual way from a value change listener (process validations > phase): > FacesMessage message = getFacesMessage(errKey); > message.setSeverity(FacesMessage.SEVERITY_ERROR); > FacesContext.getCurrentInstance().addMessage(null, message); > but the error never appears. If I have an h:messages on the page which is ajax > rendered the message appears ok. > Regards, > Brendan. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 22 08:10:47 2012 From: jira-events at lists.jboss.org (Jean ANDRE (JIRA)) Date: Thu, 22 Mar 2012 08:10:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12038) IE8 - Object does not support this property or method - a4j:jsFunction In-Reply-To: <1674243330.3069.1331568048477.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <975804099.25246.1332418247825.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678625#comment-12678625 ] Jean ANDRE commented on RF-12038: --------------------------------- Is it possible to add a check for null (NPE) before calling if(!element.name) to see if the case can be resolved like this? - Could you please try it?. See the screen shot above this comment:(ScreenShot_RF-12038.png) - Thank you very much. > IE8 - Object does not support this property or method - a4j:jsFunction > ---------------------------------------------------------------------- > > Key: RF-12038 > URL: https://issues.jboss.org/browse/RF-12038 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.2.0.Final > Environment: cssparser-0.9.6- guava-11.0.1 - hibernate-validator-4.2.0.Final - JSF/Mojarra 2.1.6 - springframework-3.0.6.RELEASE - sac-1.3 - Windows 7 - IE 8.0.1.7601.17514 > Reporter: Jean ANDRE > Fix For: 4.2.1.CR1 > > Attachments: index.xhtml, NestedWeb.zip, NestedWeb_RF-12038.zip, ScreenShot_RF-12038.png > > > Under IE8, IE reports the following error message due to a javascript error. However, the page are well displayed and the application is running ok. > Object doesn't support this property or method line 177 caracter 1 > Object doesn't support this property or method line 177 caracter 99 > Under IE Debugger, the line is: > {code} > closeTab=function(tabId){RichFaces.ajax("closeTab",null,{"incId":"1","parameters":{"tabId":tabId} } )};< > The caracter 99, is..............................................................................| (here) > {code} > This is a code generated by a4j:jsFunction from the XHTML > {code} > > > > > > > {code} > The rendered code is : > {code} > > > > {code} > See also this link as we got almost a similar: https://bugzilla.redhat.com/show_bug.cgi?id=601360. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 22 08:12:48 2012 From: jira-events at lists.jboss.org (Jean ANDRE (JIRA)) Date: Thu, 22 Mar 2012 08:12:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12060) element is null message when closing tab from an event click In-Reply-To: <1849991598.17427.1332167088202.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <877413323.25249.1332418368117.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678626#comment-12678626 ] Jean ANDRE commented on RF-12060: --------------------------------- Hello Brian, Based on RF-12038, is it possible to add a check for null (NPE) before calling if(!element.name) to see if the case can be resolved like this? - Could you please try it?. Thank you very much and let me know your decision. > element is null message when closing tab from an event click > ------------------------------------------------------------ > > Key: RF-12060 > URL: https://issues.jboss.org/browse/RF-12060 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.2.0.Final > Environment: Websphere 8.0.0.2 - RAD 8 - JSF Mojorra 2.1.6 - Spring 3.0.6 Final - Firefox 10.0.2 - Windows 7 (6.1 sp1) - AspectJ 1.6.12 / AJDT - RichFaces 4.2.0 Final - Hibernate Validator 4.2.0 Final > Reporter: Jean ANDRE > Fix For: 4.Future > > Attachments: NestedWeb_RF-12060.zip > > > There is a link to RF-11950. > We got the message "element is null" when we send a click event for closing a tab. To retrieve the id of the close button (an image), we use the function getElementById (because of RF-11950). The click function calls a javascript function declared by a4j:jsFunction (see index.hxtml file - close task). > This is the only information we have from firebug. When we close the tab directly by clicking on the close button/image, it works perfectly. > *Note :* Moreover, there is also a strange behavior related to generated id on close button/image. When we specified a fix id on the h:graphicImage, the first id is correct but there is no id on other close button/image from other tabs!???. Having a fix id should trigger a duplicate ID but as the ids are not generated on other tabs, it does not. > {code} > >   title="#{msg[task.uiActivity.headerKey]}" /> >   styleClass="closeButton" > onclick="closeTask('#{task.id}');event.stopPropagation();" /> > > > > > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 22 08:55:47 2012 From: jira-events at lists.jboss.org (Markus Staab (JIRA)) Date: Thu, 22 Mar 2012 08:55:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12078) action fired twice, when invoked by a a4j:commandButton residing in a tables' footer facet Message-ID: <729908046.25329.1332420947280.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Markus Staab created RF-12078: --------------------------------- Summary: action fired twice, when invoked by a a4j:commandButton residing in a tables' footer facet Key: RF-12078 URL: https://issues.jboss.org/browse/RF-12078 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 3.3.3.Final Environment: Liferay 5.2.4, Portlet 2.0, JSF 1.2, Richfaces 3.3.3 Reporter: Markus Staab when adding a a4j:commandButton inside a rich:databables footer-facet, the corresponding action will be invoked twice while the process action phase. The problem only occurs, when the commandButton 'process'es the datatable itself. {code} A HEADER SOME CONTENT IN THE ROW {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 22 09:25:47 2012 From: jira-events at lists.jboss.org (Markus Staab (JIRA)) Date: Thu, 22 Mar 2012 09:25:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12078) action fired twice, when invoked by a a4j:commandButton residing in a tables' footer facet In-Reply-To: <729908046.25329.1332420947280.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <2002649167.25463.1332422747978.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678644#comment-12678644 ] Markus Staab commented on RF-12078: ----------------------------------- the problem does not exist when the button resides in columns outside of the footer-facet. > action fired twice, when invoked by a a4j:commandButton residing in a tables' footer facet > ------------------------------------------------------------------------------------------ > > Key: RF-12078 > URL: https://issues.jboss.org/browse/RF-12078 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 3.3.3.Final > Environment: Liferay 5.2.4, Portlet 2.0, JSF 1.2, Richfaces 3.3.3 > Reporter: Markus Staab > > when adding a a4j:commandButton inside a rich:databables footer-facet, the corresponding action will be invoked twice while the process action phase. > The problem only occurs, when the commandButton 'process'es the datatable itself. > {code} > > > A HEADER > SOME CONTENT IN THE ROW > > > > > value="ADD ANOTHER ROW" > reRender="myTable" > action="#{form.addNewRow}" ajaxSingle="true" > process="myTable" > /> > > > > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 22 10:07:47 2012 From: jira-events at lists.jboss.org (Wesley Menezes (JIRA)) Date: Thu, 22 Mar 2012 10:07:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12079) ignores Message-ID: <2129957963.25561.1332425267314.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Wesley Menezes created RF-12079: ----------------------------------- Summary: ignores Key: RF-12079 URL: https://issues.jboss.org/browse/RF-12079 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-tree Affects Versions: 4.2.0.Final Environment: RichFaces 4.2.0 and JSF 2.2 with CDI (Bean type "javax.inject.Named") Application Server GlassFish Server Open Source Edition 3.1.2 (build 23) Reporter: Wesley Menezes In JSF with a and this have nested, if is applied in , the ajax listener isn't called. Obs. In RichFaces 4.2.0 Final showcase, the has the attribute "selectionChangeListener", but I found only "treeSelectionChangeListener" in jars of RichFaces (like attribute of the tag, or like a tag ) - "Component_Reference.pdf" is ok. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 22 13:11:54 2012 From: jira-events at lists.jboss.org (Juraj Huska (JIRA)) Date: Thu, 22 Mar 2012 13:11:54 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11995) autocomplete only displaying select popup on minChars + 1 In-Reply-To: <1491446387.30098.1329818436170.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1496597023.26561.1332436314161.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678740#comment-12678740 ] Juraj Huska commented on RF-11995: ---------------------------------- I was not able to reproduce the error, I tried all the mentioned settings and it is behaving fine. So the settings I tried it on: - Chrome 17 - Glassfish 3.1.1 with Mojarra 2.1.7 - also on JBoss AS 7.1.1.Final and Firefox - both with resource optimization and without I tried it on [this|https://github.com/jhuska/richfaces-sanbox/tree/RF-11995] example. > autocomplete only displaying select popup on minChars + 1 > --------------------------------------------------------- > > Key: RF-11995 > URL: https://issues.jboss.org/browse/RF-11995 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.2.0.CR1 > Environment: Glassfish 3.1.1 / Mojarra 2.1.7 / Chrome browser > Reporter: Brendan Healey > Assignee: Juraj Huska > > I'm running the following test with org.richfaces.resourceOptimization.enabled > set to true. > After typing the minChars number of characters (2), I see an ajax request being > sent to the server and a response is successfully returned (observed using chrome > developer tools), but the popup selection list does not appear until minChars + 1 > (3) characters are entered. > Typing the third character causes a get request for combo_list_shadow.png to be > sent. > {code} > mode="cachedAjax" > var="var" > fetchValue="#{var.name}" > minChars="2" > autocompleteMethod="#{bean.doSearch}"> > > > > > {code} > w > I've only just migrated to rich:autocomplete from a self-developed custom component > so I don't know if this behavior existed in any richfaces version prior to 4.2.0.CR1. > I tried this on the showcase example here: > http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=autocomplete&skin=blueSky > (in the first autocomplete on the page) and could not reproduce the behavior. > I tried using mode="ajax" and mode="client" and could not get the popup to show in > either case, although I'd only ever want to use cachedAjax mode normally. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 22 13:13:48 2012 From: jira-events at lists.jboss.org (Juraj Huska (JIRA)) Date: Thu, 22 Mar 2012 13:13:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11995) autocomplete only displaying select popup on minChars + 1 In-Reply-To: <1491446387.30098.1329818436170.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <442739532.26583.1332436428407.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj Huska reassigned RF-11995: -------------------------------- Assignee: (was: Juraj Huska) > autocomplete only displaying select popup on minChars + 1 > --------------------------------------------------------- > > Key: RF-11995 > URL: https://issues.jboss.org/browse/RF-11995 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.2.0.CR1 > Environment: Glassfish 3.1.1 / Mojarra 2.1.7 / Chrome browser > Reporter: Brendan Healey > > I'm running the following test with org.richfaces.resourceOptimization.enabled > set to true. > After typing the minChars number of characters (2), I see an ajax request being > sent to the server and a response is successfully returned (observed using chrome > developer tools), but the popup selection list does not appear until minChars + 1 > (3) characters are entered. > Typing the third character causes a get request for combo_list_shadow.png to be > sent. > {code} > mode="cachedAjax" > var="var" > fetchValue="#{var.name}" > minChars="2" > autocompleteMethod="#{bean.doSearch}"> > > > > > {code} > w > I've only just migrated to rich:autocomplete from a self-developed custom component > so I don't know if this behavior existed in any richfaces version prior to 4.2.0.CR1. > I tried this on the showcase example here: > http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=autocomplete&skin=blueSky > (in the first autocomplete on the page) and could not reproduce the behavior. > I tried using mode="ajax" and mode="client" and could not get the popup to show in > either case, although I'd only ever want to use cachedAjax mode normally. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 22 13:54:47 2012 From: jira-events at lists.jboss.org (Wesley Menezes (JIRA)) Date: Thu, 22 Mar 2012 13:54:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12079) ignores In-Reply-To: <2129957963.25561.1332425267314.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <2124930821.26684.1332438887423.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wesley Menezes updated RF-12079: -------------------------------- Description: In JSF with a and this have nested, if is applied in , the ajax listener isn't called. But, if applied to (under) , the ajax event fires method listener call. XHTML (snippet) BEAN (snippet) /*imports...*/ @Named @SessionScoped public class CadCustomerBean implements Serializable { public void processTreeSelectionChange (MyClass myObject) { System.out.println(myObject); } } Obs. In RichFaces 4.2.0 Final showcase, the has the attribute "selectionChangeListener", but I found only "treeSelectionChangeListener" in jars of RichFaces (like attribute of the tag, or like a tag ). The "Component_Reference.pdf" is ok. was: In JSF with a and this have nested, if is applied in , the ajax listener isn't called. Obs. In RichFaces 4.2.0 Final showcase, the has the attribute "selectionChangeListener", but I found only "treeSelectionChangeListener" in jars of RichFaces (like attribute of the tag, or like a tag ) - "Component_Reference.pdf" is ok. Forum Reference: https://community.jboss.org/message/725244?tstart=0 (was: https://community.jboss.org/message/725244?tstart=0) > ignores > ---------------------------------- > > Key: RF-12079 > URL: https://issues.jboss.org/browse/RF-12079 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tree > Affects Versions: 4.2.0.Final > Environment: RichFaces 4.2.0 and JSF 2.2 with CDI (Bean type "javax.inject.Named") > Application Server GlassFish Server Open Source Edition 3.1.2 (build 23) > Reporter: Wesley Menezes > > In JSF with a and this have nested, if is applied in , the ajax listener isn't called. > But, if applied to (under) , the ajax event fires method listener call. > XHTML (snippet) > id="memoriaTree" > value="#{cadCustomerBean.rootNodes}" > toggleType="client" > var="node" > nodeType="#{node.data.type}" > > > > id="memoriaRoot" > type="customer" > iconLeaf="../images/fichario.gif" > data="#{node.data.id}"> > > > > immediate="true" > execute="@this" > event="mousedown" > listener="#{cadCustomerBean.processTreeSelectionChange(node.data)}"/> > > > > BEAN (snippet) > /*imports...*/ > @Named > @SessionScoped > public class CadCustomerBean implements Serializable { > public void processTreeSelectionChange (MyClass myObject) { > > System.out.println(myObject); > } > } > Obs. In RichFaces 4.2.0 Final showcase, the has the attribute "selectionChangeListener", but I found only "treeSelectionChangeListener" in jars of RichFaces (like attribute of the tag, or like a tag ). The "Component_Reference.pdf" is ok. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 22 14:07:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 22 Mar 2012 14:07:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11833) Label for calendar results in non-valid markup In-Reply-To: <1824573501.21859.1324327990123.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1979042059.26719.1332439667453.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678761#comment-12678761 ] Luk?? Fry? commented on RF-11833: --------------------------------- We have discussed this issue on the team meeting [1] and decided to file spec issue. [1] https://community.jboss.org/wiki/RichFacesTeamMeetingAgenda2012-03-20 > Label for calendar results in non-valid markup > ---------------------------------------------- > > Key: RF-11833 > URL: https://issues.jboss.org/browse/RF-11833 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.1.0.Final > Reporter: Pavol Pitonak > Assignee: Brian Leathem > Fix For: 4.2.1.CR1 > > > The code in first code snippet results in markup below which is not valid. The for attribute of the label element must refer to a form control, e.g. the actual input inside calendar (that with ID dateForm:fromDateInputDate). > {code:xml} > > > {code} > {code:xml} > > > > > ... > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 22 15:14:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Thu, 22 Mar 2012 15:14:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12078) action fired twice, when invoked by a a4j:commandButton residing in a tables' footer facet In-Reply-To: <729908046.25329.1332420947280.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <555701402.26824.1332443687632.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12078: ------------------------------- Fix Version/s: 4.Future > action fired twice, when invoked by a a4j:commandButton residing in a tables' footer facet > ------------------------------------------------------------------------------------------ > > Key: RF-12078 > URL: https://issues.jboss.org/browse/RF-12078 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 3.3.3.Final > Environment: Liferay 5.2.4, Portlet 2.0, JSF 1.2, Richfaces 3.3.3 > Reporter: Markus Staab > Fix For: 4.Future > > > when adding a a4j:commandButton inside a rich:databables footer-facet, the corresponding action will be invoked twice while the process action phase. > The problem only occurs, when the commandButton 'process'es the datatable itself. > {code} > > > A HEADER > SOME CONTENT IN THE ROW > > > > > value="ADD ANOTHER ROW" > reRender="myTable" > action="#{form.addNewRow}" ajaxSingle="true" > process="myTable" > /> > > > > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 22 15:16:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Thu, 22 Mar 2012 15:16:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11995) autocomplete only displaying select popup on minChars + 1 In-Reply-To: <1491446387.30098.1329818436170.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <324215520.26838.1332443807914.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-11995. -------------------------------- Resolution: Cannot Reproduce Bug Feel free to re-open this issue with an example demonstrating the behavior. For tips on writing an effective sample, see: https://community.jboss.org/wiki/SubmittingEffectiveIssueReports > autocomplete only displaying select popup on minChars + 1 > --------------------------------------------------------- > > Key: RF-11995 > URL: https://issues.jboss.org/browse/RF-11995 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.2.0.CR1 > Environment: Glassfish 3.1.1 / Mojarra 2.1.7 / Chrome browser > Reporter: Brendan Healey > > I'm running the following test with org.richfaces.resourceOptimization.enabled > set to true. > After typing the minChars number of characters (2), I see an ajax request being > sent to the server and a response is successfully returned (observed using chrome > developer tools), but the popup selection list does not appear until minChars + 1 > (3) characters are entered. > Typing the third character causes a get request for combo_list_shadow.png to be > sent. > {code} > mode="cachedAjax" > var="var" > fetchValue="#{var.name}" > minChars="2" > autocompleteMethod="#{bean.doSearch}"> > > > > > {code} > w > I've only just migrated to rich:autocomplete from a self-developed custom component > so I don't know if this behavior existed in any richfaces version prior to 4.2.0.CR1. > I tried this on the showcase example here: > http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=autocomplete&skin=blueSky > (in the first autocomplete on the page) and could not reproduce the behavior. > I tried using mode="ajax" and mode="client" and could not get the popup to show in > either case, although I'd only ever want to use cachedAjax mode normally. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 22 15:20:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Thu, 22 Mar 2012 15:20:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12077) Selection in extendedDataTable doesn't work in Chrome In-Reply-To: <2021407965.24539.1332406547698.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <979919896.26852.1332444047579.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678776#comment-12678776 ] Brian Leathem commented on RF-12077: ------------------------------------ This works fine for me with the extendeddatatable selection sample in the showcase: http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=extendedDataTable&sample=exTableSelection&skin=blueSky Please include a example demonstrating this problem. See: https://community.jboss.org/wiki/SubmittingEffectiveIssueReports > Selection in extendedDataTable doesn't work in Chrome > ----------------------------------------------------- > > Key: RF-12077 > URL: https://issues.jboss.org/browse/RF-12077 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.2.0.Final > Environment: Windows XP. JBoss AS 7 Chrome 17.0.963.83 > Reporter: Vladimir Romashov > Priority: Blocker > Labels: waiting_on_user > > JavaScript error in console on rendered page with > Uncaught TypeError: Cannot read property 'length' of null > richfaces.utils.getCSSRule extendedDataTable.js.jsf:40 > richfaces.ui.ExtendedDataTable.richfaces.BaseComponent.extendClass.initialize extendedDataTable.js.jsf:362 > jQuery.extend.proxy.proxyjquery.js.jsf:814 > jQuery.Callbacks.firejquery.js.jsf:1046 > jQuery.Callbacks.self.fireWithjquery.js.jsf:1164 > jQuery.extend.readyjquery.js.jsf:435 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 22 15:22:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Thu, 22 Mar 2012 15:22:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12079) ignores In-Reply-To: <2129957963.25561.1332425267314.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <950448524.26855.1332444167460.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12079: ------------------------------- Description: In JSF with a and this have nested, if is applied in , the ajax listener isn't called. But, if applied to (under) , the ajax event fires method listener call. {code:title=XHTML (snippet)} {code} {code:title=BEAN (snippet)} /*imports...*/ @Named @SessionScoped public class CadCustomerBean implements Serializable { public void processTreeSelectionChange (MyClass myObject) { System.out.println(myObject); } } {code} Obs. In RichFaces 4.2.0 Final showcase, the has the attribute "selectionChangeListener", but I found only "treeSelectionChangeListener" in jars of RichFaces (like attribute of the tag, or like a tag ). The "Component_Reference.pdf" is ok. was: In JSF with a and this have nested, if is applied in , the ajax listener isn't called. But, if applied to (under) , the ajax event fires method listener call. XHTML (snippet) BEAN (snippet) /*imports...*/ @Named @SessionScoped public class CadCustomerBean implements Serializable { public void processTreeSelectionChange (MyClass myObject) { System.out.println(myObject); } } Obs. In RichFaces 4.2.0 Final showcase, the has the attribute "selectionChangeListener", but I found only "treeSelectionChangeListener" in jars of RichFaces (like attribute of the tag, or like a tag ). The "Component_Reference.pdf" is ok. Forum Reference: https://community.jboss.org/message/725244?tstart=0 (was: https://community.jboss.org/message/725244?tstart=0) > ignores > ---------------------------------- > > Key: RF-12079 > URL: https://issues.jboss.org/browse/RF-12079 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tree > Affects Versions: 4.2.0.Final > Environment: RichFaces 4.2.0 and JSF 2.2 with CDI (Bean type "javax.inject.Named") > Application Server GlassFish Server Open Source Edition 3.1.2 (build 23) > Reporter: Wesley Menezes > > In JSF with a and this have nested, if is applied in , the ajax listener isn't called. > But, if applied to (under) , the ajax event fires method listener call. > {code:title=XHTML (snippet)} > id="memoriaTree" > value="#{cadCustomerBean.rootNodes}" > toggleType="client" > var="node" > nodeType="#{node.data.type}" > > > id="memoriaRoot" > type="customer" > iconLeaf="../images/fichario.gif" > data="#{node.data.id}"> > > immediate="true" > execute="@this" > event="mousedown" > listener="#{cadCustomerBean.processTreeSelectionChange(node.data)}"/> > > > {code} > {code:title=BEAN (snippet)} > /*imports...*/ > @Named > @SessionScoped > public class CadCustomerBean implements Serializable { > public void processTreeSelectionChange (MyClass myObject) { > > System.out.println(myObject); > } > } > {code} > Obs. In RichFaces 4.2.0 Final showcase, the has the attribute "selectionChangeListener", but I found only "treeSelectionChangeListener" in jars of RichFaces (like attribute of the tag, or like a tag ). The "Component_Reference.pdf" is ok. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 22 15:31:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Thu, 22 Mar 2012 15:31:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12079) ignores In-Reply-To: <2129957963.25561.1332425267314.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <647508853.26863.1332444707918.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem reassigned RF-12079: ---------------------------------- Assignee: Pavol Pitonak QE, please confirm > ignores > ---------------------------------- > > Key: RF-12079 > URL: https://issues.jboss.org/browse/RF-12079 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tree > Affects Versions: 4.2.0.Final > Environment: RichFaces 4.2.0 and JSF 2.2 with CDI (Bean type "javax.inject.Named") > Application Server GlassFish Server Open Source Edition 3.1.2 (build 23) > Reporter: Wesley Menezes > Assignee: Pavol Pitonak > > In JSF with a and this have nested, if is applied in , the ajax listener isn't called. > But, if applied to (under) , the ajax event fires method listener call. > {code:title=XHTML (snippet)} > id="memoriaTree" > value="#{cadCustomerBean.rootNodes}" > toggleType="client" > var="node" > nodeType="#{node.data.type}" > > > id="memoriaRoot" > type="customer" > iconLeaf="../images/fichario.gif" > data="#{node.data.id}"> > > immediate="true" > execute="@this" > event="mousedown" > listener="#{cadCustomerBean.processTreeSelectionChange(node.data)}"/> > > > {code} > {code:title=BEAN (snippet)} > /*imports...*/ > @Named > @SessionScoped > public class CadCustomerBean implements Serializable { > public void processTreeSelectionChange (MyClass myObject) { > > System.out.println(myObject); > } > } > {code} > Obs. In RichFaces 4.2.0 Final showcase, the has the attribute "selectionChangeListener", but I found only "treeSelectionChangeListener" in jars of RichFaces (like attribute of the tag, or like a tag ). The "Component_Reference.pdf" is ok. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 22 16:39:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Thu, 22 Mar 2012 16:39:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11968) 4.2.0.CR1 contextMenu positioning incorrect when dynamically rendering on row select In-Reply-To: <784637995.32591.1328750928377.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1790754653.26979.1332448787963.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem reassigned RF-11968: ---------------------------------- Assignee: Brian Leathem > 4.2.0.CR1 contextMenu positioning incorrect when dynamically rendering on row select > ------------------------------------------------------------------------------------ > > Key: RF-11968 > URL: https://issues.jboss.org/browse/RF-11968 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-menu > Affects Versions: 4.2.0.CR1 > Environment: Chrome browser Glassfish 3.1.1 Mojarra 2.1.6 > Reporter: Brendan Healey > Assignee: Brian Leathem > Fix For: 4.2.1.CR1 > > Attachments: contextMenuWrongPositioning.png > > > There's a positioning error with contextMenu in the following scenario. > I have an extendedDataTable which renders a rich:panel when a row in the > table is selected. Initially no row is selected and the rich:panel is not > rendered. I right click in the table and the menuItem appears way below > the row I right clicked. > {code} > id="mytable" value="#{bean.someList}" var="var" > selection="#{bean.selectedRow}" > selectionMode="single"> > event="selectionchange" > listener="#{bean.doRowSelect}"/> > ... > > > > ... > > > > > > {code} > {code} > public void doRowSelect(...) { > selectedDepartment = ... (usual stuff); > } > {code} > Also tried with contextMenu mode="client" with the same result. > Regards, > Brendan. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 22 16:39:48 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Thu, 22 Mar 2012 16:39:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11936) rich:contextMenu activation is possible outside of tree nodes In-Reply-To: <643933580.14431.1328103828616.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1225670342.26982.1332448788391.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem reassigned RF-11936: ---------------------------------- Assignee: Brian Leathem > rich:contextMenu activation is possible outside of tree nodes > ------------------------------------------------------------- > > Key: RF-11936 > URL: https://issues.jboss.org/browse/RF-11936 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-menu, component-tree > Affects Versions: 4.2.0.CR1 > Environment: browsers: all browsers > Reporter: Juraj Huska > Assignee: Brian Leathem > Fix For: 4.2.1.CR1 > > Attachments: contextMenu.png, exdt_cm1.png, exdt_cm2.png > > > In the showcase demo for rich:contextMenu, the sample Tree ContextMenu, it is possible to activate the context menu not only from the nodes, but also outside of thenodes. > It is *rather a problem of the rich:tree*, since its rows contains nodes, which are rendered with 100% width. > When it is then selected with the contextMenu item, a popup with empty content is displayed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 22 16:42:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Thu, 22 Mar 2012 16:42:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12073) Kitchensink archetype - creating enterprise project requires also community richfaces version In-Reply-To: <2091208867.23183.1332345047625.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1532426554.26987.1332448967928.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-12073. -------------------------------- Fix Version/s: (was: 4.2.1.CR1) Resolution: Won't Fix Behaviour is the same as for simpleapp. It's not possible to create an archetype with a conditional question flow. This could be better handled as a forge plugin, or with separate community/enterprise archetypes. > Kitchensink archetype - creating enterprise project requires also community richfaces version > --------------------------------------------------------------------------------------------- > > Key: RF-12073 > URL: https://issues.jboss.org/browse/RF-12073 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: archetype > Affects Versions: 4.2.0.Final > Reporter: Juraj Huska > Assignee: Brian Leathem > Priority: Optional > > When generating enterprise richfaces maven project from kitchensink archetype, it is also prompting for community richfaces version. And then the community version is not used in the generated pom.xml > The log from this: > {noformat} > [INFO] Using property: groupId = bla.bla > [INFO] Using property: artifactId = foo_bla > Define value for property 'version': 1.0-SNAPSHOT: : > [INFO] Using property: package = bla.bla > [INFO] Using property: enterprise = n > [INFO] Using property: richfaces-enterprise-version = 4.2.0.Final-redhat-1 > [INFO] Using property: richfaces-version = 4.3.0-SNAPSHOT > Confirm properties configuration: > groupId: bla.bla > artifactId: foo_bla > version: 1.0-SNAPSHOT > package: bla.bla > enterprise: n > richfaces-enterprise-version: 4.2.0.Final-redhat-1 > richfaces-version: 4.3.0-SNAPSHOT > Y: : N > [INFO] Using property: groupId = bla.bla > [INFO] Using property: artifactId = foo_bla > Define value for property 'version': 1.0-SNAPSHOT: : > Define value for property 'package': bla.bla: : > Define value for property 'enterprise': n: : y > Define value for property 'richfaces-enterprise-version': 4.2.0.Final-redhat-1: : > Define value for property 'richfaces-version': 4.3.0-SNAPSHOT: : > Confirm properties configuration: > groupId: bla.bla > artifactId: foo_bla > version: 1.0-SNAPSHOT > package: bla.bla > enterprise: y > richfaces-enterprise-version: 4.2.0.Final-redhat-1 > richfaces-version: 4.3.0-SNAPSHOT > Y: : y > [INFO] ------------------------------------------------------------------------ > [INFO] BUILD SUCCESS > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 54.442s > [INFO] Finished at: Wed Mar 21 16:38:02 CET 2012 > [INFO] Final Memory: 9M/129M > [INFO] ------------------------------------------------------------------------ > jhuska at laptop:~/workspace_jbossTools33M5$ > {noformat} > *Steps to reproduce:* > 1. _mvn archetype:generate -DarchetypeGroupId=org.richfaces.archetypes -DarchetypeArtifactId=richfaces-archetype-kitchensink -DarchetypeVersion=4.3.0-SNAPSHOT -DgroupId=bla.bla -DartifactId=foo_bla_ > 2. When prompting: ?Define value for property 'version': 1.0-SNAPSHOT:_, press just enter. > 3. When prompting for confirming predefined values: type N > 4. When prompting for _Define value for property 'version': 1.0-SNAPSHOT: :_ press just enter. > 5. _Define value for property 'package': bla.bla: : _ just enter > 6. _Define value for property 'enterprise': n: :_ type y > 7. _Define value for property 'richfaces-enterprise-version': 4.2.0.Final-redhat-1: :_ just enter > 8. now you should be prompted for _Define value for property 'richfaces-version': 4.3.0-SNAPSHOT: :_, which you should not. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 22 16:44:49 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Thu, 22 Mar 2012 16:44:49 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11833) Label for calendar results in non-valid markup In-Reply-To: <1824573501.21859.1324327990123.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <338833292.26993.1332449089610.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-11833. -------------------------------- Assignee: Luk?? Fry? (was: Brian Leathem) Resolution: Won't Fix Upstream issue reported. > Label for calendar results in non-valid markup > ---------------------------------------------- > > Key: RF-11833 > URL: https://issues.jboss.org/browse/RF-11833 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.1.0.Final > Reporter: Pavol Pitonak > Assignee: Luk?? Fry? > Fix For: 4.2.1.CR1 > > > The code in first code snippet results in markup below which is not valid. The for attribute of the label element must refer to a form control, e.g. the actual input inside calendar (that with ID dateForm:fromDateInputDate). > {code:xml} > > > {code} > {code:xml} > > > > > ... > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 22 16:44:49 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Thu, 22 Mar 2012 16:44:49 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11833) Label for calendar results in non-valid markup In-Reply-To: <1824573501.21859.1324327990123.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <248978526.26996.1332449089911.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-11833: ------------------------------- Comment: was deleted (was: Upstream issue reported.) > Label for calendar results in non-valid markup > ---------------------------------------------- > > Key: RF-11833 > URL: https://issues.jboss.org/browse/RF-11833 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.1.0.Final > Reporter: Pavol Pitonak > Assignee: Luk?? Fry? > > The code in first code snippet results in markup below which is not valid. The for attribute of the label element must refer to a form control, e.g. the actual input inside calendar (that with ID dateForm:fromDateInputDate). > {code:xml} > > > {code} > {code:xml} > > > > > ... > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 22 16:44:50 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Thu, 22 Mar 2012 16:44:50 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11833) Label for calendar results in non-valid markup In-Reply-To: <1824573501.21859.1324327990123.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1143799871.26999.1332449090022.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-11833: ------------------------------- Fix Version/s: (was: 4.2.1.CR1) > Label for calendar results in non-valid markup > ---------------------------------------------- > > Key: RF-11833 > URL: https://issues.jboss.org/browse/RF-11833 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.1.0.Final > Reporter: Pavol Pitonak > Assignee: Luk?? Fry? > > The code in first code snippet results in markup below which is not valid. The for attribute of the label element must refer to a form control, e.g. the actual input inside calendar (that with ID dateForm:fromDateInputDate). > {code:xml} > > > {code} > {code:xml} > > > > > ... > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 22 16:46:48 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Thu, 22 Mar 2012 16:46:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12026) Javascript error in AjaxRequests on FireFox "invalid 'in' operand event" In-Reply-To: <1447882664.73686.1331126016454.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1507298744.27003.1332449208123.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem reassigned RF-12026: ---------------------------------- Assignee: Pavol Pitonak (was: Brian Leathem) Pavol, I'd scheduled this issue for 4.2.1.CR1, as it sounded like a regression, but I am not able to reproduce the issue. Would you please work some QE magic on this issue, and see if you can reproduce the behaviour? > Javascript error in AjaxRequests on FireFox "invalid 'in' operand event" > ------------------------------------------------------------------------ > > Key: RF-12026 > URL: https://issues.jboss.org/browse/RF-12026 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 4.2.0.Final > Environment: FireFox 3.6.27 > Reporter: Ulf Almehed > Assignee: Pavol Pitonak > Priority: Minor > Labels: regression > Fix For: 4.2.1.CR1 > > > Ajax request fails with javascript error "invalid 'in' operand event", richfaces-queue.js line 130. > This was introduced by the fix in RF-11943. Checking for existence of layerX fails if event isn't an Object (but a simple type). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 22 23:43:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Thu, 22 Mar 2012 23:43:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11948) rich:extendedDataTable generates a js-error stating this.normalPartStyle is undefined In-Reply-To: <2050628653.20854.1328272188456.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <467107210.27301.1332474227476.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678840#comment-12678840 ] Brian Leathem commented on RF-11948: ------------------------------------ Thanks for the detailed analysis Jan, that helped a lot. The fundamental problem here is that the _initialize_ method is not called until the page has loaded. See: {code:title=extendedDataTable.js, L#362} jQuery(document).ready(jQuery.proxy(this.initialize, this)); {code} Calling this initialize method before all the DOM objects have loaded would have negative side effects. Similarly, advancing this one initialisation piece (the normalPartStyle) to an earlier stage would treat the symptom but not cure the problem - meaning this would come up again for some other value that was not initialzed in time. The solution I'm proposing is to fire a "rich:ready" event when the initialisation is complete. With this in place, the above code sample would look like: {code} JSF Test ColA #{item.itemA} {code} Where we register a jQuery event handler for the rich:ready event fired by the extendedDataTable. > rich:extendedDataTable generates a js-error stating this.normalPartStyle is undefined > ------------------------------------------------------------------------------------- > > Key: RF-11948 > URL: https://issues.jboss.org/browse/RF-11948 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.2.0.CR1 > Environment: richfaces-4.2.0-SNAPSHOT, Firefox 10, IE8 > Reporter: Rene O > Assignee: Brian Leathem > Fix For: 4.2.1.CR1 > > > If you use rich:extendedDataTable and manually set the width of a column afterwards, a js error occurs > {code:title=page-snippet to reproduce the issue} > > xmlns:h="http://java.sun.com/jsf/html" > xmlns:f="http://java.sun.com/jsf/core" > xmlns:ui="http://java.sun.com/jsf/facelets" > xmlns:a4j="http://richfaces.org/a4j" > xmlns:rich="http://richfaces.org/rich" > > > > JSF Test > > > > > > > > > > ColA > > #{item.itemA} > > > > > > > {code} > {code:title=js error} > Fehler: this.normalPartStyle is undefined > Quelldatei: http://localhost:8080/jsftest/javax.faces.resource/extendedDataTable.js.jsf?ln=org.richfaces > Zeile: 279 > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 22 23:47:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Thu, 22 Mar 2012 23:47:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11948) rich:extendedDataTable generates a js-error stating this.normalPartStyle is undefined In-Reply-To: <2050628653.20854.1328272188456.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <710858119.27304.1332474467353.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-11948. -------------------------------- Resolution: Done Fired a rich:ready event when the extendedDataTable has finished initializing > rich:extendedDataTable generates a js-error stating this.normalPartStyle is undefined > ------------------------------------------------------------------------------------- > > Key: RF-11948 > URL: https://issues.jboss.org/browse/RF-11948 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.2.0.CR1 > Environment: richfaces-4.2.0-SNAPSHOT, Firefox 10, IE8 > Reporter: Rene O > Assignee: Brian Leathem > Fix For: 4.2.1.CR1 > > > If you use rich:extendedDataTable and manually set the width of a column afterwards, a js error occurs > {code:title=page-snippet to reproduce the issue} > > xmlns:h="http://java.sun.com/jsf/html" > xmlns:f="http://java.sun.com/jsf/core" > xmlns:ui="http://java.sun.com/jsf/facelets" > xmlns:a4j="http://richfaces.org/a4j" > xmlns:rich="http://richfaces.org/rich" > > > > JSF Test > > > > > > > > > > ColA > > #{item.itemA} > > > > > > > {code} > {code:title=js error} > Fehler: this.normalPartStyle is undefined > Quelldatei: http://localhost:8080/jsftest/javax.faces.resource/extendedDataTable.js.jsf?ln=org.richfaces > Zeile: 279 > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 23 00:08:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Fri, 23 Mar 2012 00:08:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11989) The jointpoint attribute of the contextMenu should be removed In-Reply-To: <1380056299.13648.1329430792396.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <2125836865.27311.1332475727333.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-11989. -------------------------------- Resolution: Done Hid the jointPoint attribute for the contextMenu > The jointpoint attribute of the contextMenu should be removed > ------------------------------------------------------------- > > Key: RF-11989 > URL: https://issues.jboss.org/browse/RF-11989 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-menu > Affects Versions: 4.2.0.CR1 > Reporter: Brian Leathem > Assignee: Brian Leathem > Priority: Minor > Fix For: 4.2.1.CR1 > > > This was erroneously left in place, when the contextMenu was forked from the dropDownMenu. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 23 00:41:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Fri, 23 Mar 2012 00:41:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12042) Metamer: rich:contextMenu doesn't disappear after clicking out of the menu in IE9 and Google Chrome In-Reply-To: <1422678186.9420.1331737667612.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1331666389.27330.1332477707454.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678846#comment-12678846 ] Brian Leathem commented on RF-12042: ------------------------------------ This is the same behaviour as in RichFaces 3. See: http://livedemo.exadel.com/richfaces-demo/richfaces/contextMenu.jsf > Metamer: rich:contextMenu doesn't disappear after clicking out of the menu in IE9 and Google Chrome > --------------------------------------------------------------------------------------------------- > > Key: RF-12042 > URL: https://issues.jboss.org/browse/RF-12042 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-menu > Affects Versions: 4.2.0.Final > Environment: ?RichFaces 4.2.1-SNAPSHOT > ?Metamer 4.2.1-SNAPSHOT > ?Mojarra 2.1.5-SNAPSHOT > ?JBoss AS 7.1.0.Final > ?Java(TM) SE Runtime Environment 1.6.0_31-b04 @ Linux > ?Internet Explorer 9.0 @ Win32 > RichFaces 4.2.1-SNAPSHOT > Metamer 4.2.1-SNAPSHOT > Mojarra 2.1.5-SNAPSHOT > JBoss AS 7.1.0.Final > Java(TM) SE Runtime Environment 1.6.0_31-b04 @ Linux > Chrome 17.0.963.78 @ Linux i686 > Reporter: Jan Papousek > Assignee: Brian Leathem > Labels: Chrome, IE9, needs-qe > Fix For: 4.2.1.CR1 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 23 00:41:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Fri, 23 Mar 2012 00:41:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12042) Metamer: rich:contextMenu doesn't disappear after clicking out of the menu in IE9 and Google Chrome In-Reply-To: <1422678186.9420.1331737667612.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <479195901.27332.1332477707572.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-12042. -------------------------------- Resolution: Done Registered a body click listener to trigger the menuLeaveHandler. Note, I change the menu base component, so QE should check the other menu components to guard against any regressions. > Metamer: rich:contextMenu doesn't disappear after clicking out of the menu in IE9 and Google Chrome > --------------------------------------------------------------------------------------------------- > > Key: RF-12042 > URL: https://issues.jboss.org/browse/RF-12042 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-menu > Affects Versions: 4.2.0.Final > Environment: ?RichFaces 4.2.1-SNAPSHOT > ?Metamer 4.2.1-SNAPSHOT > ?Mojarra 2.1.5-SNAPSHOT > ?JBoss AS 7.1.0.Final > ?Java(TM) SE Runtime Environment 1.6.0_31-b04 @ Linux > ?Internet Explorer 9.0 @ Win32 > RichFaces 4.2.1-SNAPSHOT > Metamer 4.2.1-SNAPSHOT > Mojarra 2.1.5-SNAPSHOT > JBoss AS 7.1.0.Final > Java(TM) SE Runtime Environment 1.6.0_31-b04 @ Linux > Chrome 17.0.963.78 @ Linux i686 > Reporter: Jan Papousek > Assignee: Brian Leathem > Labels: Chrome, IE9 > Fix For: 4.2.1.CR1 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 23 01:21:48 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Fri, 23 Mar 2012 01:21:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11967) rich:contextMenu can't be attached to body In-Reply-To: <597989296.31587.1328723868544.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <2146348531.27362.1332480108876.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-11967: ------------------------------- Fix Version/s: 4.Future (was: 4.2.1.CR1) Workaround Description: Wrap your content in a top level div, as in: {code} .... {code} This is currently not possible, as the parent is looked up by id. The id is then fed into document.getElementById before being fed to jQuery as a selector, to overcome the JSF id separator problem with jQuery. However, document.getElementById returns null when you try to look up the body by id. To overcome this, we will have to come up with a better means of looking up and attaching to the parent. See the workaround of introducing an extra div in your html to hold the contextMenu. > rich:contextMenu can't be attached to body > ------------------------------------------ > > Key: RF-11967 > URL: https://issues.jboss.org/browse/RF-11967 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-menu > Affects Versions: 4.2.0.CR1 > Reporter: Rene O > Assignee: Brian Leathem > Fix For: 4.Future > > > I haved tried to attach the contextMenu to the body element > {code:title=example.xhtml} > > xmlns:h="http://java.sun.com/jsf/html" > xmlns:f="http://java.sun.com/jsf/core" > xmlns:ui="http://java.sun.com/jsf/facelets" > xmlns:a4j="http://richfaces.org/a4j" > xmlns:rich="http://richfaces.org/rich"> > > > example > > > > > > > > contextMenuItem > > > > > {code} > The contextMenu only appears if i right-click the outputText. If i right-click somewhere else inside the page the contextMenu doesn't appear. I think, that this is a bug. I want the contextMenu all over the site. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 23 01:50:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Fri, 23 Mar 2012 01:50:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12043) Metamer: rich:contextMenu isn't rendered correctly in IE 9 compatibility mode In-Reply-To: <714594071.9445.1331737907625.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <371904395.27364.1332481847937.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678849#comment-12678849 ] Brian Leathem commented on RF-12043: ------------------------------------ This is also broken for rich:dropDownMenu in compatibility mode. > Metamer: rich:contextMenu isn't rendered correctly in IE 9 compatibility mode > ----------------------------------------------------------------------------- > > Key: RF-12043 > URL: https://issues.jboss.org/browse/RF-12043 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-menu > Affects Versions: 4.2.0.Final > Environment: RichFaces 4.2.1-SNAPSHOT > Metamer 4.2.1-SNAPSHOT > Mojarra 2.1.5-SNAPSHOT > JBoss AS 7.1.0.Final > Java(TM) SE Runtime Environment 1.6.0_31-b04 @ Linux > Internet Explorer 7.0 @ Win32 (this is IE 9 Compatibility Mode) > Reporter: Jan Papousek > Assignee: Brian Leathem > Labels: IE9 > Fix For: 4.2.1.CR1 > > Attachments: metamer-ie-9-rich_contextMenu.png > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 23 02:22:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Fri, 23 Mar 2012 02:22:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12043) Metamer: rich:contextMenu isn't rendered correctly in IE 9 compatibility mode In-Reply-To: <714594071.9445.1331737907625.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1695210083.27381.1332483767327.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-12043. -------------------------------- Resolution: Done Changed the empty icon containers to span elements > Metamer: rich:contextMenu isn't rendered correctly in IE 9 compatibility mode > ----------------------------------------------------------------------------- > > Key: RF-12043 > URL: https://issues.jboss.org/browse/RF-12043 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-menu > Affects Versions: 4.2.0.Final > Environment: RichFaces 4.2.1-SNAPSHOT > Metamer 4.2.1-SNAPSHOT > Mojarra 2.1.5-SNAPSHOT > JBoss AS 7.1.0.Final > Java(TM) SE Runtime Environment 1.6.0_31-b04 @ Linux > Internet Explorer 7.0 @ Win32 (this is IE 9 Compatibility Mode) > Reporter: Jan Papousek > Assignee: Brian Leathem > Labels: IE9, regression > Fix For: 4.2.1.CR1 > > Attachments: metamer-ie-9-rich_contextMenu.png > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 23 02:22:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Fri, 23 Mar 2012 02:22:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12038) IE8 - Object does not support this property or method - a4j:jsFunction In-Reply-To: <1674243330.3069.1331568048477.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1823508067.27383.1332483768006.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem reassigned RF-12038: ---------------------------------- Assignee: Brian Leathem > IE8 - Object does not support this property or method - a4j:jsFunction > ---------------------------------------------------------------------- > > Key: RF-12038 > URL: https://issues.jboss.org/browse/RF-12038 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.2.0.Final > Environment: cssparser-0.9.6- guava-11.0.1 - hibernate-validator-4.2.0.Final - JSF/Mojarra 2.1.6 - springframework-3.0.6.RELEASE - sac-1.3 - Windows 7 - IE 8.0.1.7601.17514 > Reporter: Jean ANDRE > Assignee: Brian Leathem > Fix For: 4.2.1.CR1 > > Attachments: index.xhtml, NestedWeb.zip, NestedWeb_RF-12038.zip, ScreenShot_RF-12038.png > > > Under IE8, IE reports the following error message due to a javascript error. However, the page are well displayed and the application is running ok. > Object doesn't support this property or method line 177 caracter 1 > Object doesn't support this property or method line 177 caracter 99 > Under IE Debugger, the line is: > {code} > closeTab=function(tabId){RichFaces.ajax("closeTab",null,{"incId":"1","parameters":{"tabId":tabId} } )};< > The caracter 99, is..............................................................................| (here) > {code} > This is a code generated by a4j:jsFunction from the XHTML > {code} > > > > > > > {code} > The rendered code is : > {code} > > > > {code} > See also this link as we got almost a similar: https://bugzilla.redhat.com/show_bug.cgi?id=601360. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 23 02:28:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Fri, 23 Mar 2012 02:28:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12038) IE8 - Object does not support this property or method - a4j:jsFunction In-Reply-To: <1674243330.3069.1331568048477.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <997760427.27385.1332484127690.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678854#comment-12678854 ] Brian Leathem commented on RF-12038: ------------------------------------ The link you provided is for RichFaces 3, the code samples there will not necessarily apply to RichFaces 4. > IE8 - Object does not support this property or method - a4j:jsFunction > ---------------------------------------------------------------------- > > Key: RF-12038 > URL: https://issues.jboss.org/browse/RF-12038 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.2.0.Final > Environment: cssparser-0.9.6- guava-11.0.1 - hibernate-validator-4.2.0.Final - JSF/Mojarra 2.1.6 - springframework-3.0.6.RELEASE - sac-1.3 - Windows 7 - IE 8.0.1.7601.17514 > Reporter: Jean ANDRE > Assignee: Brian Leathem > Fix For: 4.2.1.CR1 > > Attachments: index.xhtml, NestedWeb.zip, NestedWeb_RF-12038.zip, ScreenShot_RF-12038.png > > > Under IE8, IE reports the following error message due to a javascript error. However, the page are well displayed and the application is running ok. > Object doesn't support this property or method line 177 caracter 1 > Object doesn't support this property or method line 177 caracter 99 > Under IE Debugger, the line is: > {code} > closeTab=function(tabId){RichFaces.ajax("closeTab",null,{"incId":"1","parameters":{"tabId":tabId} } )};< > The caracter 99, is..............................................................................| (here) > {code} > This is a code generated by a4j:jsFunction from the XHTML > {code} > > > > > > > {code} > The rendered code is : > {code} > > > > {code} > See also this link as we got almost a similar: https://bugzilla.redhat.com/show_bug.cgi?id=601360. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 23 02:34:48 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Fri, 23 Mar 2012 02:34:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12038) IE8 - Object does not support this property or method - a4j:jsFunction In-Reply-To: <1674243330.3069.1331568048477.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1901373593.27391.1332484488694.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678855#comment-12678855 ] Brian Leathem commented on RF-12038: ------------------------------------ I'm curious why does your generated id match the id you assigned in the facelet file? The generated id should have the form id prepended to it (and separated by a ":"). If that were happening (as it should be), then the generated id would always be different from the name. > IE8 - Object does not support this property or method - a4j:jsFunction > ---------------------------------------------------------------------- > > Key: RF-12038 > URL: https://issues.jboss.org/browse/RF-12038 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.2.0.Final > Environment: cssparser-0.9.6- guava-11.0.1 - hibernate-validator-4.2.0.Final - JSF/Mojarra 2.1.6 - springframework-3.0.6.RELEASE - sac-1.3 - Windows 7 - IE 8.0.1.7601.17514 > Reporter: Jean ANDRE > Assignee: Brian Leathem > Labels: waiting_on_user > Attachments: index.xhtml, NestedWeb.zip, NestedWeb_RF-12038.zip, ScreenShot_RF-12038.png > > > Under IE8, IE reports the following error message due to a javascript error. However, the page are well displayed and the application is running ok. > Object doesn't support this property or method line 177 caracter 1 > Object doesn't support this property or method line 177 caracter 99 > Under IE Debugger, the line is: > {code} > closeTab=function(tabId){RichFaces.ajax("closeTab",null,{"incId":"1","parameters":{"tabId":tabId} } )};< > The caracter 99, is..............................................................................| (here) > {code} > This is a code generated by a4j:jsFunction from the XHTML > {code} > > > > > > > {code} > The rendered code is : > {code} > > > > {code} > See also this link as we got almost a similar: https://bugzilla.redhat.com/show_bug.cgi?id=601360. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 23 02:34:48 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Fri, 23 Mar 2012 02:34:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12038) IE8 - Object does not support this property or method - a4j:jsFunction In-Reply-To: <1674243330.3069.1331568048477.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <796351162.27393.1332484488751.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12038: ------------------------------- Fix Version/s: (was: 4.2.1.CR1) Labels: waiting_on_user (was: ) > IE8 - Object does not support this property or method - a4j:jsFunction > ---------------------------------------------------------------------- > > Key: RF-12038 > URL: https://issues.jboss.org/browse/RF-12038 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.2.0.Final > Environment: cssparser-0.9.6- guava-11.0.1 - hibernate-validator-4.2.0.Final - JSF/Mojarra 2.1.6 - springframework-3.0.6.RELEASE - sac-1.3 - Windows 7 - IE 8.0.1.7601.17514 > Reporter: Jean ANDRE > Assignee: Brian Leathem > Labels: waiting_on_user > Attachments: index.xhtml, NestedWeb.zip, NestedWeb_RF-12038.zip, ScreenShot_RF-12038.png > > > Under IE8, IE reports the following error message due to a javascript error. However, the page are well displayed and the application is running ok. > Object doesn't support this property or method line 177 caracter 1 > Object doesn't support this property or method line 177 caracter 99 > Under IE Debugger, the line is: > {code} > closeTab=function(tabId){RichFaces.ajax("closeTab",null,{"incId":"1","parameters":{"tabId":tabId} } )};< > The caracter 99, is..............................................................................| (here) > {code} > This is a code generated by a4j:jsFunction from the XHTML > {code} > > > > > > > {code} > The rendered code is : > {code} > > > > {code} > See also this link as we got almost a similar: https://bugzilla.redhat.com/show_bug.cgi?id=601360. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 23 02:36:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Fri, 23 Mar 2012 02:36:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12064) Remove the superfluous versions from the generated pom in the kitchensink archetype In-Reply-To: <1846737024.18946.1332201047228.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1224139953.27398.1332484607701.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem reassigned RF-12064: ---------------------------------- Assignee: Brian Leathem > Remove the superfluous versions from the generated pom in the kitchensink archetype > ----------------------------------------------------------------------------------- > > Key: RF-12064 > URL: https://issues.jboss.org/browse/RF-12064 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: archetype, build/distribution > Reporter: Brian Leathem > Assignee: Brian Leathem > Priority: Minor > Fix For: 4.2.1.CR1 > > > The kitchensink archetype unnecessarily specifies version for it's dependencies. The dependency version that are already specified in the BOM should be removed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 23 03:39:47 2012 From: jira-events at lists.jboss.org (Michael Heinen (JIRA)) Date: Fri, 23 Mar 2012 03:39:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12080) rich:hotKey usage clears body onload attribute Message-ID: <1411413331.27453.1332488387294.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Michael Heinen created RF-12080: ----------------------------------- Summary: rich:hotKey usage clears body onload attribute Key: RF-12080 URL: https://issues.jboss.org/browse/RF-12080 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component Affects Versions: 4.2.0.Final Environment: myfaces 2.1.6, tomahawk 1.1.11 Reporter: Michael Heinen Priority: Minor I'm happy to see rich:hotKey in richfaces 4.2, I used it already with richfaces 3.3.3. One thing I noticed now is that the onload attribute of t:documentboy is cleared on clientside as soon as rich:hotKey is used on a page. Maybe caused by jquery usage? >From my pov this should be either fixed or documented in the component guide as well as in the showcase sample. Workaround is obvious: Instead of onload use document.ready -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 23 04:02:54 2012 From: jira-events at lists.jboss.org (Ulf Almehed (JIRA)) Date: Fri, 23 Mar 2012 04:02:54 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12026) Javascript error in AjaxRequests on FireFox "invalid 'in' operand event" In-Reply-To: <1447882664.73686.1331126016454.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1731604149.27508.1332489774244.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678870#comment-12678870 ] Ulf Almehed commented on RF-12026: ---------------------------------- Brian: Yes, here is a small sample that will reproduce the error: It displays an ExtendedDataTable with the clientRows property set. If you drag the vertical scroller to the bottom, the table wount render anything due to the js-error. Browser: FireFox 3.6.28 A fix would be to replace the guard "if (event) {" with "if (event && event instanceof Object) {" (line 129 in richfaces-queue.js). edt.xhtml: JSF Demo EdtBean.java: package org.bogus; import java.io.Serializable; import java.util.ArrayList; import java.util.List; import java.util.Locale; import javax.enterprise.context.SessionScoped; import javax.inject.Named; //@RequestScoped @SessionScoped @Named public class EdtBean implements Serializable { private static final long serialVersionUID = 1L; private List mEdtData = new ArrayList(); public EdtBean() { mEdtData.add(new String[]{"Apa", "Boa", "Cikada"}); mEdtData.add(new String[]{"Doris", "Emma", "Frida"}); mEdtData.add(new String[]{"Glosa", "Hemkunskap", "IG"}); mEdtData.add(new String[]{"Jul", "Kristihimmelf?rdsdag", "L?ngfredag"}); mEdtData.add(new String[]{"Mousaka", "Nudlar", "Omelett"}); mEdtData.add(new String[]{"Paris", "Quibet", "Rotebro"}); mEdtData.add(new String[]{"Skotland", "Tanzania", "Uruguay"}); mEdtData.add(new String[]{"Vask", "Whiteboard", "X-krok"}); mEdtData.add(new String[]{"Youngblood", "ZZ-Top", "?dalen31"}); mEdtData.add(new String[]{"Apa", "Boa", "Cikada"}); mEdtData.add(new String[]{"Doris", "Emma", "Frida"}); mEdtData.add(new String[]{"Glosa", "Hemkunskap", "IG"}); mEdtData.add(new String[]{"Jul", "Kristihimmelf?rdsdag", "L?ngfredag"}); mEdtData.add(new String[]{"Mousaka", "Nudlar", "Omelett"}); mEdtData.add(new String[]{"Paris", "Quibet", "Rotebro"}); mEdtData.add(new String[]{"Skotland", "Tanzania", "Uruguay"}); mEdtData.add(new String[]{"Vask", "Whiteboard", "X-krok"}); mEdtData.add(new String[]{"Youngblood", "ZZ-Top", "?dalen31"}); mEdtData.add(new String[]{"Apa", "Boa", "Cikada"}); mEdtData.add(new String[]{"Doris", "Emma", "Frida"}); mEdtData.add(new String[]{"Glosa", "Hemkunskap", "IG"}); mEdtData.add(new String[]{"Jul", "Kristihimmelf?rdsdag", "L?ngfredag"}); mEdtData.add(new String[]{"Mousaka", "Nudlar", "Omelett"}); mEdtData.add(new String[]{"Paris", "Quibet", "Rotebro"}); mEdtData.add(new String[]{"Skotland", "Tanzania", "Uruguay"}); mEdtData.add(new String[]{"Vask", "Whiteboard", "X-krok"}); mEdtData.add(new String[]{"Youngblood", "ZZ-Top", "?dalen31"}); mEdtData.add(new String[]{"Apa", "Boa", "Cikada"}); mEdtData.add(new String[]{"Doris", "Emma", "Frida"}); mEdtData.add(new String[]{"Glosa", "Hemkunskap", "IG"}); mEdtData.add(new String[]{"Jul", "Kristihimmelf?rdsdag", "L?ngfredag"}); mEdtData.add(new String[]{"Mousaka", "Nudlar", "Omelett"}); mEdtData.add(new String[]{"Paris", "Quibet", "Rotebro"}); mEdtData.add(new String[]{"Skotland", "Tanzania", "Uruguay"}); mEdtData.add(new String[]{"Vask", "Whiteboard", "X-krok"}); mEdtData.add(new String[]{"Youngblood", "ZZ-Top", "?dalen31"}); } public void setEdtData(List mEdtData) { this.mEdtData = mEdtData; } public List getEdtData() { return mEdtData; } } > Javascript error in AjaxRequests on FireFox "invalid 'in' operand event" > ------------------------------------------------------------------------ > > Key: RF-12026 > URL: https://issues.jboss.org/browse/RF-12026 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 4.2.0.Final > Environment: FireFox 3.6.27 > Reporter: Ulf Almehed > Assignee: Pavol Pitonak > Priority: Minor > Labels: regression > Fix For: 4.2.1.CR1 > > > Ajax request fails with javascript error "invalid 'in' operand event", richfaces-queue.js line 130. > This was introduced by the fix in RF-11943. Checking for existence of layerX fails if event isn't an Object (but a simple type). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 23 04:04:47 2012 From: jira-events at lists.jboss.org (Rene O (JIRA)) Date: Fri, 23 Mar 2012 04:04:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11967) rich:contextMenu can't be attached to body In-Reply-To: <597989296.31587.1328723868544.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <531684893.27511.1332489887505.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678871#comment-12678871 ] Rene O commented on RF-11967: ----------------------------- The suggested workaround works. > rich:contextMenu can't be attached to body > ------------------------------------------ > > Key: RF-11967 > URL: https://issues.jboss.org/browse/RF-11967 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-menu > Affects Versions: 4.2.0.CR1 > Reporter: Rene O > Assignee: Brian Leathem > Fix For: 4.Future > > > I haved tried to attach the contextMenu to the body element > {code:title=example.xhtml} > > xmlns:h="http://java.sun.com/jsf/html" > xmlns:f="http://java.sun.com/jsf/core" > xmlns:ui="http://java.sun.com/jsf/facelets" > xmlns:a4j="http://richfaces.org/a4j" > xmlns:rich="http://richfaces.org/rich"> > > > example > > > > > > > > contextMenuItem > > > > > {code} > The contextMenu only appears if i right-click the outputText. If i right-click somewhere else inside the page the contextMenu doesn't appear. I think, that this is a bug. I want the contextMenu all over the site. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 23 04:55:47 2012 From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA)) Date: Fri, 23 Mar 2012 04:55:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11833) Label for calendar results in non-valid markup In-Reply-To: <1824573501.21859.1324327990123.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1314783541.27597.1332492947588.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678881#comment-12678881 ] Pavol Pitonak commented on RF-11833: ------------------------------------ Lukas, please add here spec issue link. > Label for calendar results in non-valid markup > ---------------------------------------------- > > Key: RF-11833 > URL: https://issues.jboss.org/browse/RF-11833 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.1.0.Final > Reporter: Pavol Pitonak > Assignee: Luk?? Fry? > > The code in first code snippet results in markup below which is not valid. The for attribute of the label element must refer to a form control, e.g. the actual input inside calendar (that with ID dateForm:fromDateInputDate). > {code:xml} > > > {code} > {code:xml} > > > > > ... > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 23 05:57:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 23 Mar 2012 05:57:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11294) Log: implement console mode In-Reply-To: <1295714463.14772.1313060931665.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1024970507.27681.1332496667789.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated RF-11294: ---------------------------- Fix Version/s: 4.3.0.Milestone1 (was: 4.Future) Git Pull Request: https://github.com/richfaces/components/pull/24 (was: https://github.com/richfaces/components/pull/24) > Log: implement console mode > --------------------------- > > Key: RF-11294 > URL: https://issues.jboss.org/browse/RF-11294 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-a4j-core > Reporter: Pavol Pitonak > Fix For: 4.3.0.Milestone1 > > > Enum org/richfaces/component/LogMode.java contains mode "console" which is not implemented. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 23 05:57:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 23 Mar 2012 05:57:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11294) Log: implement console mode In-Reply-To: <1295714463.14772.1313060931665.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <677287999.27682.1332496667824.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678892#comment-12678892 ] Luk?? Fry? commented on RF-11294: --------------------------------- Added pull request for implementing console log mode. > Log: implement console mode > --------------------------- > > Key: RF-11294 > URL: https://issues.jboss.org/browse/RF-11294 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-a4j-core > Reporter: Pavol Pitonak > Fix For: 4.3.0.Milestone1 > > > Enum org/richfaces/component/LogMode.java contains mode "console" which is not implemented. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 23 06:07:49 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 23 Mar 2012 06:07:49 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11940) mobile showcase - a4j:push - not retrieving pushes from server on Android In-Reply-To: <125521490.15036.1328110250830.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1186186416.27726.1332497269397.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved RF-11940. ----------------------------- Resolution: Done > mobile showcase - a4j:push - not retrieving pushes from server on Android > ------------------------------------------------------------------------- > > Key: RF-11940 > URL: https://issues.jboss.org/browse/RF-11940 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll, mobile, showcase > Environment: container: JBoss AS 7.1.0.CR1b > device: Motorola Xoom(Android 3.2.1) > Reporter: Juraj Huska > Assignee: Luk?? Fry? > Priority: Critical > Fix For: 4.2.1.CR1 > > > There is no push done in demo for a4j:push, however push demo work for desktop fine. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 23 06:13:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 23 Mar 2012 06:13:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12013) Deadlock in push component In-Reply-To: <654291399.48838.1330441536575.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <292243213.27736.1332497627448.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678896#comment-12678896 ] Luk?? Fry? commented on RF-12013: --------------------------------- Hey Stian, thanks for your efforts. I'm looking into RF-12072 now. Just for clarity, RF-12072 appeared with this patch or have you experienced it before? Just note that CDI events just delegates to TopicsContext, so {{Service Tracker has not been initialized}} issue won't disappear. I would recommend you readinghttp://rik-ansikter.blogspot.com/2012/02/configuring-richfaces-push-with-42.html and the troubleshooting section linked there. > Deadlock in push component > -------------------------- > > Key: RF-12013 > URL: https://issues.jboss.org/browse/RF-12013 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Affects Versions: 4.2.0.Final > Reporter: Stian Thorgersen > Assignee: Luk?? Fry? > Fix For: 4.2.1.CR1 > > > Deadlocked threads in the push component prevented server from stopping. Not sure whether or not this happened when I initiated shutdown or if these where hanging around for a while. > Relevant output from jstack: > {code} > Found one Java-level deadlock: > ============================= > "push-publish-thread-1": > waiting to lock monitor 0x0000000042650238 (object 0x00000000e5ed5a50, a org.richfaces.application.push.impl.RequestImpl), > which is held by "Atmosphere-AsyncWrite-0" > "Atmosphere-AsyncWrite-0": > waiting to lock monitor 0x00000000427d9ec0 (object 0x00000000e5ed59a0, a org.richfaces.application.push.impl.SessionImpl), > which is held by "push-publish-thread-1" > Java stack information for the threads listed above: > =================================================== > "push-publish-thread-1": > at org.richfaces.application.push.impl.RequestImpl.postMessages(RequestImpl.java:85) > - waiting to lock <0x00000000e5ed5a50> (a org.richfaces.application.push.impl.RequestImpl) > at org.richfaces.application.push.impl.SessionImpl.push(SessionImpl.java:237) > - locked <0x00000000e5ed59a0> (a org.richfaces.application.push.impl.SessionImpl) > at org.richfaces.application.push.impl.TopicImpl$TopicContext.publishMessages(TopicImpl.java:88) > at org.richfaces.application.push.impl.TopicImpl$PublishTask.run(TopicImpl.java:53) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:662) > "Atmosphere-AsyncWrite-0": > at org.richfaces.application.push.impl.SessionImpl.disconnect(SessionImpl.java:117) > - waiting to lock <0x00000000e5ed59a0> (a org.richfaces.application.push.impl.SessionImpl) > at org.richfaces.application.push.impl.RequestImpl.disconnect(RequestImpl.java:107) > at org.richfaces.application.push.impl.RequestImpl.onResume(RequestImpl.java:115) > at org.atmosphere.cpr.AtmosphereResourceImpl.onResume(AtmosphereResourceImpl.java:651) > at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:600) > at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:584) > at org.atmosphere.cpr.AtmosphereResourceImpl.resume(AtmosphereResourceImpl.java:185) > - locked <0x00000000e5ee3380> (a org.atmosphere.cpr.AtmosphereResourceEventImpl) > at org.richfaces.application.push.impl.RequestImpl.onBroadcast(RequestImpl.java:129) > - locked <0x00000000e5ed5a50> (a org.richfaces.application.push.impl.RequestImpl) > at org.atmosphere.cpr.AtmosphereResourceImpl.onBroadcast(AtmosphereResourceImpl.java:663) > at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:608) > at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:584) > at org.atmosphere.cpr.DefaultBroadcaster.executeAsyncWrite(DefaultBroadcaster.java:713) > at org.atmosphere.cpr.DefaultBroadcaster$3.run(DefaultBroadcaster.java:747) > - locked <0x00000000e5ed5a88> (a org.atmosphere.cpr.AtmosphereResourceImpl) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:662) > Found 1 deadlock. > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 23 06:48:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 23 Mar 2012 06:48:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12072) Lost event in push In-Reply-To: <1823827590.22721.1332335688298.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1050478041.27846.1332499727817.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678906#comment-12678906 ] Luk?? Fry? commented on RF-12072: --------------------------------- Hey Stian, I have imported your sample, just little modified the bean to get some debugging output: {code:Java} @SessionScoped @ManagedBean public class RichBean { private AtomicInteger count = new AtomicInteger(0); public int getCount() { int c = count.get(); System.out.println("getCount - start " + c); new Thread() { public void run() { try { Thread.sleep(5000); count.incrementAndGet(); TopicKey topicKey = new TopicKey("chat"); TopicsContext topicsContext = TopicsContext.lookup(); System.out.println("push " + count.get()); topicsContext.publish(topicKey, ""); } catch (Exception e) { e.printStackTrace(); } }; }.start(); if (c > 0) { try { Thread.sleep(10000); } catch (InterruptedException e) { } } System.out.println("getCount - end " + c); return c; } } {code} Now, the output from server is: {code} 11:39:33,582 INFO [stdout] (Thread-28) push 1 11:39:33,634 INFO [stdout] (http--0.0.0.0-8080-4) getCount - start 1 11:39:38,635 INFO [stdout] (Thread-29) push 2 11:39:43,635 INFO [stdout] (http--0.0.0.0-8080-4) getCount - end 1 11:39:43,660 INFO [stdout] (http--0.0.0.0-8080-4) getCount - start 2 11:39:48,661 INFO [stdout] (Thread-30) push 3 11:39:53,661 INFO [stdout] (http--0.0.0.0-8080-4) getCount - end 2 11:39:53,681 INFO [stdout] (http--0.0.0.0-8080-4) getCount - start 3 11:39:58,686 INFO [stdout] (Thread-31) push 4 11:40:03,686 INFO [stdout] (http--0.0.0.0-8080-4) getCount - end 3 11:40:03,717 INFO [stdout] (http--0.0.0.0-8080-4) getCount - start 4 11:40:08,720 INFO [stdout] (Thread-32) push 5 11:40:13,720 INFO [stdout] (http--0.0.0.0-8080-4) getCount - end 4 11:40:13,744 INFO [stdout] (http--0.0.0.0-8080-4) getCount - start 5 11:40:18,745 INFO [stdout] (Thread-33) push 6 11:40:23,744 INFO [stdout] (http--0.0.0.0-8080-4) getCount - end 5 11:40:23,768 INFO [stdout] (http--0.0.0.0-8080-4) getCount - start 6 11:40:28,769 INFO [stdout] (Thread-34) push 7 11:40:33,769 INFO [stdout] (http--0.0.0.0-8080-4) getCount - end 6 11:40:33,796 INFO [stdout] (http--0.0.0.0-8080-4) getCount - start 7 11:40:38,797 INFO [stdout] (Thread-35) push 8 11:40:43,797 INFO [stdout] (http--0.0.0.0-8080-4) getCount - end 7 11:40:43,820 INFO [stdout] (http--0.0.0.0-8080-4) getCount - start 8 11:40:48,821 INFO [stdout] (Thread-36) push 9 11:40:53,821 INFO [stdout] (http--0.0.0.0-8080-4) getCount - end 8 11:40:53,841 INFO [stdout] (http--0.0.0.0-8080-4) getCount - start 9 11:40:58,842 INFO [stdout] (Thread-37) push 10 11:41:03,842 INFO [stdout] (http--0.0.0.0-8080-4) getCount - end 9 11:41:03,862 INFO [stdout] (http--0.0.0.0-8080-4) getCount - start 10 11:41:08,863 INFO [stdout] (Thread-38) push 11 11:41:13,863 INFO [stdout] (http--0.0.0.0-8080-4) getCount - end 10 11:41:13,889 INFO [stdout] (http--0.0.0.0-8080-4) getCount - start 11 11:41:18,890 INFO [stdout] (Thread-39) push 12 11:41:23,889 INFO [stdout] (http--0.0.0.0-8080-4) getCount - end 11 11:41:23,911 INFO [stdout] (http--0.0.0.0-8080-4) getCount - start 12 11:41:28,912 INFO [stdout] (Thread-40) push 13 11:41:33,912 INFO [stdout] (http--0.0.0.0-8080-4) getCount - end 12 11:41:33,937 INFO [stdout] (http--0.0.0.0-8080-4) getCount - start 13 11:41:38,938 INFO [stdout] (Thread-41) push 14 11:41:43,938 INFO [stdout] (http--0.0.0.0-8080-4) getCount - end 13 11:41:43,961 INFO [stdout] (http--0.0.0.0-8080-4) getCount - start 14 11:41:48,961 INFO [stdout] (Thread-42) push 15 11:41:53,961 INFO [stdout] (http--0.0.0.0-8080-4) getCount - end 14 11:41:53,982 INFO [stdout] (http--0.0.0.0-8080-4) getCount - start 15 11:41:58,982 INFO [stdout] (Thread-43) push 16 11:42:03,982 INFO [stdout] (http--0.0.0.0-8080-4) getCount - end 15 11:42:03,993 INFO [stdout] (http--0.0.0.0-8080-4) getCount - start 16 11:42:08,994 INFO [stdout] (Thread-44) push 17 11:42:13,993 INFO [stdout] (http--0.0.0.0-8080-4) getCount - end 16 11:42:14,026 INFO [stdout] (http--0.0.0.0-8080-4) getCount - start 17 11:42:19,027 INFO [stdout] (Thread-45) push 18 11:42:24,027 INFO [stdout] (http--0.0.0.0-8080-4) getCount - end 17 11:42:24,050 INFO [stdout] (http--0.0.0.0-8080-4) getCount - start 18 {code} The AJAX re-render is actually done each 10 seconds, thus it returns stale value, but that's completely expected behavior since the {{getCount}} needs to wait for returning previous value (it's JSF requirement- only one AJAX request at time). When we comment the {{Thread.sleep(10000);}} we get: {code} 11:43:13,067 INFO [stdout] (Thread-50) push 1 11:43:13,123 INFO [stdout] (http--0.0.0.0-8080-3) getCount - start 1 11:43:13,124 INFO [stdout] (http--0.0.0.0-8080-3) getCount - end 1 11:43:18,136 INFO [stdout] (Thread-51) push 2 11:43:18,167 INFO [stdout] (http--0.0.0.0-8080-4) getCount - start 2 11:43:18,174 INFO [stdout] (http--0.0.0.0-8080-4) getCount - end 2 11:43:23,180 INFO [stdout] (Thread-52) push 3 11:43:23,203 INFO [stdout] (http--0.0.0.0-8080-4) getCount - start 3 11:43:23,203 INFO [stdout] (http--0.0.0.0-8080-4) getCount - end 3 11:43:28,205 INFO [stdout] (Thread-53) push 4 11:43:28,225 INFO [stdout] (http--0.0.0.0-8080-3) getCount - start 4 11:43:28,247 INFO [stdout] (http--0.0.0.0-8080-3) getCount - end 4 11:43:33,254 INFO [stdout] (Thread-54) push 5 11:43:33,277 INFO [stdout] (http--0.0.0.0-8080-3) getCount - start 5 11:43:33,278 INFO [stdout] (http--0.0.0.0-8080-3) getCount - end 5 {code} > Lost event in push > ------------------ > > Key: RF-12072 > URL: https://issues.jboss.org/browse/RF-12072 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Reporter: Stian Thorgersen > Assignee: Luk?? Fry? > > Event can be lost if produced while a response is being prepared. I've attached an example where a push event is used to refresh a count whenever an event is fired. It's using Thread.sleep to simulate an event being produced while the response is being prepared. Note, if the sleep just before returning the count is removed it all works fine, and the page is refreshed every 5 seconds, but with the sleep in place the event is lost. > View: > {code} > > > xmlns:f="http://java.sun.com/jsf/core" > xmlns:h="http://java.sun.com/jsf/html" > xmlns:a4j="http://richfaces.org/a4j" > xmlns:rich="http://richfaces.org/rich"> > > > > > > > > > > > > > {code} > Bean: > {code} > package com.example; > import java.io.Serializable; > import java.util.concurrent.atomic.AtomicInteger; > import javax.enterprise.context.SessionScoped; > import javax.inject.Named; > import org.richfaces.application.push.TopicKey; > import org.richfaces.application.push.TopicsContext; > @Named > @SessionScoped > public class MyBean implements Serializable > { > private AtomicInteger count = new AtomicInteger(); > public int getCount() > { > int c = count.get(); > new Thread() > { > public void run() > { > try > { > Thread.sleep(5000); > count.incrementAndGet(); > TopicKey topicKey = new TopicKey("chat"); > TopicsContext topicsContext = TopicsContext.lookup(); > topicsContext.publish(topicKey, ""); > } > catch (Exception e) > { > e.printStackTrace(); > } > }; > }.start(); > > try > { > Thread.sleep(10000); > } > catch (InterruptedException e) > { > } > return c; > } > } > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 23 06:48:48 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 23 Mar 2012 06:48:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12072) Lost event in push In-Reply-To: <1823827590.22721.1332335688298.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1753419203.27863.1332499728291.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved RF-12072. ----------------------------- Fix Version/s: (was: 4.2.1.CR1) Resolution: Rejected > Lost event in push > ------------------ > > Key: RF-12072 > URL: https://issues.jboss.org/browse/RF-12072 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Reporter: Stian Thorgersen > Assignee: Luk?? Fry? > > Event can be lost if produced while a response is being prepared. I've attached an example where a push event is used to refresh a count whenever an event is fired. It's using Thread.sleep to simulate an event being produced while the response is being prepared. Note, if the sleep just before returning the count is removed it all works fine, and the page is refreshed every 5 seconds, but with the sleep in place the event is lost. > View: > {code} > > > xmlns:f="http://java.sun.com/jsf/core" > xmlns:h="http://java.sun.com/jsf/html" > xmlns:a4j="http://richfaces.org/a4j" > xmlns:rich="http://richfaces.org/rich"> > > > > > > > > > > > > > {code} > Bean: > {code} > package com.example; > import java.io.Serializable; > import java.util.concurrent.atomic.AtomicInteger; > import javax.enterprise.context.SessionScoped; > import javax.inject.Named; > import org.richfaces.application.push.TopicKey; > import org.richfaces.application.push.TopicsContext; > @Named > @SessionScoped > public class MyBean implements Serializable > { > private AtomicInteger count = new AtomicInteger(); > public int getCount() > { > int c = count.get(); > new Thread() > { > public void run() > { > try > { > Thread.sleep(5000); > count.incrementAndGet(); > TopicKey topicKey = new TopicKey("chat"); > TopicsContext topicsContext = TopicsContext.lookup(); > topicsContext.publish(topicKey, ""); > } > catch (Exception e) > { > e.printStackTrace(); > } > }; > }.start(); > > try > { > Thread.sleep(10000); > } > catch (InterruptedException e) > { > } > return c; > } > } > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 23 06:48:48 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 23 Mar 2012 06:48:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12072) Lost event in push In-Reply-To: <1823827590.22721.1332335688298.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <573425194.27861.1332499728241.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678907#comment-12678907 ] Luk?? Fry? commented on RF-12072: --------------------------------- With regards to previous records I'm rejecting this issue. Feel free to reopen it when necessary. > Lost event in push > ------------------ > > Key: RF-12072 > URL: https://issues.jboss.org/browse/RF-12072 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Reporter: Stian Thorgersen > Assignee: Luk?? Fry? > > Event can be lost if produced while a response is being prepared. I've attached an example where a push event is used to refresh a count whenever an event is fired. It's using Thread.sleep to simulate an event being produced while the response is being prepared. Note, if the sleep just before returning the count is removed it all works fine, and the page is refreshed every 5 seconds, but with the sleep in place the event is lost. > View: > {code} > > > xmlns:f="http://java.sun.com/jsf/core" > xmlns:h="http://java.sun.com/jsf/html" > xmlns:a4j="http://richfaces.org/a4j" > xmlns:rich="http://richfaces.org/rich"> > > > > > > > > > > > > > {code} > Bean: > {code} > package com.example; > import java.io.Serializable; > import java.util.concurrent.atomic.AtomicInteger; > import javax.enterprise.context.SessionScoped; > import javax.inject.Named; > import org.richfaces.application.push.TopicKey; > import org.richfaces.application.push.TopicsContext; > @Named > @SessionScoped > public class MyBean implements Serializable > { > private AtomicInteger count = new AtomicInteger(); > public int getCount() > { > int c = count.get(); > new Thread() > { > public void run() > { > try > { > Thread.sleep(5000); > count.incrementAndGet(); > TopicKey topicKey = new TopicKey("chat"); > TopicsContext topicsContext = TopicsContext.lookup(); > topicsContext.publish(topicKey, ""); > } > catch (Exception e) > { > e.printStackTrace(); > } > }; > }.start(); > > try > { > Thread.sleep(10000); > } > catch (InterruptedException e) > { > } > return c; > } > } > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 23 06:54:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 23 Mar 2012 06:54:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12013) Deadlock in push component In-Reply-To: <654291399.48838.1330441536575.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1335438138.27886.1332500087537.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678896#comment-12678896 ] Luk?? Fry? edited comment on RF-12013 at 3/23/12 6:54 AM: ---------------------------------------------------------- Hey Stian, thanks for your efforts. I'm looking into RF-12072 now. Just for clarity, RF-12072 appeared with this patch or have you experienced it before? Just note that CDI events just delegates to TopicsContext, so {{Service Tracker has not been initialized}} issue won't disappear. I would recommend you reading http://rik-ansikter.blogspot.com/2012/02/configuring-richfaces-push-with-42.html and the troubleshooting section linked there. was (Author: lfryc): Hey Stian, thanks for your efforts. I'm looking into RF-12072 now. Just for clarity, RF-12072 appeared with this patch or have you experienced it before? Just note that CDI events just delegates to TopicsContext, so {{Service Tracker has not been initialized}} issue won't disappear. I would recommend you readinghttp://rik-ansikter.blogspot.com/2012/02/configuring-richfaces-push-with-42.html and the troubleshooting section linked there. > Deadlock in push component > -------------------------- > > Key: RF-12013 > URL: https://issues.jboss.org/browse/RF-12013 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Affects Versions: 4.2.0.Final > Reporter: Stian Thorgersen > Assignee: Luk?? Fry? > Fix For: 4.2.1.CR1 > > > Deadlocked threads in the push component prevented server from stopping. Not sure whether or not this happened when I initiated shutdown or if these where hanging around for a while. > Relevant output from jstack: > {code} > Found one Java-level deadlock: > ============================= > "push-publish-thread-1": > waiting to lock monitor 0x0000000042650238 (object 0x00000000e5ed5a50, a org.richfaces.application.push.impl.RequestImpl), > which is held by "Atmosphere-AsyncWrite-0" > "Atmosphere-AsyncWrite-0": > waiting to lock monitor 0x00000000427d9ec0 (object 0x00000000e5ed59a0, a org.richfaces.application.push.impl.SessionImpl), > which is held by "push-publish-thread-1" > Java stack information for the threads listed above: > =================================================== > "push-publish-thread-1": > at org.richfaces.application.push.impl.RequestImpl.postMessages(RequestImpl.java:85) > - waiting to lock <0x00000000e5ed5a50> (a org.richfaces.application.push.impl.RequestImpl) > at org.richfaces.application.push.impl.SessionImpl.push(SessionImpl.java:237) > - locked <0x00000000e5ed59a0> (a org.richfaces.application.push.impl.SessionImpl) > at org.richfaces.application.push.impl.TopicImpl$TopicContext.publishMessages(TopicImpl.java:88) > at org.richfaces.application.push.impl.TopicImpl$PublishTask.run(TopicImpl.java:53) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:662) > "Atmosphere-AsyncWrite-0": > at org.richfaces.application.push.impl.SessionImpl.disconnect(SessionImpl.java:117) > - waiting to lock <0x00000000e5ed59a0> (a org.richfaces.application.push.impl.SessionImpl) > at org.richfaces.application.push.impl.RequestImpl.disconnect(RequestImpl.java:107) > at org.richfaces.application.push.impl.RequestImpl.onResume(RequestImpl.java:115) > at org.atmosphere.cpr.AtmosphereResourceImpl.onResume(AtmosphereResourceImpl.java:651) > at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:600) > at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:584) > at org.atmosphere.cpr.AtmosphereResourceImpl.resume(AtmosphereResourceImpl.java:185) > - locked <0x00000000e5ee3380> (a org.atmosphere.cpr.AtmosphereResourceEventImpl) > at org.richfaces.application.push.impl.RequestImpl.onBroadcast(RequestImpl.java:129) > - locked <0x00000000e5ed5a50> (a org.richfaces.application.push.impl.RequestImpl) > at org.atmosphere.cpr.AtmosphereResourceImpl.onBroadcast(AtmosphereResourceImpl.java:663) > at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:608) > at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:584) > at org.atmosphere.cpr.DefaultBroadcaster.executeAsyncWrite(DefaultBroadcaster.java:713) > at org.atmosphere.cpr.DefaultBroadcaster$3.run(DefaultBroadcaster.java:747) > - locked <0x00000000e5ed5a88> (a org.atmosphere.cpr.AtmosphereResourceImpl) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:662) > Found 1 deadlock. > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 23 06:54:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 23 Mar 2012 06:54:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12013) Deadlock in push component In-Reply-To: <654291399.48838.1330441536575.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1945283698.27888.1332500087664.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678910#comment-12678910 ] Luk?? Fry? commented on RF-12013: --------------------------------- Merged to {{release/4.2.1.CR1}}. > Deadlock in push component > -------------------------- > > Key: RF-12013 > URL: https://issues.jboss.org/browse/RF-12013 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Affects Versions: 4.2.0.Final > Reporter: Stian Thorgersen > Assignee: Luk?? Fry? > Fix For: 4.2.1.CR1 > > > Deadlocked threads in the push component prevented server from stopping. Not sure whether or not this happened when I initiated shutdown or if these where hanging around for a while. > Relevant output from jstack: > {code} > Found one Java-level deadlock: > ============================= > "push-publish-thread-1": > waiting to lock monitor 0x0000000042650238 (object 0x00000000e5ed5a50, a org.richfaces.application.push.impl.RequestImpl), > which is held by "Atmosphere-AsyncWrite-0" > "Atmosphere-AsyncWrite-0": > waiting to lock monitor 0x00000000427d9ec0 (object 0x00000000e5ed59a0, a org.richfaces.application.push.impl.SessionImpl), > which is held by "push-publish-thread-1" > Java stack information for the threads listed above: > =================================================== > "push-publish-thread-1": > at org.richfaces.application.push.impl.RequestImpl.postMessages(RequestImpl.java:85) > - waiting to lock <0x00000000e5ed5a50> (a org.richfaces.application.push.impl.RequestImpl) > at org.richfaces.application.push.impl.SessionImpl.push(SessionImpl.java:237) > - locked <0x00000000e5ed59a0> (a org.richfaces.application.push.impl.SessionImpl) > at org.richfaces.application.push.impl.TopicImpl$TopicContext.publishMessages(TopicImpl.java:88) > at org.richfaces.application.push.impl.TopicImpl$PublishTask.run(TopicImpl.java:53) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:662) > "Atmosphere-AsyncWrite-0": > at org.richfaces.application.push.impl.SessionImpl.disconnect(SessionImpl.java:117) > - waiting to lock <0x00000000e5ed59a0> (a org.richfaces.application.push.impl.SessionImpl) > at org.richfaces.application.push.impl.RequestImpl.disconnect(RequestImpl.java:107) > at org.richfaces.application.push.impl.RequestImpl.onResume(RequestImpl.java:115) > at org.atmosphere.cpr.AtmosphereResourceImpl.onResume(AtmosphereResourceImpl.java:651) > at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:600) > at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:584) > at org.atmosphere.cpr.AtmosphereResourceImpl.resume(AtmosphereResourceImpl.java:185) > - locked <0x00000000e5ee3380> (a org.atmosphere.cpr.AtmosphereResourceEventImpl) > at org.richfaces.application.push.impl.RequestImpl.onBroadcast(RequestImpl.java:129) > - locked <0x00000000e5ed5a50> (a org.richfaces.application.push.impl.RequestImpl) > at org.atmosphere.cpr.AtmosphereResourceImpl.onBroadcast(AtmosphereResourceImpl.java:663) > at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:608) > at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:584) > at org.atmosphere.cpr.DefaultBroadcaster.executeAsyncWrite(DefaultBroadcaster.java:713) > at org.atmosphere.cpr.DefaultBroadcaster$3.run(DefaultBroadcaster.java:747) > - locked <0x00000000e5ed5a88> (a org.atmosphere.cpr.AtmosphereResourceImpl) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:662) > Found 1 deadlock. > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 23 07:26:47 2012 From: jira-events at lists.jboss.org (phelen harg (JIRA)) Date: Fri, 23 Mar 2012 07:26:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12081) Problem with RichEditor RF 4.2.0 Message-ID: <1278339548.27975.1332502007395.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> phelen harg created RF-12081: -------------------------------- Summary: Problem with RichEditor RF 4.2.0 Key: RF-12081 URL: https://issues.jboss.org/browse/RF-12081 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-input Affects Versions: 4.2.0.Final Reporter: phelen harg I'm migrating my Application from RF 3.3.3 to RF 4.2.0. But now i'm facing a problem with the richEditor. When I load the the component, all the links in application receive a background like this picture: Analizing the code with Firebug, I found the problem in the CSS of RichEditor. /org.richfaces.resources/javax.faces.resource/org.richfaces.ckeditor/skins/richfaces/editor.ecss?db=eAHj0yqqAgACGAEl If I erase the CSS the backgroud disappear. There is some kind of workaround for this? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 23 07:43:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 23 Mar 2012 07:43:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11833) Label for calendar results in non-valid markup In-Reply-To: <1824573501.21859.1324327990123.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <355068690.27992.1332503027429.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? reopened RF-11833: ----------------------------- > Label for calendar results in non-valid markup > ---------------------------------------------- > > Key: RF-11833 > URL: https://issues.jboss.org/browse/RF-11833 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.1.0.Final > Reporter: Pavol Pitonak > Assignee: Luk?? Fry? > > The code in first code snippet results in markup below which is not valid. The for attribute of the label element must refer to a form control, e.g. the actual input inside calendar (that with ID dateForm:fromDateInputDate). > {code:xml} > > > {code} > {code:xml} > > > > > ... > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 23 07:43:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 23 Mar 2012 07:43:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11833) Label for calendar results in non-valid markup In-Reply-To: <1824573501.21859.1324327990123.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <407597700.27994.1332503027548.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated RF-11833: ---------------------------- Comment: was deleted (was: A comment with security level 'JBoss Employee' was removed.) > Label for calendar results in non-valid markup > ---------------------------------------------- > > Key: RF-11833 > URL: https://issues.jboss.org/browse/RF-11833 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.1.0.Final > Reporter: Pavol Pitonak > Assignee: Luk?? Fry? > > The code in first code snippet results in markup below which is not valid. The for attribute of the label element must refer to a form control, e.g. the actual input inside calendar (that with ID dateForm:fromDateInputDate). > {code:xml} > > > {code} > {code:xml} > > > > > ... > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 23 07:49:47 2012 From: jira-events at lists.jboss.org (Stian Thorgersen (JIRA)) Date: Fri, 23 Mar 2012 07:49:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12072) Lost event in push In-Reply-To: <1823827590.22721.1332335688298.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <526475191.28003.1332503387346.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678923#comment-12678923 ] Stian Thorgersen commented on RF-12072: --------------------------------------- By wrapping "Thread.sleep(10000);" with "if (c > 0)" the example doesn't work, as you allow the page to be rendered fully before the first event is sent, hence bypassing the problem. In my application I use the push component to refresh the views when new data is available. The application allows users to "add/change" data asynchronously, so the data may be already changed when the model values are updated, or it may be changed later. In certain situations, especially when the server is running on a slow machine, the client can miss the update events altogether: * Client presses commandButton * Asynchronous change to data started * JSF model values updated * Data updated + update event is fired * Page is viewed in browser, but update event is lost It works fine in either of the following scenarios: * Client presses commandButton * Asynchronous change to data started * Data updated + update event is fired * JSF model values updated (missed event isn't a problem as data is changed before model values are updated) * Page is viewed in browser and: * Client presses commandButton * Asynchronous change to data started * JSF model values updated * Page is viewed in browser * Data updated + update event is fired (page is refreshed by push component and new values are retrieved from server) The example tries to force the first scenario where the data is lost by making sure the page is viewed after the event is fired. > Lost event in push > ------------------ > > Key: RF-12072 > URL: https://issues.jboss.org/browse/RF-12072 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Reporter: Stian Thorgersen > Assignee: Luk?? Fry? > > Event can be lost if produced while a response is being prepared. I've attached an example where a push event is used to refresh a count whenever an event is fired. It's using Thread.sleep to simulate an event being produced while the response is being prepared. Note, if the sleep just before returning the count is removed it all works fine, and the page is refreshed every 5 seconds, but with the sleep in place the event is lost. > View: > {code} > > > xmlns:f="http://java.sun.com/jsf/core" > xmlns:h="http://java.sun.com/jsf/html" > xmlns:a4j="http://richfaces.org/a4j" > xmlns:rich="http://richfaces.org/rich"> > > > > > > > > > > > > > {code} > Bean: > {code} > package com.example; > import java.io.Serializable; > import java.util.concurrent.atomic.AtomicInteger; > import javax.enterprise.context.SessionScoped; > import javax.inject.Named; > import org.richfaces.application.push.TopicKey; > import org.richfaces.application.push.TopicsContext; > @Named > @SessionScoped > public class MyBean implements Serializable > { > private AtomicInteger count = new AtomicInteger(); > public int getCount() > { > int c = count.get(); > new Thread() > { > public void run() > { > try > { > Thread.sleep(5000); > count.incrementAndGet(); > TopicKey topicKey = new TopicKey("chat"); > TopicsContext topicsContext = TopicsContext.lookup(); > topicsContext.publish(topicKey, ""); > } > catch (Exception e) > { > e.printStackTrace(); > } > }; > }.start(); > > try > { > Thread.sleep(10000); > } > catch (InterruptedException e) > { > } > return c; > } > } > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 23 08:25:47 2012 From: jira-events at lists.jboss.org (Jan Papousek (JIRA)) Date: Fri, 23 Mar 2012 08:25:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12082) Components: Output UI module doesn't pass unit tests (AbstractTogglePanelTest#testGetChildName) Message-ID: <147991329.28097.1332505547854.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Jan Papousek created RF-12082: --------------------------------- Summary: Components: Output UI module doesn't pass unit tests (AbstractTogglePanelTest#testGetChildName) Key: RF-12082 URL: https://issues.jboss.org/browse/RF-12082 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-output Affects Versions: 4.3.0.Milestone1 Reporter: Jan Papousek Priority: Critical {code} ------------------------------------------------------------------------------- Test set: org.richfaces.component.AbstractTogglePanelTest ------------------------------------------------------------------------------- Tests run: 5, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.022 sec <<< FAILURE! testGetChildName(org.richfaces.component.AbstractTogglePanelTest) Time elapsed: 0.005 sec <<< FAILURE! java.lang.AssertionError: Expected exception: java.lang.IllegalArgumentException at org.junit.internal.runners.statements.ExpectException.evaluate(ExpectException.java:32) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) at org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) at org.junit.runners.ParentRunner.run(ParentRunner.java:236) at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:234) at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:133) at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:114) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:188) at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:166) at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:86) at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:101) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74) {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 23 08:29:48 2012 From: jira-events at lists.jboss.org (Jan Papousek (JIRA)) Date: Fri, 23 Mar 2012 08:29:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12083) Components: Output UI module doesn't pass unit tests (MenuItemRendererTest and DropDownMenuRendererTest) Message-ID: <356683327.28101.1332505788416.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Jan Papousek created RF-12083: --------------------------------- Summary: Components: Output UI module doesn't pass unit tests (MenuItemRendererTest and DropDownMenuRendererTest) Key: RF-12083 URL: https://issues.jboss.org/browse/RF-12083 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-output Affects Versions: 4.2.1.CR1 Reporter: Jan Papousek Priority: Critical {code} ------------------------------------------------------------------------------- Test set: org.richfaces.renderkit.html.MenuItemRendererTest ------------------------------------------------------------------------------- Tests run: 6, Failures: 3, Errors: 0, Skipped: 1, Time elapsed: 3.172 sec <<< FAILURE! testDoEncodeServerMode(org.richfaces.renderkit.html.MenuItemRendererTest) Time elapsed: 0.566 sec <<< FAILURE! java.lang.AssertionError: XML was not similar:org.custommonkey.xmlunit.Diff [different] Expected element tag name 'div' but was 'span' - comparing at /div[1]/div[1] to at /div[1]/span[1]
    Test
    at org.junit.Assert.fail(Assert.java:91) at org.junit.Assert.assertTrue(Assert.java:43) at org.richfaces.renderkit.html.RendererTestBase.checkXmlStructure(RendererTestBase.java:93) at org.richfaces.renderkit.html.RendererTestBase.doTest(RendererTestBase.java:81) at org.richfaces.renderkit.html.RendererTestBase.doTest(RendererTestBase.java:73) at org.richfaces.renderkit.html.MenuItemRendererTest.testDoEncodeServerMode(MenuItemRendererTest.java:51) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31) at org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) at org.junit.runners.ParentRunner.run(ParentRunner.java:236) at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:234) at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:133) at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:114) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:188) at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:166) at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:86) at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:101) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74) testDoEncodeAjaxMode(org.richfaces.renderkit.html.MenuItemRendererTest) Time elapsed: 0.613 sec <<< FAILURE! java.lang.AssertionError: XML was not similar:org.custommonkey.xmlunit.Diff [different] Expected element tag name 'div' but was 'span' - comparing at /div[1]/div[1] to at /div[1]/span[1]
    Test
    at org.junit.Assert.fail(Assert.java:91) at org.junit.Assert.assertTrue(Assert.java:43) at org.richfaces.renderkit.html.RendererTestBase.checkXmlStructure(RendererTestBase.java:93) at org.richfaces.renderkit.html.RendererTestBase.doTest(RendererTestBase.java:81) at org.richfaces.renderkit.html.RendererTestBase.doTest(RendererTestBase.java:73) at org.richfaces.renderkit.html.MenuItemRendererTest.testDoEncodeAjaxMode(MenuItemRendererTest.java:71) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31) at org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) at org.junit.runners.ParentRunner.run(ParentRunner.java:236) at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:234) at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:133) at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:114) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:188) at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:166) at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:86) at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:101) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74) testDoEncodeClientMode(org.richfaces.renderkit.html.MenuItemRendererTest) Time elapsed: 0.724 sec <<< FAILURE! java.lang.AssertionError: XML was not similar:org.custommonkey.xmlunit.Diff [different] Expected element tag name 'div' but was 'span' - comparing at /div[1]/div[1] to at /div[1]/span[1]
    Test
    at org.junit.Assert.fail(Assert.java:91) at org.junit.Assert.assertTrue(Assert.java:43) at org.richfaces.renderkit.html.RendererTestBase.checkXmlStructure(RendererTestBase.java:93) at org.richfaces.renderkit.html.RendererTestBase.doTest(RendererTestBase.java:81) at org.richfaces.renderkit.html.RendererTestBase.doTest(RendererTestBase.java:73) at org.richfaces.renderkit.html.MenuItemRendererTest.testDoEncodeClientMode(MenuItemRendererTest.java:88) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31) at org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) at org.junit.runners.ParentRunner.run(ParentRunner.java:236) at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:234) at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:133) at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:114) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:188) at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:166) at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:86) at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:101) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74) {code} {code} ------------------------------------------------------------------------------- Test set: org.richfaces.renderkit.html.DropDownMenuRendererTest ------------------------------------------------------------------------------- Tests run: 4, Failures: 2, Errors: 0, Skipped: 1, Time elapsed: 2.206 sec <<< FAILURE! testDoEncodeServerMode(org.richfaces.renderkit.html.DropDownMenuRendererTest) Time elapsed: 0.729 sec <<< FAILURE! java.lang.AssertionError: XML was not similar:org.custommonkey.xmlunit.Diff [different] Expected element tag name 'div' but was 'span' - comparing at /div[1]/div[2]/div[1]/div[1]/div[1]/div[1] to at /div[1]/div[2]/div[1]/div[1]/div[1]/span[1]
    File
    at org.junit.Assert.fail(Assert.java:91) at org.junit.Assert.assertTrue(Assert.java:43) at org.richfaces.renderkit.html.RendererTestBase.checkXmlStructure(RendererTestBase.java:93) at org.richfaces.renderkit.html.RendererTestBase.doTest(RendererTestBase.java:81) at org.richfaces.renderkit.html.RendererTestBase.doTest(RendererTestBase.java:73) at org.richfaces.renderkit.html.DropDownMenuRendererTest.testDoEncodeServerMode(DropDownMenuRendererTest.java:51) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31) at org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) at org.junit.runners.ParentRunner.run(ParentRunner.java:236) at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:234) at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:133) at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:114) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:188) at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:166) at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:86) at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:101) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74) testDoEncodeAjaxMode(org.richfaces.renderkit.html.DropDownMenuRendererTest) Time elapsed: 0.677 sec <<< FAILURE! java.lang.AssertionError: XML was not similar:org.custommonkey.xmlunit.Diff [different] Expected element tag name 'div' but was 'span' - comparing at /div[1]/div[2]/div[1]/div[1]/div[1]/div[1] to at /div[1]/div[2]/div[1]/div[1]/div[1]/span[1]
    File
    at org.junit.Assert.fail(Assert.java:91) at org.junit.Assert.assertTrue(Assert.java:43) at org.richfaces.renderkit.html.RendererTestBase.checkXmlStructure(RendererTestBase.java:93) at org.richfaces.renderkit.html.RendererTestBase.doTest(RendererTestBase.java:81) at org.richfaces.renderkit.html.RendererTestBase.doTest(RendererTestBase.java:73) at org.richfaces.renderkit.html.DropDownMenuRendererTest.testDoEncodeAjaxMode(DropDownMenuRendererTest.java:56) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31) at org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) at org.junit.runners.ParentRunner.run(ParentRunner.java:236) at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:234) at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:133) at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:114) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:188) at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:166) at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:86) at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:101) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74) {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 23 09:04:47 2012 From: jira-events at lists.jboss.org (Jean ANDRE (JIRA)) Date: Fri, 23 Mar 2012 09:04:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12038) IE8 - Object does not support this property or method - a4j:jsFunction In-Reply-To: <1674243330.3069.1331568048477.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <683919181.28169.1332507887342.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678936#comment-12678936 ] Jean ANDRE commented on RF-12038: --------------------------------- Yes, I know about the link then...is there a better way? I'm not sure I understand your question. Well, we use Mojarra 2.1.6 and if you install and run the workbench, probably you can see and reproduce the phenomenon. It is a specific IE problem, not a FireFox problem. Under IE, this is the explanation found in forum, IE generates a javascript variable which has the same id as the component (the tag). Like this, I imagine, it is easier to manipulate the component via this variable. But in our case, relate to the a4j:function, Richfaces declares also a javascript variable as an handle to a function. Then, there is a clash, one variable is hidden/destroy by the other as they have the same name, just because we gave to a4j:function the same id as the name of the function. When you try to access to the function, it does not work because it is a tag object and then you receive the famous message... So, to summarize, by knowing the way of IE works, developers have to pay attention about this fact. It is not a problem of RichFaces but RichFaces can probably display a warning message or have a specific compatibility note in their PDF/HTML documentation. Now, it seems that the error occurs in JSF itself, inside JSF itself. Note that the same error occurs when from a button, we send a click event to the close image of the tab - RF-12060 Reported by IE ============ {code} Agent utilisateur : Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729) Horodateur : Fri, 23 Mar 2012 13:03:12 UTC Message?: Cet objet ne g?re pas cette propri?t? ou cette m?thode Ligne?: 89 Caract?re?: 28 Code?: 0 URI?: http://localhost:12000/CrmWeb/pages/index.jsf Message?: Objet requis Ligne?: 1 Caract?re?: 22732 Code?: 0 URI?: http://localhost:12000/CrmWeb/javax.faces.resource/jsf.js.jsf?ln=javax.faces {code} > IE8 - Object does not support this property or method - a4j:jsFunction > ---------------------------------------------------------------------- > > Key: RF-12038 > URL: https://issues.jboss.org/browse/RF-12038 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.2.0.Final > Environment: cssparser-0.9.6- guava-11.0.1 - hibernate-validator-4.2.0.Final - JSF/Mojarra 2.1.6 - springframework-3.0.6.RELEASE - sac-1.3 - Windows 7 - IE 8.0.1.7601.17514 > Reporter: Jean ANDRE > Assignee: Brian Leathem > Labels: waiting_on_user > Attachments: index.xhtml, NestedWeb.zip, NestedWeb_RF-12038.zip, ScreenShot_RF-12038.png > > > Under IE8, IE reports the following error message due to a javascript error. However, the page are well displayed and the application is running ok. > Object doesn't support this property or method line 177 caracter 1 > Object doesn't support this property or method line 177 caracter 99 > Under IE Debugger, the line is: > {code} > closeTab=function(tabId){RichFaces.ajax("closeTab",null,{"incId":"1","parameters":{"tabId":tabId} } )};< > The caracter 99, is..............................................................................| (here) > {code} > This is a code generated by a4j:jsFunction from the XHTML > {code} > > > > > > > {code} > The rendered code is : > {code} > > > > {code} > See also this link as we got almost a similar: https://bugzilla.redhat.com/show_bug.cgi?id=601360. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 23 09:28:49 2012 From: jira-events at lists.jboss.org (Jean ANDRE (JIRA)) Date: Fri, 23 Mar 2012 09:28:49 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12038) IE8 - Object does not support this property or method - a4j:jsFunction In-Reply-To: <1674243330.3069.1331568048477.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <356770682.28226.1332509329537.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678949#comment-12678949 ] Jean ANDRE commented on RF-12038: --------------------------------- And the line 89 is the function close on a second . It seems there is another clash even if this time, there is no id given to the tag... {code}

    		Work Items
    		Search
    		 ?Clients List (1) ?

    ?
    ?
    ?
    {code} > IE8 - Object does not support this property or method - a4j:jsFunction > ---------------------------------------------------------------------- > > Key: RF-12038 > URL: https://issues.jboss.org/browse/RF-12038 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.2.0.Final > Environment: cssparser-0.9.6- guava-11.0.1 - hibernate-validator-4.2.0.Final - JSF/Mojarra 2.1.6 - springframework-3.0.6.RELEASE - sac-1.3 - Windows 7 - IE 8.0.1.7601.17514 > Reporter: Jean ANDRE > Assignee: Brian Leathem > Labels: waiting_on_user > Attachments: index.xhtml, NestedWeb.zip, NestedWeb_RF-12038.zip, ScreenShot_RF-12038.png > > > Under IE8, IE reports the following error message due to a javascript error. However, the page are well displayed and the application is running ok. > Object doesn't support this property or method line 177 caracter 1 > Object doesn't support this property or method line 177 caracter 99 > Under IE Debugger, the line is: > {code} > closeTab=function(tabId){RichFaces.ajax("closeTab",null,{"incId":"1","parameters":{"tabId":tabId} } )};< > The caracter 99, is..............................................................................| (here) > {code} > This is a code generated by a4j:jsFunction from the XHTML > {code} > > > > > > > {code} > The rendered code is : > {code} > > > > {code} > See also this link as we got almost a similar: https://bugzilla.redhat.com/show_bug.cgi?id=601360. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 23 09:40:47 2012 From: jira-events at lists.jboss.org (Ulf Almehed (JIRA)) Date: Fri, 23 Mar 2012 09:40:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12026) Javascript error in AjaxRequests on FireFox "invalid 'in' operand event" In-Reply-To: <1447882664.73686.1331126016454.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <594013720.28248.1332510047340.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678954#comment-12678954 ] Ulf Almehed commented on RF-12026: ---------------------------------- I have tested with some different browsers, and I can repeat the problem with different Firefox browsers (3.6 - 11), but not with Chrome, IE or Safari. > Javascript error in AjaxRequests on FireFox "invalid 'in' operand event" > ------------------------------------------------------------------------ > > Key: RF-12026 > URL: https://issues.jboss.org/browse/RF-12026 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 4.2.0.Final > Environment: FireFox 3.6.27 > Reporter: Ulf Almehed > Assignee: Pavol Pitonak > Priority: Minor > Labels: regression > Fix For: 4.2.1.CR1 > > > Ajax request fails with javascript error "invalid 'in' operand event", richfaces-queue.js line 130. > This was introduced by the fix in RF-11943. Checking for existence of layerX fails if event isn't an Object (but a simple type). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 23 10:11:47 2012 From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA)) Date: Fri, 23 Mar 2012 10:11:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-10968) Tree: treeSelectionChangeListener and treeToggleListener do not work In-Reply-To: <35352639.27278.1304411418583.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <147548398.28316.1332511907859.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-10968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678967#comment-12678967 ] Pavol Pitonak commented on RF-10968: ------------------------------------ Component reference [1] documents the correct attributes. On the other hand, VDL doc [2] contains wrong attributes. [1] http://docs.jboss.org/richfaces/4.2.X/4.2.0.Final/Component_Reference/en-US/html_single/#sect-Component_Reference-richtree-Event_handling [2] http://docs.jboss.org/richfaces/4.2.X/4.2.0.Final/vdldoc/rich/tree.html > Tree: treeSelectionChangeListener and treeToggleListener do not work > -------------------------------------------------------------------- > > Key: RF-10968 > URL: https://issues.jboss.org/browse/RF-10968 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: base functionality , component-tree > Affects Versions: 4.0.0.Final > Environment: RichFaces 4.1.0-SNAPSHOT r.22458 > Metamer 4.1.0-SNAPSHOT r.22459 > Mojarra 2.0.3- > JBoss AS 6.0.0.Final > OpenJDK Runtime Environment 1.6.0_20-b20 @ Linux > Chrome 11.0.696.57 @ Linux i686 > Reporter: Pavol Pitonak > Fix For: 4.3-Tracking > > Attachments: NodesTreeSequenceKeyModelImpl.java, tree.xhtml, TreeBean.java, TreeNodeImpl.java > > > Attributes treeSelectionChangeListener and treeToggleListener in rich:tree do not work. However, attributes selectionChangeListener and toggleListener do work. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 23 10:22:50 2012 From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA)) Date: Fri, 23 Mar 2012 10:22:50 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12079) ignores In-Reply-To: <2129957963.25561.1332425267314.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1529841444.28344.1332512570497.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678970#comment-12678970 ] Pavol Pitonak commented on RF-12079: ------------------------------------ There is an issue for tree's listeners - RF-10968. a4j:ajax doesn't accept listener methods as is used in the sample above. See documentation for a4j:ajax: {quote} The expression must evaluate to a public method that takes an ActionEvent parameter, with a return type of void, or to a public method that takes no arguments with a return type of void. {quote} > ignores > ---------------------------------- > > Key: RF-12079 > URL: https://issues.jboss.org/browse/RF-12079 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tree > Affects Versions: 4.2.0.Final > Environment: RichFaces 4.2.0 and JSF 2.2 with CDI (Bean type "javax.inject.Named") > Application Server GlassFish Server Open Source Edition 3.1.2 (build 23) > Reporter: Wesley Menezes > Assignee: Pavol Pitonak > > In JSF with a and this have nested, if is applied in , the ajax listener isn't called. > But, if applied to (under) , the ajax event fires method listener call. > {code:title=XHTML (snippet)} > id="memoriaTree" > value="#{cadCustomerBean.rootNodes}" > toggleType="client" > var="node" > nodeType="#{node.data.type}" > > > id="memoriaRoot" > type="customer" > iconLeaf="../images/fichario.gif" > data="#{node.data.id}"> > > immediate="true" > execute="@this" > event="mousedown" > listener="#{cadCustomerBean.processTreeSelectionChange(node.data)}"/> > > > {code} > {code:title=BEAN (snippet)} > /*imports...*/ > @Named > @SessionScoped > public class CadCustomerBean implements Serializable { > public void processTreeSelectionChange (MyClass myObject) { > > System.out.println(myObject); > } > } > {code} > Obs. In RichFaces 4.2.0 Final showcase, the has the attribute "selectionChangeListener", but I found only "treeSelectionChangeListener" in jars of RichFaces (like attribute of the tag, or like a tag ). The "Component_Reference.pdf" is ok. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 23 10:22:50 2012 From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA)) Date: Fri, 23 Mar 2012 10:22:50 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12079) ignores In-Reply-To: <2129957963.25561.1332425267314.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <610051988.28347.1332512570594.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavol Pitonak reassigned RF-12079: ---------------------------------- Assignee: Brian Leathem (was: Pavol Pitonak) > ignores > ---------------------------------- > > Key: RF-12079 > URL: https://issues.jboss.org/browse/RF-12079 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tree > Affects Versions: 4.2.0.Final > Environment: RichFaces 4.2.0 and JSF 2.2 with CDI (Bean type "javax.inject.Named") > Application Server GlassFish Server Open Source Edition 3.1.2 (build 23) > Reporter: Wesley Menezes > Assignee: Brian Leathem > > In JSF with a and this have nested, if is applied in , the ajax listener isn't called. > But, if applied to (under) , the ajax event fires method listener call. > {code:title=XHTML (snippet)} > id="memoriaTree" > value="#{cadCustomerBean.rootNodes}" > toggleType="client" > var="node" > nodeType="#{node.data.type}" > > > id="memoriaRoot" > type="customer" > iconLeaf="../images/fichario.gif" > data="#{node.data.id}"> > > immediate="true" > execute="@this" > event="mousedown" > listener="#{cadCustomerBean.processTreeSelectionChange(node.data)}"/> > > > {code} > {code:title=BEAN (snippet)} > /*imports...*/ > @Named > @SessionScoped > public class CadCustomerBean implements Serializable { > public void processTreeSelectionChange (MyClass myObject) { > > System.out.println(myObject); > } > } > {code} > Obs. In RichFaces 4.2.0 Final showcase, the has the attribute "selectionChangeListener", but I found only "treeSelectionChangeListener" in jars of RichFaces (like attribute of the tag, or like a tag ). The "Component_Reference.pdf" is ok. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 23 11:41:47 2012 From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA)) Date: Fri, 23 Mar 2012 11:41:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12026) Javascript error in AjaxRequests on FireFox "invalid 'in' operand event" In-Reply-To: <1447882664.73686.1331126016454.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1535268655.28477.1332517307458.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavol Pitonak reassigned RF-12026: ---------------------------------- Assignee: Brian Leathem (was: Pavol Pitonak) I was able to reproduce in both Firefox 3.6.13 and 11.0. I added a new sample to Metamer which can be accessed after deploy on http://localhost:8080/metamer/faces/components/richExtendedDataTable/rf-12026.xhtml > Javascript error in AjaxRequests on FireFox "invalid 'in' operand event" > ------------------------------------------------------------------------ > > Key: RF-12026 > URL: https://issues.jboss.org/browse/RF-12026 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 4.2.0.Final > Environment: FireFox 3.6.27 > Reporter: Ulf Almehed > Assignee: Brian Leathem > Priority: Minor > Labels: regression > Fix For: 4.2.1.CR1 > > > Ajax request fails with javascript error "invalid 'in' operand event", richfaces-queue.js line 130. > This was introduced by the fix in RF-11943. Checking for existence of layerX fails if event isn't an Object (but a simple type). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 23 11:41:47 2012 From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA)) Date: Fri, 23 Mar 2012 11:41:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12026) Javascript error in AjaxRequests on FireFox "invalid 'in' operand event" In-Reply-To: <1447882664.73686.1331126016454.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <163479656.28481.1332517307790.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavol Pitonak updated RF-12026: ------------------------------- Environment: Firefox 3.6.27, 11.0 (was: FireFox 3.6.27) > Javascript error in AjaxRequests on FireFox "invalid 'in' operand event" > ------------------------------------------------------------------------ > > Key: RF-12026 > URL: https://issues.jboss.org/browse/RF-12026 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 4.2.0.Final > Environment: Firefox 3.6.27, 11.0 > Reporter: Ulf Almehed > Assignee: Brian Leathem > Priority: Minor > Labels: regression > Fix For: 4.2.1.CR1 > > > Ajax request fails with javascript error "invalid 'in' operand event", richfaces-queue.js line 130. > This was introduced by the fix in RF-11943. Checking for existence of layerX fails if event isn't an Object (but a simple type). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 23 11:56:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Fri, 23 Mar 2012 11:56:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12026) Javascript error in AjaxRequests on FireFox "invalid 'in' operand event" In-Reply-To: <1447882664.73686.1331126016454.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <2101963775.28511.1332518207642.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678870#comment-12678870 ] Brian Leathem edited comment on RF-12026 at 3/23/12 11:54 AM: -------------------------------------------------------------- Brian: Yes, here is a small sample that will reproduce the error: It displays an ExtendedDataTable with the clientRows property set. If you drag the vertical scroller to the bottom, the table wount render anything due to the js-error. Browser: FireFox 3.6.28 A fix would be to replace the guard "if (event) {" with "if (event && event instanceof Object) {" (line 129 in richfaces-queue.js). {code:title=edt.xhtml} JSF Demo {code} {code:title=EdtBean.java} package org.bogus; import java.io.Serializable; import java.util.ArrayList; import java.util.List; import java.util.Locale; import javax.enterprise.context.SessionScoped; import javax.inject.Named; //@RequestScoped @SessionScoped @Named public class EdtBean implements Serializable { private static final long serialVersionUID = 1L; private List mEdtData = new ArrayList(); public EdtBean() { mEdtData.add(new String[]{"Apa", "Boa", "Cikada"}); mEdtData.add(new String[]{"Doris", "Emma", "Frida"}); mEdtData.add(new String[]{"Glosa", "Hemkunskap", "IG"}); mEdtData.add(new String[]{"Jul", "Kristihimmelf?rdsdag", "L?ngfredag"}); mEdtData.add(new String[]{"Mousaka", "Nudlar", "Omelett"}); mEdtData.add(new String[]{"Paris", "Quibet", "Rotebro"}); mEdtData.add(new String[]{"Skotland", "Tanzania", "Uruguay"}); mEdtData.add(new String[]{"Vask", "Whiteboard", "X-krok"}); mEdtData.add(new String[]{"Youngblood", "ZZ-Top", "?dalen31"}); mEdtData.add(new String[]{"Apa", "Boa", "Cikada"}); mEdtData.add(new String[]{"Doris", "Emma", "Frida"}); mEdtData.add(new String[]{"Glosa", "Hemkunskap", "IG"}); mEdtData.add(new String[]{"Jul", "Kristihimmelf?rdsdag", "L?ngfredag"}); mEdtData.add(new String[]{"Mousaka", "Nudlar", "Omelett"}); mEdtData.add(new String[]{"Paris", "Quibet", "Rotebro"}); mEdtData.add(new String[]{"Skotland", "Tanzania", "Uruguay"}); mEdtData.add(new String[]{"Vask", "Whiteboard", "X-krok"}); mEdtData.add(new String[]{"Youngblood", "ZZ-Top", "?dalen31"}); mEdtData.add(new String[]{"Apa", "Boa", "Cikada"}); mEdtData.add(new String[]{"Doris", "Emma", "Frida"}); mEdtData.add(new String[]{"Glosa", "Hemkunskap", "IG"}); mEdtData.add(new String[]{"Jul", "Kristihimmelf?rdsdag", "L?ngfredag"}); mEdtData.add(new String[]{"Mousaka", "Nudlar", "Omelett"}); mEdtData.add(new String[]{"Paris", "Quibet", "Rotebro"}); mEdtData.add(new String[]{"Skotland", "Tanzania", "Uruguay"}); mEdtData.add(new String[]{"Vask", "Whiteboard", "X-krok"}); mEdtData.add(new String[]{"Youngblood", "ZZ-Top", "?dalen31"}); mEdtData.add(new String[]{"Apa", "Boa", "Cikada"}); mEdtData.add(new String[]{"Doris", "Emma", "Frida"}); mEdtData.add(new String[]{"Glosa", "Hemkunskap", "IG"}); mEdtData.add(new String[]{"Jul", "Kristihimmelf?rdsdag", "L?ngfredag"}); mEdtData.add(new String[]{"Mousaka", "Nudlar", "Omelett"}); mEdtData.add(new String[]{"Paris", "Quibet", "Rotebro"}); mEdtData.add(new String[]{"Skotland", "Tanzania", "Uruguay"}); mEdtData.add(new String[]{"Vask", "Whiteboard", "X-krok"}); mEdtData.add(new String[]{"Youngblood", "ZZ-Top", "?dalen31"}); } public void setEdtData(List mEdtData) { this.mEdtData = mEdtData; } public List getEdtData() { return mEdtData; } } {code} was (Author: uad): Brian: Yes, here is a small sample that will reproduce the error: It displays an ExtendedDataTable with the clientRows property set. If you drag the vertical scroller to the bottom, the table wount render anything due to the js-error. Browser: FireFox 3.6.28 A fix would be to replace the guard "if (event) {" with "if (event && event instanceof Object) {" (line 129 in richfaces-queue.js). edt.xhtml: JSF Demo EdtBean.java: package org.bogus; import java.io.Serializable; import java.util.ArrayList; import java.util.List; import java.util.Locale; import javax.enterprise.context.SessionScoped; import javax.inject.Named; //@RequestScoped @SessionScoped @Named public class EdtBean implements Serializable { private static final long serialVersionUID = 1L; private List mEdtData = new ArrayList(); public EdtBean() { mEdtData.add(new String[]{"Apa", "Boa", "Cikada"}); mEdtData.add(new String[]{"Doris", "Emma", "Frida"}); mEdtData.add(new String[]{"Glosa", "Hemkunskap", "IG"}); mEdtData.add(new String[]{"Jul", "Kristihimmelf?rdsdag", "L?ngfredag"}); mEdtData.add(new String[]{"Mousaka", "Nudlar", "Omelett"}); mEdtData.add(new String[]{"Paris", "Quibet", "Rotebro"}); mEdtData.add(new String[]{"Skotland", "Tanzania", "Uruguay"}); mEdtData.add(new String[]{"Vask", "Whiteboard", "X-krok"}); mEdtData.add(new String[]{"Youngblood", "ZZ-Top", "?dalen31"}); mEdtData.add(new String[]{"Apa", "Boa", "Cikada"}); mEdtData.add(new String[]{"Doris", "Emma", "Frida"}); mEdtData.add(new String[]{"Glosa", "Hemkunskap", "IG"}); mEdtData.add(new String[]{"Jul", "Kristihimmelf?rdsdag", "L?ngfredag"}); mEdtData.add(new String[]{"Mousaka", "Nudlar", "Omelett"}); mEdtData.add(new String[]{"Paris", "Quibet", "Rotebro"}); mEdtData.add(new String[]{"Skotland", "Tanzania", "Uruguay"}); mEdtData.add(new String[]{"Vask", "Whiteboard", "X-krok"}); mEdtData.add(new String[]{"Youngblood", "ZZ-Top", "?dalen31"}); mEdtData.add(new String[]{"Apa", "Boa", "Cikada"}); mEdtData.add(new String[]{"Doris", "Emma", "Frida"}); mEdtData.add(new String[]{"Glosa", "Hemkunskap", "IG"}); mEdtData.add(new String[]{"Jul", "Kristihimmelf?rdsdag", "L?ngfredag"}); mEdtData.add(new String[]{"Mousaka", "Nudlar", "Omelett"}); mEdtData.add(new String[]{"Paris", "Quibet", "Rotebro"}); mEdtData.add(new String[]{"Skotland", "Tanzania", "Uruguay"}); mEdtData.add(new String[]{"Vask", "Whiteboard", "X-krok"}); mEdtData.add(new String[]{"Youngblood", "ZZ-Top", "?dalen31"}); mEdtData.add(new String[]{"Apa", "Boa", "Cikada"}); mEdtData.add(new String[]{"Doris", "Emma", "Frida"}); mEdtData.add(new String[]{"Glosa", "Hemkunskap", "IG"}); mEdtData.add(new String[]{"Jul", "Kristihimmelf?rdsdag", "L?ngfredag"}); mEdtData.add(new String[]{"Mousaka", "Nudlar", "Omelett"}); mEdtData.add(new String[]{"Paris", "Quibet", "Rotebro"}); mEdtData.add(new String[]{"Skotland", "Tanzania", "Uruguay"}); mEdtData.add(new String[]{"Vask", "Whiteboard", "X-krok"}); mEdtData.add(new String[]{"Youngblood", "ZZ-Top", "?dalen31"}); } public void setEdtData(List mEdtData) { this.mEdtData = mEdtData; } public List getEdtData() { return mEdtData; } } > Javascript error in AjaxRequests on FireFox "invalid 'in' operand event" > ------------------------------------------------------------------------ > > Key: RF-12026 > URL: https://issues.jboss.org/browse/RF-12026 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 4.2.0.Final > Environment: Firefox 3.6.27, 11.0 > Reporter: Ulf Almehed > Assignee: Brian Leathem > Priority: Minor > Labels: regression > Fix For: 4.2.1.CR1 > > > Ajax request fails with javascript error "invalid 'in' operand event", richfaces-queue.js line 130. > This was introduced by the fix in RF-11943. Checking for existence of layerX fails if event isn't an Object (but a simple type). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 23 12:14:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 23 Mar 2012 12:14:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12072) Lost event in push In-Reply-To: <1823827590.22721.1332335688298.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1748295460.28537.1332519287398.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? reopened RF-12072: ----------------------------- > Lost event in push > ------------------ > > Key: RF-12072 > URL: https://issues.jboss.org/browse/RF-12072 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Reporter: Stian Thorgersen > Assignee: Luk?? Fry? > > Event can be lost if produced while a response is being prepared. I've attached an example where a push event is used to refresh a count whenever an event is fired. It's using Thread.sleep to simulate an event being produced while the response is being prepared. Note, if the sleep just before returning the count is removed it all works fine, and the page is refreshed every 5 seconds, but with the sleep in place the event is lost. > View: > {code} > > > xmlns:f="http://java.sun.com/jsf/core" > xmlns:h="http://java.sun.com/jsf/html" > xmlns:a4j="http://richfaces.org/a4j" > xmlns:rich="http://richfaces.org/rich"> > > > > > > > > > > > > > {code} > Bean: > {code} > package com.example; > import java.io.Serializable; > import java.util.concurrent.atomic.AtomicInteger; > import javax.enterprise.context.SessionScoped; > import javax.inject.Named; > import org.richfaces.application.push.TopicKey; > import org.richfaces.application.push.TopicsContext; > @Named > @SessionScoped > public class MyBean implements Serializable > { > private AtomicInteger count = new AtomicInteger(); > public int getCount() > { > int c = count.get(); > new Thread() > { > public void run() > { > try > { > Thread.sleep(5000); > count.incrementAndGet(); > TopicKey topicKey = new TopicKey("chat"); > TopicsContext topicsContext = TopicsContext.lookup(); > topicsContext.publish(topicKey, ""); > } > catch (Exception e) > { > e.printStackTrace(); > } > }; > }.start(); > > try > { > Thread.sleep(10000); > } > catch (InterruptedException e) > { > } > return c; > } > } > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 23 12:14:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 23 Mar 2012 12:14:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12072) Lost event in push In-Reply-To: <1823827590.22721.1332335688298.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <801088249.28542.1332519287552.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678996#comment-12678996 ] Luk?? Fry? commented on RF-12072: --------------------------------- Hi Stian, you are right, it's the problem of timing, I forgot I have added the condition. > Lost event in push > ------------------ > > Key: RF-12072 > URL: https://issues.jboss.org/browse/RF-12072 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Reporter: Stian Thorgersen > Assignee: Luk?? Fry? > > Event can be lost if produced while a response is being prepared. I've attached an example where a push event is used to refresh a count whenever an event is fired. It's using Thread.sleep to simulate an event being produced while the response is being prepared. Note, if the sleep just before returning the count is removed it all works fine, and the page is refreshed every 5 seconds, but with the sleep in place the event is lost. > View: > {code} > > > xmlns:f="http://java.sun.com/jsf/core" > xmlns:h="http://java.sun.com/jsf/html" > xmlns:a4j="http://richfaces.org/a4j" > xmlns:rich="http://richfaces.org/rich"> > > > > > > > > > > > > > {code} > Bean: > {code} > package com.example; > import java.io.Serializable; > import java.util.concurrent.atomic.AtomicInteger; > import javax.enterprise.context.SessionScoped; > import javax.inject.Named; > import org.richfaces.application.push.TopicKey; > import org.richfaces.application.push.TopicsContext; > @Named > @SessionScoped > public class MyBean implements Serializable > { > private AtomicInteger count = new AtomicInteger(); > public int getCount() > { > int c = count.get(); > new Thread() > { > public void run() > { > try > { > Thread.sleep(5000); > count.incrementAndGet(); > TopicKey topicKey = new TopicKey("chat"); > TopicsContext topicsContext = TopicsContext.lookup(); > topicsContext.publish(topicKey, ""); > } > catch (Exception e) > { > e.printStackTrace(); > } > }; > }.start(); > > try > { > Thread.sleep(10000); > } > catch (InterruptedException e) > { > } > return c; > } > } > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 23 12:16:47 2012 From: jira-events at lists.jboss.org (Jean ANDRE (JIRA)) Date: Fri, 23 Mar 2012 12:16:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12038) IE8 - Object does not support this property or method - a4j:jsFunction In-Reply-To: <1674243330.3069.1331568048477.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1805396347.28547.1332519407524.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678997#comment-12678997 ] Jean ANDRE commented on RF-12038: --------------------------------- The problem under IE is really about: event.stopPropagation(). Removing the instruction removes the error. To summarize, we have 2 errors. The first comes from event.stopPropagation(). Is there a variable clash with event object under IE and what is the substitute solution? and the second if about the null element inside the jsf.js.jsf?ln=javax.faces. with the instruction: if(!element.name). > IE8 - Object does not support this property or method - a4j:jsFunction > ---------------------------------------------------------------------- > > Key: RF-12038 > URL: https://issues.jboss.org/browse/RF-12038 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.2.0.Final > Environment: cssparser-0.9.6- guava-11.0.1 - hibernate-validator-4.2.0.Final - JSF/Mojarra 2.1.6 - springframework-3.0.6.RELEASE - sac-1.3 - Windows 7 - IE 8.0.1.7601.17514 > Reporter: Jean ANDRE > Assignee: Brian Leathem > Labels: waiting_on_user > Attachments: index.xhtml, NestedWeb.zip, NestedWeb_RF-12038.zip, ScreenShot_RF-12038.png > > > Under IE8, IE reports the following error message due to a javascript error. However, the page are well displayed and the application is running ok. > Object doesn't support this property or method line 177 caracter 1 > Object doesn't support this property or method line 177 caracter 99 > Under IE Debugger, the line is: > {code} > closeTab=function(tabId){RichFaces.ajax("closeTab",null,{"incId":"1","parameters":{"tabId":tabId} } )};< > The caracter 99, is..............................................................................| (here) > {code} > This is a code generated by a4j:jsFunction from the XHTML > {code} > > > > > > > {code} > The rendered code is : > {code} > > > > {code} > See also this link as we got almost a similar: https://bugzilla.redhat.com/show_bug.cgi?id=601360. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 23 12:20:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 23 Mar 2012 12:20:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12072) Lost event in push In-Reply-To: <1823827590.22721.1332335688298.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1941075761.28557.1332519647840.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated RF-12072: ---------------------------- Fix Version/s: 4.2.1.CR1 > Lost event in push > ------------------ > > Key: RF-12072 > URL: https://issues.jboss.org/browse/RF-12072 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Reporter: Stian Thorgersen > Assignee: Luk?? Fry? > Fix For: 4.2.1.CR1 > > > Event can be lost if produced while a response is being prepared. I've attached an example where a push event is used to refresh a count whenever an event is fired. It's using Thread.sleep to simulate an event being produced while the response is being prepared. Note, if the sleep just before returning the count is removed it all works fine, and the page is refreshed every 5 seconds, but with the sleep in place the event is lost. > View: > {code} > > > xmlns:f="http://java.sun.com/jsf/core" > xmlns:h="http://java.sun.com/jsf/html" > xmlns:a4j="http://richfaces.org/a4j" > xmlns:rich="http://richfaces.org/rich"> > > > > > > > > > > > > > {code} > Bean: > {code} > package com.example; > import java.io.Serializable; > import java.util.concurrent.atomic.AtomicInteger; > import javax.enterprise.context.SessionScoped; > import javax.inject.Named; > import org.richfaces.application.push.TopicKey; > import org.richfaces.application.push.TopicsContext; > @Named > @SessionScoped > public class MyBean implements Serializable > { > private AtomicInteger count = new AtomicInteger(); > public int getCount() > { > int c = count.get(); > new Thread() > { > public void run() > { > try > { > Thread.sleep(5000); > count.incrementAndGet(); > TopicKey topicKey = new TopicKey("chat"); > TopicsContext topicsContext = TopicsContext.lookup(); > topicsContext.publish(topicKey, ""); > } > catch (Exception e) > { > e.printStackTrace(); > } > }; > }.start(); > > try > { > Thread.sleep(10000); > } > catch (InterruptedException e) > { > } > return c; > } > } > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 23 12:22:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Fri, 23 Mar 2012 12:22:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12026) Javascript error in AjaxRequests on FireFox "invalid 'in' operand event" In-Reply-To: <1447882664.73686.1331126016454.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <813272285.28563.1332519767589.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-12026. -------------------------------- Resolution: Done Thanks Ulf, Pavol for your help in reproducing this issue. I added an instanceof object check before the layerX/Y removal. > Javascript error in AjaxRequests on FireFox "invalid 'in' operand event" > ------------------------------------------------------------------------ > > Key: RF-12026 > URL: https://issues.jboss.org/browse/RF-12026 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 4.2.0.Final > Environment: Firefox 3.6.27, 11.0 > Reporter: Ulf Almehed > Assignee: Brian Leathem > Priority: Minor > Labels: regression > Fix For: 4.2.1.CR1 > > > Ajax request fails with javascript error "invalid 'in' operand event", richfaces-queue.js line 130. > This was introduced by the fix in RF-11943. Checking for existence of layerX fails if event isn't an Object (but a simple type). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 23 12:26:47 2012 From: jira-events at lists.jboss.org (Jean ANDRE (JIRA)) Date: Fri, 23 Mar 2012 12:26:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12038) IE8 - Object does not support this property or method - a4j:jsFunction In-Reply-To: <1674243330.3069.1331568048477.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1264409403.28576.1332520007454.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679002#comment-12679002 ] Jean ANDRE commented on RF-12038: --------------------------------- Solution found by setting the following script inside the header. There is some adapation for FireFox does not recognize: "window.event is undefined" but now under FireFox we have the NPE. {code} {code} To conclude, the solution is really to stop event propagation to ovoid the NPE inside jsf.js.jsf but the way to be done must be adapted to each browser. > IE8 - Object does not support this property or method - a4j:jsFunction > ---------------------------------------------------------------------- > > Key: RF-12038 > URL: https://issues.jboss.org/browse/RF-12038 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.2.0.Final > Environment: cssparser-0.9.6- guava-11.0.1 - hibernate-validator-4.2.0.Final - JSF/Mojarra 2.1.6 - springframework-3.0.6.RELEASE - sac-1.3 - Windows 7 - IE 8.0.1.7601.17514 > Reporter: Jean ANDRE > Assignee: Brian Leathem > Labels: waiting_on_user > Attachments: index.xhtml, NestedWeb.zip, NestedWeb_RF-12038.zip, ScreenShot_RF-12038.png > > > Under IE8, IE reports the following error message due to a javascript error. However, the page are well displayed and the application is running ok. > Object doesn't support this property or method line 177 caracter 1 > Object doesn't support this property or method line 177 caracter 99 > Under IE Debugger, the line is: > {code} > closeTab=function(tabId){RichFaces.ajax("closeTab",null,{"incId":"1","parameters":{"tabId":tabId} } )};< > The caracter 99, is..............................................................................| (here) > {code} > This is a code generated by a4j:jsFunction from the XHTML > {code} > > > > > > > {code} > The rendered code is : > {code} > > > > {code} > See also this link as we got almost a similar: https://bugzilla.redhat.com/show_bug.cgi?id=601360. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 23 12:57:47 2012 From: jira-events at lists.jboss.org (Jean ANDRE (JIRA)) Date: Fri, 23 Mar 2012 12:57:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12038) IE8 - Object does not support this property or method - a4j:jsFunction In-Reply-To: <1674243330.3069.1331568048477.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1353223282.28619.1332521867370.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679002#comment-12679002 ] Jean ANDRE edited comment on RF-12038 at 3/23/12 12:56 PM: ----------------------------------------------------------- Solution found by setting the following script somewhere. There is some adapation for FireFox but now under FireFox we have the NPE: {code} window.event.cancelBubble = true; {code} To conclude, the solution is really to stop event propagation to ovoid the NPE inside jsf.js.jsf but the way to be done must be adapted to each browser. was (Author: jorelia64): Solution found by setting the following script inside the header. There is some adapation for FireFox does not recognize: "window.event is undefined" but now under FireFox we have the NPE. {code} {code} To conclude, the solution is really to stop event propagation to ovoid the NPE inside jsf.js.jsf but the way to be done must be adapted to each browser. > IE8 - Object does not support this property or method - a4j:jsFunction > ---------------------------------------------------------------------- > > Key: RF-12038 > URL: https://issues.jboss.org/browse/RF-12038 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.2.0.Final > Environment: cssparser-0.9.6- guava-11.0.1 - hibernate-validator-4.2.0.Final - JSF/Mojarra 2.1.6 - springframework-3.0.6.RELEASE - sac-1.3 - Windows 7 - IE 8.0.1.7601.17514 > Reporter: Jean ANDRE > Assignee: Brian Leathem > Labels: waiting_on_user > Attachments: index.xhtml, NestedWeb.zip, NestedWeb_RF-12038.zip, ScreenShot_RF-12038.png > > > Under IE8, IE reports the following error message due to a javascript error. However, the page are well displayed and the application is running ok. > Object doesn't support this property or method line 177 caracter 1 > Object doesn't support this property or method line 177 caracter 99 > Under IE Debugger, the line is: > {code} > closeTab=function(tabId){RichFaces.ajax("closeTab",null,{"incId":"1","parameters":{"tabId":tabId} } )};< > The caracter 99, is..............................................................................| (here) > {code} > This is a code generated by a4j:jsFunction from the XHTML > {code} > > > > > > > {code} > The rendered code is : > {code} > > > > {code} > See also this link as we got almost a similar: https://bugzilla.redhat.com/show_bug.cgi?id=601360. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 23 13:35:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Fri, 23 Mar 2012 13:35:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11996) rich:contextMenu on several rows in extendedDataTable In-Reply-To: <1622600198.30257.1329820356436.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <821304956.28645.1332524147554.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679015#comment-12679015 ] Brian Leathem commented on RF-11996: ------------------------------------ I'll compare it to the desktop experience: # right click on an icon on your desktop ## it gets selected, and the contextmenu appears # right click on another icon ## the selection changes, and the contextmenu appears # hold shift/ctrl and right click on another icon, they all are selected and the contextMenu appears To me, this is the behaviour we should be emulating, and works today, excpet we need to make the change: {quote} if (rightClick && selected) { do not select } {quote} > rich:contextMenu on several rows in extendedDataTable > ----------------------------------------------------- > > Key: RF-11996 > URL: https://issues.jboss.org/browse/RF-11996 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-menu, component-tables > Affects Versions: 4.2.0.CR1 > Reporter: Philip Maes > Assignee: Brian Leathem > Fix For: 4.2.1.CR1 > > > Hi, > I was using the contextmenu from the sandbox and now I'm using the one from 4.2.0.RC1. With the sandbox contextmenu, when several rows in a table were selected the right-click to open the contextmenu didn't unselect others rows. > The new rich:contextMenu does unselect the other rows. It's quite embarassing because we can't use it to apply a contextmenu for several selected rows... > Thanks in advance, > best regards. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 23 13:35:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Fri, 23 Mar 2012 13:35:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11996) rich:contextMenu on several rows in extendedDataTable In-Reply-To: <1622600198.30257.1329820356436.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1199211820.28647.1332524147618.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679015#comment-12679015 ] Brian Leathem edited comment on RF-11996 at 3/23/12 1:34 PM: ------------------------------------------------------------- I'll compare it to the desktop experience: # right click on an icon on your desktop #* it gets selected, and the contextmenu appears # right click on another icon #* the selection changes, and the contextmenu appears # hold shift/ctrl and right click on another icon, they all are selected and the contextMenu appears To me, this is the behaviour we should be emulating, and works today, excpet we need to make the change: {quote} if (rightClick && selected) { do not select } {quote} was (Author: bleathem): I'll compare it to the desktop experience: # right click on an icon on your desktop ## it gets selected, and the contextmenu appears # right click on another icon ## the selection changes, and the contextmenu appears # hold shift/ctrl and right click on another icon, they all are selected and the contextMenu appears To me, this is the behaviour we should be emulating, and works today, excpet we need to make the change: {quote} if (rightClick && selected) { do not select } {quote} > rich:contextMenu on several rows in extendedDataTable > ----------------------------------------------------- > > Key: RF-11996 > URL: https://issues.jboss.org/browse/RF-11996 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-menu, component-tables > Affects Versions: 4.2.0.CR1 > Reporter: Philip Maes > Assignee: Brian Leathem > Fix For: 4.2.1.CR1 > > > Hi, > I was using the contextmenu from the sandbox and now I'm using the one from 4.2.0.RC1. With the sandbox contextmenu, when several rows in a table were selected the right-click to open the contextmenu didn't unselect others rows. > The new rich:contextMenu does unselect the other rows. It's quite embarassing because we can't use it to apply a contextmenu for several selected rows... > Thanks in advance, > best regards. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 23 16:37:48 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 23 Mar 2012 16:37:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12072) Lost event in push In-Reply-To: <1823827590.22721.1332335688298.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <712040448.28978.1332535068085.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated RF-12072: ---------------------------- Workaround Description: Use {{a4j:jsFunction}} and {{}} {code:XML} {code} Workaround: Workaround Exists > Lost event in push > ------------------ > > Key: RF-12072 > URL: https://issues.jboss.org/browse/RF-12072 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Reporter: Stian Thorgersen > Assignee: Luk?? Fry? > Fix For: 4.2.1.CR1 > > > Event can be lost if produced while a response is being prepared. I've attached an example where a push event is used to refresh a count whenever an event is fired. It's using Thread.sleep to simulate an event being produced while the response is being prepared. Note, if the sleep just before returning the count is removed it all works fine, and the page is refreshed every 5 seconds, but with the sleep in place the event is lost. > View: > {code} > > > xmlns:f="http://java.sun.com/jsf/core" > xmlns:h="http://java.sun.com/jsf/html" > xmlns:a4j="http://richfaces.org/a4j" > xmlns:rich="http://richfaces.org/rich"> > > > > > > > > > > > > > {code} > Bean: > {code} > package com.example; > import java.io.Serializable; > import java.util.concurrent.atomic.AtomicInteger; > import javax.enterprise.context.SessionScoped; > import javax.inject.Named; > import org.richfaces.application.push.TopicKey; > import org.richfaces.application.push.TopicsContext; > @Named > @SessionScoped > public class MyBean implements Serializable > { > private AtomicInteger count = new AtomicInteger(); > public int getCount() > { > int c = count.get(); > new Thread() > { > public void run() > { > try > { > Thread.sleep(5000); > count.incrementAndGet(); > TopicKey topicKey = new TopicKey("chat"); > TopicsContext topicsContext = TopicsContext.lookup(); > topicsContext.publish(topicKey, ""); > } > catch (Exception e) > { > e.printStackTrace(); > } > }; > }.start(); > > try > { > Thread.sleep(10000); > } > catch (InterruptedException e) > { > } > return c; > } > } > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 23 16:37:48 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 23 Mar 2012 16:37:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12072) Lost event in push In-Reply-To: <1823827590.22721.1332335688298.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1053617124.28988.1332535068577.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679059#comment-12679059 ] Luk?? Fry? commented on RF-12072: --------------------------------- Hey Stian, I have added simple naive workaround for this issue. > Lost event in push > ------------------ > > Key: RF-12072 > URL: https://issues.jboss.org/browse/RF-12072 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Reporter: Stian Thorgersen > Assignee: Luk?? Fry? > Fix For: 4.2.1.CR1 > > > Event can be lost if produced while a response is being prepared. I've attached an example where a push event is used to refresh a count whenever an event is fired. It's using Thread.sleep to simulate an event being produced while the response is being prepared. Note, if the sleep just before returning the count is removed it all works fine, and the page is refreshed every 5 seconds, but with the sleep in place the event is lost. > View: > {code} > > > xmlns:f="http://java.sun.com/jsf/core" > xmlns:h="http://java.sun.com/jsf/html" > xmlns:a4j="http://richfaces.org/a4j" > xmlns:rich="http://richfaces.org/rich"> > > > > > > > > > > > > > {code} > Bean: > {code} > package com.example; > import java.io.Serializable; > import java.util.concurrent.atomic.AtomicInteger; > import javax.enterprise.context.SessionScoped; > import javax.inject.Named; > import org.richfaces.application.push.TopicKey; > import org.richfaces.application.push.TopicsContext; > @Named > @SessionScoped > public class MyBean implements Serializable > { > private AtomicInteger count = new AtomicInteger(); > public int getCount() > { > int c = count.get(); > new Thread() > { > public void run() > { > try > { > Thread.sleep(5000); > count.incrementAndGet(); > TopicKey topicKey = new TopicKey("chat"); > TopicsContext topicsContext = TopicsContext.lookup(); > topicsContext.publish(topicKey, ""); > } > catch (Exception e) > { > e.printStackTrace(); > } > }; > }.start(); > > try > { > Thread.sleep(10000); > } > catch (InterruptedException e) > { > } > return c; > } > } > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 23 16:42:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 23 Mar 2012 16:42:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12072) Lost event in push In-Reply-To: <1823827590.22721.1332335688298.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1968623475.28993.1332535367456.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679060#comment-12679060 ] Luk?? Fry? commented on RF-12072: --------------------------------- Currently {{a4j:push}} subscribes once page is fully loaded [1]. What we can do is subscribe immediately, but queue all requests which will come before document is ready. Then on document ready event, we will fire all events queued before. [1] https://github.com/richfaces/components/blob/develop/core/ui/src/main/resources/META-INF/resources/org.richfaces/push.js#L185 > Lost event in push > ------------------ > > Key: RF-12072 > URL: https://issues.jboss.org/browse/RF-12072 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Reporter: Stian Thorgersen > Assignee: Luk?? Fry? > Fix For: 4.2.1.CR1 > > > Event can be lost if produced while a response is being prepared. I've attached an example where a push event is used to refresh a count whenever an event is fired. It's using Thread.sleep to simulate an event being produced while the response is being prepared. Note, if the sleep just before returning the count is removed it all works fine, and the page is refreshed every 5 seconds, but with the sleep in place the event is lost. > View: > {code} > > > xmlns:f="http://java.sun.com/jsf/core" > xmlns:h="http://java.sun.com/jsf/html" > xmlns:a4j="http://richfaces.org/a4j" > xmlns:rich="http://richfaces.org/rich"> > > > > > > > > > > > > > {code} > Bean: > {code} > package com.example; > import java.io.Serializable; > import java.util.concurrent.atomic.AtomicInteger; > import javax.enterprise.context.SessionScoped; > import javax.inject.Named; > import org.richfaces.application.push.TopicKey; > import org.richfaces.application.push.TopicsContext; > @Named > @SessionScoped > public class MyBean implements Serializable > { > private AtomicInteger count = new AtomicInteger(); > public int getCount() > { > int c = count.get(); > new Thread() > { > public void run() > { > try > { > Thread.sleep(5000); > count.incrementAndGet(); > TopicKey topicKey = new TopicKey("chat"); > TopicsContext topicsContext = TopicsContext.lookup(); > topicsContext.publish(topicKey, ""); > } > catch (Exception e) > { > e.printStackTrace(); > } > }; > }.start(); > > try > { > Thread.sleep(10000); > } > catch (InterruptedException e) > { > } > return c; > } > } > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 23 16:44:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 23 Mar 2012 16:44:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12072) Lost event in push In-Reply-To: <1823827590.22721.1332335688298.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <729187840.29004.1332535487310.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679062#comment-12679062 ] Luk?? Fry? commented on RF-12072: --------------------------------- Hey Stian, any chance you could look into fixing the issue the proposed way ^ ? > Lost event in push > ------------------ > > Key: RF-12072 > URL: https://issues.jboss.org/browse/RF-12072 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Reporter: Stian Thorgersen > Assignee: Luk?? Fry? > Fix For: 4.2.1.CR1 > > > Event can be lost if produced while a response is being prepared. I've attached an example where a push event is used to refresh a count whenever an event is fired. It's using Thread.sleep to simulate an event being produced while the response is being prepared. Note, if the sleep just before returning the count is removed it all works fine, and the page is refreshed every 5 seconds, but with the sleep in place the event is lost. > View: > {code} > > > xmlns:f="http://java.sun.com/jsf/core" > xmlns:h="http://java.sun.com/jsf/html" > xmlns:a4j="http://richfaces.org/a4j" > xmlns:rich="http://richfaces.org/rich"> > > > > > > > > > > > > > {code} > Bean: > {code} > package com.example; > import java.io.Serializable; > import java.util.concurrent.atomic.AtomicInteger; > import javax.enterprise.context.SessionScoped; > import javax.inject.Named; > import org.richfaces.application.push.TopicKey; > import org.richfaces.application.push.TopicsContext; > @Named > @SessionScoped > public class MyBean implements Serializable > { > private AtomicInteger count = new AtomicInteger(); > public int getCount() > { > int c = count.get(); > new Thread() > { > public void run() > { > try > { > Thread.sleep(5000); > count.incrementAndGet(); > TopicKey topicKey = new TopicKey("chat"); > TopicsContext topicsContext = TopicsContext.lookup(); > topicsContext.publish(topicKey, ""); > } > catch (Exception e) > { > e.printStackTrace(); > } > }; > }.start(); > > try > { > Thread.sleep(10000); > } > catch (InterruptedException e) > { > } > return c; > } > } > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Sat Mar 24 13:09:48 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Sat, 24 Mar 2012 13:09:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-10968) Tree: treeSelectionChangeListener and treeToggleListener do not work In-Reply-To: <35352639.27278.1304411418583.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <178634877.29388.1332608988642.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-10968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-10968: ------------------------------- Fix Version/s: 4.2.1.CR1 (was: 4.3-Tracking) > Tree: treeSelectionChangeListener and treeToggleListener do not work > -------------------------------------------------------------------- > > Key: RF-10968 > URL: https://issues.jboss.org/browse/RF-10968 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: base functionality , component-tree > Affects Versions: 4.0.0.Final > Environment: RichFaces 4.1.0-SNAPSHOT r.22458 > Metamer 4.1.0-SNAPSHOT r.22459 > Mojarra 2.0.3- > JBoss AS 6.0.0.Final > OpenJDK Runtime Environment 1.6.0_20-b20 @ Linux > Chrome 11.0.696.57 @ Linux i686 > Reporter: Pavol Pitonak > Fix For: 4.2.1.CR1 > > Attachments: NodesTreeSequenceKeyModelImpl.java, tree.xhtml, TreeBean.java, TreeNodeImpl.java > > > Attributes treeSelectionChangeListener and treeToggleListener in rich:tree do not work. However, attributes selectionChangeListener and toggleListener do work. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Sat Mar 24 13:11:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Sat, 24 Mar 2012 13:11:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12080) rich:hotKey usage clears body onload attribute In-Reply-To: <1411413331.27453.1332488387294.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1525891085.29390.1332609107715.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12080: ------------------------------- Fix Version/s: 4.2.1.CR1 > rich:hotKey usage clears body onload attribute > ---------------------------------------------- > > Key: RF-12080 > URL: https://issues.jboss.org/browse/RF-12080 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component > Affects Versions: 4.2.0.Final > Environment: myfaces 2.1.6, tomahawk 1.1.11 > Reporter: Michael Heinen > Priority: Minor > Fix For: 4.2.1.CR1 > > > I'm happy to see rich:hotKey in richfaces 4.2, I used it already with richfaces 3.3.3. > One thing I noticed now is that the onload attribute of t:documentboy is cleared on clientside as soon as rich:hotKey is used on a page. Maybe caused by jquery usage? > From my pov this should be either fixed or documented in the component guide as well as in the showcase sample. > Workaround is obvious: Instead of onload use document.ready -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Sat Mar 24 13:13:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Sat, 24 Mar 2012 13:13:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12081) Problem with RichEditor RF 4.2.0 In-Reply-To: <1278339548.27975.1332502007395.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <2005441719.29392.1332609227304.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12081: ------------------------------- Labels: waiting_on_user (was: ) Can you upload the picture you are referring to? Also, do you see this problem with the showcase? http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=editor > Problem with RichEditor RF 4.2.0 > -------------------------------- > > Key: RF-12081 > URL: https://issues.jboss.org/browse/RF-12081 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.2.0.Final > Reporter: phelen harg > Labels: waiting_on_user > > I'm migrating my Application from RF 3.3.3 to RF 4.2.0. But now i'm facing a problem with the richEditor. When I load the the component, all the links in application receive a background like this picture: > Analizing the code with Firebug, I found the problem in the CSS of RichEditor. /org.richfaces.resources/javax.faces.resource/org.richfaces.ckeditor/skins/richfaces/editor.ecss?db=eAHj0yqqAgACGAEl > If I erase the CSS the backgroud disappear. There is some kind of workaround for this? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Sat Mar 24 13:15:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Sat, 24 Mar 2012 13:15:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12082) Components: Output UI module doesn't pass unit tests (AbstractTogglePanelTest#testGetChildName) In-Reply-To: <147991329.28097.1332505547854.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <380516993.29394.1332609347988.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-12082. -------------------------------- Assignee: Brian Leathem Resolution: Out of Date This has already been fixed with commit: https://github.com/richfaces/components/commit/286b32c76a39564b739c4d46de28f3f2fea77bc4 > Components: Output UI module doesn't pass unit tests (AbstractTogglePanelTest#testGetChildName) > ----------------------------------------------------------------------------------------------- > > Key: RF-12082 > URL: https://issues.jboss.org/browse/RF-12082 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.3.0.Milestone1 > Reporter: Jan Papousek > Assignee: Brian Leathem > Priority: Critical > > {code} > ------------------------------------------------------------------------------- > Test set: org.richfaces.component.AbstractTogglePanelTest > ------------------------------------------------------------------------------- > Tests run: 5, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.022 sec <<< FAILURE! > testGetChildName(org.richfaces.component.AbstractTogglePanelTest) Time elapsed: 0.005 sec <<< FAILURE! > java.lang.AssertionError: Expected exception: java.lang.IllegalArgumentException > at org.junit.internal.runners.statements.ExpectException.evaluate(ExpectException.java:32) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) > at org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) > at org.junit.runners.ParentRunner.run(ParentRunner.java:236) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:234) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:133) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:114) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:188) > at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:166) > at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:86) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:101) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74) > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Sat Mar 24 13:15:48 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Sat, 24 Mar 2012 13:15:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12083) Components: Output UI module doesn't pass unit tests (MenuItemRendererTest and DropDownMenuRendererTest) In-Reply-To: <356683327.28101.1332505788416.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1182282289.29396.1332609348133.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12083: ------------------------------- Fix Version/s: 4.2.1.CR1 Assignee: Brian Leathem > Components: Output UI module doesn't pass unit tests (MenuItemRendererTest and DropDownMenuRendererTest) > -------------------------------------------------------------------------------------------------------- > > Key: RF-12083 > URL: https://issues.jboss.org/browse/RF-12083 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.2.1.CR1 > Reporter: Jan Papousek > Assignee: Brian Leathem > Priority: Critical > Fix For: 4.2.1.CR1 > > > {code} > ------------------------------------------------------------------------------- > Test set: org.richfaces.renderkit.html.MenuItemRendererTest > ------------------------------------------------------------------------------- > Tests run: 6, Failures: 3, Errors: 0, Skipped: 1, Time elapsed: 3.172 sec <<< FAILURE! > testDoEncodeServerMode(org.richfaces.renderkit.html.MenuItemRendererTest) Time elapsed: 0.566 sec <<< FAILURE! > java.lang.AssertionError: XML was not similar:org.custommonkey.xmlunit.Diff > [different] Expected element tag name 'div' but was 'span' - comparing at /div[1]/div[1] to at /div[1]/span[1] >
    > > > > > > Test > > >
    > at org.junit.Assert.fail(Assert.java:91) > at org.junit.Assert.assertTrue(Assert.java:43) > at org.richfaces.renderkit.html.RendererTestBase.checkXmlStructure(RendererTestBase.java:93) > at org.richfaces.renderkit.html.RendererTestBase.doTest(RendererTestBase.java:81) > at org.richfaces.renderkit.html.RendererTestBase.doTest(RendererTestBase.java:73) > at org.richfaces.renderkit.html.MenuItemRendererTest.testDoEncodeServerMode(MenuItemRendererTest.java:51) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) > at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31) > at org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) > at org.junit.runners.ParentRunner.run(ParentRunner.java:236) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:234) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:133) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:114) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:188) > at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:166) > at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:86) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:101) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74) > testDoEncodeAjaxMode(org.richfaces.renderkit.html.MenuItemRendererTest) Time elapsed: 0.613 sec <<< FAILURE! > java.lang.AssertionError: XML was not similar:org.custommonkey.xmlunit.Diff > [different] Expected element tag name 'div' but was 'span' - comparing at /div[1]/div[1] to at /div[1]/span[1] >
    > > > > > > Test > > >
    > at org.junit.Assert.fail(Assert.java:91) > at org.junit.Assert.assertTrue(Assert.java:43) > at org.richfaces.renderkit.html.RendererTestBase.checkXmlStructure(RendererTestBase.java:93) > at org.richfaces.renderkit.html.RendererTestBase.doTest(RendererTestBase.java:81) > at org.richfaces.renderkit.html.RendererTestBase.doTest(RendererTestBase.java:73) > at org.richfaces.renderkit.html.MenuItemRendererTest.testDoEncodeAjaxMode(MenuItemRendererTest.java:71) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) > at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31) > at org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) > at org.junit.runners.ParentRunner.run(ParentRunner.java:236) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:234) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:133) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:114) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:188) > at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:166) > at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:86) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:101) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74) > testDoEncodeClientMode(org.richfaces.renderkit.html.MenuItemRendererTest) Time elapsed: 0.724 sec <<< FAILURE! > java.lang.AssertionError: XML was not similar:org.custommonkey.xmlunit.Diff > [different] Expected element tag name 'div' but was 'span' - comparing at /div[1]/div[1] to at /div[1]/span[1] >
    > > > > > > Test > > >
    > at org.junit.Assert.fail(Assert.java:91) > at org.junit.Assert.assertTrue(Assert.java:43) > at org.richfaces.renderkit.html.RendererTestBase.checkXmlStructure(RendererTestBase.java:93) > at org.richfaces.renderkit.html.RendererTestBase.doTest(RendererTestBase.java:81) > at org.richfaces.renderkit.html.RendererTestBase.doTest(RendererTestBase.java:73) > at org.richfaces.renderkit.html.MenuItemRendererTest.testDoEncodeClientMode(MenuItemRendererTest.java:88) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) > at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31) > at org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) > at org.junit.runners.ParentRunner.run(ParentRunner.java:236) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:234) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:133) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:114) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:188) > at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:166) > at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:86) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:101) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74) > {code} > {code} > ------------------------------------------------------------------------------- > Test set: org.richfaces.renderkit.html.DropDownMenuRendererTest > ------------------------------------------------------------------------------- > Tests run: 4, Failures: 2, Errors: 0, Skipped: 1, Time elapsed: 2.206 sec <<< FAILURE! > testDoEncodeServerMode(org.richfaces.renderkit.html.DropDownMenuRendererTest) Time elapsed: 0.729 sec <<< FAILURE! > java.lang.AssertionError: XML was not similar:org.custommonkey.xmlunit.Diff > [different] Expected element tag name 'div' but was 'span' - comparing at /div[1]/div[2]/div[1]/div[1]/div[1]/div[1] to at /div[1]/div[2]/div[1]/div[1]/div[1]/span[1] >
    >
    > > File >
    >
    > >
    > >
    > at org.junit.Assert.fail(Assert.java:91) > at org.junit.Assert.assertTrue(Assert.java:43) > at org.richfaces.renderkit.html.RendererTestBase.checkXmlStructure(RendererTestBase.java:93) > at org.richfaces.renderkit.html.RendererTestBase.doTest(RendererTestBase.java:81) > at org.richfaces.renderkit.html.RendererTestBase.doTest(RendererTestBase.java:73) > at org.richfaces.renderkit.html.DropDownMenuRendererTest.testDoEncodeServerMode(DropDownMenuRendererTest.java:51) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) > at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31) > at org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) > at org.junit.runners.ParentRunner.run(ParentRunner.java:236) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:234) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:133) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:114) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:188) > at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:166) > at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:86) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:101) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74) > testDoEncodeAjaxMode(org.richfaces.renderkit.html.DropDownMenuRendererTest) Time elapsed: 0.677 sec <<< FAILURE! > java.lang.AssertionError: XML was not similar:org.custommonkey.xmlunit.Diff > [different] Expected element tag name 'div' but was 'span' - comparing at /div[1]/div[2]/div[1]/div[1]/div[1]/div[1] to at /div[1]/div[2]/div[1]/div[1]/div[1]/span[1] >
    >
    > > File >
    >
    > >
    > >
    > at org.junit.Assert.fail(Assert.java:91) > at org.junit.Assert.assertTrue(Assert.java:43) > at org.richfaces.renderkit.html.RendererTestBase.checkXmlStructure(RendererTestBase.java:93) > at org.richfaces.renderkit.html.RendererTestBase.doTest(RendererTestBase.java:81) > at org.richfaces.renderkit.html.RendererTestBase.doTest(RendererTestBase.java:73) > at org.richfaces.renderkit.html.DropDownMenuRendererTest.testDoEncodeAjaxMode(DropDownMenuRendererTest.java:56) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) > at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31) > at org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) > at org.junit.runners.ParentRunner.run(ParentRunner.java:236) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:234) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:133) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:114) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:188) > at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:166) > at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:86) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:101) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74) > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Sat Mar 24 13:55:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Sat, 24 Mar 2012 13:55:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11936) rich:contextMenu activation is possible outside of tree nodes In-Reply-To: <643933580.14431.1328103828616.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <845620540.29415.1332611747803.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-11936. -------------------------------- Resolution: Done Added a selector filtering which DOM elements trigger the contextMenu. This selector can be overridden with the "targetSelector" attribute. > rich:contextMenu activation is possible outside of tree nodes > ------------------------------------------------------------- > > Key: RF-11936 > URL: https://issues.jboss.org/browse/RF-11936 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-menu, component-tree > Affects Versions: 4.2.0.CR1 > Environment: browsers: all browsers > Reporter: Juraj Huska > Assignee: Brian Leathem > Fix For: 4.2.1.CR1 > > Attachments: contextMenu.png, exdt_cm1.png, exdt_cm2.png > > > In the showcase demo for rich:contextMenu, the sample Tree ContextMenu, it is possible to activate the context menu not only from the nodes, but also outside of thenodes. > It is *rather a problem of the rich:tree*, since its rows contains nodes, which are rendered with 100% width. > When it is then selected with the contextMenu item, a popup with empty content is displayed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Sun Mar 25 14:52:49 2012 From: jira-events at lists.jboss.org (Ivan Costa (JIRA)) Date: Sun, 25 Mar 2012 14:52:49 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12084) Richfaces 4.2 when inside dont work and causes 'identifier resolved to null' Message-ID: <1382382061.29574.1332701569056.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Ivan Costa created RF-12084: ------------------------------- Summary: Richfaces 4.2 when inside dont work and causes 'identifier resolved to null' Key: RF-12084 URL: https://issues.jboss.org/browse/RF-12084 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-a4j-core Affects Versions: 4.2.0.Final Environment: Windows Vista, Firefox 11, Richfaces 4.2 Final, Mojarra 2.1.7, Tomcat 7.0.26 Reporter: Ivan Costa a4j:commandLink or a4j:ajax tags inside ui:fragment causes 'identifier resolved to null', but h:commandLink + f:ajax (both from Mojarra) works perfectly fine! The problem is described here https://community.jboss.org/message/723859 and here: https://community.jboss.org/thread/196867 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 26 00:10:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 26 Mar 2012 00:10:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12083) Components: Output UI module doesn't pass unit tests (MenuItemRendererTest and DropDownMenuRendererTest) In-Reply-To: <356683327.28101.1332505788416.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1964342779.29746.1332735047851.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-12083. -------------------------------- Resolution: Done > Components: Output UI module doesn't pass unit tests (MenuItemRendererTest and DropDownMenuRendererTest) > -------------------------------------------------------------------------------------------------------- > > Key: RF-12083 > URL: https://issues.jboss.org/browse/RF-12083 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.2.1.CR1 > Reporter: Jan Papousek > Assignee: Brian Leathem > Priority: Critical > Fix For: 4.2.1.CR1 > > > {code} > ------------------------------------------------------------------------------- > Test set: org.richfaces.renderkit.html.MenuItemRendererTest > ------------------------------------------------------------------------------- > Tests run: 6, Failures: 3, Errors: 0, Skipped: 1, Time elapsed: 3.172 sec <<< FAILURE! > testDoEncodeServerMode(org.richfaces.renderkit.html.MenuItemRendererTest) Time elapsed: 0.566 sec <<< FAILURE! > java.lang.AssertionError: XML was not similar:org.custommonkey.xmlunit.Diff > [different] Expected element tag name 'div' but was 'span' - comparing at /div[1]/div[1] to at /div[1]/span[1] >
    > > > > > > Test > > >
    > at org.junit.Assert.fail(Assert.java:91) > at org.junit.Assert.assertTrue(Assert.java:43) > at org.richfaces.renderkit.html.RendererTestBase.checkXmlStructure(RendererTestBase.java:93) > at org.richfaces.renderkit.html.RendererTestBase.doTest(RendererTestBase.java:81) > at org.richfaces.renderkit.html.RendererTestBase.doTest(RendererTestBase.java:73) > at org.richfaces.renderkit.html.MenuItemRendererTest.testDoEncodeServerMode(MenuItemRendererTest.java:51) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) > at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31) > at org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) > at org.junit.runners.ParentRunner.run(ParentRunner.java:236) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:234) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:133) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:114) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:188) > at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:166) > at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:86) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:101) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74) > testDoEncodeAjaxMode(org.richfaces.renderkit.html.MenuItemRendererTest) Time elapsed: 0.613 sec <<< FAILURE! > java.lang.AssertionError: XML was not similar:org.custommonkey.xmlunit.Diff > [different] Expected element tag name 'div' but was 'span' - comparing at /div[1]/div[1] to at /div[1]/span[1] >
    > > > > > > Test > > >
    > at org.junit.Assert.fail(Assert.java:91) > at org.junit.Assert.assertTrue(Assert.java:43) > at org.richfaces.renderkit.html.RendererTestBase.checkXmlStructure(RendererTestBase.java:93) > at org.richfaces.renderkit.html.RendererTestBase.doTest(RendererTestBase.java:81) > at org.richfaces.renderkit.html.RendererTestBase.doTest(RendererTestBase.java:73) > at org.richfaces.renderkit.html.MenuItemRendererTest.testDoEncodeAjaxMode(MenuItemRendererTest.java:71) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) > at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31) > at org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) > at org.junit.runners.ParentRunner.run(ParentRunner.java:236) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:234) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:133) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:114) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:188) > at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:166) > at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:86) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:101) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74) > testDoEncodeClientMode(org.richfaces.renderkit.html.MenuItemRendererTest) Time elapsed: 0.724 sec <<< FAILURE! > java.lang.AssertionError: XML was not similar:org.custommonkey.xmlunit.Diff > [different] Expected element tag name 'div' but was 'span' - comparing at /div[1]/div[1] to at /div[1]/span[1] >
    > > > > > > Test > > >
    > at org.junit.Assert.fail(Assert.java:91) > at org.junit.Assert.assertTrue(Assert.java:43) > at org.richfaces.renderkit.html.RendererTestBase.checkXmlStructure(RendererTestBase.java:93) > at org.richfaces.renderkit.html.RendererTestBase.doTest(RendererTestBase.java:81) > at org.richfaces.renderkit.html.RendererTestBase.doTest(RendererTestBase.java:73) > at org.richfaces.renderkit.html.MenuItemRendererTest.testDoEncodeClientMode(MenuItemRendererTest.java:88) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) > at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31) > at org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) > at org.junit.runners.ParentRunner.run(ParentRunner.java:236) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:234) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:133) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:114) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:188) > at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:166) > at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:86) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:101) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74) > {code} > {code} > ------------------------------------------------------------------------------- > Test set: org.richfaces.renderkit.html.DropDownMenuRendererTest > ------------------------------------------------------------------------------- > Tests run: 4, Failures: 2, Errors: 0, Skipped: 1, Time elapsed: 2.206 sec <<< FAILURE! > testDoEncodeServerMode(org.richfaces.renderkit.html.DropDownMenuRendererTest) Time elapsed: 0.729 sec <<< FAILURE! > java.lang.AssertionError: XML was not similar:org.custommonkey.xmlunit.Diff > [different] Expected element tag name 'div' but was 'span' - comparing at /div[1]/div[2]/div[1]/div[1]/div[1]/div[1] to at /div[1]/div[2]/div[1]/div[1]/div[1]/span[1] >
    >
    > > File >
    >
    > >
    > >
    > at org.junit.Assert.fail(Assert.java:91) > at org.junit.Assert.assertTrue(Assert.java:43) > at org.richfaces.renderkit.html.RendererTestBase.checkXmlStructure(RendererTestBase.java:93) > at org.richfaces.renderkit.html.RendererTestBase.doTest(RendererTestBase.java:81) > at org.richfaces.renderkit.html.RendererTestBase.doTest(RendererTestBase.java:73) > at org.richfaces.renderkit.html.DropDownMenuRendererTest.testDoEncodeServerMode(DropDownMenuRendererTest.java:51) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) > at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31) > at org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) > at org.junit.runners.ParentRunner.run(ParentRunner.java:236) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:234) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:133) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:114) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:188) > at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:166) > at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:86) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:101) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74) > testDoEncodeAjaxMode(org.richfaces.renderkit.html.DropDownMenuRendererTest) Time elapsed: 0.677 sec <<< FAILURE! > java.lang.AssertionError: XML was not similar:org.custommonkey.xmlunit.Diff > [different] Expected element tag name 'div' but was 'span' - comparing at /div[1]/div[2]/div[1]/div[1]/div[1]/div[1] to at /div[1]/div[2]/div[1]/div[1]/div[1]/span[1] >
    >
    > > File >
    >
    > >
    > >
    > at org.junit.Assert.fail(Assert.java:91) > at org.junit.Assert.assertTrue(Assert.java:43) > at org.richfaces.renderkit.html.RendererTestBase.checkXmlStructure(RendererTestBase.java:93) > at org.richfaces.renderkit.html.RendererTestBase.doTest(RendererTestBase.java:81) > at org.richfaces.renderkit.html.RendererTestBase.doTest(RendererTestBase.java:73) > at org.richfaces.renderkit.html.DropDownMenuRendererTest.testDoEncodeAjaxMode(DropDownMenuRendererTest.java:56) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) > at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31) > at org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) > at org.junit.runners.ParentRunner.run(ParentRunner.java:236) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:234) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:133) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:114) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:188) > at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:166) > at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:86) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:101) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74) > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 26 00:29:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 26 Mar 2012 00:29:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11996) rich:contextMenu on several rows in extendedDataTable In-Reply-To: <1622600198.30257.1329820356436.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <76253475.29769.1332736187450.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-11996. -------------------------------- Resolution: Done Prevented the contextMenu click from triggering an EDT row selection if the row was already selected. Feel free to re-open this issue, if you have a use case that does not fit this solution. > rich:contextMenu on several rows in extendedDataTable > ----------------------------------------------------- > > Key: RF-11996 > URL: https://issues.jboss.org/browse/RF-11996 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-menu, component-tables > Affects Versions: 4.2.0.CR1 > Reporter: Philip Maes > Assignee: Brian Leathem > Fix For: 4.2.1.CR1 > > > Hi, > I was using the contextmenu from the sandbox and now I'm using the one from 4.2.0.RC1. With the sandbox contextmenu, when several rows in a table were selected the right-click to open the contextmenu didn't unselect others rows. > The new rich:contextMenu does unselect the other rows. It's quite embarassing because we can't use it to apply a contextmenu for several selected rows... > Thanks in advance, > best regards. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 26 01:03:15 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 26 Mar 2012 01:03:15 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11968) 4.2.0.CR1 contextMenu positioning incorrect when dynamically rendering on row select In-Reply-To: <784637995.32591.1328750928377.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1079512174.29793.1332738195798.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-11968: ------------------------------- Fix Version/s: 4.Future (was: 4.2.1.CR1) Workaround Description: Declare the contextMenu component before the dynamically rendered div, as in: {code} ... ... {code} This way, the dynamic rendering of the panel div does not affect the position of the contextMenu was:None tested. Workaround description updated, further resolution of this issue will continue when the positioning jQuery plugin has adequate Qunit tests. > 4.2.0.CR1 contextMenu positioning incorrect when dynamically rendering on row select > ------------------------------------------------------------------------------------ > > Key: RF-11968 > URL: https://issues.jboss.org/browse/RF-11968 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-menu > Affects Versions: 4.2.0.CR1 > Environment: Chrome browser Glassfish 3.1.1 Mojarra 2.1.6 > Reporter: Brendan Healey > Assignee: Brian Leathem > Fix For: 4.Future > > Attachments: contextMenuWrongPositioning.png > > > There's a positioning error with contextMenu in the following scenario. > I have an extendedDataTable which renders a rich:panel when a row in the > table is selected. Initially no row is selected and the rich:panel is not > rendered. I right click in the table and the menuItem appears way below > the row I right clicked. > {code} > id="mytable" value="#{bean.someList}" var="var" > selection="#{bean.selectedRow}" > selectionMode="single"> > event="selectionchange" > listener="#{bean.doRowSelect}"/> > ... > > > > ... > > > > > > {code} > {code} > public void doRowSelect(...) { > selectedDepartment = ... (usual stuff); > } > {code} > Also tried with contextMenu mode="client" with the same result. > Regards, > Brendan. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 26 01:06:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 26 Mar 2012 01:06:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12085) The richfaces version change script is missing version strings in the kitchensink archetype file Message-ID: <1849208334.29814.1332738407483.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Brian Leathem created RF-12085: ---------------------------------- Summary: The richfaces version change script is missing version strings in the kitchensink archetype file Key: RF-12085 URL: https://issues.jboss.org/browse/RF-12085 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: archetype, build/distribution Reporter: Brian Leathem Assignee: Luk?? Fry? Priority: Critical Fix For: 4.2.1.CR1 {code} [archetypes (release/4.2.1.CR1)]> ack 4.3.0 components/component/src/main/resources/META-INF/maven/archetype-metadata.xml 39: 4.3.0-SNAPSHOT components/components-aggregator/src/main/resources/META-INF/maven/archetype-metadata.xml 36: 4.3.0-SNAPSHOT components/component-short/src/main/resources/META-INF/maven/archetype-metadata.xml 39: 4.3.0-SNAPSHOT kitchensink/src/main/resources/META-INF/maven/archetype-metadata.xml 10: 4.3.0-SNAPSHOT kitchensink/src/test/resources/projects/basic/archetype.properties 5:richfaces-version=4.3.0-SNAPSHOT {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 26 01:08:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 26 Mar 2012 01:08:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12086) Update the RichFaces WFK version in the archetypes Message-ID: <1088995279.29817.1332738527229.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Brian Leathem created RF-12086: ---------------------------------- Summary: Update the RichFaces WFK version in the archetypes Key: RF-12086 URL: https://issues.jboss.org/browse/RF-12086 Project: RichFaces Issue Type: Task Security Level: Public (Everyone can see) Components: archetype Reporter: Brian Leathem Priority: Critical Fix For: 4.2.1.CR1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 26 01:19:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 26 Mar 2012 01:19:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12086) Update the RichFaces WFK version in the archetypes In-Reply-To: <1088995279.29817.1332738527229.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <885881222.29818.1332739187342.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-12086. -------------------------------- Resolution: Done > Update the RichFaces WFK version in the archetypes > -------------------------------------------------- > > Key: RF-12086 > URL: https://issues.jboss.org/browse/RF-12086 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: archetype > Reporter: Brian Leathem > Priority: Critical > Fix For: 4.2.1.CR1 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 26 01:19:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 26 Mar 2012 01:19:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12086) Update the RichFaces WFK version in the archetypes In-Reply-To: <1088995279.29817.1332738527229.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1534781798.29819.1332739187410.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem reassigned RF-12086: ---------------------------------- Assignee: Brian Leathem > Update the RichFaces WFK version in the archetypes > -------------------------------------------------- > > Key: RF-12086 > URL: https://issues.jboss.org/browse/RF-12086 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: archetype > Reporter: Brian Leathem > Assignee: Brian Leathem > Priority: Critical > Fix For: 4.2.1.CR1 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 26 01:19:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 26 Mar 2012 01:19:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12086) Update the RichFaces WFK version in the archetypes In-Reply-To: <1088995279.29817.1332738527229.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1250851143.29820.1332739187458.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem reopened RF-12086: -------------------------------- > Update the RichFaces WFK version in the archetypes > -------------------------------------------------- > > Key: RF-12086 > URL: https://issues.jboss.org/browse/RF-12086 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: archetype > Reporter: Brian Leathem > Assignee: Brian Leathem > Priority: Critical > Fix For: 4.2.1.CR1 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 26 01:19:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 26 Mar 2012 01:19:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12086) Update the RichFaces WFK version in the archetypes In-Reply-To: <1088995279.29817.1332738527229.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1872675132.29821.1332739187526.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem reassigned RF-12086: ---------------------------------- Assignee: (was: Brian Leathem) > Update the RichFaces WFK version in the archetypes > -------------------------------------------------- > > Key: RF-12086 > URL: https://issues.jboss.org/browse/RF-12086 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: archetype > Reporter: Brian Leathem > Priority: Critical > Fix For: 4.2.1.CR1 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 26 01:21:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 26 Mar 2012 01:21:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12064) Remove the superfluous versions from the generated pom in the kitchensink archetype In-Reply-To: <1846737024.18946.1332201047228.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <375879157.29822.1332739307657.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-12064. -------------------------------- Resolution: Done > Remove the superfluous versions from the generated pom in the kitchensink archetype > ----------------------------------------------------------------------------------- > > Key: RF-12064 > URL: https://issues.jboss.org/browse/RF-12064 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: archetype, build/distribution > Reporter: Brian Leathem > Assignee: Brian Leathem > Priority: Minor > Fix For: 4.2.1.CR1 > > > The kitchensink archetype unnecessarily specifies version for it's dependencies. The dependency version that are already specified in the BOM should be removed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 26 01:21:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 26 Mar 2012 01:21:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12086) Update the RichFaces WFK version in the archetypes In-Reply-To: <1088995279.29817.1332738527229.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <2054192308.29823.1332739307713.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem reassigned RF-12086: ---------------------------------- Assignee: Brian Leathem > Update the RichFaces WFK version in the archetypes > -------------------------------------------------- > > Key: RF-12086 > URL: https://issues.jboss.org/browse/RF-12086 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: archetype > Reporter: Brian Leathem > Assignee: Brian Leathem > Priority: Critical > Fix For: 4.2.1.CR1 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 26 01:21:48 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 26 Mar 2012 01:21:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11977) Multiple fileUpload controls on the same page do not work In-Reply-To: <1904484642.1106.1329137880969.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1317389287.29825.1332739308317.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem reassigned RF-11977: ---------------------------------- Assignee: Brian Leathem > Multiple fileUpload controls on the same page do not work > --------------------------------------------------------- > > Key: RF-11977 > URL: https://issues.jboss.org/browse/RF-11977 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.1.0.Final > Environment: IE7,8,9, FireFox, Google Chrome > Reporter: Roxana Balaci > Assignee: Brian Leathem > Fix For: 4.2.1.CR1 > > Attachments: rf-11977-chromium-afterClickOn2ndUploadBtn.png, rf-11977-Chromium.png, rf-11977-ff11.png > > > Situation: > Two rich:fileUpload controls, in the same form. > When: > # choose first file for upload > # choose second file for upload > # click upload button for the first file > The first control disappears from the page and you cannot upload the second file (the upload event is never caught). > Could you please indicate a solution for this problem? > Thank you very much! > Part of the code used for testing is the following: > {code} > > > > fileUploadListener="#{bean.method1}" maxFilesQuantity="1" > immediateUpload="true" listHeight="65px" > > > fileUploadListener="#{bean.method2}" maxFilesQuantity="1" > immediateUpload="true" listHeight="65px" > > > render="stg" /> > > > > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 26 01:21:50 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 26 Mar 2012 01:21:50 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-10968) Tree: treeSelectionChangeListener and treeToggleListener do not work In-Reply-To: <35352639.27278.1304411418583.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <815305212.29830.1332739310792.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-10968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem reassigned RF-10968: ---------------------------------- Assignee: Brian Leathem > Tree: treeSelectionChangeListener and treeToggleListener do not work > -------------------------------------------------------------------- > > Key: RF-10968 > URL: https://issues.jboss.org/browse/RF-10968 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: base functionality , component-tree > Affects Versions: 4.0.0.Final > Environment: RichFaces 4.1.0-SNAPSHOT r.22458 > Metamer 4.1.0-SNAPSHOT r.22459 > Mojarra 2.0.3- > JBoss AS 6.0.0.Final > OpenJDK Runtime Environment 1.6.0_20-b20 @ Linux > Chrome 11.0.696.57 @ Linux i686 > Reporter: Pavol Pitonak > Assignee: Brian Leathem > Fix For: 4.2.1.CR1 > > Attachments: NodesTreeSequenceKeyModelImpl.java, tree.xhtml, TreeBean.java, TreeNodeImpl.java > > > Attributes treeSelectionChangeListener and treeToggleListener in rich:tree do not work. However, attributes selectionChangeListener and toggleListener do work. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 26 04:06:47 2012 From: jira-events at lists.jboss.org (Vladimir Romashov (JIRA)) Date: Mon, 26 Mar 2012 04:06:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12077) Selection in extendedDataTable doesn't work in Chrome In-Reply-To: <2021407965.24539.1332406547698.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <68795795.30005.1332749207538.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679168#comment-12679168 ] Vladimir Romashov commented on RF-12077: ---------------------------------------- I found problem. I have addon AdBlock 2.5.22 in my chrome, if I disable it, selection works fine. I close issuer. > Selection in extendedDataTable doesn't work in Chrome > ----------------------------------------------------- > > Key: RF-12077 > URL: https://issues.jboss.org/browse/RF-12077 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.2.0.Final > Environment: Windows XP. JBoss AS 7 Chrome 17.0.963.83 > Reporter: Vladimir Romashov > Priority: Blocker > Labels: waiting_on_user > > JavaScript error in console on rendered page with > Uncaught TypeError: Cannot read property 'length' of null > richfaces.utils.getCSSRule extendedDataTable.js.jsf:40 > richfaces.ui.ExtendedDataTable.richfaces.BaseComponent.extendClass.initialize extendedDataTable.js.jsf:362 > jQuery.extend.proxy.proxyjquery.js.jsf:814 > jQuery.Callbacks.firejquery.js.jsf:1046 > jQuery.Callbacks.self.fireWithjquery.js.jsf:1164 > jQuery.extend.readyjquery.js.jsf:435 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 26 04:08:47 2012 From: jira-events at lists.jboss.org (Vladimir Romashov (JIRA)) Date: Mon, 26 Mar 2012 04:08:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12077) Selection in extendedDataTable doesn't work in Chrome In-Reply-To: <2021407965.24539.1332406547698.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <311868608.30008.1332749327720.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Romashov closed RF-12077. ---------------------------------- Resolution: Rejected Problem in chrome addon AdBlock 2.5.22. > Selection in extendedDataTable doesn't work in Chrome > ----------------------------------------------------- > > Key: RF-12077 > URL: https://issues.jboss.org/browse/RF-12077 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.2.0.Final > Environment: Windows XP. JBoss AS 7 Chrome 17.0.963.83 > Reporter: Vladimir Romashov > Priority: Blocker > Labels: waiting_on_user > > JavaScript error in console on rendered page with > Uncaught TypeError: Cannot read property 'length' of null > richfaces.utils.getCSSRule extendedDataTable.js.jsf:40 > richfaces.ui.ExtendedDataTable.richfaces.BaseComponent.extendClass.initialize extendedDataTable.js.jsf:362 > jQuery.extend.proxy.proxyjquery.js.jsf:814 > jQuery.Callbacks.firejquery.js.jsf:1046 > jQuery.Callbacks.self.fireWithjquery.js.jsf:1164 > jQuery.extend.readyjquery.js.jsf:435 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 26 04:10:50 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 26 Mar 2012 04:10:50 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12085) The richfaces version change script is missing version strings in the kitchensink archetype file In-Reply-To: <1849208334.29814.1332738407483.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1911036480.30028.1332749450084.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679173#comment-12679173 ] Luk?? Fry? commented on RF-12085: --------------------------------- Hi Brian, nice catch. I forgot to change version in regular files (other than {{pom.xml}}) in {{archetypes}}. Other modules are okay. > The richfaces version change script is missing version strings in the kitchensink archetype file > ------------------------------------------------------------------------------------------------ > > Key: RF-12085 > URL: https://issues.jboss.org/browse/RF-12085 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: archetype, build/distribution > Reporter: Brian Leathem > Assignee: Luk?? Fry? > Priority: Critical > Fix For: 4.2.1.CR1 > > > {code} > [archetypes (release/4.2.1.CR1)]> ack 4.3.0 > components/component/src/main/resources/META-INF/maven/archetype-metadata.xml > 39: 4.3.0-SNAPSHOT > components/components-aggregator/src/main/resources/META-INF/maven/archetype-metadata.xml > 36: 4.3.0-SNAPSHOT > components/component-short/src/main/resources/META-INF/maven/archetype-metadata.xml > 39: 4.3.0-SNAPSHOT > kitchensink/src/main/resources/META-INF/maven/archetype-metadata.xml > 10: 4.3.0-SNAPSHOT > kitchensink/src/test/resources/projects/basic/archetype.properties > 5:richfaces-version=4.3.0-SNAPSHOT > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 26 04:10:50 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 26 Mar 2012 04:10:50 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12085) The richfaces version change script is missing version strings in the kitchensink archetype file In-Reply-To: <1849208334.29814.1332738407483.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <583572585.30031.1332749450214.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved RF-12085. ----------------------------- Resolution: Done > The richfaces version change script is missing version strings in the kitchensink archetype file > ------------------------------------------------------------------------------------------------ > > Key: RF-12085 > URL: https://issues.jboss.org/browse/RF-12085 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: archetype, build/distribution > Reporter: Brian Leathem > Assignee: Luk?? Fry? > Priority: Critical > Fix For: 4.2.1.CR1 > > > {code} > [archetypes (release/4.2.1.CR1)]> ack 4.3.0 > components/component/src/main/resources/META-INF/maven/archetype-metadata.xml > 39: 4.3.0-SNAPSHOT > components/components-aggregator/src/main/resources/META-INF/maven/archetype-metadata.xml > 36: 4.3.0-SNAPSHOT > components/component-short/src/main/resources/META-INF/maven/archetype-metadata.xml > 39: 4.3.0-SNAPSHOT > kitchensink/src/main/resources/META-INF/maven/archetype-metadata.xml > 10: 4.3.0-SNAPSHOT > kitchensink/src/test/resources/projects/basic/archetype.properties > 5:richfaces-version=4.3.0-SNAPSHOT > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 26 04:14:48 2012 From: jira-events at lists.jboss.org (Juraj Huska (JIRA)) Date: Mon, 26 Mar 2012 04:14:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11965) showcase - a4j:push - error thrown after creating topic for pushCdi In-Reply-To: <1869426390.30466.1328703648739.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1128609033.30048.1332749688946.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679176#comment-12679176 ] Juraj Huska commented on RF-11965: ---------------------------------- Verified that it is OK now. > showcase - a4j:push - error thrown after creating topic for pushCdi > ------------------------------------------------------------------- > > Key: RF-11965 > URL: https://issues.jboss.org/browse/RF-11965 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll, showcase > Affects Versions: 4.2.0.Final > Environment: container: JBoss AS 7.1.0.CR1b > Reporter: Juraj Huska > Assignee: Luk?? Fry? > Priority: Minor > Fix For: 4.2.1.CR1 > > > When deploying showcase 4.2.0.CR1 then after pushCdi topic created an error is thrown: > {code} > 18:13:42,211 INFO [org.richfaces.demo.push.JMSInitializer] (MSC service thread 1-2) initializing > 18:13:42,219 INFO [org.richfaces.demo.push.JMSInitializer] (MSC service thread 1-2) AS7MessagingProviderManagement initialized > 18:13:42,219 INFO [org.richfaces.demo.push.JMSInitializer] (MSC service thread 1-2) creating topic pushJms > 18:13:42,761 INFO [org.richfaces.demo.push.JMSInitializer] (MSC service thread 1-2) creating topic pushTopicsContext > 18:13:42,802 INFO [org.richfaces.demo.push.JMSInitializer] (MSC service thread 1-2) creating topic pushCdi > 18:13:42,972 SEVERE [org.richfaces.demo.push.MessageProducerRunnable] (MessageProducerThread) javax.faces.FacesException: topic/pushTopicsContext -- service jboss.naming.context.java.topic.$ > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:397) [guava-10.0.1.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl.createTopic(JMSTopicsContextImpl.java:281) [richfaces-core-impl-4.2.0.CR1.jar:] > at org.richfaces.application.push.TopicsContext.getOrCreateTopic(TopicsContext.java:48) [richfaces-core-api-4.2.0.CR1.jar:] > at org.richfaces.application.push.TopicsContext.publish(TopicsContext.java:69) [richfaces-core-api-4.2.0.CR1.jar:] > at org.richfaces.demo.push.TopicsContextMessageProducer.sendMessage(TopicsContextMessageProducer.java:46) [classes:] > at org.richfaces.demo.push.MessageProducerRunnable.run(MessageProducerRunnable.java:57) [classes:] > at java.lang.Thread.run(Thread.java:662) [:1.6.0_22] > Caused by: javax.faces.FacesException: topic/pushTopicsContext -- service jboss.naming.context.java.topic.pushTopicsContext > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:207) [richfaces-core-impl-4.2.0.CR1.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:195) [richfaces-core-impl-4.2.0.CR1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingValueReference.compute(ComputingConcurrentHashMap.java:355) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.compute(ComputingConcurrentHashMap.java:184) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.getOrCompute(ComputingConcurrentHashMap.java:153) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap.getOrCompute(ComputingConcurrentHashMap.java:69) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:393) [guava-10.0.1.jar:] > ... 6 more > Caused by: javax.naming.NameNotFoundException: topic/pushTopicsContext -- service jboss.naming.context.java.topic.pushTopicsContext > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:92) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:177) > at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:87) > at javax.naming.InitialContext.lookup(InitialContext.java:396) [:1.6.0_22] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.lookupTopic(JMSTopicsContextImpl.java:94) [richfaces-core-impl-4.2.0-20120130.140419-26.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.start(JMSTopicsContextImpl.java:125) [richfaces-core-impl-4.2.0-20120130.140419-26.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:199) [richfaces-core-impl-4.2.0-20120130.140419-26.jar:] > ... 12 more > {code} > The functionality of push demos is fine, just the tests are not passing on Hudson, which I have to investigate whether it is caused by this one. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 26 04:14:49 2012 From: jira-events at lists.jboss.org (Juraj Huska (JIRA)) Date: Mon, 26 Mar 2012 04:14:49 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11965) showcase - a4j:push - error thrown after creating topic for pushCdi In-Reply-To: <1869426390.30466.1328703648739.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1075411159.30052.1332749689315.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj Huska closed RF-11965. ---------------------------- > showcase - a4j:push - error thrown after creating topic for pushCdi > ------------------------------------------------------------------- > > Key: RF-11965 > URL: https://issues.jboss.org/browse/RF-11965 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll, showcase > Affects Versions: 4.2.0.Final > Environment: container: JBoss AS 7.1.0.CR1b > Reporter: Juraj Huska > Assignee: Luk?? Fry? > Priority: Minor > Fix For: 4.2.1.CR1 > > > When deploying showcase 4.2.0.CR1 then after pushCdi topic created an error is thrown: > {code} > 18:13:42,211 INFO [org.richfaces.demo.push.JMSInitializer] (MSC service thread 1-2) initializing > 18:13:42,219 INFO [org.richfaces.demo.push.JMSInitializer] (MSC service thread 1-2) AS7MessagingProviderManagement initialized > 18:13:42,219 INFO [org.richfaces.demo.push.JMSInitializer] (MSC service thread 1-2) creating topic pushJms > 18:13:42,761 INFO [org.richfaces.demo.push.JMSInitializer] (MSC service thread 1-2) creating topic pushTopicsContext > 18:13:42,802 INFO [org.richfaces.demo.push.JMSInitializer] (MSC service thread 1-2) creating topic pushCdi > 18:13:42,972 SEVERE [org.richfaces.demo.push.MessageProducerRunnable] (MessageProducerThread) javax.faces.FacesException: topic/pushTopicsContext -- service jboss.naming.context.java.topic.$ > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:397) [guava-10.0.1.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl.createTopic(JMSTopicsContextImpl.java:281) [richfaces-core-impl-4.2.0.CR1.jar:] > at org.richfaces.application.push.TopicsContext.getOrCreateTopic(TopicsContext.java:48) [richfaces-core-api-4.2.0.CR1.jar:] > at org.richfaces.application.push.TopicsContext.publish(TopicsContext.java:69) [richfaces-core-api-4.2.0.CR1.jar:] > at org.richfaces.demo.push.TopicsContextMessageProducer.sendMessage(TopicsContextMessageProducer.java:46) [classes:] > at org.richfaces.demo.push.MessageProducerRunnable.run(MessageProducerRunnable.java:57) [classes:] > at java.lang.Thread.run(Thread.java:662) [:1.6.0_22] > Caused by: javax.faces.FacesException: topic/pushTopicsContext -- service jboss.naming.context.java.topic.pushTopicsContext > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:207) [richfaces-core-impl-4.2.0.CR1.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:195) [richfaces-core-impl-4.2.0.CR1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingValueReference.compute(ComputingConcurrentHashMap.java:355) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.compute(ComputingConcurrentHashMap.java:184) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.getOrCompute(ComputingConcurrentHashMap.java:153) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap.getOrCompute(ComputingConcurrentHashMap.java:69) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:393) [guava-10.0.1.jar:] > ... 6 more > Caused by: javax.naming.NameNotFoundException: topic/pushTopicsContext -- service jboss.naming.context.java.topic.pushTopicsContext > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:92) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:177) > at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:87) > at javax.naming.InitialContext.lookup(InitialContext.java:396) [:1.6.0_22] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.lookupTopic(JMSTopicsContextImpl.java:94) [richfaces-core-impl-4.2.0-20120130.140419-26.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.start(JMSTopicsContextImpl.java:125) [richfaces-core-impl-4.2.0-20120130.140419-26.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:199) [richfaces-core-impl-4.2.0-20120130.140419-26.jar:] > ... 12 more > {code} > The functionality of push demos is fine, just the tests are not passing on Hudson, which I have to investigate whether it is caused by this one. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 26 04:16:49 2012 From: jira-events at lists.jboss.org (Juraj Huska (JIRA)) Date: Mon, 26 Mar 2012 04:16:49 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11905) showcase - shutdown of the JBoss AS with showcase deployed throws DB error In-Reply-To: <567082387.11072.1326986119167.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <451026666.30061.1332749809675.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679178#comment-12679178 ] Juraj Huska commented on RF-11905: ---------------------------------- Verified that it is OK now. > showcase - shutdown of the JBoss AS with showcase deployed throws DB error > -------------------------------------------------------------------------- > > Key: RF-11905 > URL: https://issues.jboss.org/browse/RF-11905 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: showcase > Affects Versions: 4.1.0.Final > Environment: container: JBoss AS 7.1.0.CR1b, 7.0.2.Final > app: showcase 4.2.0-SNAPSHOT > Reporter: Juraj Huska > Assignee: Luk?? Fry? > Priority: Minor > Fix For: 4.2.1.CR1 > > > When shutting down JBoss AS 7 with showcase deployed, then the DB error is thrown: > {code} > 16:09:52,334 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] HHH000231: Schema export unsuccessful: org.h2.jdbc.JdbcSQLException: Database is already closed (to disable automatic closing at VM shutdown, add ";DB_CLOSE_ON_EXIT=FALSE" to the db URL) [90121-161] > at org.h2.message.DbException.getJdbcSQLException(DbException.java:329) > at org.h2.message.DbException.get(DbException.java:169) > at org.h2.message.DbException.get(DbException.java:146) > at org.h2.message.DbException.get(DbException.java:135) > at org.h2.jdbc.JdbcConnection.checkClosed(JdbcConnection.java:1394) > at org.h2.jdbc.JdbcConnection.checkClosed(JdbcConnection.java:1369) > at org.h2.jdbc.JdbcConnection.createStatement(JdbcConnection.java:191) > at org.jboss.jca.adapters.jdbc.WrappedConnection.createStatement(WrappedConnection.java:301) > at org.hibernate.tool.hbm2ddl.DatabaseExporter.(DatabaseExporter.java:54) [hibernate-core-4.0.0.Final.jar:4.0.0.Final] > at org.hibernate.tool.hbm2ddl.SchemaExport.execute(SchemaExport.java:368) [hibernate-core-4.0.0.Final.jar:4.0.0.Final] > at org.hibernate.tool.hbm2ddl.SchemaExport.drop(SchemaExport.java:319) [hibernate-core-4.0.0.Final.jar:4.0.0.Final] > at org.hibernate.tool.hbm2ddl.SchemaExport.drop(SchemaExport.java:315) [hibernate-core-4.0.0.Final.jar:4.0.0.Final] > at org.hibernate.internal.SessionFactoryImpl.close(SessionFactoryImpl.java:1305) [hibernate-core-4.0.0.Final.jar:4.0.0.Final] > at org.hibernate.ejb.EntityManagerFactoryImpl.close(EntityManagerFactoryImpl.java:126) [hibernate-entitymanager-4.0.0.Final.jar:4.0.0.Final] > at org.richfaces.demo.arrangeablemodel.PersistenceService.destroy(PersistenceService.java:159) [classes:] > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_22] > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_22] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_22] > at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_22] > at org.jboss.as.ee.component.ManagedReferenceLifecycleMethodInterceptorFactory$ManagedReferenceLifecycleMethodInterceptor.processInvocation(ManagedReferenceLifecycleMethodInterceptorFactory.java:130) [jboss-as-ee-7.1.0.CR1b.jar:7.1.0.CR1b] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final] > at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final] > at org.jboss.as.ee.component.ManagedReferenceReleaseInterceptorFactory$ManagedReferenceReleaseInterceptor.processInvocation(ManagedReferenceReleaseInterceptorFactory.java:90) [jboss-as-ee-7.1.0.CR1b.jar:7.1.0.CR1b] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final] > at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final] > at org.jboss.as.ee.component.TCCLInterceptor.processInvocation(TCCLInterceptor.java:45) [jboss-as-ee-7.1.0.CR1b.jar:7.1.0.CR1b] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final] > at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final] > at org.jboss.as.ee.component.BasicComponentInstance.destroy(BasicComponentInstance.java:122) [jboss-as-ee-7.1.0.CR1b.jar:7.1.0.CR1b] > at org.jboss.as.web.deployment.component.WebComponentInstantiator$2.release(WebComponentInstantiator.java:102) [jboss-as-web-7.1.0.CR1b.jar:7.1.0.CR1b] > at org.jboss.as.web.deployment.WebInjectionContainer.destroyInstance(WebInjectionContainer.java:67) [jboss-as-web-7.1.0.CR1b.jar:7.1.0.CR1b] > at org.jboss.as.web.deployment.jsf.JsfInjectionProvider.invokePreDestroy(JsfInjectionProvider.java:56) [jboss-as-web-7.1.0.CR1b.jar:7.1.0.CR1b] > at com.sun.faces.mgbean.BeanBuilder.destroy(BeanBuilder.java:116) [jsf-impl-2.1.5-jbossorg-1.jar:2.1.5-SNAPSHOT] > at com.sun.faces.mgbean.BeanManager.destroy(BeanManager.java:283) [jsf-impl-2.1.5-jbossorg-1.jar:2.1.5-SNAPSHOT] > at com.sun.faces.application.WebappLifecycleListener.handleAttributeEvent(WebappLifecycleListener.java:314) [jsf-impl-2.1.5-jbossorg-1.jar:2.1.5-SNAPSHOT] > at com.sun.faces.application.WebappLifecycleListener.contextDestroyed(WebappLifecycleListener.java:368) [jsf-impl-2.1.5-jbossorg-1.jar:2.1.5-SNAPSHOT] > at com.sun.faces.config.ConfigureListener.contextDestroyed(ConfigureListener.java:308) [jsf-impl-2.1.5-jbossorg-1.jar:2.1.5-SNAPSHOT] > at org.apache.catalina.core.StandardContext.listenerStop(StandardContext.java:3489) [jbossweb-7.0.7.Final.jar:] > at org.apache.catalina.core.StandardContext.stop(StandardContext.java:3999) [jbossweb-7.0.7.Final.jar:] > at org.jboss.as.web.deployment.WebDeploymentService.stop(WebDeploymentService.java:96) [jboss-as-web-7.1.0.CR1b.jar:7.1.0.CR1b] > at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:1909) > at org.jboss.msc.service.ServiceControllerImpl$StopTask.run(ServiceControllerImpl.java:1872) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_22] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_22] > at java.lang.Thread.run(Thread.java:662) [:1.6.0_22] > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 26 04:16:49 2012 From: jira-events at lists.jboss.org (Juraj Huska (JIRA)) Date: Mon, 26 Mar 2012 04:16:49 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11905) showcase - shutdown of the JBoss AS with showcase deployed throws DB error In-Reply-To: <567082387.11072.1326986119167.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1691788823.30064.1332749810026.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj Huska closed RF-11905. ---------------------------- > showcase - shutdown of the JBoss AS with showcase deployed throws DB error > -------------------------------------------------------------------------- > > Key: RF-11905 > URL: https://issues.jboss.org/browse/RF-11905 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: showcase > Affects Versions: 4.1.0.Final > Environment: container: JBoss AS 7.1.0.CR1b, 7.0.2.Final > app: showcase 4.2.0-SNAPSHOT > Reporter: Juraj Huska > Assignee: Luk?? Fry? > Priority: Minor > Fix For: 4.2.1.CR1 > > > When shutting down JBoss AS 7 with showcase deployed, then the DB error is thrown: > {code} > 16:09:52,334 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] HHH000231: Schema export unsuccessful: org.h2.jdbc.JdbcSQLException: Database is already closed (to disable automatic closing at VM shutdown, add ";DB_CLOSE_ON_EXIT=FALSE" to the db URL) [90121-161] > at org.h2.message.DbException.getJdbcSQLException(DbException.java:329) > at org.h2.message.DbException.get(DbException.java:169) > at org.h2.message.DbException.get(DbException.java:146) > at org.h2.message.DbException.get(DbException.java:135) > at org.h2.jdbc.JdbcConnection.checkClosed(JdbcConnection.java:1394) > at org.h2.jdbc.JdbcConnection.checkClosed(JdbcConnection.java:1369) > at org.h2.jdbc.JdbcConnection.createStatement(JdbcConnection.java:191) > at org.jboss.jca.adapters.jdbc.WrappedConnection.createStatement(WrappedConnection.java:301) > at org.hibernate.tool.hbm2ddl.DatabaseExporter.(DatabaseExporter.java:54) [hibernate-core-4.0.0.Final.jar:4.0.0.Final] > at org.hibernate.tool.hbm2ddl.SchemaExport.execute(SchemaExport.java:368) [hibernate-core-4.0.0.Final.jar:4.0.0.Final] > at org.hibernate.tool.hbm2ddl.SchemaExport.drop(SchemaExport.java:319) [hibernate-core-4.0.0.Final.jar:4.0.0.Final] > at org.hibernate.tool.hbm2ddl.SchemaExport.drop(SchemaExport.java:315) [hibernate-core-4.0.0.Final.jar:4.0.0.Final] > at org.hibernate.internal.SessionFactoryImpl.close(SessionFactoryImpl.java:1305) [hibernate-core-4.0.0.Final.jar:4.0.0.Final] > at org.hibernate.ejb.EntityManagerFactoryImpl.close(EntityManagerFactoryImpl.java:126) [hibernate-entitymanager-4.0.0.Final.jar:4.0.0.Final] > at org.richfaces.demo.arrangeablemodel.PersistenceService.destroy(PersistenceService.java:159) [classes:] > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_22] > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_22] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_22] > at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_22] > at org.jboss.as.ee.component.ManagedReferenceLifecycleMethodInterceptorFactory$ManagedReferenceLifecycleMethodInterceptor.processInvocation(ManagedReferenceLifecycleMethodInterceptorFactory.java:130) [jboss-as-ee-7.1.0.CR1b.jar:7.1.0.CR1b] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final] > at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final] > at org.jboss.as.ee.component.ManagedReferenceReleaseInterceptorFactory$ManagedReferenceReleaseInterceptor.processInvocation(ManagedReferenceReleaseInterceptorFactory.java:90) [jboss-as-ee-7.1.0.CR1b.jar:7.1.0.CR1b] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final] > at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final] > at org.jboss.as.ee.component.TCCLInterceptor.processInvocation(TCCLInterceptor.java:45) [jboss-as-ee-7.1.0.CR1b.jar:7.1.0.CR1b] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final] > at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final] > at org.jboss.as.ee.component.BasicComponentInstance.destroy(BasicComponentInstance.java:122) [jboss-as-ee-7.1.0.CR1b.jar:7.1.0.CR1b] > at org.jboss.as.web.deployment.component.WebComponentInstantiator$2.release(WebComponentInstantiator.java:102) [jboss-as-web-7.1.0.CR1b.jar:7.1.0.CR1b] > at org.jboss.as.web.deployment.WebInjectionContainer.destroyInstance(WebInjectionContainer.java:67) [jboss-as-web-7.1.0.CR1b.jar:7.1.0.CR1b] > at org.jboss.as.web.deployment.jsf.JsfInjectionProvider.invokePreDestroy(JsfInjectionProvider.java:56) [jboss-as-web-7.1.0.CR1b.jar:7.1.0.CR1b] > at com.sun.faces.mgbean.BeanBuilder.destroy(BeanBuilder.java:116) [jsf-impl-2.1.5-jbossorg-1.jar:2.1.5-SNAPSHOT] > at com.sun.faces.mgbean.BeanManager.destroy(BeanManager.java:283) [jsf-impl-2.1.5-jbossorg-1.jar:2.1.5-SNAPSHOT] > at com.sun.faces.application.WebappLifecycleListener.handleAttributeEvent(WebappLifecycleListener.java:314) [jsf-impl-2.1.5-jbossorg-1.jar:2.1.5-SNAPSHOT] > at com.sun.faces.application.WebappLifecycleListener.contextDestroyed(WebappLifecycleListener.java:368) [jsf-impl-2.1.5-jbossorg-1.jar:2.1.5-SNAPSHOT] > at com.sun.faces.config.ConfigureListener.contextDestroyed(ConfigureListener.java:308) [jsf-impl-2.1.5-jbossorg-1.jar:2.1.5-SNAPSHOT] > at org.apache.catalina.core.StandardContext.listenerStop(StandardContext.java:3489) [jbossweb-7.0.7.Final.jar:] > at org.apache.catalina.core.StandardContext.stop(StandardContext.java:3999) [jbossweb-7.0.7.Final.jar:] > at org.jboss.as.web.deployment.WebDeploymentService.stop(WebDeploymentService.java:96) [jboss-as-web-7.1.0.CR1b.jar:7.1.0.CR1b] > at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:1909) > at org.jboss.msc.service.ServiceControllerImpl$StopTask.run(ServiceControllerImpl.java:1872) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_22] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_22] > at java.lang.Thread.run(Thread.java:662) [:1.6.0_22] > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 26 04:23:48 2012 From: jira-events at lists.jboss.org (Juraj Huska (JIRA)) Date: Mon, 26 Mar 2012 04:23:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11936) rich:contextMenu activation is possible outside of tree nodes In-Reply-To: <643933580.14431.1328103828616.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1051976863.30076.1332750228266.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj Huska closed RF-11936. ---------------------------- Verified that it is OK now. > rich:contextMenu activation is possible outside of tree nodes > ------------------------------------------------------------- > > Key: RF-11936 > URL: https://issues.jboss.org/browse/RF-11936 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-menu, component-tree > Affects Versions: 4.2.0.CR1 > Environment: browsers: all browsers > Reporter: Juraj Huska > Assignee: Brian Leathem > Fix For: 4.2.1.CR1 > > Attachments: contextMenu.png, exdt_cm1.png, exdt_cm2.png > > > In the showcase demo for rich:contextMenu, the sample Tree ContextMenu, it is possible to activate the context menu not only from the nodes, but also outside of thenodes. > It is *rather a problem of the rich:tree*, since its rows contains nodes, which are rendered with 100% width. > When it is then selected with the contextMenu item, a popup with empty content is displayed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 26 04:30:47 2012 From: jira-events at lists.jboss.org (Juraj Huska (JIRA)) Date: Mon, 26 Mar 2012 04:30:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11936) rich:contextMenu activation is possible outside of tree nodes In-Reply-To: <643933580.14431.1328103828616.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <915786401.30088.1332750647423.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679183#comment-12679183 ] Juraj Huska commented on RF-11936: ---------------------------------- However, the issue mentioned by Pjotr Andreev is still occurring. Should I file another JIRA for it ? > rich:contextMenu activation is possible outside of tree nodes > ------------------------------------------------------------- > > Key: RF-11936 > URL: https://issues.jboss.org/browse/RF-11936 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-menu, component-tree > Affects Versions: 4.2.0.CR1 > Environment: browsers: all browsers > Reporter: Juraj Huska > Assignee: Brian Leathem > Fix For: 4.2.1.CR1 > > Attachments: contextMenu.png, exdt_cm1.png, exdt_cm2.png > > > In the showcase demo for rich:contextMenu, the sample Tree ContextMenu, it is possible to activate the context menu not only from the nodes, but also outside of thenodes. > It is *rather a problem of the rich:tree*, since its rows contains nodes, which are rendered with 100% width. > When it is then selected with the contextMenu item, a popup with empty content is displayed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 26 04:30:47 2012 From: jira-events at lists.jboss.org (Juraj Huska (JIRA)) Date: Mon, 26 Mar 2012 04:30:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11936) rich:contextMenu activation is possible outside of tree nodes In-Reply-To: <643933580.14431.1328103828616.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1435450267.30093.1332750647615.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj Huska reopened RF-11936: ------------------------------ > rich:contextMenu activation is possible outside of tree nodes > ------------------------------------------------------------- > > Key: RF-11936 > URL: https://issues.jboss.org/browse/RF-11936 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-menu, component-tree > Affects Versions: 4.2.0.CR1 > Environment: browsers: all browsers > Reporter: Juraj Huska > Assignee: Brian Leathem > Fix For: 4.2.1.CR1 > > Attachments: contextMenu.png, exdt_cm1.png, exdt_cm2.png > > > In the showcase demo for rich:contextMenu, the sample Tree ContextMenu, it is possible to activate the context menu not only from the nodes, but also outside of thenodes. > It is *rather a problem of the rich:tree*, since its rows contains nodes, which are rendered with 100% width. > When it is then selected with the contextMenu item, a popup with empty content is displayed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 26 04:48:48 2012 From: jira-events at lists.jboss.org (Juraj Huska (JIRA)) Date: Mon, 26 Mar 2012 04:48:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11936) rich:contextMenu activation is possible outside of tree nodes In-Reply-To: <643933580.14431.1328103828616.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1200632084.30152.1332751728461.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj Huska closed RF-11936. ---------------------------- Resolution: Done Sorry, I have built showcase with older RichFaces libraries. I have also verified that both mentioned issues are OK now. > rich:contextMenu activation is possible outside of tree nodes > ------------------------------------------------------------- > > Key: RF-11936 > URL: https://issues.jboss.org/browse/RF-11936 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-menu, component-tree > Affects Versions: 4.2.0.CR1 > Environment: browsers: all browsers > Reporter: Juraj Huska > Assignee: Brian Leathem > Fix For: 4.2.1.CR1 > > Attachments: contextMenu.png, exdt_cm1.png, exdt_cm2.png > > > In the showcase demo for rich:contextMenu, the sample Tree ContextMenu, it is possible to activate the context menu not only from the nodes, but also outside of thenodes. > It is *rather a problem of the rich:tree*, since its rows contains nodes, which are rendered with 100% width. > When it is then selected with the contextMenu item, a popup with empty content is displayed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 26 05:20:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Mon, 26 Mar 2012 05:20:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12087) itemChangeListener attribute @listener does not work Message-ID: <1894988349.30243.1332753647412.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Ji?? ?tefek created RF-12087: -------------------------------- Summary: itemChangeListener attribute @listener does not work Key: RF-12087 URL: https://issues.jboss.org/browse/RF-12087 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-misc Environment: RichFaces 4.2.1-SNAPSHOT Metamer 4.2.1-SNAPSHOT Mojarra 2.1.5-SNAPSHOT JBoss AS 7.1.0.Final OpenJDK Runtime Environment 1.6.0_24-b24 @ Linux Firefox 11.0 @ Linux x86_64 Reporter: Ji?? ?tefek # Deploy Metamer. # Open http://localhost:8080/metamer/faces/components/richItemChangeListener/accordion.xhtml ( or http://localhost:8080/metamer/faces/components/richItemChangeListener/panelMenu.xhtml or http://localhost:8080/metamer/faces/components/richItemChangeListener/tabPanel.xhtml or http://localhost:8080/metamer/faces/components/richItemChangeListener/togglePanel.xhtml ) # Click on accordion panel Item 2. # 2 messages with "* itemChangeListenerBean item changed: null -> item2" should appear in phases list. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 26 05:54:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Mon, 26 Mar 2012 05:54:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12088) itemChangeListener attribute @for does not work Message-ID: <1852550807.30367.1332755687380.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Ji?? ?tefek created RF-12088: -------------------------------- Summary: itemChangeListener attribute @for does not work Key: RF-12088 URL: https://issues.jboss.org/browse/RF-12088 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-misc Affects Versions: 4.2.0.Final Environment: RichFaces 4.2.1-SNAPSHOT Metamer 4.2.1-SNAPSHOT Mojarra 2.1.5-SNAPSHOT JBoss AS 7.1.0.Final OpenJDK Runtime Environment 1.6.0_24-b24 @ Linux Firefox 11.0 @ Linux x86_64 Reporter: Ji?? ?tefek TODO -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 26 05:56:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Mon, 26 Mar 2012 05:56:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12088) itemChangeListener attribute @for does not work Message-ID: <2040324573.30371.1332755807474.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek deleted RF-12088: ----------------------------- > itemChangeListener attribute @for does not work > ----------------------------------------------- > > Key: RF-12088 > URL: https://issues.jboss.org/browse/RF-12088 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Environment: RichFaces 4.2.1-SNAPSHOT > Metamer 4.2.1-SNAPSHOT > Mojarra 2.1.5-SNAPSHOT > JBoss AS 7.1.0.Final > OpenJDK Runtime Environment 1.6.0_24-b24 @ Linux > Firefox 11.0 @ Linux x86_64 > Reporter: Ji?? ?tefek > > TODO -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 26 06:00:49 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Mon, 26 Mar 2012 06:00:49 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12089) itemChangeListener attribute @for does not work Message-ID: <405838573.30375.1332756049100.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Ji?? ?tefek created RF-12089: -------------------------------- Summary: itemChangeListener attribute @for does not work Key: RF-12089 URL: https://issues.jboss.org/browse/RF-12089 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-misc Affects Versions: 4.2.0.Final Environment: RichFaces 4.2.1-SNAPSHOT Metamer 4.2.1-SNAPSHOT Mojarra 2.1.5-SNAPSHOT JBoss AS 7.1.0.Final OpenJDK Runtime Environment 1.6.0_24-b24 @ Linux Firefox 11.0 @ Linux x86_64 Reporter: Ji?? ?tefek TODO -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 26 06:14:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Mon, 26 Mar 2012 06:14:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12089) itemChangeListener attribute @for does not work In-Reply-To: <405838573.30375.1332756049100.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1836835142.30392.1332756887516.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek updated RF-12089: ----------------------------- Description: # Deploy Metamer. # Open http://localhost:8080/metamer/faces/components/richItemChangeListener/RF-12089.xhtml . was:TODO > itemChangeListener attribute @for does not work > ----------------------------------------------- > > Key: RF-12089 > URL: https://issues.jboss.org/browse/RF-12089 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-misc > Affects Versions: 4.2.0.Final > Environment: RichFaces 4.2.1-SNAPSHOT > Metamer 4.2.1-SNAPSHOT > Mojarra 2.1.5-SNAPSHOT > JBoss AS 7.1.0.Final > OpenJDK Runtime Environment 1.6.0_24-b24 @ Linux > Firefox 11.0 @ Linux x86_64 > Reporter: Ji?? ?tefek > > # Deploy Metamer. > # Open http://localhost:8080/metamer/faces/components/richItemChangeListener/RF-12089.xhtml . -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 26 06:20:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 26 Mar 2012 06:20:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12051) Showcase: simplified Push CDI sample which wouldn't use subtopics In-Reply-To: <1777587358.12158.1331830847464.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1727261770.30417.1332757247334.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved RF-12051. ----------------------------- Resolution: Done Removed subtopics usage - added safeHtml validator. > Showcase: simplified Push CDI sample which wouldn't use subtopics > ----------------------------------------------------------------- > > Key: RF-12051 > URL: https://issues.jboss.org/browse/RF-12051 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: showcase > Affects Versions: 4.2.0.Final > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Priority: Minor > Fix For: 4.2.1.CR1 > > > Push CDI sample in Showcase is currently quite complex and people run into issues when starting to use it, > because there is usage of subtopics. > There are two alternative ways how to address it: > # simplify current sample > # provide new sample as alternative to this one -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 26 07:08:48 2012 From: jira-events at lists.jboss.org (Morten Ludvigsen (JIRA)) Date: Mon, 26 Mar 2012 07:08:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11339) selection hangs in extendedDataTable when there are more than one table in the view In-Reply-To: <980202873.13540.1313853617638.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <879710814.30540.1332760128058.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12622305#comment-12622305 ] Morten Ludvigsen edited comment on RF-11339 at 3/26/12 7:07 AM: ---------------------------------------------------------------- Fix for this issue is: https://github.com/richfaces/components/commit/e16faf320ebac41ea870ab5868ed8be2a87aadcf was (Author: mortenlud): Fix for this issue is: https://github.com/mortenlud/components/commit/2363ce22f999470ffa3190ecdd596361fecffab6 > selection hangs in extendedDataTable when there are more than one table in the view > ----------------------------------------------------------------------------------- > > Key: RF-11339 > URL: https://issues.jboss.org/browse/RF-11339 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.0.0.Final > Environment: GlassFish 3.1, and Chrome 13 > Reporter: Morten Ludvigsen > Assignee: Luk?? Fry? > Labels: ExtendedDataTable, selection > Fix For: 4.1.0.Milestone3 > > > I have a problem with selection in extendedDataTables when there are two tables in the view. > Some of the selections are not removed when a new row is selected. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 26 07:42:48 2012 From: jira-events at lists.jboss.org (Jean ANDRE (JIRA)) Date: Mon, 26 Mar 2012 07:42:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12038) IE8 - Object does not support this property or method - a4j:jsFunction In-Reply-To: <1674243330.3069.1331568048477.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1361777422.30640.1332762168071.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679239#comment-12679239 ] Jean ANDRE commented on RF-12038: --------------------------------- More information... the object event received under IE is MSHTML::DispCEventObj and it is not the event we got under FireFox (from jQuery?). {code} {code} There is certainly a way to do better - Accessing directly to window.event inside onclick does not work. Then the javascript code below was put insider the HTML header. {code} function stopPropagation(event) { if (isWindows()) { window.event.cancelBubble = true; } else { event.stopPropagation(); } {code} > IE8 - Object does not support this property or method - a4j:jsFunction > ---------------------------------------------------------------------- > > Key: RF-12038 > URL: https://issues.jboss.org/browse/RF-12038 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.2.0.Final > Environment: cssparser-0.9.6- guava-11.0.1 - hibernate-validator-4.2.0.Final - JSF/Mojarra 2.1.6 - springframework-3.0.6.RELEASE - sac-1.3 - Windows 7 - IE 8.0.1.7601.17514 > Reporter: Jean ANDRE > Assignee: Brian Leathem > Labels: waiting_on_user > Attachments: index.xhtml, NestedWeb.zip, NestedWeb_RF-12038.zip, ScreenShot_RF-12038.png > > > Under IE8, IE reports the following error message due to a javascript error. However, the page are well displayed and the application is running ok. > Object doesn't support this property or method line 177 caracter 1 > Object doesn't support this property or method line 177 caracter 99 > Under IE Debugger, the line is: > {code} > closeTab=function(tabId){RichFaces.ajax("closeTab",null,{"incId":"1","parameters":{"tabId":tabId} } )};< > The caracter 99, is..............................................................................| (here) > {code} > This is a code generated by a4j:jsFunction from the XHTML > {code} > > > > > > > {code} > The rendered code is : > {code} > > > > {code} > See also this link as we got almost a similar: https://bugzilla.redhat.com/show_bug.cgi?id=601360. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 26 07:52:47 2012 From: jira-events at lists.jboss.org (phelen harg (JIRA)) Date: Mon, 26 Mar 2012 07:52:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12081) Problem with RichEditor RF 4.2.0 In-Reply-To: <1278339548.27975.1332502007395.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <2128524434.30694.1332762767520.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] phelen harg updated RF-12081: ----------------------------- Attachment: Sem t?tulo.jpg > Problem with RichEditor RF 4.2.0 > -------------------------------- > > Key: RF-12081 > URL: https://issues.jboss.org/browse/RF-12081 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.2.0.Final > Reporter: phelen harg > Labels: waiting_on_user > Attachments: Sem t?tulo.jpg > > > I'm migrating my Application from RF 3.3.3 to RF 4.2.0. But now i'm facing a problem with the richEditor. When I load the the component, all the links in application receive a background like this picture: > Analizing the code with Firebug, I found the problem in the CSS of RichEditor. /org.richfaces.resources/javax.faces.resource/org.richfaces.ckeditor/skins/richfaces/editor.ecss?db=eAHj0yqqAgACGAEl > If I erase the CSS the backgroud disappear. There is some kind of workaround for this? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 26 07:54:48 2012 From: jira-events at lists.jboss.org (phelen harg (JIRA)) Date: Mon, 26 Mar 2012 07:54:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12081) Problem with RichEditor RF 4.2.0 In-Reply-To: <1278339548.27975.1332502007395.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <93904904.30711.1332762888110.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679249#comment-12679249 ] phelen harg commented on RF-12081: ---------------------------------- I attached the picture. No, in the showcase doesn't have this problem. Only on my workspace. I't can be a problem with the configuration? Because i'm migrating from 3.3 to 4.2. > Problem with RichEditor RF 4.2.0 > -------------------------------- > > Key: RF-12081 > URL: https://issues.jboss.org/browse/RF-12081 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.2.0.Final > Reporter: phelen harg > Labels: waiting_on_user > Attachments: Sem t?tulo.jpg > > > I'm migrating my Application from RF 3.3.3 to RF 4.2.0. But now i'm facing a problem with the richEditor. When I load the the component, all the links in application receive a background like this picture: > Analizing the code with Firebug, I found the problem in the CSS of RichEditor. /org.richfaces.resources/javax.faces.resource/org.richfaces.ckeditor/skins/richfaces/editor.ecss?db=eAHj0yqqAgACGAEl > If I erase the CSS the backgroud disappear. There is some kind of workaround for this? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 26 09:09:47 2012 From: jira-events at lists.jboss.org (Juraj Huska (JIRA)) Date: Mon, 26 Mar 2012 09:09:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11983) Showcase: can't connect to JMS on AS7.1 since it is secured In-Reply-To: <1110785355.5085.1329395076292.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <436816878.30926.1332767387936.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679280#comment-12679280 ] Juraj Huska commented on RF-11983: ---------------------------------- The behavior is the same when deploying on _JBoss AS 6.0.0.Final_. I have used similar workaround when I have set to: _JBOSS_HOME/server/default/deploy/hornetq/hornetq-configuration.xml_ the same property: _false_ > Showcase: can't connect to JMS on AS7.1 since it is secured > ----------------------------------------------------------- > > Key: RF-11983 > URL: https://issues.jboss.org/browse/RF-11983 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Environment: JBoos AS 7.0.2.Final (in default configuration) / JBoss AS 7.1.0.Final and Firefox 8.0 > Reporter: Jan Papousek > Assignee: Luk?? Fry? > Fix For: 4.3-Tracking > > > {code:title=JBoss AS 7.1.0.Final} > 13:13:03,702 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/showcase].[Faces Servlet]] (http--127.0.0.1-8080-1) Servlet.service() for servlet Faces Servlet threw exception: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:397) [guava-10.0.1.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl.createTopic(JMSTopicsContextImpl.java:281) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.TopicsContext.getOrCreateTopic(TopicsContext.java:48) [richfaces-core-api-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.SessionImpl.createSubscriptions(SessionImpl.java:182) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.SessionImpl.subscribe(SessionImpl.java:177) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.resource.PushResource.encode(PushResource.java:88) [richfaces-components-ui-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.resource.UserResourceWrapperImpl.encode(UserResourceWrapperImpl.java:188) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.resource.ResourceHandlerImpl.handleResourceRequest(ResourceHandlerImpl.java:222) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:591) [jboss-jsf-api_2.1_spec-2.0.0.Final.jar:2.0.0.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.10.Final.jar:] > at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:62) [weld-core-1.1.5.AS71.Final.jar:2012-02-10 15:31] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.10.Final.jar:] > at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.1.0.Final.jar:7.1.0.Final] > at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:154) [jboss-as-web-7.1.0.Final.jar:7.1.0.Final] > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.10.Final.jar:] > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.10.Final.jar:] > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.10.Final.jar:] > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.10.Final.jar:] > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.10.Final.jar:] > at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_22] > Caused by: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:207) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:195) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingValueReference.compute(ComputingConcurrentHashMap.java:355) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.compute(ComputingConcurrentHashMap.java:184) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.getOrCompute(ComputingConcurrentHashMap.java:153) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap.getOrCompute(ComputingConcurrentHashMap.java:69) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:393) [guava-10.0.1.jar:] > ... 25 more > Caused by: javax.naming.NameNotFoundException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:97) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:177) > at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:113) > at javax.naming.InitialContext.lookup(InitialContext.java:396) [rt.jar:1.6.0_22] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.createConnection(JMSTopicsContextImpl.java:98) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.start(JMSTopicsContextImpl.java:123) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:199) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > ... 31 more > 13:13:04,263 SEVERE [org.richfaces.demo.push.MessageProducerRunnable] (MessageProducerThread) javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:397) [guava-10.0.1.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl.createTopic(JMSTopicsContextImpl.java:281) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.TopicsContext.getOrCreateTopic(TopicsContext.java:48) [richfaces-core-api-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.TopicsContext.publish(TopicsContext.java:69) [richfaces-core-api-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.demo.push.TopicsContextMessageProducer.sendMessage(TopicsContextMessageProducer.java:46) [classes:] > at org.richfaces.demo.push.MessageProducerRunnable.run(MessageProducerRunnable.java:57) [classes:] > at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_22] > Caused by: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:207) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:195) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingValueReference.compute(ComputingConcurrentHashMap.java:355) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.compute(ComputingConcurrentHashMap.java:184) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.getOrCompute(ComputingConcurrentHashMap.java:153) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap.getOrCompute(ComputingConcurrentHashMap.java:69) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:393) [guava-10.0.1.jar:] > ... 6 more > Caused by: javax.naming.NameNotFoundException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:97) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:177) > at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:113) > at javax.naming.InitialContext.lookup(InitialContext.java:396) [rt.jar:1.6.0_22] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.createConnection(JMSTopicsContextImpl.java:98) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.start(JMSTopicsContextImpl.java:123) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:199) [richfaces-core-impl-4.2.0.Final.jar:4.2.0.Final] > ... 12 more > {code} > {code:title=JBoss AS 7.0.2.Final using default configuration} > 13:16:26,372 WARNING [javax.enterprise.resource.webcontainer.jsf.lifecycle] (http--0%3A0%3A0%3A0%3A0%3A0%3A0%3A0-8080-5) #{pushBean.sendMessage}: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory: javax.faces.FacesException: #{pushBean.sendMessage}: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:118) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > at javax.faces.component.UICommand.broadcast(UICommand.java:315) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:794) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:1259) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:81) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > at org.richfaces.demo.arrangeablemodel.PersistenceLifecycle.execute(PersistenceLifecycle.java:58) [classes:] > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:593) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:67) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:139) [jboss-as-web-7.0.2.Final.jar:7.0.2.Final] > at org.jboss.as.web.NamingValve.invoke(NamingValve.java:57) [jboss-as-web-7.0.2.Final.jar:7.0.2.Final] > at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:49) [jboss-as-jpa-7.0.2.Final.jar:7.0.2.Final] > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:154) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:667) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:952) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at java.lang.Thread.run(Thread.java:662) [:1.6.0_22] > Caused by: javax.faces.el.EvaluationException: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:102) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:102) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > ... 26 more > Caused by: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:397) [guava-10.0.1.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl.createTopic(JMSTopicsContextImpl.java:281) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.TopicsContext.getOrCreateTopic(TopicsContext.java:48) [richfaces-core-api-4.2.0.Final.jar:] > at org.richfaces.application.push.TopicsContext.publish(TopicsContext.java:69) [richfaces-core-api-4.2.0.Final.jar:] > at org.richfaces.application.push.TopicsContext$Proxy$_$$_WeldClientProxy.publish(TopicsContext$Proxy$_$$_WeldClientProxy.java) [richfaces-core-api-4.2.0.Final.jar:] > at org.richfaces.cdi.push.PushCDIExtension$PushObserverMethod.notify(PushCDIExtension.java:144) [richfaces-core-impl-4.2.0.Final.jar:] > at org.jboss.weld.manager.BeanManagerImpl.notifyObservers(BeanManagerImpl.java:635) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:628) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.jboss.weld.event.EventImpl.fire(EventImpl.java:75) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.richfaces.demo.push.PushBean.sendMessage(PushBean.java:65) [classes:] > at org.richfaces.demo.push.PushBean$Proxy$_$$_WeldClientProxy.sendMessage(PushBean$Proxy$_$$_WeldClientProxy.java) [classes:] > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_22] > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_22] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_22] > at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_22] > at org.apache.el.parser.AstValue.invoke(AstValue.java:196) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:276) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.jboss.weld.util.el.ForwardingMethodExpression.invoke(ForwardingMethodExpression.java:43) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.jboss.weld.el.WeldMethodExpression.invoke(WeldMethodExpression.java:56) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at com.sun.faces.facelets.el.TagMethodExpression.invoke(TagMethodExpression.java:105) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:88) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > ... 27 more > Caused by: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:207) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:195) [richfaces-core-impl-4.2.0.Final.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingValueReference.compute(ComputingConcurrentHashMap.java:355) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.compute(ComputingConcurrentHashMap.java:184) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.getOrCompute(ComputingConcurrentHashMap.java:153) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap.getOrCompute(ComputingConcurrentHashMap.java:69) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:393) [guava-10.0.1.jar:] > ... 47 more > Caused by: javax.naming.NameNotFoundException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:87) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:173) > at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:47) > at javax.naming.InitialContext.lookup(InitialContext.java:396) [:1.6.0_22] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.createConnection(JMSTopicsContextImpl.java:98) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.start(JMSTopicsContextImpl.java:123) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:199) [richfaces-core-impl-4.2.0.Final.jar:] > ... 53 more > 13:16:28,949 SEVERE [org.richfaces.demo.push.MessageProducerRunnable] (MessageProducerThread) javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory: com.google.common.collect.ComputationException: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:397) [guava-10.0.1.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl.createTopic(JMSTopicsContextImpl.java:281) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.TopicsContext.getOrCreateTopic(TopicsContext.java:48) [richfaces-core-api-4.2.0.Final.jar:] > at org.richfaces.application.push.TopicsContext.publish(TopicsContext.java:69) [richfaces-core-api-4.2.0.Final.jar:] > at org.richfaces.demo.push.TopicsContextMessageProducer.sendMessage(TopicsContextMessageProducer.java:46) [classes:] > at org.richfaces.demo.push.MessageProducerRunnable.run(MessageProducerRunnable.java:57) [classes:] > at java.lang.Thread.run(Thread.java:662) [:1.6.0_22] > Caused by: javax.faces.FacesException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:207) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:195) [richfaces-core-impl-4.2.0.Final.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingValueReference.compute(ComputingConcurrentHashMap.java:355) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.compute(ComputingConcurrentHashMap.java:184) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.getOrCompute(ComputingConcurrentHashMap.java:153) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap.getOrCompute(ComputingConcurrentHashMap.java:69) [guava-10.0.1.jar:] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:393) [guava-10.0.1.jar:] > ... 6 more > Caused by: javax.naming.NameNotFoundException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:87) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:173) > at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:47) > at javax.naming.InitialContext.lookup(InitialContext.java:396) [:1.6.0_22] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.createConnection(JMSTopicsContextImpl.java:98) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.start(JMSTopicsContextImpl.java:123) [richfaces-core-impl-4.2.0.Final.jar:] > at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:199) [richfaces-core-impl-4.2.0.Final.jar:] > ... 12 more > {code} > ---- > - Showcase on Openshift Express is working (yeah, there is a really big delay, but it's working). > - Sample in Metamer is also working. > - When the JBoss AS 7.0.2.Final is running with "--server-config standalone-preview.xml", the CDI push demo works correctly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 26 09:13:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 26 Mar 2012 09:13:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12090) Components: add jrebel profile to allow rapid development Message-ID: <1665682564.30930.1332767627411.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Luk?? Fry? created RF-12090: ------------------------------- Summary: Components: add jrebel profile to allow rapid development Key: RF-12090 URL: https://issues.jboss.org/browse/RF-12090 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Components: build/distribution Reporter: Luk?? Fry? Assignee: Luk?? Fry? Fix For: 4.2.1.CR1 The {{jrebel}} profile will * generate {{rebel.xml}} * unpack project dependencies which will be used by CDK command-line generator -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 26 09:13:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 26 Mar 2012 09:13:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12090) Components: add jrebel profile to allow rapid development In-Reply-To: <1665682564.30930.1332767627411.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1302869616.30931.1332767627472.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated RF-12090: ---------------------------- Priority: Minor (was: Major) > Components: add jrebel profile to allow rapid development > --------------------------------------------------------- > > Key: RF-12090 > URL: https://issues.jboss.org/browse/RF-12090 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: build/distribution > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Priority: Minor > Fix For: 4.2.1.CR1 > > > The {{jrebel}} profile will > * generate {{rebel.xml}} > * unpack project dependencies which will be used by CDK command-line generator -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 26 09:15:54 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 26 Mar 2012 09:15:54 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-7351) Regression: "messages: globalOnly does not work properly" In-Reply-To: <11790963.1244614376426.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <22628080.30957.1332767754533.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-7351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved RF-7351. ---------------------------- Resolution: Done > Regression: "messages: globalOnly does not work properly" > --------------------------------------------------------- > > Key: RF-7351 > URL: https://issues.jboss.org/browse/RF-7351 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output, regression > Affects Versions: 3.3.1, 4.0.0.Final > Environment: Windows / JBoss 4.2.2.GA / Seam 2.1.1.GA / RichFaces 3.3.1.GA > Reporter: Joseph Miller > Assignee: Luk?? Fry? > Fix For: 4.2.1.CR1 > > Attachments: example-globalOnly-bug.zip, example-globalOnly-bug.zip, Screen shot 2011-04-22 at 16.22.11.png, Screen shot 2011-04-27 at 08.51.26.png, Screen shot 2011-04-27 at 08.52.49.png > > Time Spent: 4 hours > Remaining Estimate: 0 minutes > > Looks like a regression of RF-615... I've upgraded my Seam project to sue RF 3.3.1, in order to fix a number of other bugs, but now messages intended for a single UI component (via the for= ) are appearing in the global messages list at the top of my page. > My page template has: > > ... > > and the controls have: > > ... > > I can switch the rich:messages to h:messages, and it behaves as it should. Also reverting back to the RichFaces 3.2.2.SR1 jars makes the problem go away, but I get the other older bugs back :( -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 26 09:15:54 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 26 Mar 2012 09:15:54 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12090) Components: add jrebel profile to allow rapid development In-Reply-To: <1665682564.30930.1332767627411.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <58097842.30959.1332767754708.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved RF-12090. ----------------------------- Resolution: Done > Components: add jrebel profile to allow rapid development > --------------------------------------------------------- > > Key: RF-12090 > URL: https://issues.jboss.org/browse/RF-12090 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: build/distribution > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Priority: Minor > Fix For: 4.2.1.CR1 > > > The {{jrebel}} profile will > * generate {{rebel.xml}} > * unpack project dependencies which will be used by CDK command-line generator -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 26 09:15:55 2012 From: jira-events at lists.jboss.org (Rene O (JIRA)) Date: Mon, 26 Mar 2012 09:15:55 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11948) rich:extendedDataTable generates a js-error stating this.normalPartStyle is undefined In-Reply-To: <2050628653.20854.1328272188456.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1801887010.30961.1332767755109.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679282#comment-12679282 ] Rene O commented on RF-11948: ----------------------------- This solution doesn't work for all usecases. If you use ajax, this solution fails. See the following code for an example: {code:title='Show table with ajax'} JSF Test

    ColA #{item.itemA}     {code} If you click the ajaxified button to show the table, the rich:ready event isn't fired and so the resizing doesn't work. If you press F5 to refresh the page, the event is fired. But this is not the wanted behaviour. The resizing also works directly, if panelGroup with id='mytableGroup' is alway rendered -> > rich:extendedDataTable generates a js-error stating this.normalPartStyle is undefined > ------------------------------------------------------------------------------------- > > Key: RF-11948 > URL: https://issues.jboss.org/browse/RF-11948 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.2.0.CR1 > Environment: richfaces-4.2.0-SNAPSHOT, Firefox 10, IE8 > Reporter: Rene O > Assignee: Brian Leathem > Fix For: 4.2.1.CR1 > > > If you use rich:extendedDataTable and manually set the width of a column afterwards, a js error occurs > {code:title=page-snippet to reproduce the issue} > > xmlns:h="http://java.sun.com/jsf/html" > xmlns:f="http://java.sun.com/jsf/core" > xmlns:ui="http://java.sun.com/jsf/facelets" > xmlns:a4j="http://richfaces.org/a4j" > xmlns:rich="http://richfaces.org/rich" > > > > JSF Test > > > > > > > > > > ColA > > #{item.itemA} > > > > > > > {code} > {code:title=js error} > Fehler: this.normalPartStyle is undefined > Quelldatei: http://localhost:8080/jsftest/javax.faces.resource/extendedDataTable.js.jsf?ln=org.richfaces > Zeile: 279 > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 26 09:17:47 2012 From: jira-events at lists.jboss.org (Rene O (JIRA)) Date: Mon, 26 Mar 2012 09:17:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11948) rich:extendedDataTable generates a js-error stating this.normalPartStyle is undefined In-Reply-To: <2050628653.20854.1328272188456.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <971068719.30968.1332767867521.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rene O reopened RF-11948: ------------------------- > rich:extendedDataTable generates a js-error stating this.normalPartStyle is undefined > ------------------------------------------------------------------------------------- > > Key: RF-11948 > URL: https://issues.jboss.org/browse/RF-11948 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.2.0.CR1 > Environment: richfaces-4.2.0-SNAPSHOT, Firefox 10, IE8 > Reporter: Rene O > Assignee: Brian Leathem > Fix For: 4.2.1.CR1 > > > If you use rich:extendedDataTable and manually set the width of a column afterwards, a js error occurs > {code:title=page-snippet to reproduce the issue} > > xmlns:h="http://java.sun.com/jsf/html" > xmlns:f="http://java.sun.com/jsf/core" > xmlns:ui="http://java.sun.com/jsf/facelets" > xmlns:a4j="http://richfaces.org/a4j" > xmlns:rich="http://richfaces.org/rich" > > > > JSF Test > > > > > > > > > > ColA > > #{item.itemA} > > > > > > > {code} > {code:title=js error} > Fehler: this.normalPartStyle is undefined > Quelldatei: http://localhost:8080/jsftest/javax.faces.resource/extendedDataTable.js.jsf?ln=org.richfaces > Zeile: 279 > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 26 09:17:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 26 Mar 2012 09:17:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12090) Components: add jrebel profile to allow rapid development In-Reply-To: <1665682564.30930.1332767627411.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1454443474.30969.1332767867577.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679283#comment-12679283 ] Luk?? Fry? commented on RF-12090: --------------------------------- https://github.com/richfaces/components/commit/c6b4287d7b08c7b33a3acf64cdcb3f6a7f5d4cbb > Components: add jrebel profile to allow rapid development > --------------------------------------------------------- > > Key: RF-12090 > URL: https://issues.jboss.org/browse/RF-12090 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: build/distribution > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Priority: Minor > Fix For: 4.2.1.CR1 > > > The {{jrebel}} profile will > * generate {{rebel.xml}} > * unpack project dependencies which will be used by CDK command-line generator -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 26 09:43:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 26 Mar 2012 09:43:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12044) Metamer: @preventDefault attribute of rich:hotKey component doesn't work in IE 9 and Google Chrome In-Reply-To: <283065864.9549.1331739467659.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1282688716.31065.1332769427341.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679287#comment-12679287 ] Luk?? Fry? commented on RF-12044: --------------------------------- Regrettably there is nothing we can do about it. As some users reports, IE handles selected shortcuts specifically: http://stackoverflow.com/questions/7883807/prevent-default-event-action-not-working We are already taking all available actions to prevent propagation: https://github.com/richfaces/components/blob/develop/misc/ui/src/main/resources/META-INF/resources/org.richfaces/hotkey.js#L51 I suggest to open issue in {{RFPL/doc}} to note this limitation in Component Reference. > Metamer: @preventDefault attribute of rich:hotKey component doesn't work in IE 9 and Google Chrome > -------------------------------------------------------------------------------------------------- > > Key: RF-12044 > URL: https://issues.jboss.org/browse/RF-12044 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-misc > Affects Versions: 4.2.0.Final > Environment: RichFaces 4.2.1-SNAPSHOT > Metamer 4.2.1-SNAPSHOT > Mojarra 2.1.5-SNAPSHOT > JBoss AS 7.1.0.Final > Java(TM) SE Runtime Environment 1.6.0_31-b04 @ Linux > Chrome 17.0.963.78 @ Linux i686 > ?RichFaces 4.2.1-SNAPSHOT > ?Metamer 4.2.1-SNAPSHOT > ?Mojarra 2.1.5-SNAPSHOT > ?JBoss AS 7.1.0.Final > ?Java(TM) SE Runtime Environment 1.6.0_31-b04 @ Linux > ?Internet Explorer 9.0 @ Win32 > Reporter: Jan Papousek > Assignee: Luk?? Fry? > Labels: Chrome, IE9 > Fix For: 4.2.1.CR1 > > > It's working correctly in Firefox 10. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 26 09:51:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 26 Mar 2012 09:51:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12044) Metamer: @preventDefault attribute of rich:hotKey component doesn't work in IE 9 and Google Chrome In-Reply-To: <283065864.9549.1331739467659.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1281719483.31086.1332769908019.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679289#comment-12679289 ] Luk?? Fry? commented on RF-12044: --------------------------------- Jan, could you please try additionally how RF3 behaved in regards to {{Alt+X}} shortcut? > Metamer: @preventDefault attribute of rich:hotKey component doesn't work in IE 9 and Google Chrome > -------------------------------------------------------------------------------------------------- > > Key: RF-12044 > URL: https://issues.jboss.org/browse/RF-12044 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-misc > Affects Versions: 4.2.0.Final > Environment: RichFaces 4.2.1-SNAPSHOT > Metamer 4.2.1-SNAPSHOT > Mojarra 2.1.5-SNAPSHOT > JBoss AS 7.1.0.Final > Java(TM) SE Runtime Environment 1.6.0_31-b04 @ Linux > Chrome 17.0.963.78 @ Linux i686 > ?RichFaces 4.2.1-SNAPSHOT > ?Metamer 4.2.1-SNAPSHOT > ?Mojarra 2.1.5-SNAPSHOT > ?JBoss AS 7.1.0.Final > ?Java(TM) SE Runtime Environment 1.6.0_31-b04 @ Linux > ?Internet Explorer 9.0 @ Win32 > Reporter: Jan Papousek > Assignee: Luk?? Fry? > Labels: Chrome, IE9 > Fix For: 4.2.1.CR1 > > > It's working correctly in Firefox 10. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 26 09:51:48 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 26 Mar 2012 09:51:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12044) Metamer: @preventDefault attribute of rich:hotKey component doesn't work in IE 9 and Google Chrome In-Reply-To: <283065864.9549.1331739467659.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <857980534.31089.1332769908323.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? reassigned RF-12044: ------------------------------- Assignee: Jan Papousek (was: Luk?? Fry?) > Metamer: @preventDefault attribute of rich:hotKey component doesn't work in IE 9 and Google Chrome > -------------------------------------------------------------------------------------------------- > > Key: RF-12044 > URL: https://issues.jboss.org/browse/RF-12044 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-misc > Affects Versions: 4.2.0.Final > Environment: RichFaces 4.2.1-SNAPSHOT > Metamer 4.2.1-SNAPSHOT > Mojarra 2.1.5-SNAPSHOT > JBoss AS 7.1.0.Final > Java(TM) SE Runtime Environment 1.6.0_31-b04 @ Linux > Chrome 17.0.963.78 @ Linux i686 > ?RichFaces 4.2.1-SNAPSHOT > ?Metamer 4.2.1-SNAPSHOT > ?Mojarra 2.1.5-SNAPSHOT > ?JBoss AS 7.1.0.Final > ?Java(TM) SE Runtime Environment 1.6.0_31-b04 @ Linux > ?Internet Explorer 9.0 @ Win32 > Reporter: Jan Papousek > Assignee: Jan Papousek > Labels: Chrome, IE9 > Fix For: 4.2.1.CR1 > > > It's working correctly in Firefox 10. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 26 09:51:48 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 26 Mar 2012 09:51:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12044) Metamer: @preventDefault attribute of rich:hotKey component doesn't work in IE 9 and Google Chrome In-Reply-To: <283065864.9549.1331739467659.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <919660236.31092.1332769908446.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679289#comment-12679289 ] Luk?? Fry? edited comment on RF-12044 at 3/26/12 9:51 AM: ---------------------------------------------------------- Jan, could you please try additionally how RF3 behaved in regards to {{Alt+X}} shortcut as we don't want to break backward compatibility? was (Author: lfryc): Jan, could you please try additionally how RF3 behaved in regards to {{Alt+X}} shortcut? > Metamer: @preventDefault attribute of rich:hotKey component doesn't work in IE 9 and Google Chrome > -------------------------------------------------------------------------------------------------- > > Key: RF-12044 > URL: https://issues.jboss.org/browse/RF-12044 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-misc > Affects Versions: 4.2.0.Final > Environment: RichFaces 4.2.1-SNAPSHOT > Metamer 4.2.1-SNAPSHOT > Mojarra 2.1.5-SNAPSHOT > JBoss AS 7.1.0.Final > Java(TM) SE Runtime Environment 1.6.0_31-b04 @ Linux > Chrome 17.0.963.78 @ Linux i686 > ?RichFaces 4.2.1-SNAPSHOT > ?Metamer 4.2.1-SNAPSHOT > ?Mojarra 2.1.5-SNAPSHOT > ?JBoss AS 7.1.0.Final > ?Java(TM) SE Runtime Environment 1.6.0_31-b04 @ Linux > ?Internet Explorer 9.0 @ Win32 > Reporter: Jan Papousek > Assignee: Jan Papousek > Labels: Chrome, IE9 > Fix For: 4.2.1.CR1 > > > It's working correctly in Firefox 10. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 26 09:56:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 26 Mar 2012 09:56:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12044) Metamer: @preventDefault attribute of rich:hotKey component doesn't work in IE 9 and Google Chrome In-Reply-To: <283065864.9549.1331739467659.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1250818346.31097.1332770207366.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? reassigned RF-12044: ------------------------------- Assignee: Pavol Pitonak (was: Jan Papousek) > Metamer: @preventDefault attribute of rich:hotKey component doesn't work in IE 9 and Google Chrome > -------------------------------------------------------------------------------------------------- > > Key: RF-12044 > URL: https://issues.jboss.org/browse/RF-12044 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-misc > Affects Versions: 4.2.0.Final > Environment: RichFaces 4.2.1-SNAPSHOT > Metamer 4.2.1-SNAPSHOT > Mojarra 2.1.5-SNAPSHOT > JBoss AS 7.1.0.Final > Java(TM) SE Runtime Environment 1.6.0_31-b04 @ Linux > Chrome 17.0.963.78 @ Linux i686 > ?RichFaces 4.2.1-SNAPSHOT > ?Metamer 4.2.1-SNAPSHOT > ?Mojarra 2.1.5-SNAPSHOT > ?JBoss AS 7.1.0.Final > ?Java(TM) SE Runtime Environment 1.6.0_31-b04 @ Linux > ?Internet Explorer 9.0 @ Win32 > Reporter: Jan Papousek > Assignee: Pavol Pitonak > Labels: Chrome, IE9 > Fix For: 4.2.1.CR1 > > > It's working correctly in Firefox 10. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 26 10:04:49 2012 From: jira-events at lists.jboss.org (RH Bugzilla Integration (JIRA)) Date: Mon, 26 Mar 2012 10:04:49 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11975) Prototype script error in Portal In-Reply-To: <1984257857.36640.1328882328345.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <316073460.31128.1332770689488.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679293#comment-12679293 ] RH Bugzilla Integration commented on RF-11975: ---------------------------------------------- Ken Finnigan made a comment on [bug 793999|https://bugzilla.redhat.com/show_bug.cgi?id=793999] Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -27,4 +27,4 @@ moving the $A function in the JavaScript to the top of the file, but this would require a patch to RichFaces RESULT -Known Issue+Known Issue - https://issues.jboss.org/browse/RF-11975 > Prototype script error in Portal > -------------------------------- > > Key: RF-11975 > URL: https://issues.jboss.org/browse/RF-11975 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: third-party > Affects Versions: 3.3.3.Final > Environment: GateIn v3.2 > JBoss PortletBridge v2.2.0.Final > Firefox > Reporter: Ken Finnigan > Priority: Minor > Fix For: 3.Future > > > When a user wants to add two separate portlets to the same portal page, with both portlets using RichFaces components, the JBoss PortletBridge needs to have the context parameter "org.jboss.portletbridge.WRAP_SCRIPTS" set to true. This wraps the RichFaces JavaScript files with a check to prevent the same file being loaded twice on the one page, as there are two portlets with RichFaces scripts being loaded. > In this situation, the prototype.js script (or framework_pack.js when LoadScriptStrategy is ALL) returns "$A() is not defined" within Firefox, but in Chrome and IE it works fine. > This JS error in Firefox can be resolved by moving the $A function to the very top of the file to ensure it is defined when needed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 26 10:04:48 2012 From: jira-events at lists.jboss.org (RH Bugzilla Integration (JIRA)) Date: Mon, 26 Mar 2012 10:04:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11975) Prototype script error in Portal In-Reply-To: <1984257857.36640.1328882328345.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <251919563.31115.1332770688092.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] RH Bugzilla Integration updated RF-11975: ----------------------------------------- Bugzilla Update: Perform > Prototype script error in Portal > -------------------------------- > > Key: RF-11975 > URL: https://issues.jboss.org/browse/RF-11975 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: third-party > Affects Versions: 3.3.3.Final > Environment: GateIn v3.2 > JBoss PortletBridge v2.2.0.Final > Firefox > Reporter: Ken Finnigan > Priority: Minor > Fix For: 3.Future > > > When a user wants to add two separate portlets to the same portal page, with both portlets using RichFaces components, the JBoss PortletBridge needs to have the context parameter "org.jboss.portletbridge.WRAP_SCRIPTS" set to true. This wraps the RichFaces JavaScript files with a check to prevent the same file being loaded twice on the one page, as there are two portlets with RichFaces scripts being loaded. > In this situation, the prototype.js script (or framework_pack.js when LoadScriptStrategy is ALL) returns "$A() is not defined" within Firefox, but in Chrome and IE it works fine. > This JS error in Firefox can be resolved by moving the $A function to the very top of the file to ensure it is defined when needed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 26 10:04:49 2012 From: jira-events at lists.jboss.org (RH Bugzilla Integration (JIRA)) Date: Mon, 26 Mar 2012 10:04:49 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11975) Prototype script error in Portal In-Reply-To: <1984257857.36640.1328882328345.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <863564851.31123.1332770689290.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679292#comment-12679292 ] RH Bugzilla Integration commented on RF-11975: ---------------------------------------------- Ken Finnigan made a comment on [bug 793999|https://bugzilla.redhat.com/show_bug.cgi?id=793999] I guess a new ticket could be opened, but I don't believe it's an issue that will ever be resolved. Best person to ask is Thomas about what he wants > Prototype script error in Portal > -------------------------------- > > Key: RF-11975 > URL: https://issues.jboss.org/browse/RF-11975 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: third-party > Affects Versions: 3.3.3.Final > Environment: GateIn v3.2 > JBoss PortletBridge v2.2.0.Final > Firefox > Reporter: Ken Finnigan > Priority: Minor > Fix For: 3.Future > > > When a user wants to add two separate portlets to the same portal page, with both portlets using RichFaces components, the JBoss PortletBridge needs to have the context parameter "org.jboss.portletbridge.WRAP_SCRIPTS" set to true. This wraps the RichFaces JavaScript files with a check to prevent the same file being loaded twice on the one page, as there are two portlets with RichFaces scripts being loaded. > In this situation, the prototype.js script (or framework_pack.js when LoadScriptStrategy is ALL) returns "$A() is not defined" within Firefox, but in Chrome and IE it works fine. > This JS error in Firefox can be resolved by moving the $A function to the very top of the file to ensure it is defined when needed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 26 10:04:48 2012 From: jira-events at lists.jboss.org (RH Bugzilla Integration (JIRA)) Date: Mon, 26 Mar 2012 10:04:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11975) Prototype script error in Portal In-Reply-To: <1984257857.36640.1328882328345.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1934877958.31119.1332770688955.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] RH Bugzilla Integration updated RF-11975: ----------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=793999 > Prototype script error in Portal > -------------------------------- > > Key: RF-11975 > URL: https://issues.jboss.org/browse/RF-11975 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: third-party > Affects Versions: 3.3.3.Final > Environment: GateIn v3.2 > JBoss PortletBridge v2.2.0.Final > Firefox > Reporter: Ken Finnigan > Priority: Minor > Fix For: 3.Future > > > When a user wants to add two separate portlets to the same portal page, with both portlets using RichFaces components, the JBoss PortletBridge needs to have the context parameter "org.jboss.portletbridge.WRAP_SCRIPTS" set to true. This wraps the RichFaces JavaScript files with a check to prevent the same file being loaded twice on the one page, as there are two portlets with RichFaces scripts being loaded. > In this situation, the prototype.js script (or framework_pack.js when LoadScriptStrategy is ALL) returns "$A() is not defined" within Firefox, but in Chrome and IE it works fine. > This JS error in Firefox can be resolved by moving the $A function to the very top of the file to ensure it is defined when needed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 26 10:10:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 26 Mar 2012 10:10:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12080) rich:hotKey usage clears body onload attribute In-Reply-To: <1411413331.27453.1332488387294.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <779412766.31153.1332771047302.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? reassigned RF-12080: ------------------------------- Assignee: Luk?? Fry? > rich:hotKey usage clears body onload attribute > ---------------------------------------------- > > Key: RF-12080 > URL: https://issues.jboss.org/browse/RF-12080 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component > Affects Versions: 4.2.0.Final > Environment: myfaces 2.1.6, tomahawk 1.1.11 > Reporter: Michael Heinen > Assignee: Luk?? Fry? > Priority: Minor > Fix For: 4.2.1.CR1 > > > I'm happy to see rich:hotKey in richfaces 4.2, I used it already with richfaces 3.3.3. > One thing I noticed now is that the onload attribute of t:documentboy is cleared on clientside as soon as rich:hotKey is used on a page. Maybe caused by jquery usage? > From my pov this should be either fixed or documented in the component guide as well as in the showcase sample. > Workaround is obvious: Instead of onload use document.ready -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 26 10:35:48 2012 From: jira-events at lists.jboss.org (Dupont Dupont (JIRA)) Date: Mon, 26 Mar 2012 10:35:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12091) rich:dataScroller scrollListener not documented Message-ID: <1487113708.31251.1332772548274.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Dupont Dupont created RF-12091: ---------------------------------- Summary: rich:dataScroller scrollListener not documented Key: RF-12091 URL: https://issues.jboss.org/browse/RF-12091 Project: RichFaces Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 4.2.0.Final Reporter: Dupont Dupont rich:dataScroller has a scrollListener attribute, but it's not documented (no occurence in component reference or in taglib.xml). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 26 11:05:48 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 26 Mar 2012 11:05:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11990) client-side validation and ajax calls create maleformed javascript In-Reply-To: <941910750.25122.1329496418429.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <210647362.31355.1332774348258.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679321#comment-12679321 ] Luk?? Fry? commented on RF-11990: --------------------------------- This is the upstream issue: MyFaces does not separate these two scripts with comma. We would need to simpler sample for having this fixed. > client-side validation and ajax calls create maleformed javascript > ------------------------------------------------------------------ > > Key: RF-11990 > URL: https://issues.jboss.org/browse/RF-11990 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-validators > Affects Versions: 4.0.0.Final, 4.1.0.Final > Environment: MyFaces 2.1.5, Hibernate-Validation 4.2.0.Final > Reporter: Daniel G > Assignee: Luk?? Fry? > Priority: Minor > Labels: javascript, myfaces, richfaces, validation > Fix For: 4.2.1.CR1 > > > Using rich:validation and f:ajax together, maleformed JavaScript is generated. > I'm having a composite component, that has to be able to refresh given other components on change, but the JavaScript code generated by: > {quote} > > > > {quote} > is missing a comma between the Chain parameters. > see the red {color:red}'{color} > {quote} > onchange="jsf.util.chain(document.getElementById('idForm:bNr:input'), > event,'jsf.ajax.request(\'idForm:bNr:input\',event,\{render:\'idForm:idToolBar:idSaveButton\',\'javax.faces.behavior.event\':\'change\'\}){color:red}''{color}idForm_3AbNr_3Ainput_3Av(event,"idForm:kopf:bezugNr:input","idForm:kopf:bezugNr:input")'); return false;" /> > {quote} > the code is tanken from 4.0.0.Final, but looks similar in 4.1.0.Final -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 26 11:09:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 26 Mar 2012 11:09:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11990) client-side validation and ajax calls create maleformed javascript In-Reply-To: <941910750.25122.1329496418429.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1815348497.31365.1332774587847.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679322#comment-12679322 ] Luk?? Fry? commented on RF-11990: --------------------------------- Daniel, just one point: when {{f:ajax}} is attached to the component, you don't need to use {{rich:validator}}, since ajax request will validate the input and produce faces message. > client-side validation and ajax calls create maleformed javascript > ------------------------------------------------------------------ > > Key: RF-11990 > URL: https://issues.jboss.org/browse/RF-11990 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-validators > Affects Versions: 4.0.0.Final, 4.1.0.Final > Environment: MyFaces 2.1.5, Hibernate-Validation 4.2.0.Final > Reporter: Daniel G > Assignee: Luk?? Fry? > Priority: Minor > Labels: javascript, myfaces, richfaces, validation > Fix For: 4.2.1.CR1 > > > Using rich:validation and f:ajax together, maleformed JavaScript is generated. > I'm having a composite component, that has to be able to refresh given other components on change, but the JavaScript code generated by: > {quote} > > > > {quote} > is missing a comma between the Chain parameters. > see the red {color:red}'{color} > {quote} > onchange="jsf.util.chain(document.getElementById('idForm:bNr:input'), > event,'jsf.ajax.request(\'idForm:bNr:input\',event,\{render:\'idForm:idToolBar:idSaveButton\',\'javax.faces.behavior.event\':\'change\'\}){color:red}''{color}idForm_3AbNr_3Ainput_3Av(event,"idForm:kopf:bezugNr:input","idForm:kopf:bezugNr:input")'); return false;" /> > {quote} > the code is tanken from 4.0.0.Final, but looks similar in 4.1.0.Final -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 26 11:34:49 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 26 Mar 2012 11:34:49 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11990) client-side validation and ajax calls create maleformed javascript In-Reply-To: <941910750.25122.1329496418429.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1705692282.31445.1332776089300.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679336#comment-12679336 ] Luk?? Fry? commented on RF-11990: --------------------------------- Following behavior reproduces the issue as well: {code:java} @FacesBehavior("eu.fryc.Behavior1") public class Behavior1 extends ClientBehaviorBase { @Override public String getScript(ClientBehaviorContext behaviorContext) { return "alert('xyz')"; } } {code} {code:xml} http://fryc.eu/behavior behavior1 eu.fryc.Behavior1 {code} {code:XML} {code} It produces: {code:XML} {code} > client-side validation and ajax calls create maleformed javascript > ------------------------------------------------------------------ > > Key: RF-11990 > URL: https://issues.jboss.org/browse/RF-11990 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-validators > Affects Versions: 4.0.0.Final, 4.1.0.Final > Environment: MyFaces 2.1.5, Hibernate-Validation 4.2.0.Final > Reporter: Daniel G > Assignee: Luk?? Fry? > Priority: Minor > Labels: javascript, myfaces, richfaces, validation > Fix For: 4.2.1.CR1 > > > Using rich:validation and f:ajax together, maleformed JavaScript is generated. > I'm having a composite component, that has to be able to refresh given other components on change, but the JavaScript code generated by: > {quote} > > > > {quote} > is missing a comma between the Chain parameters. > see the red {color:red}'{color} > {quote} > onchange="jsf.util.chain(document.getElementById('idForm:bNr:input'), > event,'jsf.ajax.request(\'idForm:bNr:input\',event,\{render:\'idForm:idToolBar:idSaveButton\',\'javax.faces.behavior.event\':\'change\'\}){color:red}''{color}idForm_3AbNr_3Ainput_3Av(event,"idForm:kopf:bezugNr:input","idForm:kopf:bezugNr:input")'); return false;" /> > {quote} > the code is tanken from 4.0.0.Final, but looks similar in 4.1.0.Final -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 26 11:36:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 26 Mar 2012 11:36:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11990) client-side validation and ajax calls create maleformed javascript In-Reply-To: <941910750.25122.1329496418429.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1675862592.31453.1332776207668.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679338#comment-12679338 ] Luk?? Fry? commented on RF-11990: --------------------------------- Note that explicit definition on {{event}} attributes for both behaviors (or not-defining {{event}} attributes at all) fixes the issue: {code:xml} {code} {code:xml} {code} > client-side validation and ajax calls create maleformed javascript > ------------------------------------------------------------------ > > Key: RF-11990 > URL: https://issues.jboss.org/browse/RF-11990 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-validators > Affects Versions: 4.0.0.Final, 4.1.0.Final > Environment: MyFaces 2.1.5, Hibernate-Validation 4.2.0.Final > Reporter: Daniel G > Assignee: Luk?? Fry? > Priority: Minor > Labels: javascript, myfaces, richfaces, validation > Fix For: 4.2.1.CR1 > > > Using rich:validation and f:ajax together, maleformed JavaScript is generated. > I'm having a composite component, that has to be able to refresh given other components on change, but the JavaScript code generated by: > {quote} > > > > {quote} > is missing a comma between the Chain parameters. > see the red {color:red}'{color} > {quote} > onchange="jsf.util.chain(document.getElementById('idForm:bNr:input'), > event,'jsf.ajax.request(\'idForm:bNr:input\',event,\{render:\'idForm:idToolBar:idSaveButton\',\'javax.faces.behavior.event\':\'change\'\}){color:red}''{color}idForm_3AbNr_3Ainput_3Av(event,"idForm:kopf:bezugNr:input","idForm:kopf:bezugNr:input")'); return false;" /> > {quote} > the code is tanken from 4.0.0.Final, but looks similar in 4.1.0.Final -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 26 11:38:49 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 26 Mar 2012 11:38:49 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11990) client-side validation and ajax calls create maleformed javascript In-Reply-To: <941910750.25122.1329496418429.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <407552288.31462.1332776329341.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679336#comment-12679336 ] Luk?? Fry? edited comment on RF-11990 at 3/26/12 11:37 AM: ----------------------------------------------------------- Following behavior reproduces the issue as well: {code:java|title=Behavior1.java} @FacesBehavior("eu.fryc.Behavior1") public class Behavior1 extends ClientBehaviorBase { @Override public String getScript(ClientBehaviorContext behaviorContext) { return "alert('xyz')"; } } {code} {code:xml|title=META-INF/fryc.taglib.xml} http://fryc.eu/behavior behavior1 eu.fryc.Behavior1 {code} {code:XML|title=behavior-test.xhtml} {code} It produces: {code:XML|title=output} {code} was (Author: lfryc): Following behavior reproduces the issue as well: {code:java} @FacesBehavior("eu.fryc.Behavior1") public class Behavior1 extends ClientBehaviorBase { @Override public String getScript(ClientBehaviorContext behaviorContext) { return "alert('xyz')"; } } {code} {code:xml} http://fryc.eu/behavior behavior1 eu.fryc.Behavior1 {code} {code:XML} {code} It produces: {code:XML} {code} > client-side validation and ajax calls create maleformed javascript > ------------------------------------------------------------------ > > Key: RF-11990 > URL: https://issues.jboss.org/browse/RF-11990 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-validators > Affects Versions: 4.0.0.Final, 4.1.0.Final > Environment: MyFaces 2.1.5, Hibernate-Validation 4.2.0.Final > Reporter: Daniel G > Assignee: Luk?? Fry? > Priority: Minor > Labels: javascript, myfaces, richfaces, validation > Fix For: 4.2.1.CR1 > > > Using rich:validation and f:ajax together, maleformed JavaScript is generated. > I'm having a composite component, that has to be able to refresh given other components on change, but the JavaScript code generated by: > {quote} > > > > {quote} > is missing a comma between the Chain parameters. > see the red {color:red}'{color} > {quote} > onchange="jsf.util.chain(document.getElementById('idForm:bNr:input'), > event,'jsf.ajax.request(\'idForm:bNr:input\',event,\{render:\'idForm:idToolBar:idSaveButton\',\'javax.faces.behavior.event\':\'change\'\}){color:red}''{color}idForm_3AbNr_3Ainput_3Av(event,"idForm:kopf:bezugNr:input","idForm:kopf:bezugNr:input")'); return false;" /> > {quote} > the code is tanken from 4.0.0.Final, but looks similar in 4.1.0.Final -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 26 11:42:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 26 Mar 2012 11:42:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11990) client-side validation and ajax calls create maleformed javascript In-Reply-To: <941910750.25122.1329496418429.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1722161623.31495.1332776567813.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679344#comment-12679344 ] Luk?? Fry? commented on RF-11990: --------------------------------- Note that Mojarra behaves even more invalid: {code:xml|title=test1.xhtml} {code} {code:xml|title=output1} {code} Again, it works great when {{event}} provided for both behaviors or not provided at all. > client-side validation and ajax calls create maleformed javascript > ------------------------------------------------------------------ > > Key: RF-11990 > URL: https://issues.jboss.org/browse/RF-11990 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-validators > Affects Versions: 4.0.0.Final, 4.1.0.Final > Environment: MyFaces 2.1.5, Hibernate-Validation 4.2.0.Final > Reporter: Daniel G > Assignee: Luk?? Fry? > Priority: Minor > Labels: javascript, myfaces, richfaces, validation > Fix For: 4.2.1.CR1 > > > Using rich:validation and f:ajax together, maleformed JavaScript is generated. > I'm having a composite component, that has to be able to refresh given other components on change, but the JavaScript code generated by: > {quote} > > > > {quote} > is missing a comma between the Chain parameters. > see the red {color:red}'{color} > {quote} > onchange="jsf.util.chain(document.getElementById('idForm:bNr:input'), > event,'jsf.ajax.request(\'idForm:bNr:input\',event,\{render:\'idForm:idToolBar:idSaveButton\',\'javax.faces.behavior.event\':\'change\'\}){color:red}''{color}idForm_3AbNr_3Ainput_3Av(event,"idForm:kopf:bezugNr:input","idForm:kopf:bezugNr:input")'); return false;" /> > {quote} > the code is tanken from 4.0.0.Final, but looks similar in 4.1.0.Final -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 26 13:41:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 26 Mar 2012 13:41:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12084) Richfaces 4.2 when inside dont work and causes 'identifier resolved to null' In-Reply-To: <1382382061.29574.1332701569056.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1054953498.32027.1332783707376.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12084: ------------------------------- Summary: Richfaces 4.2 when inside dont work and causes 'identifier resolved to null' (was: Richfaces 4.2 when inside dont work and causes 'identifier resolved to null') Forum Reference: https://community.jboss.org/message/723859, https://community.jboss.org/thread/196867 (was: https://community.jboss.org/message/723859, https://community.jboss.org/thread/196867) > Richfaces 4.2 when inside dont work and causes 'identifier resolved to null' > ----------------------------------------------------------------------------------------------------- > > Key: RF-12084 > URL: https://issues.jboss.org/browse/RF-12084 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.2.0.Final > Environment: Windows Vista, Firefox 11, Richfaces 4.2 Final, Mojarra 2.1.7, Tomcat 7.0.26 > Reporter: Ivan Costa > Labels: richfaces > > a4j:commandLink or a4j:ajax tags inside ui:fragment causes 'identifier resolved to null', > but h:commandLink + f:ajax (both from Mojarra) works perfectly fine! > The problem is described here > https://community.jboss.org/message/723859 > and here: > https://community.jboss.org/thread/196867 > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 26 14:02:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 26 Mar 2012 14:02:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12091) rich:dataScroller scrollListener not documented In-Reply-To: <1487113708.31251.1332772548274.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1631546630.32095.1332784967316.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12091: ------------------------------- Fix Version/s: 4.2.1.CR1 Assignee: Brian Leathem Forum Reference: https://community.jboss.org/thread/197474 (was: https://community.jboss.org/thread/197474) Looks like the method: {code} public DataScrollListener[] getScrollListeners() { return (DataScrollListener[]) getFacesListeners(DataScrollListener.class); } {code} is missing the @Attribute annotation. It should be added, with generate=false. > rich:dataScroller scrollListener not documented > ----------------------------------------------- > > Key: RF-12091 > URL: https://issues.jboss.org/browse/RF-12091 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: 4.2.0.Final > Reporter: Dupont Dupont > Assignee: Brian Leathem > Fix For: 4.2.1.CR1 > > > rich:dataScroller has a scrollListener attribute, but it's not documented (no occurence in component reference or in taglib.xml). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 26 14:02:47 2012 From: jira-events at lists.jboss.org (Robert Gary (JIRA)) Date: Mon, 26 Mar 2012 14:02:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12092) a4j:poll : a4j:status never clears Message-ID: <69599813.32096.1332784967357.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Robert Gary created RF-12092: -------------------------------- Summary: a4j:poll : a4j:status never clears Key: RF-12092 URL: https://issues.jboss.org/browse/RF-12092 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-push/poll Affects Versions: 4.2.0.Final Reporter: Robert Gary When a4j:poll fires a4j:status correctly displays the request is in progress. However, it never shows it complete. Using any other a4j component will correctly update the a4j:status. So if the a4j:status is stuck showing its waiting because of an a4j:poll if you click on an a4j:commandButton the a4j:status will correctly show its now complete. This code works correctly in RF 3.3.3. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 26 14:10:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 26 Mar 2012 14:10:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12092) a4j:poll : a4j:status never clears In-Reply-To: <69599813.32096.1332784967357.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <653192255.32150.1332785447374.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12092: ------------------------------- Assignee: Pavol Pitonak QE, would you please create a metamer page to reproduce this issue? > a4j:poll : a4j:status never clears > ---------------------------------- > > Key: RF-12092 > URL: https://issues.jboss.org/browse/RF-12092 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Affects Versions: 4.2.0.Final > Reporter: Robert Gary > Assignee: Pavol Pitonak > > When a4j:poll fires a4j:status correctly displays the request is in progress. However, it never shows it complete. Using any other a4j component will correctly update the a4j:status. So if the a4j:status is stuck showing its waiting because of an a4j:poll if you click on an a4j:commandButton the a4j:status will correctly show its now complete. > render="#{faces$DiscoveryStatus.reRenderStr}"/> > > > > > > > > > This code works correctly in RF 3.3.3. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 26 14:12:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 26 Mar 2012 14:12:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12084) Richfaces 4.2 when inside dont work and causes 'identifier resolved to null' In-Reply-To: <1382382061.29574.1332701569056.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1541699031.32160.1332785567340.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem reassigned RF-12084: ---------------------------------- Assignee: Pavol Pitonak QE, please create a metamer page including the above test code. > Richfaces 4.2 when inside dont work and causes 'identifier resolved to null' > ----------------------------------------------------------------------------------------------------- > > Key: RF-12084 > URL: https://issues.jboss.org/browse/RF-12084 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.2.0.Final > Environment: Windows Vista, Firefox 11, Richfaces 4.2 Final, Mojarra 2.1.7, Tomcat 7.0.26 > Reporter: Ivan Costa > Assignee: Pavol Pitonak > Labels: richfaces > > a4j:commandLink or a4j:ajax tags inside ui:fragment causes 'identifier resolved to null', > but h:commandLink + f:ajax (both from Mojarra) works perfectly fine! > The problem is described here > https://community.jboss.org/message/723859 > and here: > https://community.jboss.org/thread/196867 > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 26 14:14:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 26 Mar 2012 14:14:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12087) itemChangeListener attribute @listener does not work In-Reply-To: <1894988349.30243.1332753647412.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <285109870.32164.1332785687569.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12087: ------------------------------- Fix Version/s: 4.3-Tracking > itemChangeListener attribute @listener does not work > ---------------------------------------------------- > > Key: RF-12087 > URL: https://issues.jboss.org/browse/RF-12087 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-misc > Environment: RichFaces 4.2.1-SNAPSHOT > Metamer 4.2.1-SNAPSHOT > Mojarra 2.1.5-SNAPSHOT > JBoss AS 7.1.0.Final > OpenJDK Runtime Environment 1.6.0_24-b24 @ Linux > Firefox 11.0 @ Linux x86_64 > Reporter: Ji?? ?tefek > Fix For: 4.3-Tracking > > > # Deploy Metamer. > # Open http://localhost:8080/metamer/faces/components/richItemChangeListener/accordion.xhtml > ( > or http://localhost:8080/metamer/faces/components/richItemChangeListener/panelMenu.xhtml > or http://localhost:8080/metamer/faces/components/richItemChangeListener/tabPanel.xhtml > or http://localhost:8080/metamer/faces/components/richItemChangeListener/togglePanel.xhtml > ) > # Click on accordion panel Item 2. > # 2 messages with "* itemChangeListenerBean item changed: null -> item2" should appear in phases list. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 26 14:14:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 26 Mar 2012 14:14:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12089) itemChangeListener attribute @for does not work In-Reply-To: <405838573.30375.1332756049100.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <512575733.32167.1332785687682.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12089: ------------------------------- Fix Version/s: 4.3-Tracking > itemChangeListener attribute @for does not work > ----------------------------------------------- > > Key: RF-12089 > URL: https://issues.jboss.org/browse/RF-12089 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-misc > Affects Versions: 4.2.0.Final > Environment: RichFaces 4.2.1-SNAPSHOT > Metamer 4.2.1-SNAPSHOT > Mojarra 2.1.5-SNAPSHOT > JBoss AS 7.1.0.Final > OpenJDK Runtime Environment 1.6.0_24-b24 @ Linux > Firefox 11.0 @ Linux x86_64 > Reporter: Ji?? ?tefek > Fix For: 4.3-Tracking > > > # Deploy Metamer. > # Open http://localhost:8080/metamer/faces/components/richItemChangeListener/RF-12089.xhtml . -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 26 14:18:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 26 Mar 2012 14:18:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12079) ignores In-Reply-To: <2129957963.25561.1332425267314.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1432921847.32170.1332785927494.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-12079. -------------------------------- Resolution: Duplicate Issue > ignores > ---------------------------------- > > Key: RF-12079 > URL: https://issues.jboss.org/browse/RF-12079 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tree > Affects Versions: 4.2.0.Final > Environment: RichFaces 4.2.0 and JSF 2.2 with CDI (Bean type "javax.inject.Named") > Application Server GlassFish Server Open Source Edition 3.1.2 (build 23) > Reporter: Wesley Menezes > Assignee: Brian Leathem > > In JSF with a and this have nested, if is applied in , the ajax listener isn't called. > But, if applied to (under) , the ajax event fires method listener call. > {code:title=XHTML (snippet)} > id="memoriaTree" > value="#{cadCustomerBean.rootNodes}" > toggleType="client" > var="node" > nodeType="#{node.data.type}" > > > id="memoriaRoot" > type="customer" > iconLeaf="../images/fichario.gif" > data="#{node.data.id}"> > > immediate="true" > execute="@this" > event="mousedown" > listener="#{cadCustomerBean.processTreeSelectionChange(node.data)}"/> > > > {code} > {code:title=BEAN (snippet)} > /*imports...*/ > @Named > @SessionScoped > public class CadCustomerBean implements Serializable { > public void processTreeSelectionChange (MyClass myObject) { > > System.out.println(myObject); > } > } > {code} > Obs. In RichFaces 4.2.0 Final showcase, the has the attribute "selectionChangeListener", but I found only "treeSelectionChangeListener" in jars of RichFaces (like attribute of the tag, or like a tag ). The "Component_Reference.pdf" is ok. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 26 14:18:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 26 Mar 2012 14:18:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12021) Compilation of Input UI component logs 2 errors about faces-config.xml In-Reply-To: <518462150.61467.1330674576214.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1350620685.32173.1332785927671.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12021: ------------------------------- Fix Version/s: 4.2.1.CR1 Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=801048 (was: https://bugzilla.redhat.com/show_bug.cgi?id=801048) > Compilation of Input UI component logs 2 errors about faces-config.xml > ---------------------------------------------------------------------- > > Key: RF-12021 > URL: https://issues.jboss.org/browse/RF-12021 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.2.0.Final > Reporter: Marek Novotny > Assignee: Brian Leathem > Fix For: 4.2.1.CR1 > > > Compilation of RF UI Components specifically Input UI has got 2 errors in log - related to bad faces-config.xml on line number 29 and 240. > The following is snippet of log: > {noformat} > [INFO] ------------------------------------------------------------------------ > [INFO] Building RichFaces UI Components: Input UI 4.2.0.Final > [INFO] ------------------------------------------------------------------------ > [INFO] > [INFO] --- maven-enforcer-plugin:1.0-redhat-1:enforce (enforce-java-version) @ richfaces-ui-input-ui --- > [INFO] The requirePluginVersions rule is currently not compatible with Maven3. > [INFO] > [INFO] --- maven-enforcer-plugin:1.0-redhat-1:enforce (enforce-maven-version) @ richfaces-ui-input-ui --- > [INFO] The requirePluginVersions rule is currently not compatible with Maven3. > [INFO] > [INFO] --- maven-cdk-plugin:4.2.0.Final-redhat-1:generate (cdk-generate-sources) @ richfaces-ui-input-ui --- > [Error] faces-config.xml:29:71: cvc-complex-type.2.4.a: Invalid content was found starting with element 'xi:include'. One of '{"http://java.sun.com/xml/ns/javaee":property, "http://java.sun.com/xml/ns/javaee":component-extension}' is expected. > [Error] faces-config.xml:240:71: cvc-complex-type.2.4.a: Invalid content was found starting with element 'xi:include'. One of '{"http://java.sun.com/xml/ns/javaee":property, "http://java.sun.com/xml/ns/javaee":component-extension}' is expected. > {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 26 14:39:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 26 Mar 2012 14:39:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11990) client-side validation and ajax calls create maleformed javascript In-Reply-To: <941910750.25122.1329496418429.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <70378671.32207.1332787187421.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679434#comment-12679434 ] Luk?? Fry? commented on RF-11990: --------------------------------- Issues reported in MyFaces: https://issues.apache.org/jira/browse/MYFACES-3513 > client-side validation and ajax calls create maleformed javascript > ------------------------------------------------------------------ > > Key: RF-11990 > URL: https://issues.jboss.org/browse/RF-11990 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-validators > Affects Versions: 4.0.0.Final, 4.1.0.Final > Environment: MyFaces 2.1.5, Hibernate-Validation 4.2.0.Final > Reporter: Daniel G > Assignee: Luk?? Fry? > Priority: Minor > Labels: javascript, myfaces, richfaces, validation > Fix For: 4.2.1.CR1 > > > Using rich:validation and f:ajax together, maleformed JavaScript is generated. > I'm having a composite component, that has to be able to refresh given other components on change, but the JavaScript code generated by: > {quote} > > > > {quote} > is missing a comma between the Chain parameters. > see the red {color:red}'{color} > {quote} > onchange="jsf.util.chain(document.getElementById('idForm:bNr:input'), > event,'jsf.ajax.request(\'idForm:bNr:input\',event,\{render:\'idForm:idToolBar:idSaveButton\',\'javax.faces.behavior.event\':\'change\'\}){color:red}''{color}idForm_3AbNr_3Ainput_3Av(event,"idForm:kopf:bezugNr:input","idForm:kopf:bezugNr:input")'); return false;" /> > {quote} > the code is tanken from 4.0.0.Final, but looks similar in 4.1.0.Final -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 26 14:45:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 26 Mar 2012 14:45:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11990) client-side validation and ajax calls create maleformed javascript In-Reply-To: <941910750.25122.1329496418429.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1996814340.32237.1332787547996.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679434#comment-12679434 ] Luk?? Fry? edited comment on RF-11990 at 3/26/12 2:45 PM: ---------------------------------------------------------- Issues reported in upstream projects: https://issues.apache.org/jira/browse/MYFACES-3513 http://java.net/jira/browse/JAVASERVERFACES-2354 was (Author: lfryc): Issues reported in MyFaces: https://issues.apache.org/jira/browse/MYFACES-3513 > client-side validation and ajax calls create maleformed javascript > ------------------------------------------------------------------ > > Key: RF-11990 > URL: https://issues.jboss.org/browse/RF-11990 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-validators > Affects Versions: 4.0.0.Final, 4.1.0.Final > Environment: MyFaces 2.1.5, Hibernate-Validation 4.2.0.Final > Reporter: Daniel G > Assignee: Luk?? Fry? > Priority: Minor > Labels: javascript, myfaces, richfaces, validation > Fix For: 4.2.1.CR1 > > > Using rich:validation and f:ajax together, maleformed JavaScript is generated. > I'm having a composite component, that has to be able to refresh given other components on change, but the JavaScript code generated by: > {quote} > > > > {quote} > is missing a comma between the Chain parameters. > see the red {color:red}'{color} > {quote} > onchange="jsf.util.chain(document.getElementById('idForm:bNr:input'), > event,'jsf.ajax.request(\'idForm:bNr:input\',event,\{render:\'idForm:idToolBar:idSaveButton\',\'javax.faces.behavior.event\':\'change\'\}){color:red}''{color}idForm_3AbNr_3Ainput_3Av(event,"idForm:kopf:bezugNr:input","idForm:kopf:bezugNr:input")'); return false;" /> > {quote} > the code is tanken from 4.0.0.Final, but looks similar in 4.1.0.Final -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 26 14:47:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 26 Mar 2012 14:47:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11990) client-side validation and ajax calls create maleformed javascript In-Reply-To: <941910750.25122.1329496418429.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1616072039.32241.1332787667580.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved RF-11990. ----------------------------- Fix Version/s: (was: 4.2.1.CR1) Resolution: Rejected I'm rejecting this since it is upstream projects' issue. > client-side validation and ajax calls create maleformed javascript > ------------------------------------------------------------------ > > Key: RF-11990 > URL: https://issues.jboss.org/browse/RF-11990 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-validators > Affects Versions: 4.0.0.Final, 4.1.0.Final > Environment: MyFaces 2.1.5, Hibernate-Validation 4.2.0.Final > Reporter: Daniel G > Assignee: Luk?? Fry? > Priority: Minor > Labels: javascript, myfaces, richfaces, validation > > Using rich:validation and f:ajax together, maleformed JavaScript is generated. > I'm having a composite component, that has to be able to refresh given other components on change, but the JavaScript code generated by: > {quote} > > > > {quote} > is missing a comma between the Chain parameters. > see the red {color:red}'{color} > {quote} > onchange="jsf.util.chain(document.getElementById('idForm:bNr:input'), > event,'jsf.ajax.request(\'idForm:bNr:input\',event,\{render:\'idForm:idToolBar:idSaveButton\',\'javax.faces.behavior.event\':\'change\'\}){color:red}''{color}idForm_3AbNr_3Ainput_3Av(event,"idForm:kopf:bezugNr:input","idForm:kopf:bezugNr:input")'); return false;" /> > {quote} > the code is tanken from 4.0.0.Final, but looks similar in 4.1.0.Final -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 26 14:47:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 26 Mar 2012 14:47:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11990) client-side validation and ajax calls create maleformed javascript In-Reply-To: <941910750.25122.1329496418429.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1795243020.32245.1332787667961.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679344#comment-12679344 ] Luk?? Fry? edited comment on RF-11990 at 3/26/12 2:47 PM: ---------------------------------------------------------- Note that Mojarra behaves even more wrong: {code:xml|title=test1.xhtml} {code} {code:xml|title=output1} {code} Again, it works great when {{event}} provided for both behaviors or not provided at all. was (Author: lfryc): Note that Mojarra behaves even more invalid: {code:xml|title=test1.xhtml} {code} {code:xml|title=output1} {code} Again, it works great when {{event}} provided for both behaviors or not provided at all. > client-side validation and ajax calls create maleformed javascript > ------------------------------------------------------------------ > > Key: RF-11990 > URL: https://issues.jboss.org/browse/RF-11990 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-validators > Affects Versions: 4.0.0.Final, 4.1.0.Final > Environment: MyFaces 2.1.5, Hibernate-Validation 4.2.0.Final > Reporter: Daniel G > Assignee: Luk?? Fry? > Priority: Minor > Labels: javascript, myfaces, richfaces, validation > > Using rich:validation and f:ajax together, maleformed JavaScript is generated. > I'm having a composite component, that has to be able to refresh given other components on change, but the JavaScript code generated by: > {quote} > > > > {quote} > is missing a comma between the Chain parameters. > see the red {color:red}'{color} > {quote} > onchange="jsf.util.chain(document.getElementById('idForm:bNr:input'), > event,'jsf.ajax.request(\'idForm:bNr:input\',event,\{render:\'idForm:idToolBar:idSaveButton\',\'javax.faces.behavior.event\':\'change\'\}){color:red}''{color}idForm_3AbNr_3Ainput_3Av(event,"idForm:kopf:bezugNr:input","idForm:kopf:bezugNr:input")'); return false;" /> > {quote} > the code is tanken from 4.0.0.Final, but looks similar in 4.1.0.Final -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 26 16:12:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 26 Mar 2012 16:12:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12093) ResourceServlet can't handle resources outside of specific libraries Message-ID: <346104444.32472.1332792767413.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Luk?? Fry? created RF-12093: ------------------------------- Summary: ResourceServlet can't handle resources outside of specific libraries Key: RF-12093 URL: https://issues.jboss.org/browse/RF-12093 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: core Affects Versions: 4.2.0.Final Reporter: Luk?? Fry? Assignee: Luk?? Fry? Fix For: 4.2.1.CR1 {{ResourceServlet}} is limited to what it can serve to only several specific libraries: * [{{CKEditorLibrary}}|https://github.com/richfaces/core/blob/develop/impl/src/main/java/org/richfaces/webapp/ResourceServlet.java#L194] * [{{StaticResourceLibrary}}|https://github.com/richfaces/core/blob/develop/impl/src/main/java/org/richfaces/webapp/ResourceServlet.java#L213] * [{{RichFacesImageLibrary}}|https://github.com/richfaces/core/blob/develop/impl/src/main/java/org/richfaces/webapp/ResourceServlet.java#L213] ---- We should allow to serve any resource. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 26 16:12:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 26 Mar 2012 16:12:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12093) ResourceServlet can't handle resources outside of specific libraries In-Reply-To: <346104444.32472.1332792767413.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <197597681.32473.1332792767445.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated RF-12093: ---------------------------- Description: {{ResourceServlet}} is limited to what it can serve to only several specific libraries: * [{{CKEditorLibrary}}|https://github.com/richfaces/core/blob/develop/impl/src/main/java/org/richfaces/webapp/ResourceServlet.java#L194] * [{{StaticResourceLibrary}}|https://github.com/richfaces/core/blob/develop/impl/src/main/java/org/richfaces/webapp/ResourceServlet.java#L213] * [{{RichFacesImageLibrary}}|https://github.com/richfaces/core/blob/develop/impl/src/main/java/org/richfaces/webapp/ResourceServlet.java#L213] We should allow to serve any resource. Some limitations may be placed on resources server by ResourceServlet as discussed in RF-11888. was: {{ResourceServlet}} is limited to what it can serve to only several specific libraries: * [{{CKEditorLibrary}}|https://github.com/richfaces/core/blob/develop/impl/src/main/java/org/richfaces/webapp/ResourceServlet.java#L194] * [{{StaticResourceLibrary}}|https://github.com/richfaces/core/blob/develop/impl/src/main/java/org/richfaces/webapp/ResourceServlet.java#L213] * [{{RichFacesImageLibrary}}|https://github.com/richfaces/core/blob/develop/impl/src/main/java/org/richfaces/webapp/ResourceServlet.java#L213] ---- We should allow to serve any resource. > ResourceServlet can't handle resources outside of specific libraries > -------------------------------------------------------------------- > > Key: RF-12093 > URL: https://issues.jboss.org/browse/RF-12093 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 4.2.0.Final > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 4.2.1.CR1 > > > {{ResourceServlet}} is limited to what it can serve to only several specific libraries: > * [{{CKEditorLibrary}}|https://github.com/richfaces/core/blob/develop/impl/src/main/java/org/richfaces/webapp/ResourceServlet.java#L194] > * [{{StaticResourceLibrary}}|https://github.com/richfaces/core/blob/develop/impl/src/main/java/org/richfaces/webapp/ResourceServlet.java#L213] > * [{{RichFacesImageLibrary}}|https://github.com/richfaces/core/blob/develop/impl/src/main/java/org/richfaces/webapp/ResourceServlet.java#L213] > We should allow to serve any resource. > Some limitations may be placed on resources server by ResourceServlet as discussed in RF-11888. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 26 16:52:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 26 Mar 2012 16:52:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12091) rich:dataScroller scrollListener not documented In-Reply-To: <1487113708.31251.1332772548274.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <2027483944.32594.1332795167337.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-12091. -------------------------------- Resolution: Done Added an @Attribute annotated getter for the scrollListener attribute: {code} @Attribute public abstract MethodExpression getScrollListener(); {code} > rich:dataScroller scrollListener not documented > ----------------------------------------------- > > Key: RF-12091 > URL: https://issues.jboss.org/browse/RF-12091 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: 4.2.0.Final > Reporter: Dupont Dupont > Assignee: Brian Leathem > Fix For: 4.2.1.CR1 > > > rich:dataScroller has a scrollListener attribute, but it's not documented (no occurence in component reference or in taglib.xml). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 26 17:13:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 26 Mar 2012 17:13:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-10968) Tree: treeSelectionChangeListener and treeToggleListener do not work In-Reply-To: <35352639.27278.1304411418583.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <419582021.32648.1332796427539.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-10968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-10968. -------------------------------- Resolution: Done Renamed the xml CDK attributes for the tree listeners > Tree: treeSelectionChangeListener and treeToggleListener do not work > -------------------------------------------------------------------- > > Key: RF-10968 > URL: https://issues.jboss.org/browse/RF-10968 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: base functionality , component-tree > Affects Versions: 4.0.0.Final > Environment: RichFaces 4.1.0-SNAPSHOT r.22458 > Metamer 4.1.0-SNAPSHOT r.22459 > Mojarra 2.0.3- > JBoss AS 6.0.0.Final > OpenJDK Runtime Environment 1.6.0_20-b20 @ Linux > Chrome 11.0.696.57 @ Linux i686 > Reporter: Pavol Pitonak > Assignee: Brian Leathem > Fix For: 4.2.1.CR1 > > Attachments: NodesTreeSequenceKeyModelImpl.java, tree.xhtml, TreeBean.java, TreeNodeImpl.java > > > Attributes treeSelectionChangeListener and treeToggleListener in rich:tree do not work. However, attributes selectionChangeListener and toggleListener do work. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Mar 26 18:06:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 26 Mar 2012 18:06:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12021) Compilation of Input UI component logs 2 errors about faces-config.xml In-Reply-To: <518462150.61467.1330674576214.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <824112745.32709.1332799607544.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-12021. -------------------------------- Fix Version/s: (was: 4.2.1.CR1) Resolution: Won't Fix The CDK generates a faces-config.xml using the src faces-config.xml file as a base. The CDK evaluates the xi:include statements, generating a valid faces-config.xml. It's not worth spending the time to dig into the xml parsers validation to suppress this error, given that this file producing the errors is an intermediate file, and not present in the delivered artifact. > Compilation of Input UI component logs 2 errors about faces-config.xml > ---------------------------------------------------------------------- > > Key: RF-12021 > URL: https://issues.jboss.org/browse/RF-12021 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.2.0.Final > Reporter: Marek Novotny > Assignee: Brian Leathem > > Compilation of RF UI Components specifically Input UI has got 2 errors in log - related to bad faces-config.xml on line number 29 and 240. > The following is snippet of log: > {noformat} > [INFO] ------------------------------------------------------------------------ > [INFO] Building RichFaces UI Components: Input UI 4.2.0.Final > [INFO] ------------------------------------------------------------------------ > [INFO] > [INFO] --- maven-enforcer-plugin:1.0-redhat-1:enforce (enforce-java-version) @ richfaces-ui-input-ui --- > [INFO] The requirePluginVersions rule is currently not compatible with Maven3. > [INFO] > [INFO] --- maven-enforcer-plugin:1.0-redhat-1:enforce (enforce-maven-version) @ richfaces-ui-input-ui --- > [INFO] The requirePluginVersions rule is currently not compatible with Maven3. > [INFO] > [INFO] --- maven-cdk-plugin:4.2.0.Final-redhat-1:generate (cdk-generate-sources) @ richfaces-ui-input-ui --- > [Error] faces-config.xml:29:71: cvc-complex-type.2.4.a: Invalid content was found starting with element 'xi:include'. One of '{"http://java.sun.com/xml/ns/javaee":property, "http://java.sun.com/xml/ns/javaee":component-extension}' is expected. > [Error] faces-config.xml:240:71: cvc-complex-type.2.4.a: Invalid content was found starting with element 'xi:include'. One of '{"http://java.sun.com/xml/ns/javaee":property, "http://java.sun.com/xml/ns/javaee":component-extension}' is expected. > {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 27 03:21:49 2012 From: jira-events at lists.jboss.org (Daniel G (JIRA)) Date: Tue, 27 Mar 2012 03:21:49 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11990) client-side validation and ajax calls create maleformed javascript In-Reply-To: <941910750.25122.1329496418429.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <342065594.33135.1332832909061.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679515#comment-12679515 ] Daniel G commented on RF-11990: ------------------------------- Thank you for figuring out the details. I'll check the faces messages from ajax-call-validation maybe this is even better for my components. regards Daniel > client-side validation and ajax calls create maleformed javascript > ------------------------------------------------------------------ > > Key: RF-11990 > URL: https://issues.jboss.org/browse/RF-11990 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-validators > Affects Versions: 4.0.0.Final, 4.1.0.Final > Environment: MyFaces 2.1.5, Hibernate-Validation 4.2.0.Final > Reporter: Daniel G > Assignee: Luk?? Fry? > Priority: Minor > Labels: javascript, myfaces, richfaces, validation > > Using rich:validation and f:ajax together, maleformed JavaScript is generated. > I'm having a composite component, that has to be able to refresh given other components on change, but the JavaScript code generated by: > {quote} > > > > {quote} > is missing a comma between the Chain parameters. > see the red {color:red}'{color} > {quote} > onchange="jsf.util.chain(document.getElementById('idForm:bNr:input'), > event,'jsf.ajax.request(\'idForm:bNr:input\',event,\{render:\'idForm:idToolBar:idSaveButton\',\'javax.faces.behavior.event\':\'change\'\}){color:red}''{color}idForm_3AbNr_3Ainput_3Av(event,"idForm:kopf:bezugNr:input","idForm:kopf:bezugNr:input")'); return false;" /> > {quote} > the code is tanken from 4.0.0.Final, but looks similar in 4.1.0.Final -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 27 03:32:48 2012 From: jira-events at lists.jboss.org (Dupont Dupont (JIRA)) Date: Tue, 27 Mar 2012 03:32:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12091) rich:dataScroller scrollListener not documented In-Reply-To: <1487113708.31251.1332772548274.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1949264797.33160.1332833568771.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679518#comment-12679518 ] Dupont Dupont commented on RF-12091: ------------------------------------ Thanks Brian ! > rich:dataScroller scrollListener not documented > ----------------------------------------------- > > Key: RF-12091 > URL: https://issues.jboss.org/browse/RF-12091 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: 4.2.0.Final > Reporter: Dupont Dupont > Assignee: Brian Leathem > Fix For: 4.2.1.CR1 > > > rich:dataScroller has a scrollListener attribute, but it's not documented (no occurence in component reference or in taglib.xml). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 27 03:42:52 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 27 Mar 2012 03:42:52 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12072) Lost event in push In-Reply-To: <1823827590.22721.1332335688298.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <394140560.33216.1332834172347.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679524#comment-12679524 ] Luk?? Fry? commented on RF-12072: --------------------------------- The proposed solution of queuing requests solves the issue only partially - it significantly decreases probability of losing event, but it still doesn't eliminate it completely. To ensure completeness, you would need to block until a client is subscribed to a topic before you could continue with rendering of the page. ---- Another suggestion is to create new event {{subscribed}}, allowing you to react on successful subscription with specific action - in this case partial page reload. ---- Still we need to make sure this behavior is documented properly. > Lost event in push > ------------------ > > Key: RF-12072 > URL: https://issues.jboss.org/browse/RF-12072 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Reporter: Stian Thorgersen > Assignee: Luk?? Fry? > Fix For: 4.2.1.CR1 > > > Event can be lost if produced while a response is being prepared. I've attached an example where a push event is used to refresh a count whenever an event is fired. It's using Thread.sleep to simulate an event being produced while the response is being prepared. Note, if the sleep just before returning the count is removed it all works fine, and the page is refreshed every 5 seconds, but with the sleep in place the event is lost. > View: > {code} > > > xmlns:f="http://java.sun.com/jsf/core" > xmlns:h="http://java.sun.com/jsf/html" > xmlns:a4j="http://richfaces.org/a4j" > xmlns:rich="http://richfaces.org/rich"> > > > > > > > > > > > > > {code} > Bean: > {code} > package com.example; > import java.io.Serializable; > import java.util.concurrent.atomic.AtomicInteger; > import javax.enterprise.context.SessionScoped; > import javax.inject.Named; > import org.richfaces.application.push.TopicKey; > import org.richfaces.application.push.TopicsContext; > @Named > @SessionScoped > public class MyBean implements Serializable > { > private AtomicInteger count = new AtomicInteger(); > public int getCount() > { > int c = count.get(); > new Thread() > { > public void run() > { > try > { > Thread.sleep(5000); > count.incrementAndGet(); > TopicKey topicKey = new TopicKey("chat"); > TopicsContext topicsContext = TopicsContext.lookup(); > topicsContext.publish(topicKey, ""); > } > catch (Exception e) > { > e.printStackTrace(); > } > }; > }.start(); > > try > { > Thread.sleep(10000); > } > catch (InterruptedException e) > { > } > return c; > } > } > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 27 03:58:47 2012 From: jira-events at lists.jboss.org (Karsten Wutzke (JIRA)) Date: Tue, 27 Mar 2012 03:58:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12094) Provide a feature to rich:dataTable that reflects the default sort order on a column (according to the JPQL statement that produced the list items) Message-ID: <815335129.33287.1332835127644.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Karsten Wutzke created RF-12094: ----------------------------------- Summary: Provide a feature to rich:dataTable that reflects the default sort order on a column (according to the JPQL statement that produced the list items) Key: RF-12094 URL: https://issues.jboss.org/browse/RF-12094 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Karsten Wutzke A rich:dataTable list is usually sorted by one or several columns according to the JPQL or other statement that produced the list. I would be worthwhile to have the rich:dataTable reflect the default ordering state by providing an attribute to rich:column that would set the respective up or down sort arrow instead of the default up-down arrow. By default, e.g. on page reload, if nothing was remembered by the browser, rich:dataTable defaults to the dual up-down arrow for all rich:column's. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 27 04:20:53 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 27 Mar 2012 04:20:53 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12080) rich:hotKey usage clears body onload attribute In-Reply-To: <1411413331.27453.1332488387294.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1864541917.33334.1332836453365.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679533#comment-12679533 ] Luk?? Fry? commented on RF-12080: --------------------------------- Could you please try if {{t:documentBody}} works when you place following script inside the body? {code:Javascript} $(document).ready(function() { document.title = 'xyz'; }); {code} Could you please send the respected source code generated by {{}}? ---- Anyway I think the proper fix is on the Tomahawk's side, since it seems it is doing something wrong, because simply using {{}} don't break by using {{document.ready}}: {code:html} {code} > rich:hotKey usage clears body onload attribute > ---------------------------------------------- > > Key: RF-12080 > URL: https://issues.jboss.org/browse/RF-12080 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component > Affects Versions: 4.2.0.Final > Environment: myfaces 2.1.6, tomahawk 1.1.11 > Reporter: Michael Heinen > Assignee: Luk?? Fry? > Priority: Minor > Labels: myfaces, tomahawk > Fix For: 4.2.1.CR1 > > > I'm happy to see rich:hotKey in richfaces 4.2, I used it already with richfaces 3.3.3. > One thing I noticed now is that the onload attribute of t:documentboy is cleared on clientside as soon as rich:hotKey is used on a page. Maybe caused by jquery usage? > From my pov this should be either fixed or documented in the component guide as well as in the showcase sample. > Workaround is obvious: Instead of onload use document.ready -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 27 04:20:53 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 27 Mar 2012 04:20:53 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12080) rich:hotKey usage clears body onload attribute In-Reply-To: <1411413331.27453.1332488387294.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1786290798.33336.1332836453989.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated RF-12080: ---------------------------- Workaround Description: Use [{{$(document).ready(handler)}}|http://api.jquery.com/ready/] instead of {{}}. Workaround: Workaround Exists > rich:hotKey usage clears body onload attribute > ---------------------------------------------- > > Key: RF-12080 > URL: https://issues.jboss.org/browse/RF-12080 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component > Affects Versions: 4.2.0.Final > Environment: myfaces 2.1.6, tomahawk 1.1.11 > Reporter: Michael Heinen > Assignee: Luk?? Fry? > Priority: Minor > Labels: myfaces, tomahawk > Fix For: 4.2.1.CR1 > > > I'm happy to see rich:hotKey in richfaces 4.2, I used it already with richfaces 3.3.3. > One thing I noticed now is that the onload attribute of t:documentboy is cleared on clientside as soon as rich:hotKey is used on a page. Maybe caused by jquery usage? > From my pov this should be either fixed or documented in the component guide as well as in the showcase sample. > Workaround is obvious: Instead of onload use document.ready -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 27 04:22:48 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 27 Mar 2012 04:22:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12080) rich:hotKey usage clears body onload attribute In-Reply-To: <1411413331.27453.1332488387294.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <988839671.33339.1332836568300.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679533#comment-12679533 ] Luk?? Fry? edited comment on RF-12080 at 3/27/12 4:21 AM: ---------------------------------------------------------- Could you please try if {{t:documentBody}} works when you place following script inside the body? {code:Javascript} $(document).ready(function() { document.title = 'xyz'; }); {code} Could you please send the respected source code generated by {{}}? ---- Anyway I think the proper fix is on the Tomahawk's side, since it seems it is doing something wrong, because simple {{}} don't break by using {{document.ready}}: {code:html} {code} was (Author: lfryc): Could you please try if {{t:documentBody}} works when you place following script inside the body? {code:Javascript} $(document).ready(function() { document.title = 'xyz'; }); {code} Could you please send the respected source code generated by {{}}? ---- Anyway I think the proper fix is on the Tomahawk's side, since it seems it is doing something wrong, because simply using {{}} don't break by using {{document.ready}}: {code:html} {code} > rich:hotKey usage clears body onload attribute > ---------------------------------------------- > > Key: RF-12080 > URL: https://issues.jboss.org/browse/RF-12080 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component > Affects Versions: 4.2.0.Final > Environment: myfaces 2.1.6, tomahawk 1.1.11 > Reporter: Michael Heinen > Assignee: Luk?? Fry? > Priority: Minor > Labels: myfaces, tomahawk, waiting_on_user > > I'm happy to see rich:hotKey in richfaces 4.2, I used it already with richfaces 3.3.3. > One thing I noticed now is that the onload attribute of t:documentboy is cleared on clientside as soon as rich:hotKey is used on a page. Maybe caused by jquery usage? > From my pov this should be either fixed or documented in the component guide as well as in the showcase sample. > Workaround is obvious: Instead of onload use document.ready -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 27 04:22:49 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 27 Mar 2012 04:22:49 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12080) rich:hotKey usage clears body onload attribute In-Reply-To: <1411413331.27453.1332488387294.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <938005110.33343.1332836569487.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated RF-12080: ---------------------------- Fix Version/s: (was: 4.2.1.CR1) > rich:hotKey usage clears body onload attribute > ---------------------------------------------- > > Key: RF-12080 > URL: https://issues.jboss.org/browse/RF-12080 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component > Affects Versions: 4.2.0.Final > Environment: myfaces 2.1.6, tomahawk 1.1.11 > Reporter: Michael Heinen > Assignee: Luk?? Fry? > Priority: Minor > Labels: myfaces, tomahawk, waiting_on_user > > I'm happy to see rich:hotKey in richfaces 4.2, I used it already with richfaces 3.3.3. > One thing I noticed now is that the onload attribute of t:documentboy is cleared on clientside as soon as rich:hotKey is used on a page. Maybe caused by jquery usage? > From my pov this should be either fixed or documented in the component guide as well as in the showcase sample. > Workaround is obvious: Instead of onload use document.ready -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 27 04:22:54 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 27 Mar 2012 04:22:54 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12080) rich:hotKey usage clears body onload attribute In-Reply-To: <1411413331.27453.1332488387294.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <816606518.33346.1332836575206.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679533#comment-12679533 ] Luk?? Fry? edited comment on RF-12080 at 3/27/12 4:22 AM: ---------------------------------------------------------- Could you please try if {{t:documentBody}} works when you place following script inside the body? {code:Javascript} $(document).ready(function() { document.title = 'xyz'; }); {code} Could you please send the respected source code generated by {{}}? ---- Anyway I think the proper fix is on the Tomahawk's side, since it seems it is doing something wrong, because simple {{}} don't break by using {{document.ready}}: {code:html} {code} Both alerts are shown. was (Author: lfryc): Could you please try if {{t:documentBody}} works when you place following script inside the body? {code:Javascript} $(document).ready(function() { document.title = 'xyz'; }); {code} Could you please send the respected source code generated by {{}}? ---- Anyway I think the proper fix is on the Tomahawk's side, since it seems it is doing something wrong, because simple {{}} don't break by using {{document.ready}}: {code:html} {code} > rich:hotKey usage clears body onload attribute > ---------------------------------------------- > > Key: RF-12080 > URL: https://issues.jboss.org/browse/RF-12080 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component > Affects Versions: 4.2.0.Final > Environment: myfaces 2.1.6, tomahawk 1.1.11 > Reporter: Michael Heinen > Assignee: Luk?? Fry? > Priority: Minor > Labels: myfaces, tomahawk, waiting_on_user > > I'm happy to see rich:hotKey in richfaces 4.2, I used it already with richfaces 3.3.3. > One thing I noticed now is that the onload attribute of t:documentboy is cleared on clientside as soon as rich:hotKey is used on a page. Maybe caused by jquery usage? > From my pov this should be either fixed or documented in the component guide as well as in the showcase sample. > Workaround is obvious: Instead of onload use document.ready -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 27 05:28:47 2012 From: jira-events at lists.jboss.org (Stian Thorgersen (JIRA)) Date: Tue, 27 Mar 2012 05:28:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12072) Lost event in push In-Reply-To: <1823827590.22721.1332335688298.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <191541269.33525.1332840527405.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679549#comment-12679549 ] Stian Thorgersen commented on RF-12072: --------------------------------------- {quote} Hey Stian, any chance you could look into fixing the issue the proposed way ^ ? {quote} Are you talking about the workaround or queueing requests? I think the best solution is the subscribed event, as the other solution of queueing requests sounds fairly complex + as you say it doesn't eliminate the problem. > Lost event in push > ------------------ > > Key: RF-12072 > URL: https://issues.jboss.org/browse/RF-12072 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Reporter: Stian Thorgersen > Assignee: Luk?? Fry? > Fix For: 4.2.1.CR1 > > > Event can be lost if produced while a response is being prepared. I've attached an example where a push event is used to refresh a count whenever an event is fired. It's using Thread.sleep to simulate an event being produced while the response is being prepared. Note, if the sleep just before returning the count is removed it all works fine, and the page is refreshed every 5 seconds, but with the sleep in place the event is lost. > View: > {code} > > > xmlns:f="http://java.sun.com/jsf/core" > xmlns:h="http://java.sun.com/jsf/html" > xmlns:a4j="http://richfaces.org/a4j" > xmlns:rich="http://richfaces.org/rich"> > > > > > > > > > > > > > {code} > Bean: > {code} > package com.example; > import java.io.Serializable; > import java.util.concurrent.atomic.AtomicInteger; > import javax.enterprise.context.SessionScoped; > import javax.inject.Named; > import org.richfaces.application.push.TopicKey; > import org.richfaces.application.push.TopicsContext; > @Named > @SessionScoped > public class MyBean implements Serializable > { > private AtomicInteger count = new AtomicInteger(); > public int getCount() > { > int c = count.get(); > new Thread() > { > public void run() > { > try > { > Thread.sleep(5000); > count.incrementAndGet(); > TopicKey topicKey = new TopicKey("chat"); > TopicsContext topicsContext = TopicsContext.lookup(); > topicsContext.publish(topicKey, ""); > } > catch (Exception e) > { > e.printStackTrace(); > } > }; > }.start(); > > try > { > Thread.sleep(10000); > } > catch (InterruptedException e) > { > } > return c; > } > } > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 27 06:02:48 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 27 Mar 2012 06:02:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12095) Incorrect behavior of two pushes on the page Message-ID: <2084709749.33571.1332842568105.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Luk?? Fry? created RF-12095: ------------------------------- Summary: Incorrect behavior of two pushes on the page Key: RF-12095 URL: https://issues.jboss.org/browse/RF-12095 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-push/poll Affects Versions: 4.2.0.Final Reporter: Luk?? Fry? When you have 2 pushes on the page and one is conditionally rendered, rerendering it causes unsubscribing of second push: {code:xml}




    #{richBean.date}

    #{richBean.date}     {code} {code:java} @ManagedBean public class RichBean { public Date getDate() { return new Date(); } public void push() throws MessageException { TopicKey topicKey = new TopicKey("sampleAddress"); TopicsContext topicsContext = TopicsContext.lookup(); topicsContext.publish(topicKey, new Date().toString()); System.out.println("push event"); } public void push2() throws MessageException { TopicKey topicKey = new TopicKey("sampleAddress2"); TopicsContext topicsContext = TopicsContext.lookup(); topicsContext.publish(topicKey, new Date().toString()); System.out.println("push event 2"); } } {code} Steps to reproduce: 1. open the page 2. you can see "subscribed" and "subscribed2" alert messages 3. both, Push! and Push 2! buttons reloads respective dates 4. click on checkbox and on the right of Push! button EXPECTED: only Push! should stop to work ACTUAL: both Push! and Push 2! stops to work -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 27 06:08:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 27 Mar 2012 06:08:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12096) Push: there is delay between repeated subscribtion Message-ID: <298994236.33589.1332842927828.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Luk?? Fry? created RF-12096: ------------------------------- Summary: Push: there is delay between repeated subscribtion Key: RF-12096 URL: https://issues.jboss.org/browse/RF-12096 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-push/poll Affects Versions: 4.2.0.Final Reporter: Luk?? Fry? When you have conditionally rendered {{a4j:push}} component and you disable it, then it stops to receive push events. Once you enable it, there is delay before it will start to receive events again. Sample code for reproduction: {code:xml}




    #{richBean.date}
    {code} {code:java} package demo; import java.util.Date; import javax.faces.bean.ManagedBean; import org.richfaces.application.push.MessageException; import org.richfaces.application.push.TopicKey; import org.richfaces.application.push.TopicsContext; @ManagedBean public class RichBean { public Date getDate() { return new Date(); } public void push() throws MessageException { TopicKey topicKey = new TopicKey("sampleAddress"); TopicsContext topicsContext = TopicsContext.lookup(); topicsContext.publish(topicKey, new Date().toString()); System.out.println("push event"); } } {code} Steps to reproduce: 1. open the sample page (the "subscribed" message appears) 2. click on Push! button (the date is changed) 3. check the checkbox 4. click on Push! button (the date is not changed anymore) 5. uncheck the checkbox (the "subscribed" message appears again) 6. click on Push! EXPECTED: the date should be changed ACTUAL: the date is not changed If you will wait for some seconds, the Push! button will cause change of the date, but in this delay, client can lose data updates (since "subscribed" event does not show that the client is starting to receive data). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 27 06:10:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 27 Mar 2012 06:10:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12095) Incorrect behavior of two pushes on the page In-Reply-To: <2084709749.33571.1332842568105.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <715274205.33591.1332843047742.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679555#comment-12679555 ] Luk?? Fry? commented on RF-12095: --------------------------------- There is delay in between repeated subscription after disabling and enabling push: RF-12096 > Incorrect behavior of two pushes on the page > -------------------------------------------- > > Key: RF-12095 > URL: https://issues.jboss.org/browse/RF-12095 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Affects Versions: 4.2.0.Final > Reporter: Luk?? Fry? > > When you have 2 pushes on the page and one is conditionally rendered, rerendering it causes unsubscribing of second push: > {code:xml} > "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> > xmlns:f="http://java.sun.com/jsf/core" xmlns:a4j="http://richfaces.org/a4j"> > > > > > >



    > > > > > > > > > > > > > > > > > >
    > > > #{richBean.date} > > >
    > > > > > >
    > > > #{richBean.date} > >     >     >     > > {code} > {code:java} > @ManagedBean > public class RichBean { > public Date getDate() { > return new Date(); > } > public void push() throws MessageException { > TopicKey topicKey = new TopicKey("sampleAddress"); > TopicsContext topicsContext = TopicsContext.lookup(); > topicsContext.publish(topicKey, new Date().toString()); > System.out.println("push event"); > } > > public void push2() throws MessageException { > TopicKey topicKey = new TopicKey("sampleAddress2"); > TopicsContext topicsContext = TopicsContext.lookup(); > topicsContext.publish(topicKey, new Date().toString()); > System.out.println("push event 2"); > } > } > {code} > Steps to reproduce: > 1. open the page > 2. you can see "subscribed" and "subscribed2" alert messages > 3. both, Push! and Push 2! buttons reloads respective dates > 4. click on checkbox and on the right of Push! button > EXPECTED: only Push! should stop to work > ACTUAL: both Push! and Push 2! stops to work -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 27 06:15:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 27 Mar 2012 06:15:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12095) Incorrect behavior of two pushes on the page In-Reply-To: <2084709749.33571.1332842568105.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1381895199.33600.1332843347478.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679558#comment-12679558 ] Luk?? Fry? commented on RF-12095: --------------------------------- The second push starts to work again if you will wait for some delay - this issue is discribed here: RF-12095 > Incorrect behavior of two pushes on the page > -------------------------------------------- > > Key: RF-12095 > URL: https://issues.jboss.org/browse/RF-12095 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Affects Versions: 4.2.0.Final > Reporter: Luk?? Fry? > > When you have 2 pushes on the page and one is conditionally rendered, rerendering it causes unsubscribing of second push: > {code:xml} > "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> > xmlns:f="http://java.sun.com/jsf/core" xmlns:a4j="http://richfaces.org/a4j"> > > > > > >



    > > > > > > > > > > > > > > > > > >
    > > > #{richBean.date} > > >
    > > > > > >
    > > > #{richBean.date} > >     >     >     > > {code} > {code:java} > @ManagedBean > public class RichBean { > public Date getDate() { > return new Date(); > } > public void push() throws MessageException { > TopicKey topicKey = new TopicKey("sampleAddress"); > TopicsContext topicsContext = TopicsContext.lookup(); > topicsContext.publish(topicKey, new Date().toString()); > System.out.println("push event"); > } > > public void push2() throws MessageException { > TopicKey topicKey = new TopicKey("sampleAddress2"); > TopicsContext topicsContext = TopicsContext.lookup(); > topicsContext.publish(topicKey, new Date().toString()); > System.out.println("push event 2"); > } > } > {code} > Steps to reproduce: > 1. open the page > 2. you can see "subscribed" and "subscribed2" alert messages > 3. both, Push! and Push 2! buttons reloads respective dates > 4. click on checkbox and on the right of Push! button > EXPECTED: only Push! should stop to work > ACTUAL: both Push! and Push 2! stops to work -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 27 06:15:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 27 Mar 2012 06:15:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12095) Incorrect behavior of two pushes on the page In-Reply-To: <2084709749.33571.1332842568105.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1150727644.33602.1332843347639.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679558#comment-12679558 ] Luk?? Fry? edited comment on RF-12095 at 3/27/12 6:15 AM: ---------------------------------------------------------- The second push starts to work again if you will wait for some delay - this issue is discribed here: RF-12096 was (Author: lfryc): The second push starts to work again if you will wait for some delay - this issue is discribed here: RF-12095 > Incorrect behavior of two pushes on the page > -------------------------------------------- > > Key: RF-12095 > URL: https://issues.jboss.org/browse/RF-12095 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Affects Versions: 4.2.0.Final > Reporter: Luk?? Fry? > > When you have 2 pushes on the page and one is conditionally rendered, rerendering it causes unsubscribing of second push: > {code:xml} > "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> > xmlns:f="http://java.sun.com/jsf/core" xmlns:a4j="http://richfaces.org/a4j"> > > > > > >



    > > > > > > > > > > > > > > > > > >
    > > > #{richBean.date} > > >
    > > > > > >
    > > > #{richBean.date} > >     >     >     > > {code} > {code:java} > @ManagedBean > public class RichBean { > public Date getDate() { > return new Date(); > } > public void push() throws MessageException { > TopicKey topicKey = new TopicKey("sampleAddress"); > TopicsContext topicsContext = TopicsContext.lookup(); > topicsContext.publish(topicKey, new Date().toString()); > System.out.println("push event"); > } > > public void push2() throws MessageException { > TopicKey topicKey = new TopicKey("sampleAddress2"); > TopicsContext topicsContext = TopicsContext.lookup(); > topicsContext.publish(topicKey, new Date().toString()); > System.out.println("push event 2"); > } > } > {code} > Steps to reproduce: > 1. open the page > 2. you can see "subscribed" and "subscribed2" alert messages > 3. both, Push! and Push 2! buttons reloads respective dates > 4. click on checkbox and on the right of Push! button > EXPECTED: only Push! should stop to work > ACTUAL: both Push! and Push 2! stops to work -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 27 06:17:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 27 Mar 2012 06:17:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12095) Incorrect behavior of two pushes on the page In-Reply-To: <2084709749.33571.1332842568105.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1761929447.33605.1332843467993.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved RF-12095. ----------------------------- Assignee: Luk?? Fry? Resolution: Duplicate Issue > Incorrect behavior of two pushes on the page > -------------------------------------------- > > Key: RF-12095 > URL: https://issues.jboss.org/browse/RF-12095 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Affects Versions: 4.2.0.Final > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > > When you have 2 pushes on the page and one is conditionally rendered, rerendering it causes unsubscribing of second push: > {code:xml} > "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> > xmlns:f="http://java.sun.com/jsf/core" xmlns:a4j="http://richfaces.org/a4j"> > > > > > >



    > > > > > > > > > > > > > > > > > >
    > > > #{richBean.date} > > >
    > > > > > >
    > > > #{richBean.date} > >     >     >     > > {code} > {code:java} > @ManagedBean > public class RichBean { > public Date getDate() { > return new Date(); > } > public void push() throws MessageException { > TopicKey topicKey = new TopicKey("sampleAddress"); > TopicsContext topicsContext = TopicsContext.lookup(); > topicsContext.publish(topicKey, new Date().toString()); > System.out.println("push event"); > } > > public void push2() throws MessageException { > TopicKey topicKey = new TopicKey("sampleAddress2"); > TopicsContext topicsContext = TopicsContext.lookup(); > topicsContext.publish(topicKey, new Date().toString()); > System.out.println("push event 2"); > } > } > {code} > Steps to reproduce: > 1. open the page > 2. you can see "subscribed" and "subscribed2" alert messages > 3. both, Push! and Push 2! buttons reloads respective dates > 4. click on checkbox and on the right of Push! button > EXPECTED: only Push! should stop to work > ACTUAL: both Push! and Push 2! stops to work -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 27 06:19:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 27 Mar 2012 06:19:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12072) Add onsubscribed event (was: Lost event in push) In-Reply-To: <1823827590.22721.1332335688298.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1001707987.33607.1332843587834.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated RF-12072: ---------------------------- Summary: Add onsubscribed event (was: Lost event in push) (was: Lost event in push) Affects: Documentation (Ref Guide, User Guide, etc.) > Add onsubscribed event (was: Lost event in push) > ------------------------------------------------ > > Key: RF-12072 > URL: https://issues.jboss.org/browse/RF-12072 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Reporter: Stian Thorgersen > Assignee: Luk?? Fry? > Fix For: 4.2.1.CR1 > > > Event can be lost if produced while a response is being prepared. I've attached an example where a push event is used to refresh a count whenever an event is fired. It's using Thread.sleep to simulate an event being produced while the response is being prepared. Note, if the sleep just before returning the count is removed it all works fine, and the page is refreshed every 5 seconds, but with the sleep in place the event is lost. > View: > {code} > > > xmlns:f="http://java.sun.com/jsf/core" > xmlns:h="http://java.sun.com/jsf/html" > xmlns:a4j="http://richfaces.org/a4j" > xmlns:rich="http://richfaces.org/rich"> > > > > > > > > > > > > > {code} > Bean: > {code} > package com.example; > import java.io.Serializable; > import java.util.concurrent.atomic.AtomicInteger; > import javax.enterprise.context.SessionScoped; > import javax.inject.Named; > import org.richfaces.application.push.TopicKey; > import org.richfaces.application.push.TopicsContext; > @Named > @SessionScoped > public class MyBean implements Serializable > { > private AtomicInteger count = new AtomicInteger(); > public int getCount() > { > int c = count.get(); > new Thread() > { > public void run() > { > try > { > Thread.sleep(5000); > count.incrementAndGet(); > TopicKey topicKey = new TopicKey("chat"); > TopicsContext topicsContext = TopicsContext.lookup(); > topicsContext.publish(topicKey, ""); > } > catch (Exception e) > { > e.printStackTrace(); > } > }; > }.start(); > > try > { > Thread.sleep(10000); > } > catch (InterruptedException e) > { > } > return c; > } > } > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 27 06:23:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 27 Mar 2012 06:23:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12072) Push: add onsubscribed event (was: Lost event in push) In-Reply-To: <1823827590.22721.1332335688298.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <612515439.33612.1332843827395.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated RF-12072: ---------------------------- Summary: Push: add onsubscribed event (was: Lost event in push) (was: Add onsubscribed event (was: Lost event in push)) > Push: add onsubscribed event (was: Lost event in push) > ------------------------------------------------------ > > Key: RF-12072 > URL: https://issues.jboss.org/browse/RF-12072 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Reporter: Stian Thorgersen > Assignee: Luk?? Fry? > Fix For: 4.2.1.CR1 > > > Event can be lost if produced while a response is being prepared. I've attached an example where a push event is used to refresh a count whenever an event is fired. It's using Thread.sleep to simulate an event being produced while the response is being prepared. Note, if the sleep just before returning the count is removed it all works fine, and the page is refreshed every 5 seconds, but with the sleep in place the event is lost. > View: > {code} > > > xmlns:f="http://java.sun.com/jsf/core" > xmlns:h="http://java.sun.com/jsf/html" > xmlns:a4j="http://richfaces.org/a4j" > xmlns:rich="http://richfaces.org/rich"> > > > > > > > > > > > > > {code} > Bean: > {code} > package com.example; > import java.io.Serializable; > import java.util.concurrent.atomic.AtomicInteger; > import javax.enterprise.context.SessionScoped; > import javax.inject.Named; > import org.richfaces.application.push.TopicKey; > import org.richfaces.application.push.TopicsContext; > @Named > @SessionScoped > public class MyBean implements Serializable > { > private AtomicInteger count = new AtomicInteger(); > public int getCount() > { > int c = count.get(); > new Thread() > { > public void run() > { > try > { > Thread.sleep(5000); > count.incrementAndGet(); > TopicKey topicKey = new TopicKey("chat"); > TopicsContext topicsContext = TopicsContext.lookup(); > topicsContext.publish(topicKey, ""); > } > catch (Exception e) > { > e.printStackTrace(); > } > }; > }.start(); > > try > { > Thread.sleep(10000); > } > catch (InterruptedException e) > { > } > return c; > } > } > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 27 06:25:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 27 Mar 2012 06:25:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12072) Push: add onsubscribed event (was: Lost event in push) In-Reply-To: <1823827590.22721.1332335688298.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1137216446.33616.1332843947522.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679559#comment-12679559 ] Luk?? Fry? commented on RF-12072: --------------------------------- Verified that addition of {{subscribed}} event fixes the issue: {code:xml} {code} > Push: add onsubscribed event (was: Lost event in push) > ------------------------------------------------------ > > Key: RF-12072 > URL: https://issues.jboss.org/browse/RF-12072 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Reporter: Stian Thorgersen > Assignee: Luk?? Fry? > Fix For: 4.2.1.CR1 > > > Event can be lost if produced while a response is being prepared. I've attached an example where a push event is used to refresh a count whenever an event is fired. It's using Thread.sleep to simulate an event being produced while the response is being prepared. Note, if the sleep just before returning the count is removed it all works fine, and the page is refreshed every 5 seconds, but with the sleep in place the event is lost. > View: > {code} > > > xmlns:f="http://java.sun.com/jsf/core" > xmlns:h="http://java.sun.com/jsf/html" > xmlns:a4j="http://richfaces.org/a4j" > xmlns:rich="http://richfaces.org/rich"> > > > > > > > > > > > > > {code} > Bean: > {code} > package com.example; > import java.io.Serializable; > import java.util.concurrent.atomic.AtomicInteger; > import javax.enterprise.context.SessionScoped; > import javax.inject.Named; > import org.richfaces.application.push.TopicKey; > import org.richfaces.application.push.TopicsContext; > @Named > @SessionScoped > public class MyBean implements Serializable > { > private AtomicInteger count = new AtomicInteger(); > public int getCount() > { > int c = count.get(); > new Thread() > { > public void run() > { > try > { > Thread.sleep(5000); > count.incrementAndGet(); > TopicKey topicKey = new TopicKey("chat"); > TopicsContext topicsContext = TopicsContext.lookup(); > topicsContext.publish(topicKey, ""); > } > catch (Exception e) > { > e.printStackTrace(); > } > }; > }.start(); > > try > { > Thread.sleep(10000); > } > catch (InterruptedException e) > { > } > return c; > } > } > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 27 06:27:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 27 Mar 2012 06:27:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12072) Push: add onsubscribed event (was: Lost event in push) In-Reply-To: <1823827590.22721.1332335688298.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1545645043.33621.1332844067371.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679560#comment-12679560 ] Luk?? Fry? commented on RF-12072: --------------------------------- Stian, I was talking about queuing mechanism, but we have decided to rather support {{subscribed}} event. Thanks for cooperating on this issue. > Push: add onsubscribed event (was: Lost event in push) > ------------------------------------------------------ > > Key: RF-12072 > URL: https://issues.jboss.org/browse/RF-12072 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Reporter: Stian Thorgersen > Assignee: Luk?? Fry? > Fix For: 4.2.1.CR1 > > > Event can be lost if produced while a response is being prepared. I've attached an example where a push event is used to refresh a count whenever an event is fired. It's using Thread.sleep to simulate an event being produced while the response is being prepared. Note, if the sleep just before returning the count is removed it all works fine, and the page is refreshed every 5 seconds, but with the sleep in place the event is lost. > View: > {code} > > > xmlns:f="http://java.sun.com/jsf/core" > xmlns:h="http://java.sun.com/jsf/html" > xmlns:a4j="http://richfaces.org/a4j" > xmlns:rich="http://richfaces.org/rich"> > > > > > > > > > > > > > {code} > Bean: > {code} > package com.example; > import java.io.Serializable; > import java.util.concurrent.atomic.AtomicInteger; > import javax.enterprise.context.SessionScoped; > import javax.inject.Named; > import org.richfaces.application.push.TopicKey; > import org.richfaces.application.push.TopicsContext; > @Named > @SessionScoped > public class MyBean implements Serializable > { > private AtomicInteger count = new AtomicInteger(); > public int getCount() > { > int c = count.get(); > new Thread() > { > public void run() > { > try > { > Thread.sleep(5000); > count.incrementAndGet(); > TopicKey topicKey = new TopicKey("chat"); > TopicsContext topicsContext = TopicsContext.lookup(); > topicsContext.publish(topicKey, ""); > } > catch (Exception e) > { > e.printStackTrace(); > } > }; > }.start(); > > try > { > Thread.sleep(10000); > } > catch (InterruptedException e) > { > } > return c; > } > } > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 27 06:27:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 27 Mar 2012 06:27:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12072) Push: add onsubscribed event (was: Lost event in push) In-Reply-To: <1823827590.22721.1332335688298.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1076656421.33624.1332844067480.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved RF-12072. ----------------------------- Resolution: Done > Push: add onsubscribed event (was: Lost event in push) > ------------------------------------------------------ > > Key: RF-12072 > URL: https://issues.jboss.org/browse/RF-12072 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Reporter: Stian Thorgersen > Assignee: Luk?? Fry? > Fix For: 4.2.1.CR1 > > > Event can be lost if produced while a response is being prepared. I've attached an example where a push event is used to refresh a count whenever an event is fired. It's using Thread.sleep to simulate an event being produced while the response is being prepared. Note, if the sleep just before returning the count is removed it all works fine, and the page is refreshed every 5 seconds, but with the sleep in place the event is lost. > View: > {code} > > > xmlns:f="http://java.sun.com/jsf/core" > xmlns:h="http://java.sun.com/jsf/html" > xmlns:a4j="http://richfaces.org/a4j" > xmlns:rich="http://richfaces.org/rich"> > > > > > > > > > > > > > {code} > Bean: > {code} > package com.example; > import java.io.Serializable; > import java.util.concurrent.atomic.AtomicInteger; > import javax.enterprise.context.SessionScoped; > import javax.inject.Named; > import org.richfaces.application.push.TopicKey; > import org.richfaces.application.push.TopicsContext; > @Named > @SessionScoped > public class MyBean implements Serializable > { > private AtomicInteger count = new AtomicInteger(); > public int getCount() > { > int c = count.get(); > new Thread() > { > public void run() > { > try > { > Thread.sleep(5000); > count.incrementAndGet(); > TopicKey topicKey = new TopicKey("chat"); > TopicsContext topicsContext = TopicsContext.lookup(); > topicsContext.publish(topicKey, ""); > } > catch (Exception e) > { > e.printStackTrace(); > } > }; > }.start(); > > try > { > Thread.sleep(10000); > } > catch (InterruptedException e) > { > } > return c; > } > } > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 27 06:27:47 2012 From: jira-events at lists.jboss.org (Stephan Meisinger (JIRA)) Date: Tue, 27 Mar 2012 06:27:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12097) Richfaces 4.2.0 invalid css entry for *.rf-insl-tt Message-ID: <771471005.33626.1332844067523.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Stephan Meisinger created RF-12097: -------------------------------------- Summary: Richfaces 4.2.0 invalid css entry for *.rf-insl-tt Key: RF-12097 URL: https://issues.jboss.org/browse/RF-12097 Project: RichFaces Issue Type: Bug Components: skinning Affects Versions: 4.2.0.Final Environment: Tomcat 6.0.35 Richfaces 4.2.0 Windows 7 Reporter: Stephan Meisinger a invalid css syntax for *.rf-insl-tt for PackedCompressed/DEFAULT/packed/packed.css *.rf-insl-tt{position:absolute;display:none;padding:2px;border:1px solid "#E5973E ";background-color:#FAE6B0;} should be *.rf-insl-tt{position:absolute;display:none;padding:2px;border:1px solid #E5973E;background-color:#FAE6B0;} see http://www.w3.org/TR/CSS1/#border and http://www.w3.org/TR/CSS1/#color-units -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 27 07:03:49 2012 From: jira-events at lists.jboss.org (Stefan Risto (JIRA)) Date: Tue, 27 Mar 2012 07:03:49 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-6026) PickList doesn't accept comma in string value of SelectItem In-Reply-To: <26556146.1233700724331.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <147651777.33687.1332846229142.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-6026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679565#comment-12679565 ] Stefan Risto commented on RF-6026: ---------------------------------- The problem still exists in RF 4.2. I use a converter that produces a String containing a comma. But the java script code does not escape the comma in any way, so my converter fails, because it gets two selections where it expects one, e.g. "You,me" is the selected value, but the converter is caled with "You" and a second time with "me". > PickList doesn't accept comma in string value of SelectItem > ----------------------------------------------------------- > > Key: RF-6026 > URL: https://issues.jboss.org/browse/RF-6026 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 3.3.0 > Environment: WebLogic 10, JSF 1.2, RichFaces 3.3.0, Hibernate JPA, Facelets 1.1.14 > Reporter: Andrzej Haczewski > Fix For: 3.Future > > > When you use a List where SelectItems are created like this: > new SelectItem("SOME STRING,CONTAINING COMMA", "A nice string to show in list") > as a PickList , and use List as PickList value, then PickList doesn't validate when you add that item to target list. > The reason is that UISelectMany is trying to validate values "SOME STRINGS" and "CONTAINING COMMA" with available items. > The exact point is the UISelectMany.matchValue() method, which returns false on validation of that PickList. > Sample code: > --- BackingBean.java > class BackingBean { > private List picklistItems; > private List result; > public BackingBean() { > picklistItems = new ArrayList(); > picklistItems.add(new SelectItem("SAMPLE,EXAMPLE", "Sample example")); > } > // then comes getters and setters for picklistItems and result > } > --- PickList.xhtml > > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 27 07:23:48 2012 From: jira-events at lists.jboss.org (Stefan Risto (JIRA)) Date: Tue, 27 Mar 2012 07:23:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12098) PickList doesn't accept comma in string value Message-ID: <1104299453.33800.1332847428203.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Stefan Risto created RF-12098: --------------------------------- Summary: PickList doesn't accept comma in string value Key: RF-12098 URL: https://issues.jboss.org/browse/RF-12098 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-selects Affects Versions: 4.2.0.Final Reporter: Stefan Risto The rich:pickList Component does not handle values containing commas. I used a converter and in the getAsString - Method a String containing a comma was returned, such as "You,Me". After selecting this value in the pick list the converters getAsObject method is called twice, once for "You" and once for "Me". I would expect to get the same value in getAsObject as the converters getAsString returned. Maybe the comma should be escaped by the component and/or the javascript code. This Bug seems to be related to RF-6766, but that bug is not targeted for RF 4.X -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 27 07:23:49 2012 From: jira-events at lists.jboss.org (Stefan Risto (JIRA)) Date: Tue, 27 Mar 2012 07:23:49 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12098) PickList doesn't accept comma in string value In-Reply-To: <1104299453.33800.1332847428203.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1787402807.33819.1332847429549.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Risto updated RF-12098: ------------------------------ Description: The rich:pickList Component does not handle values containing commas. I used a converter and in the getAsString - Method a String containing a comma was returned, such as "You,Me". After selecting this value in the pick list the converters getAsObject method is called twice, once for "You" and once for "Me". I would expect to get the same value in getAsObject as the converters getAsString returned. Maybe the comma should be escaped by the component and/or the javascript code. This Bug seems to be related to RF-6026, but that bug is not targeted for RF 4.X was: The rich:pickList Component does not handle values containing commas. I used a converter and in the getAsString - Method a String containing a comma was returned, such as "You,Me". After selecting this value in the pick list the converters getAsObject method is called twice, once for "You" and once for "Me". I would expect to get the same value in getAsObject as the converters getAsString returned. Maybe the comma should be escaped by the component and/or the javascript code. This Bug seems to be related to RF-6766, but that bug is not targeted for RF 4.X > PickList doesn't accept comma in string value > --------------------------------------------- > > Key: RF-12098 > URL: https://issues.jboss.org/browse/RF-12098 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 4.2.0.Final > Reporter: Stefan Risto > > The rich:pickList Component does not handle values containing commas. > I used a converter and in the getAsString - Method a String containing a comma was returned, such as "You,Me". After selecting this value in the pick list the converters getAsObject method is called twice, once for "You" and once for "Me". > I would expect to get the same value in getAsObject as the converters getAsString returned. Maybe the comma should be escaped by the component and/or the javascript code. > This Bug seems to be related to RF-6026, but that bug is not targeted for RF 4.X -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 27 07:45:49 2012 From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA)) Date: Tue, 27 Mar 2012 07:45:49 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12084) Richfaces 4.2 when inside dont work and causes 'identifier resolved to null' In-Reply-To: <1382382061.29574.1332701569056.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <605104238.34011.1332848749038.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavol Pitonak reassigned RF-12084: ---------------------------------- Assignee: J?n Jamrich (was: Pavol Pitonak) > Richfaces 4.2 when inside dont work and causes 'identifier resolved to null' > ----------------------------------------------------------------------------------------------------- > > Key: RF-12084 > URL: https://issues.jboss.org/browse/RF-12084 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.2.0.Final > Environment: Windows Vista, Firefox 11, Richfaces 4.2 Final, Mojarra 2.1.7, Tomcat 7.0.26 > Reporter: Ivan Costa > Assignee: J?n Jamrich > Labels: richfaces > > a4j:commandLink or a4j:ajax tags inside ui:fragment causes 'identifier resolved to null', > but h:commandLink + f:ajax (both from Mojarra) works perfectly fine! > The problem is described here > https://community.jboss.org/message/723859 > and here: > https://community.jboss.org/thread/196867 > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 27 08:08:48 2012 From: jira-events at lists.jboss.org (Jan Papousek (JIRA)) Date: Tue, 27 Mar 2012 08:08:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12083) Components: Output UI module doesn't pass unit tests (MenuItemRendererTest and DropDownMenuRendererTest) In-Reply-To: <356683327.28101.1332505788416.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1213706763.34116.1332850128203.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Papousek closed RF-12083. ----------------------------- > Components: Output UI module doesn't pass unit tests (MenuItemRendererTest and DropDownMenuRendererTest) > -------------------------------------------------------------------------------------------------------- > > Key: RF-12083 > URL: https://issues.jboss.org/browse/RF-12083 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.2.1.CR1 > Reporter: Jan Papousek > Assignee: Brian Leathem > Priority: Critical > Fix For: 4.2.1.CR1 > > > {code} > ------------------------------------------------------------------------------- > Test set: org.richfaces.renderkit.html.MenuItemRendererTest > ------------------------------------------------------------------------------- > Tests run: 6, Failures: 3, Errors: 0, Skipped: 1, Time elapsed: 3.172 sec <<< FAILURE! > testDoEncodeServerMode(org.richfaces.renderkit.html.MenuItemRendererTest) Time elapsed: 0.566 sec <<< FAILURE! > java.lang.AssertionError: XML was not similar:org.custommonkey.xmlunit.Diff > [different] Expected element tag name 'div' but was 'span' - comparing at /div[1]/div[1] to at /div[1]/span[1] >
    > > > > > > Test > > >
    > at org.junit.Assert.fail(Assert.java:91) > at org.junit.Assert.assertTrue(Assert.java:43) > at org.richfaces.renderkit.html.RendererTestBase.checkXmlStructure(RendererTestBase.java:93) > at org.richfaces.renderkit.html.RendererTestBase.doTest(RendererTestBase.java:81) > at org.richfaces.renderkit.html.RendererTestBase.doTest(RendererTestBase.java:73) > at org.richfaces.renderkit.html.MenuItemRendererTest.testDoEncodeServerMode(MenuItemRendererTest.java:51) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) > at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31) > at org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) > at org.junit.runners.ParentRunner.run(ParentRunner.java:236) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:234) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:133) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:114) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:188) > at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:166) > at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:86) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:101) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74) > testDoEncodeAjaxMode(org.richfaces.renderkit.html.MenuItemRendererTest) Time elapsed: 0.613 sec <<< FAILURE! > java.lang.AssertionError: XML was not similar:org.custommonkey.xmlunit.Diff > [different] Expected element tag name 'div' but was 'span' - comparing at /div[1]/div[1] to at /div[1]/span[1] >
    > > > > > > Test > > >
    > at org.junit.Assert.fail(Assert.java:91) > at org.junit.Assert.assertTrue(Assert.java:43) > at org.richfaces.renderkit.html.RendererTestBase.checkXmlStructure(RendererTestBase.java:93) > at org.richfaces.renderkit.html.RendererTestBase.doTest(RendererTestBase.java:81) > at org.richfaces.renderkit.html.RendererTestBase.doTest(RendererTestBase.java:73) > at org.richfaces.renderkit.html.MenuItemRendererTest.testDoEncodeAjaxMode(MenuItemRendererTest.java:71) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) > at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31) > at org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) > at org.junit.runners.ParentRunner.run(ParentRunner.java:236) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:234) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:133) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:114) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:188) > at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:166) > at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:86) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:101) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74) > testDoEncodeClientMode(org.richfaces.renderkit.html.MenuItemRendererTest) Time elapsed: 0.724 sec <<< FAILURE! > java.lang.AssertionError: XML was not similar:org.custommonkey.xmlunit.Diff > [different] Expected element tag name 'div' but was 'span' - comparing at /div[1]/div[1] to at /div[1]/span[1] >
    > > > > > > Test > > >
    > at org.junit.Assert.fail(Assert.java:91) > at org.junit.Assert.assertTrue(Assert.java:43) > at org.richfaces.renderkit.html.RendererTestBase.checkXmlStructure(RendererTestBase.java:93) > at org.richfaces.renderkit.html.RendererTestBase.doTest(RendererTestBase.java:81) > at org.richfaces.renderkit.html.RendererTestBase.doTest(RendererTestBase.java:73) > at org.richfaces.renderkit.html.MenuItemRendererTest.testDoEncodeClientMode(MenuItemRendererTest.java:88) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) > at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31) > at org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) > at org.junit.runners.ParentRunner.run(ParentRunner.java:236) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:234) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:133) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:114) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:188) > at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:166) > at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:86) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:101) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74) > {code} > {code} > ------------------------------------------------------------------------------- > Test set: org.richfaces.renderkit.html.DropDownMenuRendererTest > ------------------------------------------------------------------------------- > Tests run: 4, Failures: 2, Errors: 0, Skipped: 1, Time elapsed: 2.206 sec <<< FAILURE! > testDoEncodeServerMode(org.richfaces.renderkit.html.DropDownMenuRendererTest) Time elapsed: 0.729 sec <<< FAILURE! > java.lang.AssertionError: XML was not similar:org.custommonkey.xmlunit.Diff > [different] Expected element tag name 'div' but was 'span' - comparing at /div[1]/div[2]/div[1]/div[1]/div[1]/div[1] to at /div[1]/div[2]/div[1]/div[1]/div[1]/span[1] >
    >
    > > File >
    >
    > >
    > >
    > at org.junit.Assert.fail(Assert.java:91) > at org.junit.Assert.assertTrue(Assert.java:43) > at org.richfaces.renderkit.html.RendererTestBase.checkXmlStructure(RendererTestBase.java:93) > at org.richfaces.renderkit.html.RendererTestBase.doTest(RendererTestBase.java:81) > at org.richfaces.renderkit.html.RendererTestBase.doTest(RendererTestBase.java:73) > at org.richfaces.renderkit.html.DropDownMenuRendererTest.testDoEncodeServerMode(DropDownMenuRendererTest.java:51) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) > at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31) > at org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) > at org.junit.runners.ParentRunner.run(ParentRunner.java:236) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:234) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:133) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:114) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:188) > at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:166) > at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:86) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:101) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74) > testDoEncodeAjaxMode(org.richfaces.renderkit.html.DropDownMenuRendererTest) Time elapsed: 0.677 sec <<< FAILURE! > java.lang.AssertionError: XML was not similar:org.custommonkey.xmlunit.Diff > [different] Expected element tag name 'div' but was 'span' - comparing at /div[1]/div[2]/div[1]/div[1]/div[1]/div[1] to at /div[1]/div[2]/div[1]/div[1]/div[1]/span[1] >
    >
    > > File >
    >
    > >
    > >
    > at org.junit.Assert.fail(Assert.java:91) > at org.junit.Assert.assertTrue(Assert.java:43) > at org.richfaces.renderkit.html.RendererTestBase.checkXmlStructure(RendererTestBase.java:93) > at org.richfaces.renderkit.html.RendererTestBase.doTest(RendererTestBase.java:81) > at org.richfaces.renderkit.html.RendererTestBase.doTest(RendererTestBase.java:73) > at org.richfaces.renderkit.html.DropDownMenuRendererTest.testDoEncodeAjaxMode(DropDownMenuRendererTest.java:56) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) > at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31) > at org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) > at org.junit.runners.ParentRunner.run(ParentRunner.java:236) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:234) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:133) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:114) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:188) > at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:166) > at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:86) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:101) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74) > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 27 08:12:47 2012 From: jira-events at lists.jboss.org (Jan Papousek (JIRA)) Date: Tue, 27 Mar 2012 08:12:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12082) Components: Output UI module doesn't pass unit tests (AbstractTogglePanelTest#testGetChildName) In-Reply-To: <147991329.28097.1332505547854.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <2047462804.34123.1332850367820.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679602#comment-12679602 ] Jan Papousek commented on RF-12082: ----------------------------------- I see a little problem. The issues has been fixed in release/4.2.1.CR1 branch, but the develop branch (for 4.3.0) hasn't been updated. > Components: Output UI module doesn't pass unit tests (AbstractTogglePanelTest#testGetChildName) > ----------------------------------------------------------------------------------------------- > > Key: RF-12082 > URL: https://issues.jboss.org/browse/RF-12082 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.3.0.Milestone1 > Reporter: Jan Papousek > Assignee: Brian Leathem > Priority: Critical > > {code} > ------------------------------------------------------------------------------- > Test set: org.richfaces.component.AbstractTogglePanelTest > ------------------------------------------------------------------------------- > Tests run: 5, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.022 sec <<< FAILURE! > testGetChildName(org.richfaces.component.AbstractTogglePanelTest) Time elapsed: 0.005 sec <<< FAILURE! > java.lang.AssertionError: Expected exception: java.lang.IllegalArgumentException > at org.junit.internal.runners.statements.ExpectException.evaluate(ExpectException.java:32) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) > at org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) > at org.junit.runners.ParentRunner.run(ParentRunner.java:236) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:234) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:133) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:114) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:188) > at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:166) > at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:86) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:101) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74) > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 27 08:26:47 2012 From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA)) Date: Tue, 27 Mar 2012 08:26:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12092) a4j:poll : a4j:status never clears In-Reply-To: <69599813.32096.1332784967357.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1631182880.34167.1332851207617.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavol Pitonak reassigned RF-12092: ---------------------------------- Assignee: Brian Leathem (was: Pavol Pitonak) I wasn't able to reproduce the bug in Metamer (http://localhost:8080/metamer/faces/components/a4jPoll/simple.xhtml). {quote} RichFaces 4.2.1-SNAPSHOT Metamer 4.2.1-SNAPSHOT Mojarra 2.1.5 JBoss AS 7.1.0.Final OpenJDK Runtime Environment 1.6.0_24-b24 @ Linux Chrome 17.0.963.83 @ Linux i686 {quote} > a4j:poll : a4j:status never clears > ---------------------------------- > > Key: RF-12092 > URL: https://issues.jboss.org/browse/RF-12092 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Affects Versions: 4.2.0.Final > Reporter: Robert Gary > Assignee: Brian Leathem > > When a4j:poll fires a4j:status correctly displays the request is in progress. However, it never shows it complete. Using any other a4j component will correctly update the a4j:status. So if the a4j:status is stuck showing its waiting because of an a4j:poll if you click on an a4j:commandButton the a4j:status will correctly show its now complete. > render="#{faces$DiscoveryStatus.reRenderStr}"/> > > > > > > > > > This code works correctly in RF 3.3.3. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 27 08:37:47 2012 From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA)) Date: Tue, 27 Mar 2012 08:37:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12044) Metamer: @preventDefault attribute of rich:hotKey component doesn't work in IE 9 and Google Chrome In-Reply-To: <283065864.9549.1331739467659.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1601112588.34209.1332851867594.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavol Pitonak reassigned RF-12044: ---------------------------------- Assignee: Jan Papousek (was: Pavol Pitonak) It works for me in Chrome 17.0.963.83 on Linux. > Metamer: @preventDefault attribute of rich:hotKey component doesn't work in IE 9 and Google Chrome > -------------------------------------------------------------------------------------------------- > > Key: RF-12044 > URL: https://issues.jboss.org/browse/RF-12044 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-misc > Affects Versions: 4.2.0.Final > Environment: RichFaces 4.2.1-SNAPSHOT > Metamer 4.2.1-SNAPSHOT > Mojarra 2.1.5-SNAPSHOT > JBoss AS 7.1.0.Final > Java(TM) SE Runtime Environment 1.6.0_31-b04 @ Linux > Chrome 17.0.963.78 @ Linux i686 > ?RichFaces 4.2.1-SNAPSHOT > ?Metamer 4.2.1-SNAPSHOT > ?Mojarra 2.1.5-SNAPSHOT > ?JBoss AS 7.1.0.Final > ?Java(TM) SE Runtime Environment 1.6.0_31-b04 @ Linux > ?Internet Explorer 9.0 @ Win32 > Reporter: Jan Papousek > Assignee: Jan Papousek > Labels: Chrome, IE9 > Fix For: 4.2.1.CR1 > > > It's working correctly in Firefox 10. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 27 09:20:52 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 27 Mar 2012 09:20:52 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12093) ResourceServlet can't handle resources outside of specific libraries In-Reply-To: <346104444.32472.1332792767413.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1829511889.34300.1332854452392.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved RF-12093. ----------------------------- Resolution: Done > ResourceServlet can't handle resources outside of specific libraries > -------------------------------------------------------------------- > > Key: RF-12093 > URL: https://issues.jboss.org/browse/RF-12093 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 4.2.0.Final > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 4.2.1.CR1 > > > {{ResourceServlet}} is limited to what it can serve to only several specific libraries: > * [{{CKEditorLibrary}}|https://github.com/richfaces/core/blob/develop/impl/src/main/java/org/richfaces/webapp/ResourceServlet.java#L194] > * [{{StaticResourceLibrary}}|https://github.com/richfaces/core/blob/develop/impl/src/main/java/org/richfaces/webapp/ResourceServlet.java#L213] > * [{{RichFacesImageLibrary}}|https://github.com/richfaces/core/blob/develop/impl/src/main/java/org/richfaces/webapp/ResourceServlet.java#L213] > We should allow to serve any resource. > Some limitations may be placed on resources server by ResourceServlet as discussed in RF-11888. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 27 09:47:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 27 Mar 2012 09:47:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12058) rich:fileUpload - wrong upload icon if resourceOptimization param is set to true In-Reply-To: <1723961468.15563.1332085067290.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1169628380.34375.1332856067763.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679629#comment-12679629 ] Luk?? Fry? commented on RF-12058: --------------------------------- Hi Thursten, I'm not able to reproduce the issue. Could you please try to minimize the sample so you would be able to provide us WAR or source code where we could reproduce the issue? I have tried on two applications: [RichFaces Showcase hosting|http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=fileUpload&skin=blueSky] [input-demo developer example|https://github.com/richfaces/dev-examples/tree/develop/input-demo] (source) using Tomcat 6.0.33 I have also tried to look into {{richfaces-components-ui.jar/META-INF/resources/org.richfaces.staticResource/4.2.0.Final/PackedCompressed/org.richfaces.images/fu-upl.gif}} and the image there looks fine. > rich:fileUpload - wrong upload icon if resourceOptimization param is set to true > --------------------------------------------------------------------------------- > > Key: RF-12058 > URL: https://issues.jboss.org/browse/RF-12058 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input, resource handling > Affects Versions: 4.2.0.Final > Environment: Tomcat6.33, Richfaces 4.2.0 FINAL, JDK1.6 > Reporter: Thorsten Nieser > Assignee: Luk?? Fry? > Priority: Minor > Fix For: 4.2.1.CR1 > > Attachments: css-snippet.jpg, nok.jpg, ok.jpg > > > If the new resource optimization is disabled all icons of the fileUpload element are fine. > (http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=fileUpload&skin=blueSky) > But if I enabled the optimization by setting the context param to true, the upload button shows the red cross instead of the green check mark. > > org.richfaces.resourceOptimization.enabled > true > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 27 09:49:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 27 Mar 2012 09:49:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12058) rich:fileUpload - wrong upload icon if resourceOptimization param is set to true In-Reply-To: <1723961468.15563.1332085067290.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1268180601.34396.1332856187949.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved RF-12058. ----------------------------- Fix Version/s: (was: 4.2.1.CR1) Resolution: Cannot Reproduce Bug Hey Thorsten, I'm resolving this issue as {{Cannot reproduce bug}}, but feel free to reopen it if you feel you have more details which will allow us to reproduce the issue. > rich:fileUpload - wrong upload icon if resourceOptimization param is set to true > --------------------------------------------------------------------------------- > > Key: RF-12058 > URL: https://issues.jboss.org/browse/RF-12058 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input, resource handling > Affects Versions: 4.2.0.Final > Environment: Tomcat6.33, Richfaces 4.2.0 FINAL, JDK1.6 > Reporter: Thorsten Nieser > Assignee: Luk?? Fry? > Priority: Minor > Attachments: css-snippet.jpg, nok.jpg, ok.jpg > > > If the new resource optimization is disabled all icons of the fileUpload element are fine. > (http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=fileUpload&skin=blueSky) > But if I enabled the optimization by setting the context param to true, the upload button shows the red cross instead of the green check mark. > > org.richfaces.resourceOptimization.enabled > true > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 27 09:54:47 2012 From: jira-events at lists.jboss.org (kevin 2 (JIRA)) Date: Tue, 27 Mar 2012 09:54:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-10782) Input components: add attribute "width" In-Reply-To: <1936252277.35651.1300460925805.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1012864646.34409.1332856487675.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-10782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679636#comment-12679636 ] kevin 2 commented on RF-10782: ------------------------------ Is there any workaround for this issue on rich:select component ? Thanks. > Input components: add attribute "width" > --------------------------------------- > > Key: RF-10782 > URL: https://issues.jboss.org/browse/RF-10782 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: component, component-input > Affects Versions: 4.0.0.Final > Reporter: Gleb Galkin > Fix For: 4.Future > > > For input components we can define width using attribute style. For more description see the linked issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 27 10:25:48 2012 From: jira-events at lists.jboss.org (Juraj Huska (JIRA)) Date: Tue, 27 Mar 2012 10:25:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12099) Kitchensink archetype - mobile demo - loading the about page causes error on the server side Message-ID: <1483697602.34497.1332858348789.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Juraj Huska created RF-12099: -------------------------------- Summary: Kitchensink archetype - mobile demo - loading the about page causes error on the server side Key: RF-12099 URL: https://issues.jboss.org/browse/RF-12099 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: archetype Affects Versions: 4.2.0.Final Environment: mobile demo for project generated by Kitchensink archetype Reporter: Juraj Huska Priority: Minor After clicking on the link(small blue i in white circle) which should point to the about page, following error is thrown on the server side: {code} 16:15:07,894 SEVERE [org.richfaces.log.Context] (http--0.0.0.0-8080-4) /resources/components/memberForm.xhtml @19,62 value="#{cc.attrs.member.name}": Target Unreachable, 'member' returned null: javax.el.PropertyNotFoundException: /resources/components/memberForm.xhtml @19,62 value="#{cc.attrs.member.name}": Target Unreachable, 'member' returned null at com.sun.faces.facelets.el.TagValueExpression.getType(TagValueExpression.java:100) [jsf-impl-2.1.7-jbossorg-2.jar:] at com.sun.faces.renderkit.html_basic.HtmlBasicInputRenderer.getConvertedValue(HtmlBasicInputRenderer.java:95) [jsf-impl-2.1.7-jbossorg-2.jar:] at javax.faces.component.UIInput.getConvertedValue(UIInput.java:1030) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] at javax.faces.component.UIInput.validate(UIInput.java:960) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] at javax.faces.component.UIInput.executeValidate(UIInput.java:1233) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] at javax.faces.component.UIInput.processValidators(UIInput.java:698) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] at javax.faces.component.UIComponentBase.processValidators(UIComponentBase.java:1214) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] at javax.faces.component.UIComponentBase.processValidators(UIComponentBase.java:1214) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] at javax.faces.component.UIComponentBase.processValidators(UIComponentBase.java:1214) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] at javax.faces.component.UIComponentBase.processValidators(UIComponentBase.java:1214) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] at javax.faces.component.UIForm.processValidators(UIForm.java:253) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] at org.richfaces.context.PartialViewExecuteVisitCallback.visit(PartialViewExecuteVisitCallback.java:55) [richfaces-core-impl-4.3.0-20120302.170417-5.jar:4.3.0-SNAPSHOT] at org.richfaces.context.BaseExtendedVisitContext.invokeVisitCallback(BaseExtendedVisitContext.java:321) [richfaces-core-impl-4.3.0-20120302.170417-5.jar:4.3.0-SNAPSHOT] at javax.faces.component.UIForm.visitTree(UIForm.java:381) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] at javax.faces.component.UIComponent.visitTree(UIComponent.java:1623) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] at javax.faces.component.UIComponent.visitTree(UIComponent.java:1623) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] at org.richfaces.context.ExtendedPartialViewContextImpl.executeComponents(ExtendedPartialViewContextImpl.java:237) [richfaces-core-impl-4.3.0-20120302.170417-5.jar:4.3.0-SNAPSHOT] at org.richfaces.context.ExtendedPartialViewContextImpl.processPartialExecutePhase(ExtendedPartialViewContextImpl.java:217) [richfaces-core-impl-4.3.0-20120302.170417-5.jar:4.3.0-SNAPSHOT] at org.richfaces.context.ExtendedPartialViewContextImpl.processPartial(ExtendedPartialViewContextImpl.java:196) [richfaces-core-impl-4.3.0-20120302.170417-5.jar:4.3.0-SNAPSHOT] at javax.faces.component.UIViewRoot.processValidators(UIViewRoot.java:1170) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] at com.sun.faces.lifecycle.ProcessValidationsPhase.execute(ProcessValidationsPhase.java:76) [jsf-impl-2.1.7-jbossorg-2.jar:] at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) [jsf-impl-2.1.7-jbossorg-2.jar:] at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118) [jsf-impl-2.1.7-jbossorg-2.jar:] at javax.faces.webapp.FacesServlet.service(FacesServlet.java:593) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:62) [weld-core-1.1.5.AS71.Final.jar:2012-02-10 15:31] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.13.Final.jar:] at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.1.1.Final.jar:7.1.1.Final] at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.13.Final.jar:] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.13.Final.jar:] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.13.Final.jar:] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.13.Final.jar:] at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_22] {code} The about page is loaded successfully, however after next attempts to click on the same link results in loading blank page. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 27 10:25:49 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Tue, 27 Mar 2012 10:25:49 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12074) Showcase mediaOutput refers to GAE limitations In-Reply-To: <852769834.23256.1332345771654.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1794966587.34500.1332858349404.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem reassigned RF-12074: ---------------------------------- Assignee: Brian Leathem > Showcase mediaOutput refers to GAE limitations > ---------------------------------------------- > > Key: RF-12074 > URL: https://issues.jboss.org/browse/RF-12074 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: showcase > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 4.2.1.CR1 > > > {quote} > As the Google Application Engine restricts AWT class usage, this example reads the existing image and only performs re-indexing of the palette using colors you selected below. > {quote} > The example, and the wording should be re-worked to not refer to the GAE limitation. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 27 10:31:48 2012 From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA)) Date: Tue, 27 Mar 2012 10:31:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12044) Metamer: @preventDefault attribute of rich:hotKey component doesn't work in IE 9 and Google Chrome In-Reply-To: <283065864.9549.1331739467659.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1284181192.34536.1332858708532.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679610#comment-12679610 ] Pavol Pitonak edited comment on RF-12044 at 3/27/12 10:30 AM: -------------------------------------------------------------- Alt+X works for me in Chrome 17.0.963.83 on Linux with RichFaces 4. was (Author: ppitonak): It works for me in Chrome 17.0.963.83 on Linux. > Metamer: @preventDefault attribute of rich:hotKey component doesn't work in IE 9 and Google Chrome > -------------------------------------------------------------------------------------------------- > > Key: RF-12044 > URL: https://issues.jboss.org/browse/RF-12044 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-misc > Affects Versions: 4.2.0.Final > Environment: RichFaces 4.2.1-SNAPSHOT > Metamer 4.2.1-SNAPSHOT > Mojarra 2.1.5-SNAPSHOT > JBoss AS 7.1.0.Final > Java(TM) SE Runtime Environment 1.6.0_31-b04 @ Linux > Chrome 17.0.963.78 @ Linux i686 > ?RichFaces 4.2.1-SNAPSHOT > ?Metamer 4.2.1-SNAPSHOT > ?Mojarra 2.1.5-SNAPSHOT > ?JBoss AS 7.1.0.Final > ?Java(TM) SE Runtime Environment 1.6.0_31-b04 @ Linux > ?Internet Explorer 9.0 @ Win32 > Reporter: Jan Papousek > Assignee: Jan Papousek > Labels: Chrome, IE9 > Fix For: 4.2.1.CR1 > > > It's working correctly in Firefox 10. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 27 10:31:49 2012 From: jira-events at lists.jboss.org (Juraj Huska (JIRA)) Date: Tue, 27 Mar 2012 10:31:49 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12099) Kitchensink archetype - mobile demo - loading the about page causes error on the server side In-Reply-To: <1483697602.34497.1332858348789.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1611459765.34539.1332858709249.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj Huska updated RF-12099: ----------------------------- Description: After clicking on the link(the info button - small blue i in white circle) which should point to the about page, following error is thrown on the server side: {code} 16:15:07,894 SEVERE [org.richfaces.log.Context] (http--0.0.0.0-8080-4) /resources/components/memberForm.xhtml @19,62 value="#{cc.attrs.member.name}": Target Unreachable, 'member' returned null: javax.el.PropertyNotFoundException: /resources/components/memberForm.xhtml @19,62 value="#{cc.attrs.member.name}": Target Unreachable, 'member' returned null at com.sun.faces.facelets.el.TagValueExpression.getType(TagValueExpression.java:100) [jsf-impl-2.1.7-jbossorg-2.jar:] at com.sun.faces.renderkit.html_basic.HtmlBasicInputRenderer.getConvertedValue(HtmlBasicInputRenderer.java:95) [jsf-impl-2.1.7-jbossorg-2.jar:] at javax.faces.component.UIInput.getConvertedValue(UIInput.java:1030) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] at javax.faces.component.UIInput.validate(UIInput.java:960) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] at javax.faces.component.UIInput.executeValidate(UIInput.java:1233) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] at javax.faces.component.UIInput.processValidators(UIInput.java:698) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] at javax.faces.component.UIComponentBase.processValidators(UIComponentBase.java:1214) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] at javax.faces.component.UIComponentBase.processValidators(UIComponentBase.java:1214) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] at javax.faces.component.UIComponentBase.processValidators(UIComponentBase.java:1214) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] at javax.faces.component.UIComponentBase.processValidators(UIComponentBase.java:1214) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] at javax.faces.component.UIForm.processValidators(UIForm.java:253) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] at org.richfaces.context.PartialViewExecuteVisitCallback.visit(PartialViewExecuteVisitCallback.java:55) [richfaces-core-impl-4.3.0-20120302.170417-5.jar:4.3.0-SNAPSHOT] at org.richfaces.context.BaseExtendedVisitContext.invokeVisitCallback(BaseExtendedVisitContext.java:321) [richfaces-core-impl-4.3.0-20120302.170417-5.jar:4.3.0-SNAPSHOT] at javax.faces.component.UIForm.visitTree(UIForm.java:381) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] at javax.faces.component.UIComponent.visitTree(UIComponent.java:1623) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] at javax.faces.component.UIComponent.visitTree(UIComponent.java:1623) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] at org.richfaces.context.ExtendedPartialViewContextImpl.executeComponents(ExtendedPartialViewContextImpl.java:237) [richfaces-core-impl-4.3.0-20120302.170417-5.jar:4.3.0-SNAPSHOT] at org.richfaces.context.ExtendedPartialViewContextImpl.processPartialExecutePhase(ExtendedPartialViewContextImpl.java:217) [richfaces-core-impl-4.3.0-20120302.170417-5.jar:4.3.0-SNAPSHOT] at org.richfaces.context.ExtendedPartialViewContextImpl.processPartial(ExtendedPartialViewContextImpl.java:196) [richfaces-core-impl-4.3.0-20120302.170417-5.jar:4.3.0-SNAPSHOT] at javax.faces.component.UIViewRoot.processValidators(UIViewRoot.java:1170) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] at com.sun.faces.lifecycle.ProcessValidationsPhase.execute(ProcessValidationsPhase.java:76) [jsf-impl-2.1.7-jbossorg-2.jar:] at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) [jsf-impl-2.1.7-jbossorg-2.jar:] at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118) [jsf-impl-2.1.7-jbossorg-2.jar:] at javax.faces.webapp.FacesServlet.service(FacesServlet.java:593) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:62) [weld-core-1.1.5.AS71.Final.jar:2012-02-10 15:31] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.13.Final.jar:] at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.1.1.Final.jar:7.1.1.Final] at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.13.Final.jar:] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.13.Final.jar:] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.13.Final.jar:] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.13.Final.jar:] at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_22] {code} The about page is loaded successfully, however after next attempts to click on the same link results in loading blank page. was: After clicking on the link(small blue i in white circle) which should point to the about page, following error is thrown on the server side: {code} 16:15:07,894 SEVERE [org.richfaces.log.Context] (http--0.0.0.0-8080-4) /resources/components/memberForm.xhtml @19,62 value="#{cc.attrs.member.name}": Target Unreachable, 'member' returned null: javax.el.PropertyNotFoundException: /resources/components/memberForm.xhtml @19,62 value="#{cc.attrs.member.name}": Target Unreachable, 'member' returned null at com.sun.faces.facelets.el.TagValueExpression.getType(TagValueExpression.java:100) [jsf-impl-2.1.7-jbossorg-2.jar:] at com.sun.faces.renderkit.html_basic.HtmlBasicInputRenderer.getConvertedValue(HtmlBasicInputRenderer.java:95) [jsf-impl-2.1.7-jbossorg-2.jar:] at javax.faces.component.UIInput.getConvertedValue(UIInput.java:1030) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] at javax.faces.component.UIInput.validate(UIInput.java:960) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] at javax.faces.component.UIInput.executeValidate(UIInput.java:1233) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] at javax.faces.component.UIInput.processValidators(UIInput.java:698) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] at javax.faces.component.UIComponentBase.processValidators(UIComponentBase.java:1214) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] at javax.faces.component.UIComponentBase.processValidators(UIComponentBase.java:1214) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] at javax.faces.component.UIComponentBase.processValidators(UIComponentBase.java:1214) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] at javax.faces.component.UIComponentBase.processValidators(UIComponentBase.java:1214) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] at javax.faces.component.UIForm.processValidators(UIForm.java:253) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] at org.richfaces.context.PartialViewExecuteVisitCallback.visit(PartialViewExecuteVisitCallback.java:55) [richfaces-core-impl-4.3.0-20120302.170417-5.jar:4.3.0-SNAPSHOT] at org.richfaces.context.BaseExtendedVisitContext.invokeVisitCallback(BaseExtendedVisitContext.java:321) [richfaces-core-impl-4.3.0-20120302.170417-5.jar:4.3.0-SNAPSHOT] at javax.faces.component.UIForm.visitTree(UIForm.java:381) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] at javax.faces.component.UIComponent.visitTree(UIComponent.java:1623) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] at javax.faces.component.UIComponent.visitTree(UIComponent.java:1623) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] at org.richfaces.context.ExtendedPartialViewContextImpl.executeComponents(ExtendedPartialViewContextImpl.java:237) [richfaces-core-impl-4.3.0-20120302.170417-5.jar:4.3.0-SNAPSHOT] at org.richfaces.context.ExtendedPartialViewContextImpl.processPartialExecutePhase(ExtendedPartialViewContextImpl.java:217) [richfaces-core-impl-4.3.0-20120302.170417-5.jar:4.3.0-SNAPSHOT] at org.richfaces.context.ExtendedPartialViewContextImpl.processPartial(ExtendedPartialViewContextImpl.java:196) [richfaces-core-impl-4.3.0-20120302.170417-5.jar:4.3.0-SNAPSHOT] at javax.faces.component.UIViewRoot.processValidators(UIViewRoot.java:1170) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] at com.sun.faces.lifecycle.ProcessValidationsPhase.execute(ProcessValidationsPhase.java:76) [jsf-impl-2.1.7-jbossorg-2.jar:] at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) [jsf-impl-2.1.7-jbossorg-2.jar:] at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118) [jsf-impl-2.1.7-jbossorg-2.jar:] at javax.faces.webapp.FacesServlet.service(FacesServlet.java:593) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:62) [weld-core-1.1.5.AS71.Final.jar:2012-02-10 15:31] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.13.Final.jar:] at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.1.1.Final.jar:7.1.1.Final] at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.13.Final.jar:] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.13.Final.jar:] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.13.Final.jar:] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.13.Final.jar:] at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_22] {code} The about page is loaded successfully, however after next attempts to click on the same link results in loading blank page. > Kitchensink archetype - mobile demo - loading the about page causes error on the server side > -------------------------------------------------------------------------------------------- > > Key: RF-12099 > URL: https://issues.jboss.org/browse/RF-12099 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: archetype > Affects Versions: 4.2.0.Final > Environment: mobile demo for project generated by Kitchensink archetype > Reporter: Juraj Huska > Priority: Minor > > After clicking on the link(the info button - small blue i in white circle) which should point to the about page, following error is thrown on the server side: > {code} > 16:15:07,894 SEVERE [org.richfaces.log.Context] (http--0.0.0.0-8080-4) /resources/components/memberForm.xhtml @19,62 value="#{cc.attrs.member.name}": Target Unreachable, 'member' returned null: javax.el.PropertyNotFoundException: /resources/components/memberForm.xhtml @19,62 value="#{cc.attrs.member.name}": Target Unreachable, 'member' returned null > at com.sun.faces.facelets.el.TagValueExpression.getType(TagValueExpression.java:100) [jsf-impl-2.1.7-jbossorg-2.jar:] > at com.sun.faces.renderkit.html_basic.HtmlBasicInputRenderer.getConvertedValue(HtmlBasicInputRenderer.java:95) [jsf-impl-2.1.7-jbossorg-2.jar:] > at javax.faces.component.UIInput.getConvertedValue(UIInput.java:1030) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] > at javax.faces.component.UIInput.validate(UIInput.java:960) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] > at javax.faces.component.UIInput.executeValidate(UIInput.java:1233) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] > at javax.faces.component.UIInput.processValidators(UIInput.java:698) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] > at javax.faces.component.UIComponentBase.processValidators(UIComponentBase.java:1214) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] > at javax.faces.component.UIComponentBase.processValidators(UIComponentBase.java:1214) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] > at javax.faces.component.UIComponentBase.processValidators(UIComponentBase.java:1214) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] > at javax.faces.component.UIComponentBase.processValidators(UIComponentBase.java:1214) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] > at javax.faces.component.UIForm.processValidators(UIForm.java:253) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] > at org.richfaces.context.PartialViewExecuteVisitCallback.visit(PartialViewExecuteVisitCallback.java:55) [richfaces-core-impl-4.3.0-20120302.170417-5.jar:4.3.0-SNAPSHOT] > at org.richfaces.context.BaseExtendedVisitContext.invokeVisitCallback(BaseExtendedVisitContext.java:321) [richfaces-core-impl-4.3.0-20120302.170417-5.jar:4.3.0-SNAPSHOT] > at javax.faces.component.UIForm.visitTree(UIForm.java:381) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] > at javax.faces.component.UIComponent.visitTree(UIComponent.java:1623) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] > at javax.faces.component.UIComponent.visitTree(UIComponent.java:1623) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] > at org.richfaces.context.ExtendedPartialViewContextImpl.executeComponents(ExtendedPartialViewContextImpl.java:237) [richfaces-core-impl-4.3.0-20120302.170417-5.jar:4.3.0-SNAPSHOT] > at org.richfaces.context.ExtendedPartialViewContextImpl.processPartialExecutePhase(ExtendedPartialViewContextImpl.java:217) [richfaces-core-impl-4.3.0-20120302.170417-5.jar:4.3.0-SNAPSHOT] > at org.richfaces.context.ExtendedPartialViewContextImpl.processPartial(ExtendedPartialViewContextImpl.java:196) [richfaces-core-impl-4.3.0-20120302.170417-5.jar:4.3.0-SNAPSHOT] > at javax.faces.component.UIViewRoot.processValidators(UIViewRoot.java:1170) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] > at com.sun.faces.lifecycle.ProcessValidationsPhase.execute(ProcessValidationsPhase.java:76) [jsf-impl-2.1.7-jbossorg-2.jar:] > at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) [jsf-impl-2.1.7-jbossorg-2.jar:] > at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118) [jsf-impl-2.1.7-jbossorg-2.jar:] > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:593) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:62) [weld-core-1.1.5.AS71.Final.jar:2012-02-10 15:31] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.13.Final.jar:] > at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.1.1.Final.jar:7.1.1.Final] > at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final] > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.13.Final.jar:] > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.13.Final.jar:] > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.13.Final.jar:] > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.13.Final.jar:] > at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_22] > {code} > The about page is loaded successfully, however after next attempts to click on the same link results in loading blank page. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 27 11:06:52 2012 From: jira-events at lists.jboss.org (Juraj Huska (JIRA)) Date: Tue, 27 Mar 2012 11:06:52 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12100) Kitchensink archetype - mobile demo - adding new member causes rendering blank page Message-ID: <2080953888.34709.1332860812065.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Juraj Huska created RF-12100: -------------------------------- Summary: Kitchensink archetype - mobile demo - adding new member causes rendering blank page Key: RF-12100 URL: https://issues.jboss.org/browse/RF-12100 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: archetype Affects Versions: 4.2.0.Final Environment: mobile demo for Kitchensink archetype Reporter: Juraj Huska Attachments: blank.png When you add new member, either from mobile or from desktop kitchensink demo, *all loaded mobile demos* will be (after retrieving the push from the server) rendering the blank page. As blank, I mean just the header of the page, please see the screenshot. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 27 11:06:55 2012 From: jira-events at lists.jboss.org (Juraj Huska (JIRA)) Date: Tue, 27 Mar 2012 11:06:55 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12100) Kitchensink archetype - mobile demo - adding new member causes rendering blank page In-Reply-To: <2080953888.34709.1332860812065.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <651945152.34721.1332860815122.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj Huska updated RF-12100: ----------------------------- Attachment: blank.png > Kitchensink archetype - mobile demo - adding new member causes rendering blank page > ----------------------------------------------------------------------------------- > > Key: RF-12100 > URL: https://issues.jboss.org/browse/RF-12100 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: archetype > Affects Versions: 4.2.0.Final > Environment: mobile demo for Kitchensink archetype > Reporter: Juraj Huska > Attachments: blank.png > > > When you add new member, either from mobile or from desktop kitchensink demo, *all loaded mobile demos* will be (after retrieving the push from the server) rendering the blank page. > As blank, I mean just the header of the page, please see the screenshot. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 27 11:08:48 2012 From: jira-events at lists.jboss.org (Juraj Huska (JIRA)) Date: Tue, 27 Mar 2012 11:08:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12100) Kitchensink archetype - mobile demo - adding new member causes rendering blank page In-Reply-To: <2080953888.34709.1332860812065.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <663569758.34731.1332860928221.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj Huska updated RF-12100: ----------------------------- Steps to Reproduce: 1. load the *mobile* kitchensink example on several mobile devices, or on several tabs of your browser 2. add a new member, either from the desktop demo or from the mobile demo 3. see that blank page, same as in the screenshot, is rendered on all the loaded mobile demos was: 1. load the *mobile* kitchensink example on several mobile devices, or on several tabs of your browser 2. add new member, either from desktop demo or from mobile demo 3. see that blank page from the screenshot is rendered on all loaded mobile demos > Kitchensink archetype - mobile demo - adding new member causes rendering blank page > ----------------------------------------------------------------------------------- > > Key: RF-12100 > URL: https://issues.jboss.org/browse/RF-12100 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: archetype > Affects Versions: 4.2.0.Final > Environment: mobile demo for Kitchensink archetype > Reporter: Juraj Huska > Attachments: blank.png > > > When you add new member, either from mobile or from desktop kitchensink demo, *all loaded mobile demos* will be (after retrieving the push from the server) rendering the blank page. > As blank, I mean just the header of the page, please see the screenshot. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 27 11:56:47 2012 From: jira-events at lists.jboss.org (Thorsten Nieser (JIRA)) Date: Tue, 27 Mar 2012 11:56:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12058) rich:fileUpload - wrong upload icon if resourceOptimization param is set to true In-Reply-To: <1723961468.15563.1332085067290.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <835393657.35015.1332863807363.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679730#comment-12679730 ] Thorsten Nieser commented on RF-12058: -------------------------------------- Hi Lukas, Thanks for taking a look at this behaviour! Regarding your negative testing results I checked my project again, replaced some jars with newer ones (JSF impl updated to 2.1.7) and in addition I realized that I missed a mandatory jar file in my richfaces project, the cssparser one. Now, the error seems to be fixed on my side. Regards, Thorsten > rich:fileUpload - wrong upload icon if resourceOptimization param is set to true > --------------------------------------------------------------------------------- > > Key: RF-12058 > URL: https://issues.jboss.org/browse/RF-12058 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input, resource handling > Affects Versions: 4.2.0.Final > Environment: Tomcat6.33, Richfaces 4.2.0 FINAL, JDK1.6 > Reporter: Thorsten Nieser > Assignee: Luk?? Fry? > Priority: Minor > Attachments: css-snippet.jpg, nok.jpg, ok.jpg > > > If the new resource optimization is disabled all icons of the fileUpload element are fine. > (http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=fileUpload&skin=blueSky) > But if I enabled the optimization by setting the context param to true, the upload button shows the red cross instead of the green check mark. > > org.richfaces.resourceOptimization.enabled > true > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 27 12:37:47 2012 From: jira-events at lists.jboss.org (Juraj Huska (JIRA)) Date: Tue, 27 Mar 2012 12:37:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12101) Kitchensink example - rendering of the rich:messages is quite inconsistent Message-ID: <1230939528.35068.1332866267338.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Juraj Huska created RF-12101: -------------------------------- Summary: Kitchensink example - rendering of the rich:messages is quite inconsistent Key: RF-12101 URL: https://issues.jboss.org/browse/RF-12101 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: archetype Affects Versions: 4.2.0.Final Environment: app generated by the kitchensink archetype browser: Chrome, Firefox, mobile devices browser(iPhone) Reporter: Juraj Huska Priority: Minor The rich:messages tag generates messages on an inconsistent way, I think. They are rendered after BLUR event is done on the input, and the problem is that sometimes they are rendered and sometimes not. They also tend to disappear after clicking on Register button, another problem is that they are sometimes stacked, so in some cases there are more messages than inputs. IMHO the rich:messages tag should be removed, since there is already rich:message generated for every input, and they are not giving additional information, on the contrary they are misleading. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 27 12:39:47 2012 From: jira-events at lists.jboss.org (Juraj Huska (JIRA)) Date: Tue, 27 Mar 2012 12:39:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12101) Kitchensink example - rendering of the rich:messages is quite inconsistent In-Reply-To: <1230939528.35068.1332866267338.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1585711874.35074.1332866387397.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj Huska updated RF-12101: ----------------------------- Attachment: IMG_0038.PNG > Kitchensink example - rendering of the rich:messages is quite inconsistent > -------------------------------------------------------------------------- > > Key: RF-12101 > URL: https://issues.jboss.org/browse/RF-12101 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: archetype > Affects Versions: 4.2.0.Final > Environment: app generated by the kitchensink archetype > browser: Chrome, Firefox, mobile devices browser(iPhone) > Reporter: Juraj Huska > Priority: Minor > Attachments: IMG_0038.PNG > > > The rich:messages tag generates messages on an inconsistent way, I think. They are rendered after BLUR event is done on the input, and the problem is that sometimes they are rendered and sometimes not. > They also tend to disappear after clicking on Register button, another problem is that they are sometimes stacked, so in some cases there are more messages than inputs. > IMHO the rich:messages tag should be removed, since there is already rich:message generated for every input, and they are not giving additional information, on the contrary they are misleading. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 27 12:45:49 2012 From: jira-events at lists.jboss.org (Juraj Huska (JIRA)) Date: Tue, 27 Mar 2012 12:45:49 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12101) Kitchensink example - rich:messages does not provide additional info, they are quite misleading In-Reply-To: <1230939528.35068.1332866267338.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <801645815.35105.1332866749435.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj Huska updated RF-12101: ----------------------------- Summary: Kitchensink example - rich:messages does not provide additional info, they are quite misleading (was: Kitchensink example - rendering of the rich:messages is quite inconsistent) Issue Type: Enhancement (was: Bug) Description: IMHO the rich:messages tag should be removed, since there is already rich:message generated for every input, and they are not giving additional information, on the contrary they are misleading. (was: The rich:messages tag generates messages on an inconsistent way, I think. They are rendered after BLUR event is done on the input, and the problem is that sometimes they are rendered and sometimes not. They also tend to disappear after clicking on Register button, another problem is that they are sometimes stacked, so in some cases there are more messages than inputs. IMHO the rich:messages tag should be removed, since there is already rich:message generated for every input, and they are not giving additional information, on the contrary they are misleading.) Priority: Optional (was: Minor) > Kitchensink example - rich:messages does not provide additional info, they are quite misleading > ----------------------------------------------------------------------------------------------- > > Key: RF-12101 > URL: https://issues.jboss.org/browse/RF-12101 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: archetype > Affects Versions: 4.2.0.Final > Environment: app generated by the kitchensink archetype > browser: Chrome, Firefox, mobile devices browser(iPhone) > Reporter: Juraj Huska > Priority: Optional > Attachments: IMG_0038.PNG > > > IMHO the rich:messages tag should be removed, since there is already rich:message generated for every input, and they are not giving additional information, on the contrary they are misleading. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 27 12:47:47 2012 From: jira-events at lists.jboss.org (Robert Gary (JIRA)) Date: Tue, 27 Mar 2012 12:47:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12092) a4j:poll : a4j:status never clears In-Reply-To: <69599813.32096.1332784967357.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1592465123.35111.1332866867826.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679745#comment-12679745 ] Robert Gary commented on RF-12092: ---------------------------------- I'm able to reproduce it on... RichFaces 4.2.0.CR1 MyFaces MyFaces 2.0.6 JBoss 6.0.0.Final JVM 1.7_01 IE 9.0.8 FF 3.6.16 Chrome 17.0.963.83 m I'm using the following code... > a4j:poll : a4j:status never clears > ---------------------------------- > > Key: RF-12092 > URL: https://issues.jboss.org/browse/RF-12092 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Affects Versions: 4.2.0.Final > Reporter: Robert Gary > Assignee: Brian Leathem > > When a4j:poll fires a4j:status correctly displays the request is in progress. However, it never shows it complete. Using any other a4j component will correctly update the a4j:status. So if the a4j:status is stuck showing its waiting because of an a4j:poll if you click on an a4j:commandButton the a4j:status will correctly show its now complete. > render="#{faces$DiscoveryStatus.reRenderStr}"/> > > > > > > > > > This code works correctly in RF 3.3.3. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 27 13:11:47 2012 From: jira-events at lists.jboss.org (Juraj Huska (JIRA)) Date: Tue, 27 Mar 2012 13:11:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12102) Kitchensink archetype - shutdown of JBoss AS with project generated from this archetype throws error Message-ID: <1394038810.35167.1332868307274.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Juraj Huska created RF-12102: -------------------------------- Summary: Kitchensink archetype - shutdown of JBoss AS with project generated from this archetype throws error Key: RF-12102 URL: https://issues.jboss.org/browse/RF-12102 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: archetype Affects Versions: 4.2.0.Final Environment: container: JBoss AS 7.1.1.Final Reporter: Juraj Huska Priority: Trivial There is the same error thrown as in RF-11905, when shutting down the server. Kitchensink uses his own DS configuration, and it is enough to add proposed DB_CLOSE_ON_EXIT=FALSE to the connection url, in the file _/src/main/webapp/WEB-INF/kitchensink-quickstart-ds.xml_, in order to workaround the error. So it will look like: {code:xml} jdbc:h2:mem:kitchensink-quickstart;DB_CLOSE_ON_EXIT=FALSE {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 27 14:27:47 2012 From: jira-events at lists.jboss.org (Robert Gary (JIRA)) Date: Tue, 27 Mar 2012 14:27:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12092) a4j:poll : a4j:status never clears In-Reply-To: <69599813.32096.1332784967357.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1961374343.35317.1332872867377.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679764#comment-12679764 ] Robert Gary commented on RF-12092: ---------------------------------- I just reproduced this on Majarra 2.0. I'm going to attach a simple WAR that reproduces the issue with Majarro as well as MyFaces. > a4j:poll : a4j:status never clears > ---------------------------------- > > Key: RF-12092 > URL: https://issues.jboss.org/browse/RF-12092 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Affects Versions: 4.2.0.Final > Reporter: Robert Gary > Assignee: Brian Leathem > > When a4j:poll fires a4j:status correctly displays the request is in progress. However, it never shows it complete. Using any other a4j component will correctly update the a4j:status. So if the a4j:status is stuck showing its waiting because of an a4j:poll if you click on an a4j:commandButton the a4j:status will correctly show its now complete. > render="#{faces$DiscoveryStatus.reRenderStr}"/> > > > > > > > > > This code works correctly in RF 3.3.3. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 27 14:29:48 2012 From: jira-events at lists.jboss.org (Robert Gary (JIRA)) Date: Tue, 27 Mar 2012 14:29:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12092) a4j:poll : a4j:status never clears In-Reply-To: <69599813.32096.1332784967357.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <794300376.35334.1332872988153.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Gary updated RF-12092: ----------------------------- Attachment: a4jPollIssue.war Includes RF 4.1 but I'm also seeing it in RF 4.2.CR1 > a4j:poll : a4j:status never clears > ---------------------------------- > > Key: RF-12092 > URL: https://issues.jboss.org/browse/RF-12092 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Affects Versions: 4.2.0.Final > Reporter: Robert Gary > Assignee: Brian Leathem > Attachments: a4jPollIssue.war > > > When a4j:poll fires a4j:status correctly displays the request is in progress. However, it never shows it complete. Using any other a4j component will correctly update the a4j:status. So if the a4j:status is stuck showing its waiting because of an a4j:poll if you click on an a4j:commandButton the a4j:status will correctly show its now complete. > render="#{faces$DiscoveryStatus.reRenderStr}"/> > > > > > > > > > This code works correctly in RF 3.3.3. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 27 16:54:47 2012 From: jira-events at lists.jboss.org (Jason Lee (JIRA)) Date: Tue, 27 Mar 2012 16:54:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11988) rich:fileUpload doesn't seem to work on GlassFish In-Reply-To: <1031298844.7144.1329428856250.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1052813684.35678.1332881687567.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679801#comment-12679801 ] Jason Lee commented on RF-11988: -------------------------------- Any update on this issue? > rich:fileUpload doesn't seem to work on GlassFish > ------------------------------------------------- > > Key: RF-11988 > URL: https://issues.jboss.org/browse/RF-11988 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.2.0.CR1 > Environment: Mac OS X, Firefox 10, Chrome 17, GlassFish 3.1.2, GlassFish 4.0 > Reporter: Jason Lee > Fix For: 4.3-Tracking > > Attachments: rfupload.log, rfupload.tar.gz > > > While it renders fine, POSTs initiated from rich:fileUpload error out. I have tested this using both Firefox 10+ and Chrome 17+ against GlassFish 3.1.2 and GlassFish 4.0. I will attach both the log file and a sample application that should demonstrate the issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 27 17:41:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Tue, 27 Mar 2012 17:41:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11988) rich:fileUpload doesn't seem to work on GlassFish In-Reply-To: <1031298844.7144.1329428856250.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <395162121.35709.1332884507389.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679808#comment-12679808 ] Brian Leathem commented on RF-11988: ------------------------------------ This issue is currently tracking the 4.3 release, which means it will be scheduled for an upcoming 4.3 Milestone release. > rich:fileUpload doesn't seem to work on GlassFish > ------------------------------------------------- > > Key: RF-11988 > URL: https://issues.jboss.org/browse/RF-11988 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.2.0.CR1 > Environment: Mac OS X, Firefox 10, Chrome 17, GlassFish 3.1.2, GlassFish 4.0 > Reporter: Jason Lee > Fix For: 4.3-Tracking > > Attachments: rfupload.log, rfupload.tar.gz > > > While it renders fine, POSTs initiated from rich:fileUpload error out. I have tested this using both Firefox 10+ and Chrome 17+ against GlassFish 3.1.2 and GlassFish 4.0. I will attach both the log file and a sample application that should demonstrate the issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 27 17:43:47 2012 From: jira-events at lists.jboss.org (Jason Lee (JIRA)) Date: Tue, 27 Mar 2012 17:43:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11988) rich:fileUpload doesn't seem to work on GlassFish In-Reply-To: <1031298844.7144.1329428856250.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <533368171.35715.1332884627676.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679809#comment-12679809 ] Jason Lee commented on RF-11988: -------------------------------- That will work. Thanks for the update. > rich:fileUpload doesn't seem to work on GlassFish > ------------------------------------------------- > > Key: RF-11988 > URL: https://issues.jboss.org/browse/RF-11988 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.2.0.CR1 > Environment: Mac OS X, Firefox 10, Chrome 17, GlassFish 3.1.2, GlassFish 4.0 > Reporter: Jason Lee > Fix For: 4.3-Tracking > > Attachments: rfupload.log, rfupload.tar.gz > > > While it renders fine, POSTs initiated from rich:fileUpload error out. I have tested this using both Firefox 10+ and Chrome 17+ against GlassFish 3.1.2 and GlassFish 4.0. I will attach both the log file and a sample application that should demonstrate the issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 27 18:00:48 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Tue, 27 Mar 2012 18:00:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11977) Multiple fileUpload controls on the same page do not work In-Reply-To: <1904484642.1106.1329137880969.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1106831253.35727.1332885648480.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-11977. -------------------------------- Resolution: Done Re-structured the fileupload javascript, removing shared prtototype state > Multiple fileUpload controls on the same page do not work > --------------------------------------------------------- > > Key: RF-11977 > URL: https://issues.jboss.org/browse/RF-11977 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.1.0.Final > Environment: IE7,8,9, FireFox, Google Chrome > Reporter: Roxana Balaci > Assignee: Brian Leathem > Fix For: 4.2.1.CR1 > > Attachments: rf-11977-chromium-afterClickOn2ndUploadBtn.png, rf-11977-Chromium.png, rf-11977-ff11.png > > > Situation: > Two rich:fileUpload controls, in the same form. > When: > # choose first file for upload > # choose second file for upload > # click upload button for the first file > The first control disappears from the page and you cannot upload the second file (the upload event is never caught). > Could you please indicate a solution for this problem? > Thank you very much! > Part of the code used for testing is the following: > {code} > > > > fileUploadListener="#{bean.method1}" maxFilesQuantity="1" > immediateUpload="true" listHeight="65px" > > > fileUploadListener="#{bean.method2}" maxFilesQuantity="1" > immediateUpload="true" listHeight="65px" > > > render="stg" /> > > > > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 27 18:02:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Tue, 27 Mar 2012 18:02:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11977) Multiple fileUpload controls on the same page do not work In-Reply-To: <1904484642.1106.1329137880969.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1803817125.35729.1332885767282.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679812#comment-12679812 ] Brian Leathem commented on RF-11977: ------------------------------------ QE: The structure of _fileupload.js_ has changed significantly, please verify that no regressions have been introduced with this fix. > Multiple fileUpload controls on the same page do not work > --------------------------------------------------------- > > Key: RF-11977 > URL: https://issues.jboss.org/browse/RF-11977 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.1.0.Final > Environment: IE7,8,9, FireFox, Google Chrome > Reporter: Roxana Balaci > Assignee: Brian Leathem > Labels: needs-qe > Fix For: 4.2.1.CR1 > > Attachments: rf-11977-chromium-afterClickOn2ndUploadBtn.png, rf-11977-Chromium.png, rf-11977-ff11.png > > > Situation: > Two rich:fileUpload controls, in the same form. > When: > # choose first file for upload > # choose second file for upload > # click upload button for the first file > The first control disappears from the page and you cannot upload the second file (the upload event is never caught). > Could you please indicate a solution for this problem? > Thank you very much! > Part of the code used for testing is the following: > {code} > > > > fileUploadListener="#{bean.method1}" maxFilesQuantity="1" > immediateUpload="true" listHeight="65px" > > > fileUploadListener="#{bean.method2}" maxFilesQuantity="1" > immediateUpload="true" listHeight="65px" > > > render="stg" /> > > > > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 27 20:32:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Tue, 27 Mar 2012 20:32:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11948) rich:extendedDataTable generates a js-error stating this.normalPartStyle is undefined In-Reply-To: <2050628653.20854.1328272188456.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <510487768.35839.1332894767800.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679828#comment-12679828 ] Brian Leathem commented on RF-11948: ------------------------------------ Now you are addressing a different timing. If you want to set the column width on page load, listen to the rich:ready event of the EDT as mentioned above. If you want to set the column width after an ajax event, call the javascript via the oncomplete handler of the ajax method, as in: {code} {code} where setWidth is defined: {code} var setWidth = function () { var table = #{rich:component('capitals')}; table && table.setColumnWidth('colCapital','200') } var table = #{rich:component('capitals')}; table && jQuery(table.element).bind("rich:ready", setWidth); {code} Really though, doing these manipulations via the javascript API (while possible) is messy, and you should really be using the _width_ attribute of _rich:column_ if at all possible. > rich:extendedDataTable generates a js-error stating this.normalPartStyle is undefined > ------------------------------------------------------------------------------------- > > Key: RF-11948 > URL: https://issues.jboss.org/browse/RF-11948 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.2.0.CR1 > Environment: richfaces-4.2.0-SNAPSHOT, Firefox 10, IE8 > Reporter: Rene O > Assignee: Brian Leathem > Fix For: 4.2.1.CR1 > > > If you use rich:extendedDataTable and manually set the width of a column afterwards, a js error occurs > {code:title=page-snippet to reproduce the issue} > > xmlns:h="http://java.sun.com/jsf/html" > xmlns:f="http://java.sun.com/jsf/core" > xmlns:ui="http://java.sun.com/jsf/facelets" > xmlns:a4j="http://richfaces.org/a4j" > xmlns:rich="http://richfaces.org/rich" > > > > JSF Test > > > > > > > > > > ColA > > #{item.itemA} > > > > > > > {code} > {code:title=js error} > Fehler: this.normalPartStyle is undefined > Quelldatei: http://localhost:8080/jsftest/javax.faces.resource/extendedDataTable.js.jsf?ln=org.richfaces > Zeile: 279 > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Mar 27 20:32:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Tue, 27 Mar 2012 20:32:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11948) rich:extendedDataTable generates a js-error stating this.normalPartStyle is undefined In-Reply-To: <2050628653.20854.1328272188456.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1196597502.35842.1332894767917.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-11948. -------------------------------- Resolution: Done > rich:extendedDataTable generates a js-error stating this.normalPartStyle is undefined > ------------------------------------------------------------------------------------- > > Key: RF-11948 > URL: https://issues.jboss.org/browse/RF-11948 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.2.0.CR1 > Environment: richfaces-4.2.0-SNAPSHOT, Firefox 10, IE8 > Reporter: Rene O > Assignee: Brian Leathem > Fix For: 4.2.1.CR1 > > > If you use rich:extendedDataTable and manually set the width of a column afterwards, a js error occurs > {code:title=page-snippet to reproduce the issue} > > xmlns:h="http://java.sun.com/jsf/html" > xmlns:f="http://java.sun.com/jsf/core" > xmlns:ui="http://java.sun.com/jsf/facelets" > xmlns:a4j="http://richfaces.org/a4j" > xmlns:rich="http://richfaces.org/rich" > > > > JSF Test > > > > > > > > > > ColA > > #{item.itemA} > > > > > > > {code} > {code:title=js error} > Fehler: this.normalPartStyle is undefined > Quelldatei: http://localhost:8080/jsftest/javax.faces.resource/extendedDataTable.js.jsf?ln=org.richfaces > Zeile: 279 > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 28 01:03:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 28 Mar 2012 01:03:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12074) Showcase mediaOutput refers to GAE limitations In-Reply-To: <852769834.23256.1332345771654.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <538214713.36051.1332911027435.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-12074. -------------------------------- Resolution: Done Removed the GAE reference from the sample description > Showcase mediaOutput refers to GAE limitations > ---------------------------------------------- > > Key: RF-12074 > URL: https://issues.jboss.org/browse/RF-12074 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: showcase > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 4.2.1.CR1 > > > {quote} > As the Google Application Engine restricts AWT class usage, this example reads the existing image and only performs re-indexing of the palette using colors you selected below. > {quote} > The example, and the wording should be re-worked to not refer to the GAE limitation. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 28 01:15:48 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 28 Mar 2012 01:15:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11781) rich:list and rich:dataScroller: numbering on other than the first page In-Reply-To: <1768310689.66112.1322839661061.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1830398307.36058.1332911748760.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-11781: ------------------------------- Fix Version/s: 4.3-Tracking (was: 4.2.1.CR1) > rich:list and rich:dataScroller: numbering on other than the first page > ----------------------------------------------------------------------- > > Key: RF-11781 > URL: https://issues.jboss.org/browse/RF-11781 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-ScrollableDataTable > Affects Versions: 4.1.0.CR2 > Reporter: Jan Papousek > Fix For: 4.3-Tracking > > > When the rich:list and rich:dataScroller are used together, the first items in lists on pages 2, 3, ... shouldn't be numbered with number 1. For example, when the number of items on one page is limited to 10, the first item on the second page should be numbered with 11 (not 1). > To try the behaviour of this components working together deploy Metamer and open http://localhost:8080/metamer/faces/components/richList/scroller.xhtml. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 28 02:30:47 2012 From: jira-events at lists.jboss.org (Antonio Rodriguez (JIRA)) Date: Wed, 28 Mar 2012 02:30:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12103) onmouse events dont working on rich:notifyMessage Message-ID: <1986202609.36071.1332916247280.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Antonio Rodriguez created RF-12103: -------------------------------------- Summary: onmouse events dont working on rich:notifyMessage Key: RF-12103 URL: https://issues.jboss.org/browse/RF-12103 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.2.0.Final Reporter: Antonio Rodriguez Hi, im using rich:notifyStack and rich:notifyMessage to show erros of required=true h:inputText. All goes OK but i need that onclick event over the notifiyMessage, the cursor go focused on the h:inputText associated with the notifyMessage. I noticed that the events (onmouseover, onclick, onmouseout...) doesnt work on notifyMessages. However, this events goes OK on rich:message. Does anybody knows why the mouse events dont work with notifyMessages??? Thanks -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 28 02:53:48 2012 From: jira-events at lists.jboss.org (Rene O (JIRA)) Date: Wed, 28 Mar 2012 02:53:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11948) rich:extendedDataTable generates a js-error stating this.normalPartStyle is undefined In-Reply-To: <2050628653.20854.1328272188456.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <441563189.36120.1332917628821.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679866#comment-12679866 ] Rene O commented on RF-11948: ----------------------------- I would like to use the width attribute if there were the possibility to use percent values. But now you only can use static values. See RF-11174 and RF-11175 . In my usecase my table has a dynamic width and i want that the column width is calculated according to the width of the table... That there is only one button was only an example to demonstrate this problem. If the oncomplete is the only chance to do this right, i think the best solution is that the table itself has an oncomplete attribute. > rich:extendedDataTable generates a js-error stating this.normalPartStyle is undefined > ------------------------------------------------------------------------------------- > > Key: RF-11948 > URL: https://issues.jboss.org/browse/RF-11948 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.2.0.CR1 > Environment: richfaces-4.2.0-SNAPSHOT, Firefox 10, IE8 > Reporter: Rene O > Assignee: Brian Leathem > Fix For: 4.2.1.CR1 > > > If you use rich:extendedDataTable and manually set the width of a column afterwards, a js error occurs > {code:title=page-snippet to reproduce the issue} > > xmlns:h="http://java.sun.com/jsf/html" > xmlns:f="http://java.sun.com/jsf/core" > xmlns:ui="http://java.sun.com/jsf/facelets" > xmlns:a4j="http://richfaces.org/a4j" > xmlns:rich="http://richfaces.org/rich" > > > > JSF Test > > > > > > > > > > ColA > > #{item.itemA} > > > > > > > {code} > {code:title=js error} > Fehler: this.normalPartStyle is undefined > Quelldatei: http://localhost:8080/jsftest/javax.faces.resource/extendedDataTable.js.jsf?ln=org.richfaces > Zeile: 279 > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 28 02:53:48 2012 From: jira-events at lists.jboss.org (Rene O (JIRA)) Date: Wed, 28 Mar 2012 02:53:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11948) rich:extendedDataTable generates a js-error stating this.normalPartStyle is undefined In-Reply-To: <2050628653.20854.1328272188456.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <805234101.36121.1332917628867.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rene O reopened RF-11948: ------------------------- > rich:extendedDataTable generates a js-error stating this.normalPartStyle is undefined > ------------------------------------------------------------------------------------- > > Key: RF-11948 > URL: https://issues.jboss.org/browse/RF-11948 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.2.0.CR1 > Environment: richfaces-4.2.0-SNAPSHOT, Firefox 10, IE8 > Reporter: Rene O > Assignee: Brian Leathem > Fix For: 4.2.1.CR1 > > > If you use rich:extendedDataTable and manually set the width of a column afterwards, a js error occurs > {code:title=page-snippet to reproduce the issue} > > xmlns:h="http://java.sun.com/jsf/html" > xmlns:f="http://java.sun.com/jsf/core" > xmlns:ui="http://java.sun.com/jsf/facelets" > xmlns:a4j="http://richfaces.org/a4j" > xmlns:rich="http://richfaces.org/rich" > > > > JSF Test > > > > > > > > > > ColA > > #{item.itemA} > > > > > > > {code} > {code:title=js error} > Fehler: this.normalPartStyle is undefined > Quelldatei: http://localhost:8080/jsftest/javax.faces.resource/extendedDataTable.js.jsf?ln=org.richfaces > Zeile: 279 > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 28 03:11:53 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 28 Mar 2012 03:11:53 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11884) Multiple Errors with IE8/9 In-Reply-To: <1562607854.56099.1326530722497.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <129710060.36140.1332918713422.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679869#comment-12679869 ] Luk?? Fry? commented on RF-11884: --------------------------------- Problem 1: this is regular HTML feature, let's use this style for whole application/page: {code:html} {code} or define {{none}} border only to specific link: {code:xml} {code} > Multiple Errors with IE8/9 > -------------------------- > > Key: RF-11884 > URL: https://issues.jboss.org/browse/RF-11884 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes, component-tables, component-tree > Environment: Windows 7 64, Tomcat 7.0.23, Mojarra 2.1.3, IE8/9 (all errors), Chrome 16.09 (one problem), PrimesFaces 2.2.1 (ChartGraphics only, problems still persist when PF is removed) > Reporter: Friedhelm Kuehn > Assignee: Luk?? Fry? > Priority: Critical > Fix For: 4.2.1.CR1 > > Attachments: ProgramVariable_Table.xhtml, Richfaces_4.1_Problems.pdf, Richfaces_4.1_Problems_Konfiguration.pdf, Test.war > > > Problem 1: Shaded TabbedPane Tabs, not changing color when tabbing. Big spacing area below tabs (height about 20 px, should be 2px). > Problem 2: Content of not-popped-up Popup-Panel is not visible, but an area is claimed on screen. > Problem 3: with icon: Icon is surrounded by dark border > Problem 4: No Horzontal-Scroller in ExtendDatatable (with Chrome also). > Problem 5: Use of IconCollapsed/..Expanded creates double Icons in TreeNode > Problem 6: Javascript Error in ExtendedDataTable.js > Biggest Problem: We have to deliver our application in a few weeks. Support for IE8/9 is hard customer requirement. > I have a made a documentation for each problem, but don't find a way to attach a PDF to this issue - ?? > Please help ! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 28 03:11:53 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 28 Mar 2012 03:11:53 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11884) Multiple Errors with IE8/9 In-Reply-To: <1562607854.56099.1326530722497.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <783876666.36145.1332918713764.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679869#comment-12679869 ] Luk?? Fry? edited comment on RF-11884 at 3/28/12 3:08 AM: ---------------------------------------------------------- Problem 3: this is regular HTML feature, let's use this style for whole application/page: {code:html} {code} or define {{none}} border only to specific link: {code:xml} {code} was (Author: lfryc): Problem 1: this is regular HTML feature, let's use this style for whole application/page: {code:html} {code} or define {{none}} border only to specific link: {code:xml} {code} > Multiple Errors with IE8/9 > -------------------------- > > Key: RF-11884 > URL: https://issues.jboss.org/browse/RF-11884 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes, component-tables, component-tree > Environment: Windows 7 64, Tomcat 7.0.23, Mojarra 2.1.3, IE8/9 (all errors), Chrome 16.09 (one problem), PrimesFaces 2.2.1 (ChartGraphics only, problems still persist when PF is removed) > Reporter: Friedhelm Kuehn > Assignee: Luk?? Fry? > Priority: Critical > Fix For: 4.2.1.CR1 > > Attachments: ProgramVariable_Table.xhtml, Richfaces_4.1_Problems.pdf, Richfaces_4.1_Problems_Konfiguration.pdf, Test.war > > > Problem 1: Shaded TabbedPane Tabs, not changing color when tabbing. Big spacing area below tabs (height about 20 px, should be 2px). > Problem 2: Content of not-popped-up Popup-Panel is not visible, but an area is claimed on screen. > Problem 3: with icon: Icon is surrounded by dark border > Problem 4: No Horzontal-Scroller in ExtendDatatable (with Chrome also). > Problem 5: Use of IconCollapsed/..Expanded creates double Icons in TreeNode > Problem 6: Javascript Error in ExtendedDataTable.js > Biggest Problem: We have to deliver our application in a few weeks. Support for IE8/9 is hard customer requirement. > I have a made a documentation for each problem, but don't find a way to attach a PDF to this issue - ?? > Please help ! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 28 03:45:47 2012 From: jira-events at lists.jboss.org (Markus Staab (JIRA)) Date: Wed, 28 Mar 2012 03:45:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12104) BeanValidator: label not handled using MessageFactory Message-ID: <1962209716.36295.1332920747471.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Markus Staab created RF-12104: --------------------------------- Summary: BeanValidator: label not handled using MessageFactory Key: RF-12104 URL: https://issues.jboss.org/browse/RF-12104 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 3.3.3.Final Environment: Liferay 5.2.4, Portlet 2.0, JSF 1.2 Reporter: Markus Staab The BeanValidator, in contrast to most JSF validators e.g. LongRangeValidator, does not use the MessageFactory to handle validation error message. see LongRangeValidators' validate-method: {code} .... throw new ValidatorException(MessageFactory.getMessage (context, NOT_IN_RANGE_MESSAGE_ID, stringValue(component, minimum, context), stringValue(component, maximum, context), MessageFactory.getLabel(context, component))); ... {code} Therefore error-message of a BeanValidator will neither prepand the String which is provided from the components' label-attribute nor the components' client id. see BeanValidator's validate & extractMessages-method {code} .... private Collection extractMessages(Set> violations) { Collection messages = null; if (null != violations && violations.size() > 0) { messages = new ArrayList(violations.size()); for (ConstraintViolation constraintViolation : violations) { messages.add(constraintViolation.getMessage()); } } return messages; } ... {code} All error messages are taken 1:1 from the BeanValidator. While e.g. the error-message of LongRangeValidtor looks like "Startdate: Value is greater than allowable maximum of ''{0}''." the error looks like "Value is greater than allowable maximum of ''{0}''.". -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 28 03:51:47 2012 From: jira-events at lists.jboss.org (Markus Staab (JIRA)) Date: Wed, 28 Mar 2012 03:51:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12104) BeanValidator: label not handled using MessageFactory In-Reply-To: <1962209716.36295.1332920747471.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1944800509.36314.1332921107325.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Markus Staab updated RF-12104: ------------------------------ Description: The BeanValidator, in contrast to most JSF validators e.g. LongRangeValidator, does not use the MessageFactory to handle validation error message. see LongRangeValidators' validate-method: {code} .... throw new ValidatorException(MessageFactory.getMessage (context, NOT_IN_RANGE_MESSAGE_ID, stringValue(component, minimum, context), stringValue(component, maximum, context), MessageFactory.getLabel(context, component))); ... {code} Therefore error-message of a BeanValidator will neither prepand the String which is provided from the components' label-attribute nor the components' client id. see BeanValidator's validate & extractMessages-method {code} .... private Collection extractMessages(Set> violations) { Collection messages = null; if (null != violations && violations.size() > 0) { messages = new ArrayList(violations.size()); for (ConstraintViolation constraintViolation : violations) { messages.add(constraintViolation.getMessage()); } } return messages; } ... {code} All error messages are taken 1:1 from the BeanValidator. While e.g. the error-message of LongRangeValidtor looks like "Startdate: Value is greater than allowable maximum of ''{0}''." the error looks like "Value is greater than allowable maximum of ''{0}''.". The reference to the component which violates the rule is not shown. was: The BeanValidator, in contrast to most JSF validators e.g. LongRangeValidator, does not use the MessageFactory to handle validation error message. see LongRangeValidators' validate-method: {code} .... throw new ValidatorException(MessageFactory.getMessage (context, NOT_IN_RANGE_MESSAGE_ID, stringValue(component, minimum, context), stringValue(component, maximum, context), MessageFactory.getLabel(context, component))); ... {code} Therefore error-message of a BeanValidator will neither prepand the String which is provided from the components' label-attribute nor the components' client id. see BeanValidator's validate & extractMessages-method {code} .... private Collection extractMessages(Set> violations) { Collection messages = null; if (null != violations && violations.size() > 0) { messages = new ArrayList(violations.size()); for (ConstraintViolation constraintViolation : violations) { messages.add(constraintViolation.getMessage()); } } return messages; } ... {code} All error messages are taken 1:1 from the BeanValidator. While e.g. the error-message of LongRangeValidtor looks like "Startdate: Value is greater than allowable maximum of ''{0}''." the error looks like "Value is greater than allowable maximum of ''{0}''.". > BeanValidator: label not handled using MessageFactory > ----------------------------------------------------- > > Key: RF-12104 > URL: https://issues.jboss.org/browse/RF-12104 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 3.3.3.Final > Environment: Liferay 5.2.4, Portlet 2.0, JSF 1.2 > Reporter: Markus Staab > > The BeanValidator, in contrast to most JSF validators e.g. LongRangeValidator, does not use the MessageFactory to handle validation error message. > see LongRangeValidators' validate-method: > {code} > .... > throw new ValidatorException(MessageFactory.getMessage > (context, > NOT_IN_RANGE_MESSAGE_ID, > stringValue(component, minimum, context), > stringValue(component, maximum, context), > MessageFactory.getLabel(context, component))); > ... > {code} > Therefore error-message of a BeanValidator will neither prepand the String which is provided from the components' label-attribute nor the components' client id. > see BeanValidator's validate & extractMessages-method > {code} > .... > private Collection extractMessages(Set> violations) { > Collection messages = null; > if (null != violations && violations.size() > 0) { > messages = new ArrayList(violations.size()); > for (ConstraintViolation constraintViolation : violations) { > messages.add(constraintViolation.getMessage()); > } > } > return messages; > } > ... > {code} > All error messages are taken 1:1 from the BeanValidator. > While e.g. the error-message of LongRangeValidtor looks like "Startdate: Value is greater than allowable maximum of ''{0}''." the error looks like "Value is greater than allowable maximum of ''{0}''.". > The reference to the component which violates the rule is not shown. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 28 04:27:48 2012 From: jira-events at lists.jboss.org (Jan Papousek (JIRA)) Date: Wed, 28 Mar 2012 04:27:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12044) Metamer: @preventDefault attribute of rich:hotKey component doesn't work in IE 9 and Google Chrome In-Reply-To: <283065864.9549.1331739467659.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1735385158.36504.1332923268229.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679902#comment-12679902 ] Jan Papousek commented on RF-12044: ----------------------------------- Pavol: My fault. I have plugin which is activated on Alt+X. You have to change the key combination to something which is active in your installation (e.g. Ctrl+W). > Metamer: @preventDefault attribute of rich:hotKey component doesn't work in IE 9 and Google Chrome > -------------------------------------------------------------------------------------------------- > > Key: RF-12044 > URL: https://issues.jboss.org/browse/RF-12044 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-misc > Affects Versions: 4.2.0.Final > Environment: RichFaces 4.2.1-SNAPSHOT > Metamer 4.2.1-SNAPSHOT > Mojarra 2.1.5-SNAPSHOT > JBoss AS 7.1.0.Final > Java(TM) SE Runtime Environment 1.6.0_31-b04 @ Linux > Chrome 17.0.963.78 @ Linux i686 > ?RichFaces 4.2.1-SNAPSHOT > ?Metamer 4.2.1-SNAPSHOT > ?Mojarra 2.1.5-SNAPSHOT > ?JBoss AS 7.1.0.Final > ?Java(TM) SE Runtime Environment 1.6.0_31-b04 @ Linux > ?Internet Explorer 9.0 @ Win32 > Reporter: Jan Papousek > Assignee: Jan Papousek > Labels: Chrome, IE9 > Fix For: 4.2.1.CR1 > > > It's working correctly in Firefox 10. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 28 04:31:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Wed, 28 Mar 2012 04:31:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12105) panelToggleListener attribute @listener does not work Message-ID: <1942473592.36521.1332923507950.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Ji?? ?tefek created RF-12105: -------------------------------- Summary: panelToggleListener attribute @listener does not work Key: RF-12105 URL: https://issues.jboss.org/browse/RF-12105 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-misc Affects Versions: 4.2.0.Final Environment: RichFaces 4.2.1-SNAPSHOT Metamer 4.2.1-SNAPSHOT Mojarra 2.1.5-SNAPSHOT JBoss AS 7.1.0.Final OpenJDK Runtime Environment 1.6.0_24-b24 @ Linux Firefox 11.0 @ Linux x86_64 Reporter: Ji?? ?tefek # Deploy Metamer. # Open http://localhost:8080/metamer/faces/components/richPanelToggleListener/collapsiblePanel.xhtml # Click on chevron to collapse a panel. # Messages with "* pannelToggleListenerBean panel collapsed" should appear in phases list. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 28 04:43:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Wed, 28 Mar 2012 04:43:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12106) panelToggleListener attribute @for does not work Message-ID: <581703508.36545.1332924227837.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Ji?? ?tefek created RF-12106: -------------------------------- Summary: panelToggleListener attribute @for does not work Key: RF-12106 URL: https://issues.jboss.org/browse/RF-12106 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-misc Affects Versions: 4.2.0.Final Environment: RichFaces 4.2.1-SNAPSHOT Metamer 4.2.1-SNAPSHOT Mojarra 2.1.5-SNAPSHOT JBoss AS 7.1.0.Final OpenJDK Runtime Environment 1.6.0_24-b24 @ Linux Firefox 11.0 @ Linux x86_64 Reporter: Ji?? ?tefek # Deploy Metamer. # Open http://localhost:8080/metamer/faces/components/richPanelToggleListener/RF-?.xhtml //will fix the address soon -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 28 04:45:48 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Wed, 28 Mar 2012 04:45:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12106) panelToggleListener attribute @for does not work In-Reply-To: <581703508.36545.1332924227837.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <362233054.36565.1332924348076.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek updated RF-12106: ----------------------------- Description: # Deploy Metamer. # Open http://localhost:8080/metamer/faces/components/richPanelToggleListener/RF-12106.xhtml was: # Deploy Metamer. # Open http://localhost:8080/metamer/faces/components/richPanelToggleListener/RF-?.xhtml //will fix the address soon > panelToggleListener attribute @for does not work > ------------------------------------------------ > > Key: RF-12106 > URL: https://issues.jboss.org/browse/RF-12106 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-misc > Affects Versions: 4.2.0.Final > Environment: RichFaces 4.2.1-SNAPSHOT > Metamer 4.2.1-SNAPSHOT > Mojarra 2.1.5-SNAPSHOT > JBoss AS 7.1.0.Final > OpenJDK Runtime Environment 1.6.0_24-b24 @ Linux > Firefox 11.0 @ Linux x86_64 > Reporter: Ji?? ?tefek > > # Deploy Metamer. > # Open http://localhost:8080/metamer/faces/components/richPanelToggleListener/RF-12106.xhtml -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 28 04:55:47 2012 From: jira-events at lists.jboss.org (Jan Papousek (JIRA)) Date: Wed, 28 Mar 2012 04:55:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12043) Metamer: rich:contextMenu isn't rendered correctly in IE 9 compatibility mode In-Reply-To: <714594071.9445.1331737907625.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1272849507.36585.1332924947435.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Papousek closed RF-12043. ----------------------------- Verified. > Metamer: rich:contextMenu isn't rendered correctly in IE 9 compatibility mode > ----------------------------------------------------------------------------- > > Key: RF-12043 > URL: https://issues.jboss.org/browse/RF-12043 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-menu > Affects Versions: 4.2.0.Final > Environment: RichFaces 4.2.1-SNAPSHOT > Metamer 4.2.1-SNAPSHOT > Mojarra 2.1.5-SNAPSHOT > JBoss AS 7.1.0.Final > Java(TM) SE Runtime Environment 1.6.0_31-b04 @ Linux > Internet Explorer 7.0 @ Win32 (this is IE 9 Compatibility Mode) > Reporter: Jan Papousek > Assignee: Brian Leathem > Labels: IE9, needs-qe, regression > Fix For: 4.2.1.CR1 > > Attachments: metamer-ie-9-rich_contextMenu.png > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 28 04:57:48 2012 From: jira-events at lists.jboss.org (Jan Papousek (JIRA)) Date: Wed, 28 Mar 2012 04:57:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12042) Metamer: rich:contextMenu doesn't disappear after clicking out of the menu in IE9 and Google Chrome In-Reply-To: <1422678186.9420.1331737667612.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1110528261.36600.1332925068026.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Papousek closed RF-12042. ----------------------------- Verified. > Metamer: rich:contextMenu doesn't disappear after clicking out of the menu in IE9 and Google Chrome > --------------------------------------------------------------------------------------------------- > > Key: RF-12042 > URL: https://issues.jboss.org/browse/RF-12042 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-menu > Affects Versions: 4.2.0.Final > Environment: ?RichFaces 4.2.1-SNAPSHOT > ?Metamer 4.2.1-SNAPSHOT > ?Mojarra 2.1.5-SNAPSHOT > ?JBoss AS 7.1.0.Final > ?Java(TM) SE Runtime Environment 1.6.0_31-b04 @ Linux > ?Internet Explorer 9.0 @ Win32 > RichFaces 4.2.1-SNAPSHOT > Metamer 4.2.1-SNAPSHOT > Mojarra 2.1.5-SNAPSHOT > JBoss AS 7.1.0.Final > Java(TM) SE Runtime Environment 1.6.0_31-b04 @ Linux > Chrome 17.0.963.78 @ Linux i686 > Reporter: Jan Papousek > Assignee: Brian Leathem > Labels: Chrome, IE9, needs-qe > Fix For: 4.2.1.CR1 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 28 05:21:47 2012 From: jira-events at lists.jboss.org (Jan Papousek (JIRA)) Date: Wed, 28 Mar 2012 05:21:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12044) Metamer: @preventDefault attribute of rich:hotKey component doesn't work in IE 9 and Google Chrome In-Reply-To: <283065864.9549.1331739467659.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <2104915745.36656.1332926507445.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679916#comment-12679916 ] Jan Papousek commented on RF-12044: ----------------------------------- I've checked the behaviour with RichFaces 3.3.4. It seems to me that the component rich:hotkey doesn't have any attribute to prevent defaults and it doesn't prevent defaults automatically. So the key combinations like Ctrl+W (or Alt+X in IE 9) don't work correctly. > Metamer: @preventDefault attribute of rich:hotKey component doesn't work in IE 9 and Google Chrome > -------------------------------------------------------------------------------------------------- > > Key: RF-12044 > URL: https://issues.jboss.org/browse/RF-12044 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-misc > Affects Versions: 4.2.0.Final > Environment: RichFaces 4.2.1-SNAPSHOT > Metamer 4.2.1-SNAPSHOT > Mojarra 2.1.5-SNAPSHOT > JBoss AS 7.1.0.Final > Java(TM) SE Runtime Environment 1.6.0_31-b04 @ Linux > Chrome 17.0.963.78 @ Linux i686 > ?RichFaces 4.2.1-SNAPSHOT > ?Metamer 4.2.1-SNAPSHOT > ?Mojarra 2.1.5-SNAPSHOT > ?JBoss AS 7.1.0.Final > ?Java(TM) SE Runtime Environment 1.6.0_31-b04 @ Linux > ?Internet Explorer 9.0 @ Win32 > Reporter: Jan Papousek > Assignee: Jan Papousek > Labels: Chrome, IE9 > Fix For: 4.2.1.CR1 > > > It's working correctly in Firefox 10. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 28 05:25:47 2012 From: jira-events at lists.jboss.org (Jan Papousek (JIRA)) Date: Wed, 28 Mar 2012 05:25:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12044) Metamer: @preventDefault attribute of rich:hotKey component doesn't work in IE 9 and Google Chrome In-Reply-To: <283065864.9549.1331739467659.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1971839080.36660.1332926747409.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Papousek updated RF-12044: ------------------------------ Steps to Reproduce: - deploy Metamer - open http://localhost:8080/metamer/faces/components/richHotKey/orderingList.xhtml *IE 9* - click on an item in rich:orderingList - press Alt+X -> browser's action is invoked (the item should be moved to the bottom of the list instead) *Google Chrome* / *IE 9* - set key attribute to "ctrl+w" - click on an item in rich:orderingList - press Ctrl+W -> browser's tab is closed was: - deploy Metamer - open http://localhost:8080/metamer/faces/components/richHotKey/orderingList.xhtml - click on an item in rich:orderingList - press Alt+X -> browser's action is invoked (the item should be moved to the bottom of the list instead) > Metamer: @preventDefault attribute of rich:hotKey component doesn't work in IE 9 and Google Chrome > -------------------------------------------------------------------------------------------------- > > Key: RF-12044 > URL: https://issues.jboss.org/browse/RF-12044 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-misc > Affects Versions: 4.2.0.Final > Environment: RichFaces 4.2.1-SNAPSHOT > Metamer 4.2.1-SNAPSHOT > Mojarra 2.1.5-SNAPSHOT > JBoss AS 7.1.0.Final > Java(TM) SE Runtime Environment 1.6.0_31-b04 @ Linux > Chrome 17.0.963.78 @ Linux i686 > ?RichFaces 4.2.1-SNAPSHOT > ?Metamer 4.2.1-SNAPSHOT > ?Mojarra 2.1.5-SNAPSHOT > ?JBoss AS 7.1.0.Final > ?Java(TM) SE Runtime Environment 1.6.0_31-b04 @ Linux > ?Internet Explorer 9.0 @ Win32 > Reporter: Jan Papousek > Assignee: Jan Papousek > Labels: Chrome, IE9 > Fix For: 4.2.1.CR1 > > > It's working correctly in Firefox 10. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 28 05:27:47 2012 From: jira-events at lists.jboss.org (Jan Papousek (JIRA)) Date: Wed, 28 Mar 2012 05:27:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12044) Metamer: @preventDefault attribute of rich:hotKey component doesn't work in IE 9 and Google Chrome In-Reply-To: <283065864.9549.1331739467659.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <748510499.36665.1332926867487.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Papousek reassigned RF-12044: --------------------------------- Assignee: Luk?? Fry? (was: Jan Papousek) > Metamer: @preventDefault attribute of rich:hotKey component doesn't work in IE 9 and Google Chrome > -------------------------------------------------------------------------------------------------- > > Key: RF-12044 > URL: https://issues.jboss.org/browse/RF-12044 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-misc > Affects Versions: 4.2.0.Final > Environment: RichFaces 4.2.1-SNAPSHOT > Metamer 4.2.1-SNAPSHOT > Mojarra 2.1.5-SNAPSHOT > JBoss AS 7.1.0.Final > Java(TM) SE Runtime Environment 1.6.0_31-b04 @ Linux > Chrome 17.0.963.78 @ Linux i686 > ?RichFaces 4.2.1-SNAPSHOT > ?Metamer 4.2.1-SNAPSHOT > ?Mojarra 2.1.5-SNAPSHOT > ?JBoss AS 7.1.0.Final > ?Java(TM) SE Runtime Environment 1.6.0_31-b04 @ Linux > ?Internet Explorer 9.0 @ Win32 > Reporter: Jan Papousek > Assignee: Luk?? Fry? > Labels: Chrome, IE9 > Fix For: 4.2.1.CR1 > > > It's working correctly in Firefox 10. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 28 05:27:47 2012 From: jira-events at lists.jboss.org (Jan Papousek (JIRA)) Date: Wed, 28 Mar 2012 05:27:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12044) Metamer: @preventDefault attribute of rich:hotKey component doesn't work in IE 9 and Google Chrome In-Reply-To: <283065864.9549.1331739467659.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1438998121.36669.1332926867681.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679916#comment-12679916 ] Jan Papousek edited comment on RF-12044 at 3/28/12 5:27 AM: ------------------------------------------------------------ I've checked the behaviour with RichFaces 3.3.4. It seems to me that the component rich:hotkey idoesn't have any attribute to prevent defaults in 3.3.X and it doesn't prevent defaults automatically. So the key combinations like Ctrl+W (or Alt+X in IE 9) don't work correctly. was (Author: jpapouse): I've checked the behaviour with RichFaces 3.3.4. It seems to me that the component rich:hotkey doesn't have any attribute to prevent defaults and it doesn't prevent defaults automatically. So the key combinations like Ctrl+W (or Alt+X in IE 9) don't work correctly. > Metamer: @preventDefault attribute of rich:hotKey component doesn't work in IE 9 and Google Chrome > -------------------------------------------------------------------------------------------------- > > Key: RF-12044 > URL: https://issues.jboss.org/browse/RF-12044 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-misc > Affects Versions: 4.2.0.Final > Environment: RichFaces 4.2.1-SNAPSHOT > Metamer 4.2.1-SNAPSHOT > Mojarra 2.1.5-SNAPSHOT > JBoss AS 7.1.0.Final > Java(TM) SE Runtime Environment 1.6.0_31-b04 @ Linux > Chrome 17.0.963.78 @ Linux i686 > ?RichFaces 4.2.1-SNAPSHOT > ?Metamer 4.2.1-SNAPSHOT > ?Mojarra 2.1.5-SNAPSHOT > ?JBoss AS 7.1.0.Final > ?Java(TM) SE Runtime Environment 1.6.0_31-b04 @ Linux > ?Internet Explorer 9.0 @ Win32 > Reporter: Jan Papousek > Assignee: Luk?? Fry? > Labels: Chrome, IE9 > Fix For: 4.2.1.CR1 > > > It's working correctly in Firefox 10. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 28 05:37:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?J=C3=A1n_Jamrich_=28JIRA=29?=) Date: Wed, 28 Mar 2012 05:37:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12084) Richfaces 4.2 when inside dont work and causes 'identifier resolved to null' In-Reply-To: <1382382061.29574.1332701569056.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <825887521.36684.1332927467433.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] J?n Jamrich reassigned RF-12084: -------------------------------- Assignee: (was: J?n Jamrich) Issue simulated in Metamer. See Sources tab for more details. > Richfaces 4.2 when inside dont work and causes 'identifier resolved to null' > ----------------------------------------------------------------------------------------------------- > > Key: RF-12084 > URL: https://issues.jboss.org/browse/RF-12084 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.2.0.Final > Environment: Windows Vista, Firefox 11, Richfaces 4.2 Final, Mojarra 2.1.7, Tomcat 7.0.26 > Reporter: Ivan Costa > Labels: richfaces > > a4j:commandLink or a4j:ajax tags inside ui:fragment causes 'identifier resolved to null', > but h:commandLink + f:ajax (both from Mojarra) works perfectly fine! > The problem is described here > https://community.jboss.org/message/723859 > and here: > https://community.jboss.org/thread/196867 > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 28 05:41:48 2012 From: jira-events at lists.jboss.org (Jan Papousek (JIRA)) Date: Wed, 28 Mar 2012 05:41:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12082) Components: Output UI module doesn't pass unit tests (AbstractTogglePanelTest#testGetChildName) In-Reply-To: <147991329.28097.1332505547854.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <2109059964.36693.1332927708141.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679920#comment-12679920 ] Jan Papousek commented on RF-12082: ----------------------------------- To be more specific. What's the strategy of applying patches from 4.2.1 to 4.3.0? I think the issues for 4.3.0 having patches in 4.2.1 and waiting for merging should stay opened. > Components: Output UI module doesn't pass unit tests (AbstractTogglePanelTest#testGetChildName) > ----------------------------------------------------------------------------------------------- > > Key: RF-12082 > URL: https://issues.jboss.org/browse/RF-12082 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.3.0.Milestone1 > Reporter: Jan Papousek > Assignee: Brian Leathem > Priority: Critical > > {code} > ------------------------------------------------------------------------------- > Test set: org.richfaces.component.AbstractTogglePanelTest > ------------------------------------------------------------------------------- > Tests run: 5, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.022 sec <<< FAILURE! > testGetChildName(org.richfaces.component.AbstractTogglePanelTest) Time elapsed: 0.005 sec <<< FAILURE! > java.lang.AssertionError: Expected exception: java.lang.IllegalArgumentException > at org.junit.internal.runners.statements.ExpectException.evaluate(ExpectException.java:32) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) > at org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) > at org.junit.runners.ParentRunner.run(ParentRunner.java:236) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:234) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:133) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:114) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:188) > at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:166) > at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:86) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:101) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74) > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 28 05:51:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?J=C3=A1n_Jamrich_=28JIRA=29?=) Date: Wed, 28 Mar 2012 05:51:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11950) rich:findComponent does not retrieve the component for multiply-nested, dynamically generated tab components In-Reply-To: <25533681.21797.1328288808791.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1352859583.36730.1332928307618.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] J?n Jamrich reassigned RF-11950: -------------------------------- Assignee: J?n Jamrich > rich:findComponent does not retrieve the component for multiply-nested, dynamically generated tab components > ------------------------------------------------------------------------------------------------------------ > > Key: RF-11950 > URL: https://issues.jboss.org/browse/RF-11950 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: base functionality > Affects Versions: 4.1.0.Final > Environment: Websphere 8 - RAD 8 - JSF Mojorra 2.1.4 - Spring 3.0.6 Final - Firefox 10.0 - Windows 7 (6.1 sp1) > Reporter: Jean ANDRE > Assignee: J?n Jamrich > Fix For: 4.Future > > Attachments: index.xhtml, index.xhtml, listClient.xhtml, NestedWeb_RF-11950.zip, requestClientDocument.xhtml, requestClientDocument.xhtml, tabsClient.xhtml, tabsClient.xhtml > > > The rich:findComponent does not retrieve the component - What we want to achieve is to send .click() event on a command button. We got different errors depending the tests we made such as syntax error. > The involved code: > ------------------ > {code} > > > > value="#{msg['common.command.cancel']}" > onclick="#{rich:findComponent('#{activity.id}-closeCmd')}.click();;return false;" > render="#{tab.id}-tabsClient" > immediate="true" /> > {code} > The error we got: > ---------------- > {code} > syntax error - [Stopper sur une erreur] - jsf.js.jsf?ln=javax.faces (ligne 1) > .click();return false; > {code} > The corresponding view source: > ------------------------------ > {code} > onclick="jsf.util.chain(this,event,".click();return false;", > "RichFaces.ajax( \"tabbedForm:TAB_CLIENT\\u002D1\\u002Drcd\\u002DcancelCreateCmd\",event,{\"incId\":\"1\"} )"); > return false;" > name="tabbedForm:TAB_CLIENT-1-rcd-cancelCreateCmd" id="tabbedForm:TAB_CLIENT-1-rcd-cancelCreateCmd"> > {code} > The generated javaScript under firebug: > -------------------------------------- > {code} > function onclick(event) { > jsf.util.chain(this, event, ".click();return false;", "RichFaces.ajax(\"tabbedForm:TAB_CLIENT\\u002D1\\u002Drcd\\u002DcancelCreateCmd\",event,{\"incId\":\"1\"} )"); > return false; > } > {code} > If we hard code the Id instead of the calculated one we got following error: > {code} > uncaught exception: Syntax error, unrecognized expression: TAB_CLIENT-1-TAB_RCD-closeCmd > Line 0 > {code} > The generated javaScript under firebug: > -------------------------------------- > {code} > function anonymous(event) { > rich: > findComponent("TAB_CLIENT-1-TAB_RCD-closeCmd").click(); > return false; > } > {code} > If we use directly jQuery: > {code} > > > > value="#{msg['common.command.cancel']}" > onclick="$('##{activity.id}-closeCmd').click();return false;" > render="desktopTabPanel" > immediate="true" /> > {code} > {code} > missing ; before statement > http://localhost:12000/crm/javax.faces.resource/jsf.js.jsf?ln=javax.faces > Line 1 > {code} > If we hardcode an existing static Id, we got the error as shown the screen capture: > {code} > function onclick(event) { > jsf.util.chain(this, event, "org.richfaces.component.UICommandButton at 39de2ca.click();", "RichFaces.ajax(\"tabbedForm:TAB_CLIENT\\u002D1\\u002Drcd\\u002DcancelCreateCmd\",event,{\"incId\":\"1\"} )"); > return false; > } > {code} > {code} > value="#{msg['common.command.cancel']}" > onclick="#{rich:findComponent('qsearchClient')}.click();" > render="#{tab.id}-tabsClient" > immediate="true" />  > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 28 07:21:48 2012 From: jira-events at lists.jboss.org (Jan Papousek (JIRA)) Date: Wed, 28 Mar 2012 07:21:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11560) Showcase on OpenShift Express: Push stops to work after first long-polling request In-Reply-To: <703843376.3936.1318926525118.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1907121326.36990.1332933708502.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Papousek resolved RF-11560. ------------------------------- Labels: openshift (was: ) Fix Version/s: 4.2.1.CR1 Resolution: Cannot Reproduce Bug > Showcase on OpenShift Express: Push stops to work after first long-polling request > ---------------------------------------------------------------------------------- > > Key: RF-11560 > URL: https://issues.jboss.org/browse/RF-11560 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll, showcase > Affects Versions: 4.1.0.Milestone3 > Reporter: Luk?? Fry? > Assignee: Jan Papousek > Labels: openshift > Fix For: 4.2.1.CR1 > > > Both demos affected: TopicsContext and Push CDI. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 28 09:11:47 2012 From: jira-events at lists.jboss.org (Juraj Huska (JIRA)) Date: Wed, 28 Mar 2012 09:11:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12107) Kitchensink archetype - comments additions to the generated pom.xml Message-ID: <713779216.37241.1332940307373.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Juraj Huska created RF-12107: -------------------------------- Summary: Kitchensink archetype - comments additions to the generated pom.xml Key: RF-12107 URL: https://issues.jboss.org/browse/RF-12107 Project: RichFaces Issue Type: Enhancement Security Level: Public (Everyone can see) Components: archetype Affects Versions: 4.2.0.Final Environment: app generated by Kitchensink archetype Reporter: Juraj Huska Priority: Optional I would like to suggest some comments additions, to increase user's comprehension. - _To the comment above arq-jbossas-managed profile:_ There should be mentioned that you have to provide path to your JBoss instance, by changing the jbossHome property in arquillian.xml, or we can alter the profile to download and unzip JBoss distribution as it is [here|https://github.com/richfaces/qa/blob/master/pom.xml#L559]. - _In the same comment as mentioned above_ There should be definitely mentioned the version of JBoss AS it works with, or there should be this version defined explicitly, since it does not work with all AS 7 distributions - _The comment above arq-jbossas-remote profile_ There is the same problem with JBoss AS versions as mentioned above. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 28 09:52:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 28 Mar 2012 09:52:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-10754) extendedDataTable: two or more components placed on the page causes horizontal scroll to disappear In-Reply-To: <1257024085.24840.1300129130468.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <989489984.37473.1332942767928.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-10754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved RF-10754. ----------------------------- Assignee: Luk?? Fry? Fix Version/s: 4.2.1.CR1 (was: 4.Future) Resolution: Done EDT scrolling feature rewritten. > extendedDataTable: two or more components placed on the page causes horizontal scroll to disappear > -------------------------------------------------------------------------------------------------- > > Key: RF-10754 > URL: https://issues.jboss.org/browse/RF-10754 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.0.0.Final > Reporter: Ilya Shaikovsky > Assignee: Luk?? Fry? > Fix For: 4.2.1.CR1 > > > just get any example where table has horizontal scroll and add one more table by copy/paste. (change id's if need) > result: scroll disappear. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 28 09:54:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 28 Mar 2012 09:54:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-10754) extendedDataTable: two or more components placed on the page causes horizontal scroll to disappear In-Reply-To: <1257024085.24840.1300129130468.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <677496116.37484.1332942887739.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-10754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12680016#comment-12680016 ] Luk?? Fry? commented on RF-10754: --------------------------------- Thanks for the hint Peter, I have used it as the base for the rewritten version of scrolling feature. I would appreciate your feedback how the new version stands in {{4.2.1.CR1}}. Let's take in the wild! > extendedDataTable: two or more components placed on the page causes horizontal scroll to disappear > -------------------------------------------------------------------------------------------------- > > Key: RF-10754 > URL: https://issues.jboss.org/browse/RF-10754 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.0.0.Final > Reporter: Ilya Shaikovsky > Assignee: Luk?? Fry? > Fix For: 4.2.1.CR1 > > > just get any example where table has horizontal scroll and add one more table by copy/paste. (change id's if need) > result: scroll disappear. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 28 09:54:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 28 Mar 2012 09:54:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11884) Multiple Errors with IE8/9 In-Reply-To: <1562607854.56099.1326530722497.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1133561328.37490.1332942887960.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12680017#comment-12680017 ] Luk?? Fry? commented on RF-11884: --------------------------------- Problem 4: scrolling feature rewritten (RF-10754) > Multiple Errors with IE8/9 > -------------------------- > > Key: RF-11884 > URL: https://issues.jboss.org/browse/RF-11884 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes, component-tables, component-tree > Environment: Windows 7 64, Tomcat 7.0.23, Mojarra 2.1.3, IE8/9 (all errors), Chrome 16.09 (one problem), PrimesFaces 2.2.1 (ChartGraphics only, problems still persist when PF is removed) > Reporter: Friedhelm Kuehn > Assignee: Luk?? Fry? > Priority: Critical > Fix For: 4.2.1.CR1 > > Attachments: ProgramVariable_Table.xhtml, Richfaces_4.1_Problems.pdf, Richfaces_4.1_Problems_Konfiguration.pdf, Test.war > > > Problem 1: Shaded TabbedPane Tabs, not changing color when tabbing. Big spacing area below tabs (height about 20 px, should be 2px). > Problem 2: Content of not-popped-up Popup-Panel is not visible, but an area is claimed on screen. > Problem 3: with icon: Icon is surrounded by dark border > Problem 4: No Horzontal-Scroller in ExtendDatatable (with Chrome also). > Problem 5: Use of IconCollapsed/..Expanded creates double Icons in TreeNode > Problem 6: Javascript Error in ExtendedDataTable.js > Biggest Problem: We have to deliver our application in a few weeks. Support for IE8/9 is hard customer requirement. > I have a made a documentation for each problem, but don't find a way to attach a PDF to this issue - ?? > Please help ! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 28 10:07:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 28 Mar 2012 10:07:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11884) Multiple Errors with IE8/9 In-Reply-To: <1562607854.56099.1326530722497.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <644577994.37555.1332943667545.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12680027#comment-12680027 ] Luk?? Fry? commented on RF-11884: --------------------------------- Problem 1 and 2: Problem is caused by switching IE to Quirks mode, when forced to use IE8/IE9 engine, it works fine. Let's force the browser to use right mode: {code:xml} {code} {code:xml} {code} > Multiple Errors with IE8/9 > -------------------------- > > Key: RF-11884 > URL: https://issues.jboss.org/browse/RF-11884 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes, component-tables, component-tree > Environment: Windows 7 64, Tomcat 7.0.23, Mojarra 2.1.3, IE8/9 (all errors), Chrome 16.09 (one problem), PrimesFaces 2.2.1 (ChartGraphics only, problems still persist when PF is removed) > Reporter: Friedhelm Kuehn > Assignee: Luk?? Fry? > Priority: Critical > Fix For: 4.2.1.CR1 > > Attachments: ProgramVariable_Table.xhtml, Richfaces_4.1_Problems.pdf, Richfaces_4.1_Problems_Konfiguration.pdf, Test.war > > > Problem 1: Shaded TabbedPane Tabs, not changing color when tabbing. Big spacing area below tabs (height about 20 px, should be 2px). > Problem 2: Content of not-popped-up Popup-Panel is not visible, but an area is claimed on screen. > Problem 3: with icon: Icon is surrounded by dark border > Problem 4: No Horzontal-Scroller in ExtendDatatable (with Chrome also). > Problem 5: Use of IconCollapsed/..Expanded creates double Icons in TreeNode > Problem 6: Javascript Error in ExtendedDataTable.js > Biggest Problem: We have to deliver our application in a few weeks. Support for IE8/9 is hard customer requirement. > I have a made a documentation for each problem, but don't find a way to attach a PDF to this issue - ?? > Please help ! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 28 10:19:49 2012 From: jira-events at lists.jboss.org (Artur Mioduszewski (JIRA)) Date: Wed, 28 Mar 2012 10:19:49 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12108) components are not rerendered after ajax action if attribute ajaxRendered="true" inside Message-ID: <975271229.37623.1332944389491.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Artur Mioduszewski created RF-12108: --------------------------------------- Summary: components are not rerendered after ajax action if attribute ajaxRendered="true" inside Key: RF-12108 URL: https://issues.jboss.org/browse/RF-12108 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.2.0.Final Environment: JDK1.6, JBoss 6.0.Final, richfaces 4.1.0.Final/4.2.0.Final seam 3.1 IE 9 Reporter: Artur Mioduszewski In case getting 2 tabs (in my case it is primefaces tabs): {code:title=RENDERING ON SECOND TAB NOT WORKS (after clicking link)} 1. tab: 2. tab (some code with ajax) Ex. {code} {code:title=RENDERING ON SECOND TAB NOT WORKS (after clicking link)} 1. tab: 2. tab (some code with ajax) Ex. {code} When I change tabs order, problem does not exist. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 28 10:23:47 2012 From: jira-events at lists.jboss.org (Artur Mioduszewski (JIRA)) Date: Wed, 28 Mar 2012 10:23:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12108) Components second tab changes are not rendered after performing some ajax action if attribute ajaxRendered="true" inside located on first tab In-Reply-To: <975271229.37623.1332944389491.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <878469612.37651.1332944627825.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artur Mioduszewski updated RF-12108: ------------------------------------ Summary: Components second tab changes are not rendered after performing some ajax action if attribute ajaxRendered="true" inside located on first tab (was: components are not rerendered after ajax action if attribute ajaxRendered="true" inside ) > Components second tab changes are not rendered after performing some ajax action if attribute ajaxRendered="true" inside located on first tab > --------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: RF-12108 > URL: https://issues.jboss.org/browse/RF-12108 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.2.0.Final > Environment: JDK1.6, > JBoss 6.0.Final, > richfaces 4.1.0.Final/4.2.0.Final > seam 3.1 > IE 9 > Reporter: Artur Mioduszewski > > In case getting 2 tabs (in my case it is primefaces tabs): > {code:title=RENDERING ON SECOND TAB NOT WORKS (after clicking link)} > 1. tab: > > > > > 2. tab (some code with ajax) > Ex. > > > > > {code} > {code:title=RENDERING ON SECOND TAB NOT WORKS (after clicking link)} > 1. tab: > > > > > 2. tab (some code with ajax) > Ex. > > > > > {code} > When I change tabs order, problem does not exist. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 28 10:25:47 2012 From: jira-events at lists.jboss.org (Artur Mioduszewski (JIRA)) Date: Wed, 28 Mar 2012 10:25:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12108) Components second tab changes are not rendered after performing some ajax action if attribute ajaxRendered="true" inside located on first tab In-Reply-To: <975271229.37623.1332944389491.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <341971274.37657.1332944747647.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artur Mioduszewski updated RF-12108: ------------------------------------ Workaround Description: Setting rich:message attribute ajaxRendered="false" (was: Setting message attribute ajaxRendered="false" ) > Components second tab changes are not rendered after performing some ajax action if attribute ajaxRendered="true" inside located on first tab > --------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: RF-12108 > URL: https://issues.jboss.org/browse/RF-12108 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.2.0.Final > Environment: JDK1.6, > JBoss 6.0.Final, > richfaces 4.1.0.Final/4.2.0.Final > seam 3.1 > IE 9 > Reporter: Artur Mioduszewski > > In case getting 2 tabs (in my case it is primefaces tabs): > {code:title=RENDERING ON SECOND TAB NOT WORKS (after clicking link)} > 1. tab: > > > > > 2. tab (some code with ajax) > Ex. > > > > > {code} > {code:title=RENDERING ON SECOND TAB NOT WORKS (after clicking link)} > 1. tab: > > > > > 2. tab (some code with ajax) > Ex. > > > > > {code} > When I change tabs order, problem does not exist. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 28 10:35:51 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 28 Mar 2012 10:35:51 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11884) Multiple Errors with IE8/9 In-Reply-To: <1562607854.56099.1326530722497.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <616850657.37777.1332945351546.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12680044#comment-12680044 ] Luk?? Fry? commented on RF-11884: --------------------------------- I cannot reproduce *Problem 5* either. [{{dev-examples/iteration-demo}}|https://github.com/richfaces/dev-examples/tree/4085ca9b07438d2474bb6cc20cd59dbbd4abaef6/iteration-demo] works fine in IE modes. > Multiple Errors with IE8/9 > -------------------------- > > Key: RF-11884 > URL: https://issues.jboss.org/browse/RF-11884 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes, component-tables, component-tree > Environment: Windows 7 64, Tomcat 7.0.23, Mojarra 2.1.3, IE8/9 (all errors), Chrome 16.09 (one problem), PrimesFaces 2.2.1 (ChartGraphics only, problems still persist when PF is removed) > Reporter: Friedhelm Kuehn > Assignee: Luk?? Fry? > Priority: Critical > Fix For: 4.2.1.CR1 > > Attachments: ProgramVariable_Table.xhtml, Richfaces_4.1_Problems.pdf, Richfaces_4.1_Problems_Konfiguration.pdf, Test.war > > > Problem 1: Shaded TabbedPane Tabs, not changing color when tabbing. Big spacing area below tabs (height about 20 px, should be 2px). > Problem 2: Content of not-popped-up Popup-Panel is not visible, but an area is claimed on screen. > Problem 3: with icon: Icon is surrounded by dark border > Problem 4: No Horzontal-Scroller in ExtendDatatable (with Chrome also). > Problem 5: Use of IconCollapsed/..Expanded creates double Icons in TreeNode > Problem 6: Javascript Error in ExtendedDataTable.js > Biggest Problem: We have to deliver our application in a few weeks. Support for IE8/9 is hard customer requirement. > I have a made a documentation for each problem, but don't find a way to attach a PDF to this issue - ?? > Please help ! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 28 10:39:48 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 28 Mar 2012 10:39:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11884) Multiple Errors with IE8/9 In-Reply-To: <1562607854.56099.1326530722497.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <879396154.37794.1332945588133.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12680046#comment-12680046 ] Luk?? Fry? commented on RF-11884: --------------------------------- I cannot reproduce *Problem 6* either. In the code, I can see there might be theoretically negative value provided as the {{style.height}}. But without proper example we can't address this issue. > Multiple Errors with IE8/9 > -------------------------- > > Key: RF-11884 > URL: https://issues.jboss.org/browse/RF-11884 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes, component-tables, component-tree > Environment: Windows 7 64, Tomcat 7.0.23, Mojarra 2.1.3, IE8/9 (all errors), Chrome 16.09 (one problem), PrimesFaces 2.2.1 (ChartGraphics only, problems still persist when PF is removed) > Reporter: Friedhelm Kuehn > Assignee: Luk?? Fry? > Priority: Critical > Fix For: 4.2.1.CR1 > > Attachments: ProgramVariable_Table.xhtml, Richfaces_4.1_Problems.pdf, Richfaces_4.1_Problems_Konfiguration.pdf, Test.war > > > Problem 1: Shaded TabbedPane Tabs, not changing color when tabbing. Big spacing area below tabs (height about 20 px, should be 2px). > Problem 2: Content of not-popped-up Popup-Panel is not visible, but an area is claimed on screen. > Problem 3: with icon: Icon is surrounded by dark border > Problem 4: No Horzontal-Scroller in ExtendDatatable (with Chrome also). > Problem 5: Use of IconCollapsed/..Expanded creates double Icons in TreeNode > Problem 6: Javascript Error in ExtendedDataTable.js > Biggest Problem: We have to deliver our application in a few weeks. Support for IE8/9 is hard customer requirement. > I have a made a documentation for each problem, but don't find a way to attach a PDF to this issue - ?? > Please help ! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 28 10:41:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 28 Mar 2012 10:41:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11884) Multiple Errors with IE8/9 In-Reply-To: <1562607854.56099.1326530722497.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1378919520.37799.1332945707523.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12680047#comment-12680047 ] Luk?? Fry? commented on RF-11884: --------------------------------- I would like to ask you to provide *Short, Self Contained, Correct (Runnable), Example* and report each issue separately. Please consider reading [Submitting effective issue report|https://community.jboss.org/wiki/SubmittingEffectiveIssueReports]. > Multiple Errors with IE8/9 > -------------------------- > > Key: RF-11884 > URL: https://issues.jboss.org/browse/RF-11884 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes, component-tables, component-tree > Environment: Windows 7 64, Tomcat 7.0.23, Mojarra 2.1.3, IE8/9 (all errors), Chrome 16.09 (one problem), PrimesFaces 2.2.1 (ChartGraphics only, problems still persist when PF is removed) > Reporter: Friedhelm Kuehn > Assignee: Luk?? Fry? > Priority: Critical > Fix For: 4.2.1.CR1 > > Attachments: ProgramVariable_Table.xhtml, Richfaces_4.1_Problems.pdf, Richfaces_4.1_Problems_Konfiguration.pdf, Test.war > > > Problem 1: Shaded TabbedPane Tabs, not changing color when tabbing. Big spacing area below tabs (height about 20 px, should be 2px). > Problem 2: Content of not-popped-up Popup-Panel is not visible, but an area is claimed on screen. > Problem 3: with icon: Icon is surrounded by dark border > Problem 4: No Horzontal-Scroller in ExtendDatatable (with Chrome also). > Problem 5: Use of IconCollapsed/..Expanded creates double Icons in TreeNode > Problem 6: Javascript Error in ExtendedDataTable.js > Biggest Problem: We have to deliver our application in a few weeks. Support for IE8/9 is hard customer requirement. > I have a made a documentation for each problem, but don't find a way to attach a PDF to this issue - ?? > Please help ! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 28 10:47:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 28 Mar 2012 10:47:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11884) Multiple Errors with IE8/9 In-Reply-To: <1562607854.56099.1326530722497.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <351129996.37823.1332946067562.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12680047#comment-12680047 ] Luk?? Fry? edited comment on RF-11884 at 3/28/12 10:45 AM: ----------------------------------------------------------- I would like to ask you to provide *Short, Self Contained, Correct (Runnable), Example* and report each issue separately. Please take your time with reporting issues - it's highly appreciated to scan through JIRA and make sure there is no similar issue reported. Once you report issue, make it as clear as possible. Consider reading [Submitting effective issue report|https://community.jboss.org/wiki/SubmittingEffectiveIssueReports]. was (Author: lfryc): I would like to ask you to provide *Short, Self Contained, Correct (Runnable), Example* and report each issue separately. Please consider reading [Submitting effective issue report|https://community.jboss.org/wiki/SubmittingEffectiveIssueReports]. > Multiple Errors with IE8/9 > -------------------------- > > Key: RF-11884 > URL: https://issues.jboss.org/browse/RF-11884 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes, component-tables, component-tree > Environment: Windows 7 64, Tomcat 7.0.23, Mojarra 2.1.3, IE8/9 (all errors), Chrome 16.09 (one problem), PrimesFaces 2.2.1 (ChartGraphics only, problems still persist when PF is removed) > Reporter: Friedhelm Kuehn > Assignee: Luk?? Fry? > Priority: Critical > Fix For: 4.2.1.CR1 > > Attachments: ProgramVariable_Table.xhtml, Richfaces_4.1_Problems.pdf, Richfaces_4.1_Problems_Konfiguration.pdf, Test.war > > > Problem 1: Shaded TabbedPane Tabs, not changing color when tabbing. Big spacing area below tabs (height about 20 px, should be 2px). > Problem 2: Content of not-popped-up Popup-Panel is not visible, but an area is claimed on screen. > Problem 3: with icon: Icon is surrounded by dark border > Problem 4: No Horzontal-Scroller in ExtendDatatable (with Chrome also). > Problem 5: Use of IconCollapsed/..Expanded creates double Icons in TreeNode > Problem 6: Javascript Error in ExtendedDataTable.js > Biggest Problem: We have to deliver our application in a few weeks. Support for IE8/9 is hard customer requirement. > I have a made a documentation for each problem, but don't find a way to attach a PDF to this issue - ?? > Please help ! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 28 10:47:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 28 Mar 2012 10:47:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11884) Multiple Errors with IE8/9 In-Reply-To: <1562607854.56099.1326530722497.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <217603568.37831.1332946067841.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12680027#comment-12680027 ] Luk?? Fry? edited comment on RF-11884 at 3/28/12 10:47 AM: ----------------------------------------------------------- Problem 1 and 2: Problem is caused by switching IE to Quirks mode, when forced to use IE8/IE9 engine, it works fine. Let's force the browser to use right mode: {code:xml} {code} {code:xml} {code} Further reading: [Defining Document Compatibility (msdn.microsoft.com)|http://msdn.microsoft.com/en-us/library/ie/cc288325(v=vs.85).aspx] was (Author: lfryc): Problem 1 and 2: Problem is caused by switching IE to Quirks mode, when forced to use IE8/IE9 engine, it works fine. Let's force the browser to use right mode: {code:xml} {code} {code:xml} {code} > Multiple Errors with IE8/9 > -------------------------- > > Key: RF-11884 > URL: https://issues.jboss.org/browse/RF-11884 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes, component-tables, component-tree > Environment: Windows 7 64, Tomcat 7.0.23, Mojarra 2.1.3, IE8/9 (all errors), Chrome 16.09 (one problem), PrimesFaces 2.2.1 (ChartGraphics only, problems still persist when PF is removed) > Reporter: Friedhelm Kuehn > Assignee: Luk?? Fry? > Priority: Critical > Fix For: 4.2.1.CR1 > > Attachments: ProgramVariable_Table.xhtml, Richfaces_4.1_Problems.pdf, Richfaces_4.1_Problems_Konfiguration.pdf, Test.war > > > Problem 1: Shaded TabbedPane Tabs, not changing color when tabbing. Big spacing area below tabs (height about 20 px, should be 2px). > Problem 2: Content of not-popped-up Popup-Panel is not visible, but an area is claimed on screen. > Problem 3: with icon: Icon is surrounded by dark border > Problem 4: No Horzontal-Scroller in ExtendDatatable (with Chrome also). > Problem 5: Use of IconCollapsed/..Expanded creates double Icons in TreeNode > Problem 6: Javascript Error in ExtendedDataTable.js > Biggest Problem: We have to deliver our application in a few weeks. Support for IE8/9 is hard customer requirement. > I have a made a documentation for each problem, but don't find a way to attach a PDF to this issue - ?? > Please help ! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 28 10:49:48 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 28 Mar 2012 10:49:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11884) Multiple Errors with IE8/9 In-Reply-To: <1562607854.56099.1326530722497.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <294977038.37857.1332946188440.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12680055#comment-12680055 ] Luk?? Fry? commented on RF-11884: --------------------------------- If you would have more details to any of these details, please open new issue and link to this one. > Multiple Errors with IE8/9 > -------------------------- > > Key: RF-11884 > URL: https://issues.jboss.org/browse/RF-11884 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes, component-tables, component-tree > Environment: Windows 7 64, Tomcat 7.0.23, Mojarra 2.1.3, IE8/9 (all errors), Chrome 16.09 (one problem), PrimesFaces 2.2.1 (ChartGraphics only, problems still persist when PF is removed) > Reporter: Friedhelm Kuehn > Assignee: Luk?? Fry? > Priority: Critical > Fix For: 4.2.1.CR1 > > Attachments: ProgramVariable_Table.xhtml, Richfaces_4.1_Problems.pdf, Richfaces_4.1_Problems_Konfiguration.pdf, Test.war > > > Problem 1: Shaded TabbedPane Tabs, not changing color when tabbing. Big spacing area below tabs (height about 20 px, should be 2px). > Problem 2: Content of not-popped-up Popup-Panel is not visible, but an area is claimed on screen. > Problem 3: with icon: Icon is surrounded by dark border > Problem 4: No Horzontal-Scroller in ExtendDatatable (with Chrome also). > Problem 5: Use of IconCollapsed/..Expanded creates double Icons in TreeNode > Problem 6: Javascript Error in ExtendedDataTable.js > Biggest Problem: We have to deliver our application in a few weeks. Support for IE8/9 is hard customer requirement. > I have a made a documentation for each problem, but don't find a way to attach a PDF to this issue - ?? > Please help ! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 28 10:49:48 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 28 Mar 2012 10:49:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11884) Multiple Errors with IE8/9 In-Reply-To: <1562607854.56099.1326530722497.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <2001851539.37862.1332946188615.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved RF-11884. ----------------------------- Resolution: Partially Completed > Multiple Errors with IE8/9 > -------------------------- > > Key: RF-11884 > URL: https://issues.jboss.org/browse/RF-11884 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes, component-tables, component-tree > Environment: Windows 7 64, Tomcat 7.0.23, Mojarra 2.1.3, IE8/9 (all errors), Chrome 16.09 (one problem), PrimesFaces 2.2.1 (ChartGraphics only, problems still persist when PF is removed) > Reporter: Friedhelm Kuehn > Assignee: Luk?? Fry? > Priority: Critical > Fix For: 4.2.1.CR1 > > Attachments: ProgramVariable_Table.xhtml, Richfaces_4.1_Problems.pdf, Richfaces_4.1_Problems_Konfiguration.pdf, Test.war > > > Problem 1: Shaded TabbedPane Tabs, not changing color when tabbing. Big spacing area below tabs (height about 20 px, should be 2px). > Problem 2: Content of not-popped-up Popup-Panel is not visible, but an area is claimed on screen. > Problem 3: with icon: Icon is surrounded by dark border > Problem 4: No Horzontal-Scroller in ExtendDatatable (with Chrome also). > Problem 5: Use of IconCollapsed/..Expanded creates double Icons in TreeNode > Problem 6: Javascript Error in ExtendedDataTable.js > Biggest Problem: We have to deliver our application in a few weeks. Support for IE8/9 is hard customer requirement. > I have a made a documentation for each problem, but don't find a way to attach a PDF to this issue - ?? > Please help ! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 28 10:49:48 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 28 Mar 2012 10:49:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11884) Multiple Errors with IE8/9 In-Reply-To: <1562607854.56099.1326530722497.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1542946896.37864.1332946188678.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12680055#comment-12680055 ] Luk?? Fry? edited comment on RF-11884 at 3/28/12 10:49 AM: ----------------------------------------------------------- If you would have more details to any of these problems, please open new issue and link to this one. was (Author: lfryc): If you would have more details to any of these details, please open new issue and link to this one. > Multiple Errors with IE8/9 > -------------------------- > > Key: RF-11884 > URL: https://issues.jboss.org/browse/RF-11884 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes, component-tables, component-tree > Environment: Windows 7 64, Tomcat 7.0.23, Mojarra 2.1.3, IE8/9 (all errors), Chrome 16.09 (one problem), PrimesFaces 2.2.1 (ChartGraphics only, problems still persist when PF is removed) > Reporter: Friedhelm Kuehn > Assignee: Luk?? Fry? > Priority: Critical > Fix For: 4.2.1.CR1 > > Attachments: ProgramVariable_Table.xhtml, Richfaces_4.1_Problems.pdf, Richfaces_4.1_Problems_Konfiguration.pdf, Test.war > > > Problem 1: Shaded TabbedPane Tabs, not changing color when tabbing. Big spacing area below tabs (height about 20 px, should be 2px). > Problem 2: Content of not-popped-up Popup-Panel is not visible, but an area is claimed on screen. > Problem 3: with icon: Icon is surrounded by dark border > Problem 4: No Horzontal-Scroller in ExtendDatatable (with Chrome also). > Problem 5: Use of IconCollapsed/..Expanded creates double Icons in TreeNode > Problem 6: Javascript Error in ExtendedDataTable.js > Biggest Problem: We have to deliver our application in a few weeks. Support for IE8/9 is hard customer requirement. > I have a made a documentation for each problem, but don't find a way to attach a PDF to this issue - ?? > Please help ! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 28 10:51:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 28 Mar 2012 10:51:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-10754) extendedDataTable: two or more components placed on the page causes horizontal scroll to disappear In-Reply-To: <1257024085.24840.1300129130468.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1976666805.37877.1332946307961.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-10754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12680016#comment-12680016 ] Luk?? Fry? edited comment on RF-10754 at 3/28/12 10:50 AM: ----------------------------------------------------------- Thanks for the hint Peter, I have used it as the base for the rewritten version of scrolling feature. I would appreciate your feedback how the new version stands in {{4.2.1.CR1}}. Let's check it in the wild! was (Author: lfryc): Thanks for the hint Peter, I have used it as the base for the rewritten version of scrolling feature. I would appreciate your feedback how the new version stands in {{4.2.1.CR1}}. Let's take in the wild! > extendedDataTable: two or more components placed on the page causes horizontal scroll to disappear > -------------------------------------------------------------------------------------------------- > > Key: RF-10754 > URL: https://issues.jboss.org/browse/RF-10754 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.0.0.Final > Reporter: Ilya Shaikovsky > Assignee: Luk?? Fry? > Fix For: 4.2.1.CR1 > > > just get any example where table has horizontal scroll and add one more table by copy/paste. (change id's if need) > result: scroll disappear. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 28 11:01:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 28 Mar 2012 11:01:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12044) Metamer: @preventDefault attribute of rich:hotKey component doesn't work in IE 9 and Google Chrome In-Reply-To: <283065864.9549.1331739467659.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <806396444.37907.1332946907573.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12680056#comment-12680056 ] Luk?? Fry? commented on RF-12044: --------------------------------- Jan, I think preventing defaults events works out of the box in RF3: see line 92 in [hotKey.js|http://anonsvn.jboss.org/repos/richfaces/branches/community/3.3.X/ui/hotKey/src/main/resources/org/richfaces/renderkit/html/scripts/hotKey.js] > Metamer: @preventDefault attribute of rich:hotKey component doesn't work in IE 9 and Google Chrome > -------------------------------------------------------------------------------------------------- > > Key: RF-12044 > URL: https://issues.jboss.org/browse/RF-12044 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-misc > Affects Versions: 4.2.0.Final > Environment: RichFaces 4.2.1-SNAPSHOT > Metamer 4.2.1-SNAPSHOT > Mojarra 2.1.5-SNAPSHOT > JBoss AS 7.1.0.Final > Java(TM) SE Runtime Environment 1.6.0_31-b04 @ Linux > Chrome 17.0.963.78 @ Linux i686 > ?RichFaces 4.2.1-SNAPSHOT > ?Metamer 4.2.1-SNAPSHOT > ?Mojarra 2.1.5-SNAPSHOT > ?JBoss AS 7.1.0.Final > ?Java(TM) SE Runtime Environment 1.6.0_31-b04 @ Linux > ?Internet Explorer 9.0 @ Win32 > Reporter: Jan Papousek > Assignee: Luk?? Fry? > Labels: Chrome, IE9 > Fix For: 4.2.1.CR1 > > > It's working correctly in Firefox 10. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 28 11:25:47 2012 From: jira-events at lists.jboss.org (Jan Papousek (JIRA)) Date: Wed, 28 Mar 2012 11:25:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12044) Metamer: @preventDefault attribute of rich:hotKey component doesn't work in IE 9 and Google Chrome In-Reply-To: <283065864.9549.1331739467659.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <968976384.37963.1332948347459.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12680061#comment-12680061 ] Jan Papousek commented on RF-12044: ----------------------------------- Lukas: You are right. It is working in Firefox 10, but it isn't working in Google Chrome and IE 9. > Metamer: @preventDefault attribute of rich:hotKey component doesn't work in IE 9 and Google Chrome > -------------------------------------------------------------------------------------------------- > > Key: RF-12044 > URL: https://issues.jboss.org/browse/RF-12044 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-misc > Affects Versions: 4.2.0.Final > Environment: RichFaces 4.2.1-SNAPSHOT > Metamer 4.2.1-SNAPSHOT > Mojarra 2.1.5-SNAPSHOT > JBoss AS 7.1.0.Final > Java(TM) SE Runtime Environment 1.6.0_31-b04 @ Linux > Chrome 17.0.963.78 @ Linux i686 > ?RichFaces 4.2.1-SNAPSHOT > ?Metamer 4.2.1-SNAPSHOT > ?Mojarra 2.1.5-SNAPSHOT > ?JBoss AS 7.1.0.Final > ?Java(TM) SE Runtime Environment 1.6.0_31-b04 @ Linux > ?Internet Explorer 9.0 @ Win32 > Reporter: Jan Papousek > Assignee: Luk?? Fry? > Labels: Chrome, IE9 > Fix For: 4.2.1.CR1 > > > It's working correctly in Firefox 10. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 28 11:31:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 28 Mar 2012 11:31:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12109) Showcase in AS 7.1.1 (JSF 2.1.7) missing doctype and root Message-ID: <1464963313.37982.1332948707417.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Brian Leathem created RF-12109: ---------------------------------- Summary: Showcase in AS 7.1.1 (JSF 2.1.7) missing doctype and root Key: RF-12109 URL: https://issues.jboss.org/browse/RF-12109 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: showcase Reporter: Brian Leathem Assignee: Brian Leathem Priority: Critical Fix For: 4.2.1.CR1 Changes to how ui:include and templates are processed in Mojarra 2.1.7 result in the doctype and html root element being omitted from the showcase. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 28 11:39:47 2012 From: jira-events at lists.jboss.org (Rene O (JIRA)) Date: Wed, 28 Mar 2012 11:39:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11948) rich:extendedDataTable generates a js-error stating this.normalPartStyle is undefined In-Reply-To: <2050628653.20854.1328272188456.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1943236373.37991.1332949187400.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12680067#comment-12680067 ] Rene O commented on RF-11948: ----------------------------- To make things a little bit clearer, here is another example which demonstrates my problem better: {code:title="mainpage"} JSF Test {code} {code:title="includeA - active at start"} {code} {code:title="includeB - active if button within includeA is clicked"} ColA #{item.a}
    {code} The oncomplete-workaround to resize the table fails with an js error because the table itself doesn't exists during ajax execution: Zeitstempel: 28.03.2012 17:37:45 Fehler: syntax error Quelldatei: http://localhost:8080/jsf2testcase/javax.faces.resource/richfaces.js.jsf Zeile: 481 Quelltext: .setColumnWidth('colA','500');; > rich:extendedDataTable generates a js-error stating this.normalPartStyle is undefined > ------------------------------------------------------------------------------------- > > Key: RF-11948 > URL: https://issues.jboss.org/browse/RF-11948 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.2.0.CR1 > Environment: richfaces-4.2.0-SNAPSHOT, Firefox 10, IE8 > Reporter: Rene O > Assignee: Brian Leathem > Fix For: 4.2.1.CR1 > > > If you use rich:extendedDataTable and manually set the width of a column afterwards, a js error occurs > {code:title=page-snippet to reproduce the issue} > > xmlns:h="http://java.sun.com/jsf/html" > xmlns:f="http://java.sun.com/jsf/core" > xmlns:ui="http://java.sun.com/jsf/facelets" > xmlns:a4j="http://richfaces.org/a4j" > xmlns:rich="http://richfaces.org/rich" > > > > JSF Test > > > > > > > > > > ColA > > #{item.itemA} > > > > > > > {code} > {code:title=js error} > Fehler: this.normalPartStyle is undefined > Quelldatei: http://localhost:8080/jsftest/javax.faces.resource/extendedDataTable.js.jsf?ln=org.richfaces > Zeile: 279 > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 28 12:21:47 2012 From: jira-events at lists.jboss.org (Artur Mioduszewski (JIRA)) Date: Wed, 28 Mar 2012 12:21:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12108) Components second tab changes are not rendered after performing some ajax action if attribute ajaxRendered="true" inside located on first tab In-Reply-To: <975271229.37623.1332944389491.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1429606304.38142.1332951707910.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artur Mioduszewski updated RF-12108: ------------------------------------ Description: In case getting 2 tabs (in my case it is primefaces tabs): {code:title=RENDERING ON SECOND TAB NOT WORKS (after clicking link)} 1. tab: 2. tab (some code with ajax) Ex. {code} {code:title=RENDERING ON SECOND TAB CORRECTLY WORKS (after clicking link)} 1. tab: 2. tab (some code with ajax) Ex. {code} When I change tabs order, problem does not exist. was: In case getting 2 tabs (in my case it is primefaces tabs): {code:title=RENDERING ON SECOND TAB NOT WORKS (after clicking link)} 1. tab: 2. tab (some code with ajax) Ex. {code} {code:title=RENDERING ON SECOND TAB NOT WORKS (after clicking link)} 1. tab: 2. tab (some code with ajax) Ex. {code} When I change tabs order, problem does not exist. > Components second tab changes are not rendered after performing some ajax action if attribute ajaxRendered="true" inside located on first tab > --------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: RF-12108 > URL: https://issues.jboss.org/browse/RF-12108 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.2.0.Final > Environment: JDK1.6, > JBoss 6.0.Final, > richfaces 4.1.0.Final/4.2.0.Final > seam 3.1 > IE 9 > Reporter: Artur Mioduszewski > > In case getting 2 tabs (in my case it is primefaces tabs): > {code:title=RENDERING ON SECOND TAB NOT WORKS (after clicking link)} > 1. tab: > > > > > 2. tab (some code with ajax) > Ex. > > > > > {code} > {code:title=RENDERING ON SECOND TAB CORRECTLY WORKS (after clicking link)} > 1. tab: > > > > > 2. tab (some code with ajax) > Ex. > > > > > {code} > When I change tabs order, problem does not exist. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 28 12:23:48 2012 From: jira-events at lists.jboss.org (Artur Mioduszewski (JIRA)) Date: Wed, 28 Mar 2012 12:23:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12108) Components second tab changes are not rendered after performing some ajax action if attribute ajaxRendered="true" inside located on first tab In-Reply-To: <975271229.37623.1332944389491.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <45097191.38146.1332951828723.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artur Mioduszewski updated RF-12108: ------------------------------------ Description: In case getting 2 tabs (in my case it is primefaces tabs): {code:title=RENDERING ON SECOND TAB NOT WORKS (after clicking link)} First tab: Second tab (some code with ajax) Ex. {code} {code:title=RENDERING ON SECOND TAB CORRECTLY WORKS (after clicking link)} First tab: Second tab (some code with ajax) Ex. {code} When I change tabs order, problem does not exist. was: In case getting 2 tabs (in my case it is primefaces tabs): {code:title=RENDERING ON SECOND TAB NOT WORKS (after clicking link)} 1. tab: 2. tab (some code with ajax) Ex. {code} {code:title=RENDERING ON SECOND TAB CORRECTLY WORKS (after clicking link)} 1. tab: 2. tab (some code with ajax) Ex. {code} When I change tabs order, problem does not exist. > Components second tab changes are not rendered after performing some ajax action if attribute ajaxRendered="true" inside located on first tab > --------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: RF-12108 > URL: https://issues.jboss.org/browse/RF-12108 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.2.0.Final > Environment: JDK1.6, > JBoss 6.0.Final, > richfaces 4.1.0.Final/4.2.0.Final > seam 3.1 > IE 9 > Reporter: Artur Mioduszewski > > In case getting 2 tabs (in my case it is primefaces tabs): > {code:title=RENDERING ON SECOND TAB NOT WORKS (after clicking link)} > First tab: > > > > > Second tab (some code with ajax) > Ex. > > > > > {code} > {code:title=RENDERING ON SECOND TAB CORRECTLY WORKS (after clicking link)} > First tab: > > > > > Second tab (some code with ajax) > Ex. > > > > > {code} > When I change tabs order, problem does not exist. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 28 13:00:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 28 Mar 2012 13:00:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11948) rich:extendedDataTable generates a js-error stating this.normalPartStyle is undefined In-Reply-To: <2050628653.20854.1328272188456.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1996880946.38211.1332954047424.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-11948. -------------------------------- Resolution: Done Ok, I exposed the ready event described above via a facelet attribute, so you can do: {code} {code} This event is fired after the EDT is initialized, both after a page load (document ready) and after an ajax update. > rich:extendedDataTable generates a js-error stating this.normalPartStyle is undefined > ------------------------------------------------------------------------------------- > > Key: RF-11948 > URL: https://issues.jboss.org/browse/RF-11948 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.2.0.CR1 > Environment: richfaces-4.2.0-SNAPSHOT, Firefox 10, IE8 > Reporter: Rene O > Assignee: Brian Leathem > Fix For: 4.2.1.CR1 > > > If you use rich:extendedDataTable and manually set the width of a column afterwards, a js error occurs > {code:title=page-snippet to reproduce the issue} > > xmlns:h="http://java.sun.com/jsf/html" > xmlns:f="http://java.sun.com/jsf/core" > xmlns:ui="http://java.sun.com/jsf/facelets" > xmlns:a4j="http://richfaces.org/a4j" > xmlns:rich="http://richfaces.org/rich" > > > > JSF Test > > > > > > > > > > ColA > > #{item.itemA} > > > > > > > {code} > {code:title=js error} > Fehler: this.normalPartStyle is undefined > Quelldatei: http://localhost:8080/jsftest/javax.faces.resource/extendedDataTable.js.jsf?ln=org.richfaces > Zeile: 279 > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 28 13:04:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 28 Mar 2012 13:04:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12086) Update the RichFaces WFK version in the archetypes In-Reply-To: <1088995279.29817.1332738527229.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <902109341.38225.1332954287247.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-12086. -------------------------------- Resolution: Done RF-12086: Updated the WFK Richfaces version to 4.2.1.Final-redhat-1 > Update the RichFaces WFK version in the archetypes > -------------------------------------------------- > > Key: RF-12086 > URL: https://issues.jboss.org/browse/RF-12086 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: archetype > Reporter: Brian Leathem > Assignee: Brian Leathem > Priority: Critical > Fix For: 4.2.1.CR1 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 28 13:33:48 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 28 Mar 2012 13:33:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12044) Metamer: @preventDefault attribute of rich:hotKey component doesn't work in IE 9 and Google Chrome In-Reply-To: <283065864.9549.1331739467659.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <483157150.38254.1332956028487.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12680104#comment-12680104 ] Luk?? Fry? commented on RF-12044: --------------------------------- Thanks for the assistance. I'm rejecting this issue as {{Won't fix}}. > Metamer: @preventDefault attribute of rich:hotKey component doesn't work in IE 9 and Google Chrome > -------------------------------------------------------------------------------------------------- > > Key: RF-12044 > URL: https://issues.jboss.org/browse/RF-12044 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-misc > Affects Versions: 4.2.0.Final > Environment: RichFaces 4.2.1-SNAPSHOT > Metamer 4.2.1-SNAPSHOT > Mojarra 2.1.5-SNAPSHOT > JBoss AS 7.1.0.Final > Java(TM) SE Runtime Environment 1.6.0_31-b04 @ Linux > Chrome 17.0.963.78 @ Linux i686 > ?RichFaces 4.2.1-SNAPSHOT > ?Metamer 4.2.1-SNAPSHOT > ?Mojarra 2.1.5-SNAPSHOT > ?JBoss AS 7.1.0.Final > ?Java(TM) SE Runtime Environment 1.6.0_31-b04 @ Linux > ?Internet Explorer 9.0 @ Win32 > Reporter: Jan Papousek > Assignee: Luk?? Fry? > Labels: Chrome, IE9 > > It's working correctly in Firefox 10. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 28 13:33:48 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 28 Mar 2012 13:33:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12044) Metamer: @preventDefault attribute of rich:hotKey component doesn't work in IE 9 and Google Chrome In-Reply-To: <283065864.9549.1331739467659.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <634195872.38256.1332956028626.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved RF-12044. ----------------------------- Fix Version/s: (was: 4.2.1.CR1) Resolution: Won't Fix > Metamer: @preventDefault attribute of rich:hotKey component doesn't work in IE 9 and Google Chrome > -------------------------------------------------------------------------------------------------- > > Key: RF-12044 > URL: https://issues.jboss.org/browse/RF-12044 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-misc > Affects Versions: 4.2.0.Final > Environment: RichFaces 4.2.1-SNAPSHOT > Metamer 4.2.1-SNAPSHOT > Mojarra 2.1.5-SNAPSHOT > JBoss AS 7.1.0.Final > Java(TM) SE Runtime Environment 1.6.0_31-b04 @ Linux > Chrome 17.0.963.78 @ Linux i686 > ?RichFaces 4.2.1-SNAPSHOT > ?Metamer 4.2.1-SNAPSHOT > ?Mojarra 2.1.5-SNAPSHOT > ?JBoss AS 7.1.0.Final > ?Java(TM) SE Runtime Environment 1.6.0_31-b04 @ Linux > ?Internet Explorer 9.0 @ Win32 > Reporter: Jan Papousek > Assignee: Luk?? Fry? > Labels: Chrome, IE9 > > It's working correctly in Firefox 10. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 28 13:35:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 28 Mar 2012 13:35:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12044) Metamer: @preventDefault attribute of rich:hotKey component doesn't work in IE 9 and Google Chrome In-Reply-To: <283065864.9549.1331739467659.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <594384359.38259.1332956147483.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12680105#comment-12680105 ] Luk?? Fry? commented on RF-12044: --------------------------------- Documentation issue opened: RFPL-2102 > Metamer: @preventDefault attribute of rich:hotKey component doesn't work in IE 9 and Google Chrome > -------------------------------------------------------------------------------------------------- > > Key: RF-12044 > URL: https://issues.jboss.org/browse/RF-12044 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-misc > Affects Versions: 4.2.0.Final > Environment: RichFaces 4.2.1-SNAPSHOT > Metamer 4.2.1-SNAPSHOT > Mojarra 2.1.5-SNAPSHOT > JBoss AS 7.1.0.Final > Java(TM) SE Runtime Environment 1.6.0_31-b04 @ Linux > Chrome 17.0.963.78 @ Linux i686 > ?RichFaces 4.2.1-SNAPSHOT > ?Metamer 4.2.1-SNAPSHOT > ?Mojarra 2.1.5-SNAPSHOT > ?JBoss AS 7.1.0.Final > ?Java(TM) SE Runtime Environment 1.6.0_31-b04 @ Linux > ?Internet Explorer 9.0 @ Win32 > Reporter: Jan Papousek > Assignee: Luk?? Fry? > Labels: Chrome, IE9 > > It's working correctly in Firefox 10. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 28 14:21:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 28 Mar 2012 14:21:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11884) Multiple Errors with IE8/9 In-Reply-To: <1562607854.56099.1326530722497.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <804685542.38382.1332958907864.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12680121#comment-12680121 ] Luk?? Fry? commented on RF-11884: --------------------------------- Hey Friedhelm, I was able to simulate *Problem 6* with adding {code:javascript} this.bodyElement.style.height = (-1) + "px"; {code} It doesn't work in IE8 and lower, but it works fine on IE9. But since I'm not sure about the semantics, I prefer do not hide issue before we will have sample and steps for reproduction. > Multiple Errors with IE8/9 > -------------------------- > > Key: RF-11884 > URL: https://issues.jboss.org/browse/RF-11884 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes, component-tables, component-tree > Environment: Windows 7 64, Tomcat 7.0.23, Mojarra 2.1.3, IE8/9 (all errors), Chrome 16.09 (one problem), PrimesFaces 2.2.1 (ChartGraphics only, problems still persist when PF is removed) > Reporter: Friedhelm Kuehn > Assignee: Luk?? Fry? > Priority: Critical > Fix For: 4.2.1.CR1 > > Attachments: ProgramVariable_Table.xhtml, Richfaces_4.1_Problems.pdf, Richfaces_4.1_Problems_Konfiguration.pdf, Test.war > > > Problem 1: Shaded TabbedPane Tabs, not changing color when tabbing. Big spacing area below tabs (height about 20 px, should be 2px). > Problem 2: Content of not-popped-up Popup-Panel is not visible, but an area is claimed on screen. > Problem 3: with icon: Icon is surrounded by dark border > Problem 4: No Horzontal-Scroller in ExtendDatatable (with Chrome also). > Problem 5: Use of IconCollapsed/..Expanded creates double Icons in TreeNode > Problem 6: Javascript Error in ExtendedDataTable.js > Biggest Problem: We have to deliver our application in a few weeks. Support for IE8/9 is hard customer requirement. > I have a made a documentation for each problem, but don't find a way to attach a PDF to this issue - ?? > Please help ! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 28 14:25:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 28 Mar 2012 14:25:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12109) Showcase in AS 7.1.1 (JSF 2.1.7) missing doctype and root In-Reply-To: <1464963313.37982.1332948707417.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <389419011.38395.1332959147779.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-12109. -------------------------------- Resolution: Done Added doctype and html root to the welcome page > Showcase in AS 7.1.1 (JSF 2.1.7) missing doctype and root > ---------------------------------------------------------------- > > Key: RF-12109 > URL: https://issues.jboss.org/browse/RF-12109 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: showcase > Reporter: Brian Leathem > Assignee: Brian Leathem > Priority: Critical > Fix For: 4.2.1.CR1 > > > Changes to how ui:include and templates are processed in Mojarra 2.1.7 result in the doctype and html root element being omitted from the showcase. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Mar 28 16:28:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 28 Mar 2012 16:28:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11560) Showcase on OpenShift Express: Push stops to work after first long-polling request In-Reply-To: <703843376.3936.1318926525118.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1265304924.38545.1332966527516.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated RF-11560: ---------------------------- Fix Version/s: (was: 4.2.1.CR1) > Showcase on OpenShift Express: Push stops to work after first long-polling request > ---------------------------------------------------------------------------------- > > Key: RF-11560 > URL: https://issues.jboss.org/browse/RF-11560 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll, showcase > Affects Versions: 4.1.0.Milestone3 > Reporter: Luk?? Fry? > Assignee: Jan Papousek > Labels: openshift > > Both demos affected: TopicsContext and Push CDI. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 29 01:10:53 2012 From: jira-events at lists.jboss.org (Friedhelm Kuehn (JIRA)) Date: Thu, 29 Mar 2012 01:10:53 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11884) Multiple Errors with IE8/9 In-Reply-To: <1562607854.56099.1326530722497.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1782111670.38962.1332997853829.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Friedhelm Kuehn closed RF-11884. -------------------------------- Hi Lukas, thank you for (partially) solving this. I solved this myself another way. After opening this issue on 14. of January 2012 with 'critical'.. and not getting any help for 3 weeks, I decided to leave Richfaces towards ... you can guess. I needed 6 weeks to reach the target platform and had a running solution before this issue was resolved. This is not the response time we can live with. Sorry. > Multiple Errors with IE8/9 > -------------------------- > > Key: RF-11884 > URL: https://issues.jboss.org/browse/RF-11884 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes, component-tables, component-tree > Environment: Windows 7 64, Tomcat 7.0.23, Mojarra 2.1.3, IE8/9 (all errors), Chrome 16.09 (one problem), PrimesFaces 2.2.1 (ChartGraphics only, problems still persist when PF is removed) > Reporter: Friedhelm Kuehn > Assignee: Luk?? Fry? > Priority: Critical > Fix For: 4.2.1.CR1 > > Attachments: ProgramVariable_Table.xhtml, Richfaces_4.1_Problems.pdf, Richfaces_4.1_Problems_Konfiguration.pdf, Test.war > > > Problem 1: Shaded TabbedPane Tabs, not changing color when tabbing. Big spacing area below tabs (height about 20 px, should be 2px). > Problem 2: Content of not-popped-up Popup-Panel is not visible, but an area is claimed on screen. > Problem 3: with icon: Icon is surrounded by dark border > Problem 4: No Horzontal-Scroller in ExtendDatatable (with Chrome also). > Problem 5: Use of IconCollapsed/..Expanded creates double Icons in TreeNode > Problem 6: Javascript Error in ExtendedDataTable.js > Biggest Problem: We have to deliver our application in a few weeks. Support for IE8/9 is hard customer requirement. > I have a made a documentation for each problem, but don't find a way to attach a PDF to this issue - ?? > Please help ! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 29 03:21:47 2012 From: jira-events at lists.jboss.org (Rene O (JIRA)) Date: Thu, 29 Mar 2012 03:21:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11948) rich:extendedDataTable generates a js-error stating this.normalPartStyle is undefined In-Reply-To: <2050628653.20854.1328272188456.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <494333638.39196.1333005707984.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12680214#comment-12680214 ] Rene O commented on RF-11948: ----------------------------- Thanks a lot Brian. This solution works. > rich:extendedDataTable generates a js-error stating this.normalPartStyle is undefined > ------------------------------------------------------------------------------------- > > Key: RF-11948 > URL: https://issues.jboss.org/browse/RF-11948 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.2.0.CR1 > Environment: richfaces-4.2.0-SNAPSHOT, Firefox 10, IE8 > Reporter: Rene O > Assignee: Brian Leathem > Fix For: 4.2.1.CR1 > > > If you use rich:extendedDataTable and manually set the width of a column afterwards, a js error occurs > {code:title=page-snippet to reproduce the issue} > > xmlns:h="http://java.sun.com/jsf/html" > xmlns:f="http://java.sun.com/jsf/core" > xmlns:ui="http://java.sun.com/jsf/facelets" > xmlns:a4j="http://richfaces.org/a4j" > xmlns:rich="http://richfaces.org/rich" > > > > JSF Test > > > > > > > > > > ColA > > #{item.itemA} > > > > > > > {code} > {code:title=js error} > Fehler: this.normalPartStyle is undefined > Quelldatei: http://localhost:8080/jsftest/javax.faces.resource/extendedDataTable.js.jsf?ln=org.richfaces > Zeile: 279 > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 29 03:56:51 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 29 Mar 2012 03:56:51 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11884) Multiple Errors with IE8/9 In-Reply-To: <1562607854.56099.1326530722497.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <977429598.39344.1333007811497.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12680220#comment-12680220 ] Luk?? Fry? commented on RF-11884: --------------------------------- Hi Friedhelm, just note that RichFaces is truly open source project, you can ever step into and analyse/highlight problems, which will increase chance to get issue you experience fixed. Clear and consistent issue report is the base! > Multiple Errors with IE8/9 > -------------------------- > > Key: RF-11884 > URL: https://issues.jboss.org/browse/RF-11884 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes, component-tables, component-tree > Environment: Windows 7 64, Tomcat 7.0.23, Mojarra 2.1.3, IE8/9 (all errors), Chrome 16.09 (one problem), PrimesFaces 2.2.1 (ChartGraphics only, problems still persist when PF is removed) > Reporter: Friedhelm Kuehn > Assignee: Luk?? Fry? > Priority: Critical > Fix For: 4.2.1.CR1 > > Attachments: ProgramVariable_Table.xhtml, Richfaces_4.1_Problems.pdf, Richfaces_4.1_Problems_Konfiguration.pdf, Test.war > > > Problem 1: Shaded TabbedPane Tabs, not changing color when tabbing. Big spacing area below tabs (height about 20 px, should be 2px). > Problem 2: Content of not-popped-up Popup-Panel is not visible, but an area is claimed on screen. > Problem 3: with icon: Icon is surrounded by dark border > Problem 4: No Horzontal-Scroller in ExtendDatatable (with Chrome also). > Problem 5: Use of IconCollapsed/..Expanded creates double Icons in TreeNode > Problem 6: Javascript Error in ExtendedDataTable.js > Biggest Problem: We have to deliver our application in a few weeks. Support for IE8/9 is hard customer requirement. > I have a made a documentation for each problem, but don't find a way to attach a PDF to this issue - ?? > Please help ! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 29 07:04:48 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?J=C3=A1n_Jamrich_=28JIRA=29?=) Date: Thu, 29 Mar 2012 07:04:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11950) rich:findComponent does not retrieve the component for multiply-nested, dynamically generated tab components In-Reply-To: <25533681.21797.1328288808791.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <279166879.39940.1333019088194.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] J?n Jamrich reassigned RF-11950: -------------------------------- Assignee: (was: J?n Jamrich) > rich:findComponent does not retrieve the component for multiply-nested, dynamically generated tab components > ------------------------------------------------------------------------------------------------------------ > > Key: RF-11950 > URL: https://issues.jboss.org/browse/RF-11950 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: base functionality > Affects Versions: 4.1.0.Final > Environment: Websphere 8 - RAD 8 - JSF Mojorra 2.1.4 - Spring 3.0.6 Final - Firefox 10.0 - Windows 7 (6.1 sp1) > Reporter: Jean ANDRE > Fix For: 4.Future > > Attachments: index.xhtml, index.xhtml, listClient.xhtml, NestedWeb_RF-11950.zip, requestClientDocument.xhtml, requestClientDocument.xhtml, tabsClient.xhtml, tabsClient.xhtml > > > The rich:findComponent does not retrieve the component - What we want to achieve is to send .click() event on a command button. We got different errors depending the tests we made such as syntax error. > The involved code: > ------------------ > {code} > > > > value="#{msg['common.command.cancel']}" > onclick="#{rich:findComponent('#{activity.id}-closeCmd')}.click();;return false;" > render="#{tab.id}-tabsClient" > immediate="true" /> > {code} > The error we got: > ---------------- > {code} > syntax error - [Stopper sur une erreur] - jsf.js.jsf?ln=javax.faces (ligne 1) > .click();return false; > {code} > The corresponding view source: > ------------------------------ > {code} > onclick="jsf.util.chain(this,event,".click();return false;", > "RichFaces.ajax( \"tabbedForm:TAB_CLIENT\\u002D1\\u002Drcd\\u002DcancelCreateCmd\",event,{\"incId\":\"1\"} )"); > return false;" > name="tabbedForm:TAB_CLIENT-1-rcd-cancelCreateCmd" id="tabbedForm:TAB_CLIENT-1-rcd-cancelCreateCmd"> > {code} > The generated javaScript under firebug: > -------------------------------------- > {code} > function onclick(event) { > jsf.util.chain(this, event, ".click();return false;", "RichFaces.ajax(\"tabbedForm:TAB_CLIENT\\u002D1\\u002Drcd\\u002DcancelCreateCmd\",event,{\"incId\":\"1\"} )"); > return false; > } > {code} > If we hard code the Id instead of the calculated one we got following error: > {code} > uncaught exception: Syntax error, unrecognized expression: TAB_CLIENT-1-TAB_RCD-closeCmd > Line 0 > {code} > The generated javaScript under firebug: > -------------------------------------- > {code} > function anonymous(event) { > rich: > findComponent("TAB_CLIENT-1-TAB_RCD-closeCmd").click(); > return false; > } > {code} > If we use directly jQuery: > {code} > > > > value="#{msg['common.command.cancel']}" > onclick="$('##{activity.id}-closeCmd').click();return false;" > render="desktopTabPanel" > immediate="true" /> > {code} > {code} > missing ; before statement > http://localhost:12000/crm/javax.faces.resource/jsf.js.jsf?ln=javax.faces > Line 1 > {code} > If we hardcode an existing static Id, we got the error as shown the screen capture: > {code} > function onclick(event) { > jsf.util.chain(this, event, "org.richfaces.component.UICommandButton at 39de2ca.click();", "RichFaces.ajax(\"tabbedForm:TAB_CLIENT\\u002D1\\u002Drcd\\u002DcancelCreateCmd\",event,{\"incId\":\"1\"} )"); > return false; > } > {code} > {code} > value="#{msg['common.command.cancel']}" > onclick="#{rich:findComponent('qsearchClient')}.click();" > render="#{tab.id}-tabsClient" > immediate="true" />  > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 29 07:54:47 2012 From: jira-events at lists.jboss.org (Rene O (JIRA)) Date: Thu, 29 Mar 2012 07:54:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12110) [rich:contextMenu] contextmenu doesn't work anymore if an ajax request is fired while contextmenu is visible Message-ID: <2058795180.40029.1333022087624.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Rene O created RF-12110: --------------------------- Summary: [rich:contextMenu] contextmenu doesn't work anymore if an ajax request is fired while contextmenu is visible Key: RF-12110 URL: https://issues.jboss.org/browse/RF-12110 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.2.0.Final Environment: Tomcat 7, myfaces-2.1.6, richfaces-4.2.0.Final and 4.2.1-SNAPSHOT Reporter: Rene O The example shows the problem: {code:title=example.xhtml} JSF Test Steps to reproduce the issue:

    1. right click to show context menu
    2. wait till context menu hides
    3. click button 'click me'
    4. right click to show context menu
    5. context menu is visible

    Now do the following
    1. right click to show context menu
    2. click button 'click me' before context menu hides
    3. right click to show context menu
    4. context menu doesn't work anymore...


    right click for context-menu Test     {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 29 09:34:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Nicholas_Oxh=C3=B8j_=28JIRA=29?=) Date: Thu, 29 Mar 2012 09:34:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12111) Threading/performance issues with DocumentBuilder/ResponseWriterContentHandler Message-ID: <4872397.40358.1333028087560.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Nicholas Oxh?j created RF-12111: ----------------------------------- Summary: Threading/performance issues with DocumentBuilder/ResponseWriterContentHandler Key: RF-12111 URL: https://issues.jboss.org/browse/RF-12111 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 3.3.3.Final Reporter: Nicholas Oxh?j Hi We have recently encountered some threading/performance issues with the way DocumentBuilder is used in ResponseWriterContentHandler in RichFaces 3.3.3. Upon investigation, we discovered that this issue was apparently already reported in an "RF-10035 DocumentBuilder performance issue" and fixed in RichFaces 3.3.1.SP3 on Jan. 31, 2011. See https://issues.jboss.org/browse/JBPAPP-6166 The problem is that these bug fixes, were apparently NOT carried forward to the later branches (3.3.2 and 3.3.3). Was this just forgotten or is there a specific reason why these ServicePack fixes were left out? Regards, Nicholas Weise Oxh?j -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 29 10:19:47 2012 From: jira-events at lists.jboss.org (Tanya Ruttenberg (JIRA)) Date: Thu, 29 Mar 2012 10:19:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12112) inputText not putting in data from rich:popupPanel Message-ID: <1217484082.40487.1333030787274.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Tanya Ruttenberg created RF-12112: ------------------------------------- Summary: inputText not putting in data from rich:popupPanel Key: RF-12112 URL: https://issues.jboss.org/browse/RF-12112 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-input Affects Versions: 4.2.0.Final Environment: Windows Vista, EAP 6beta, eclipse indigo Reporter: Tanya Ruttenberg Fix For: 4.2.0.Final a rich:popupPanel containing h:inputText does not input the data for either an a4j:commandButton or h:commandButton. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 29 10:21:47 2012 From: jira-events at lists.jboss.org (Tanya Ruttenberg (JIRA)) Date: Thu, 29 Mar 2012 10:21:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12112) inputText not putting in data from rich:popupPanel In-Reply-To: <1217484082.40487.1333030787274.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1117591853.40491.1333030907656.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12680343#comment-12680343 ] Tanya Ruttenberg commented on RF-12112: --------------------------------------- My little richfaces-webapp was created by clicking on RichFaces Project in the Create Projects section of JBoss Central view in eclipse. I didn't do this from scratch. I'm uploading the source files and pom. > inputText not putting in data from rich:popupPanel > -------------------------------------------------- > > Key: RF-12112 > URL: https://issues.jboss.org/browse/RF-12112 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.2.0.Final > Environment: Windows Vista, EAP 6beta, eclipse indigo > Reporter: Tanya Ruttenberg > Labels: richfaces > Fix For: 4.2.0.Final > > > a rich:popupPanel containing h:inputText does not input the data for either an a4j:commandButton or h:commandButton. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 29 10:39:47 2012 From: jira-events at lists.jboss.org (Tanya Ruttenberg (JIRA)) Date: Thu, 29 Mar 2012 10:39:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12112) inputText not putting in data from rich:popupPanel In-Reply-To: <1217484082.40487.1333030787274.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1118729409.40503.1333031987458.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tanya Ruttenberg updated RF-12112: ---------------------------------- Attachment: richfaces-tdr.zip contains sourcefiles and pom.xml > inputText not putting in data from rich:popupPanel > -------------------------------------------------- > > Key: RF-12112 > URL: https://issues.jboss.org/browse/RF-12112 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.2.0.Final > Environment: Windows Vista, EAP 6beta, eclipse indigo > Reporter: Tanya Ruttenberg > Labels: richfaces > Fix For: 4.2.0.Final > > Attachments: richfaces-tdr.zip > > > a rich:popupPanel containing h:inputText does not input the data for either an a4j:commandButton or h:commandButton. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 29 11:15:48 2012 From: jira-events at lists.jboss.org (Leo Higgins (JIRA)) Date: Thu, 29 Mar 2012 11:15:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12113) rich:inputNumberSpinner minValue and maxValue being ignored after second request Message-ID: <1286311086.40531.1333034148641.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Leo Higgins created RF-12113: -------------------------------- Summary: rich:inputNumberSpinner minValue and maxValue being ignored after second request Key: RF-12113 URL: https://issues.jboss.org/browse/RF-12113 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-input Affects Versions: 4.2.0.Final Environment: Windows 7 x64, Firefox/Waterfox v10.0.1, Chrome v17.0.963.83 m, IE8 64-bit v8.0.7601.17514 Reporter: Leo Higgins When setting the value of the component to a value either below the specified minValue or above the specified maxValue, the component correctly sets the value to either the minValue or the maxValue. On a subsequent request, however, the component does not set the value to the minValue or the maxValue. This bug exists on all above browsers at the Richfaces showcase here: http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=inputNumberSpinner&skin=blueSky -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 29 15:26:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Thu, 29 Mar 2012 15:26:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12111) Threading/performance issues with DocumentBuilder/ResponseWriterContentHandler In-Reply-To: <4872397.40358.1333028087560.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <84303719.41365.1333049207849.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12111: ------------------------------- Fix Version/s: 3.Future > Threading/performance issues with DocumentBuilder/ResponseWriterContentHandler > ------------------------------------------------------------------------------ > > Key: RF-12111 > URL: https://issues.jboss.org/browse/RF-12111 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 3.3.3.Final > Reporter: Nicholas Oxh?j > Fix For: 3.Future > > > Hi > We have recently encountered some threading/performance issues with the way DocumentBuilder is used in ResponseWriterContentHandler in RichFaces 3.3.3. Upon investigation, we discovered that this issue was apparently already reported in an "RF-10035 DocumentBuilder performance issue" and fixed in RichFaces 3.3.1.SP3 on Jan. 31, 2011. See https://issues.jboss.org/browse/JBPAPP-6166 > The problem is that these bug fixes, were apparently NOT carried forward to the later branches (3.3.2 and 3.3.3). > Was this just forgotten or is there a specific reason why these ServicePack fixes were left out? > Regards, > Nicholas Weise Oxh?j -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 29 15:26:48 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Thu, 29 Mar 2012 15:26:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12104) BeanValidator: label not handled using MessageFactory In-Reply-To: <1962209716.36295.1332920747471.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <539814225.41367.1333049208061.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12104: ------------------------------- Fix Version/s: 3.Future > BeanValidator: label not handled using MessageFactory > ----------------------------------------------------- > > Key: RF-12104 > URL: https://issues.jboss.org/browse/RF-12104 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 3.3.3.Final > Environment: Liferay 5.2.4, Portlet 2.0, JSF 1.2 > Reporter: Markus Staab > Fix For: 3.Future > > > The BeanValidator, in contrast to most JSF validators e.g. LongRangeValidator, does not use the MessageFactory to handle validation error message. > see LongRangeValidators' validate-method: > {code} > .... > throw new ValidatorException(MessageFactory.getMessage > (context, > NOT_IN_RANGE_MESSAGE_ID, > stringValue(component, minimum, context), > stringValue(component, maximum, context), > MessageFactory.getLabel(context, component))); > ... > {code} > Therefore error-message of a BeanValidator will neither prepand the String which is provided from the components' label-attribute nor the components' client id. > see BeanValidator's validate & extractMessages-method > {code} > .... > private Collection extractMessages(Set> violations) { > Collection messages = null; > if (null != violations && violations.size() > 0) { > messages = new ArrayList(violations.size()); > for (ConstraintViolation constraintViolation : violations) { > messages.add(constraintViolation.getMessage()); > } > } > return messages; > } > ... > {code} > All error messages are taken 1:1 from the BeanValidator. > While e.g. the error-message of LongRangeValidtor looks like "Startdate: Value is greater than allowable maximum of ''{0}''." the error looks like "Value is greater than allowable maximum of ''{0}''.". > The reference to the component which violates the rule is not shown. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 29 15:26:49 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Thu, 29 Mar 2012 15:26:49 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12092) a4j:poll : a4j:status never clears In-Reply-To: <69599813.32096.1332784967357.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <840461084.41372.1333049209575.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679745#comment-12679745 ] Brian Leathem edited comment on RF-12092 at 3/29/12 3:26 PM: ------------------------------------------------------------- I'm able to reproduce it on... RichFaces 4.2.0.CR1 MyFaces MyFaces 2.0.6 JBoss 6.0.0.Final JVM 1.7_01 IE 9.0.8 FF 3.6.16 Chrome 17.0.963.83 m I'm using the following code... {code} {code} was (Author: RobertGary1): I'm able to reproduce it on... RichFaces 4.2.0.CR1 MyFaces MyFaces 2.0.6 JBoss 6.0.0.Final JVM 1.7_01 IE 9.0.8 FF 3.6.16 Chrome 17.0.963.83 m I'm using the following code... > a4j:poll : a4j:status never clears > ---------------------------------- > > Key: RF-12092 > URL: https://issues.jboss.org/browse/RF-12092 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Affects Versions: 4.2.0.Final > Reporter: Robert Gary > Assignee: Brian Leathem > Attachments: a4jPollIssue.war > > > When a4j:poll fires a4j:status correctly displays the request is in progress. However, it never shows it complete. Using any other a4j component will correctly update the a4j:status. So if the a4j:status is stuck showing its waiting because of an a4j:poll if you click on an a4j:commandButton the a4j:status will correctly show its now complete. > render="#{faces$DiscoveryStatus.reRenderStr}"/> > > > > > > > > > This code works correctly in RF 3.3.3. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 29 15:35:48 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Thu, 29 Mar 2012 15:35:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-9324) a4j:queue event handlers doesn't work at all In-Reply-To: <137221601.9097.1283870812840.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <2083740640.41390.1333049748221.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-9324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-9324. ------------------------------- Assignee: (was: Ilya Shaikovsky) Fix Version/s: (was: 4.Future) Resolution: Duplicate Issue > a4j:queue event handlers doesn't work at all > -------------------------------------------- > > Key: RF-9324 > URL: https://issues.jboss.org/browse/RF-9324 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.0.0.Milestone2 > Environment: Java(TM) SE Runtime Environment 1.6.0_20-b02 > Linux 2.6.31-22-generic > Mojarra 2.0.2-FCS > Firefox 3.6.3 > Apache Tomcat 6.0.26 > core-demo : M2 https://repository.jboss.org/nexus/content/groups/public/org/richfaces/examples/core-demo/4.0.0.20100826-M2/core-demo-4.0.0.20100826-M2-tomcat6.war > http://localhost:8080/core-demo/queue.jsf > Reporter: Luk?? Fry? > > I modified queue.html sample to look like this: > > > > > > > It seems queue is working, because it handles multiple events and triggers only one request, but alert is not shown on completion. > The same for all other event handlers. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 29 15:37:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Thu, 29 Mar 2012 15:37:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12092) a4j:poll : a4j:status never clears In-Reply-To: <69599813.32096.1332784967357.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <98263931.41394.1333049867338.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem reassigned RF-12092: ---------------------------------- Assignee: Pavol Pitonak (was: Brian Leathem) Pavol, can you please try agin to re-produce in metamer, with the user-provided source? > a4j:poll : a4j:status never clears > ---------------------------------- > > Key: RF-12092 > URL: https://issues.jboss.org/browse/RF-12092 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Affects Versions: 4.2.0.Final > Reporter: Robert Gary > Assignee: Pavol Pitonak > Attachments: a4jPollIssue.war > > > When a4j:poll fires a4j:status correctly displays the request is in progress. However, it never shows it complete. Using any other a4j component will correctly update the a4j:status. So if the a4j:status is stuck showing its waiting because of an a4j:poll if you click on an a4j:commandButton the a4j:status will correctly show its now complete. > render="#{faces$DiscoveryStatus.reRenderStr}"/> > > > > > > > > > This code works correctly in RF 3.3.3. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 29 15:39:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Thu, 29 Mar 2012 15:39:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12028) a4j:outputPanel - Error message enhancement In-Reply-To: <1368665910.75459.1331155416313.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <901635050.41399.1333049987470.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12680435#comment-12680435 ] Brian Leathem commented on RF-12028: ------------------------------------ Understood, what I'm asking is to see what error message you get with a JSF standard component, when you reference a non existing attribute. Something like: {code} {code} > a4j:outputPanel - Error message enhancement > ------------------------------------------- > > Key: RF-12028 > URL: https://issues.jboss.org/browse/RF-12028 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Environment: JSF / Mojarra 2.1.6 - cssparser-0.9.6 - guava-11.0.1 - hibernate-validator-4.2.0.Final - springframework 3.0.6.RELEASE - richfaces--4.2.0.Final - sac-1.3 - FireFox 10 - WAS 8.0.0.1 / Windows 7 > Reporter: Jean ANDRE > Labels: waiting_on_user > > When we set an non existing attribute on a4j:outputPanel, for eg. "class" because we have converted a div to a a4j:outputPanel, the error message displayed at the user interface does not inform the developer about the faulty component. The message we got is only : > > Error 500: javax.servlet.ServletException: Setter not found for property class > This error message is not very helpful to debug.... ;) > {code} > layout="block" > class="dark-box" > rendered="#{productBean.expanded eq true}"> > {code} > We should have, as usual, the line of the XHTML file or the component name, the line number, well something more accurate that really help to go faster. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 29 16:06:47 2012 From: jira-events at lists.jboss.org (Jean ANDRE (JIRA)) Date: Thu, 29 Mar 2012 16:06:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12028) a4j:outputPanel - Error message enhancement In-Reply-To: <1368665910.75459.1331155416313.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <423714547.41444.1333051607459.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12680439#comment-12680439 ] Jean ANDRE commented on RF-12028: --------------------------------- Well, - for a div -> silent, ignore, no message - for a div with duplicate attribute -> Error 500: javax.servlet.ServletException: Error Parsing /pages/client/infoClient.xhtml: Error Traced[line: 30] L'attribut "class" a d?j? ?t? indiqu? pour l'?l?ment "div". - for a h:message -> silent, ignore, no message Error 500: javax.servlet.ServletException: Error Parsing /pages/client/infoClient.xhtml: Error Traced[line: 49] L'attribut "globalOnly" a d?j? ?t? indiqu? pour l'?l?ment "h:messages" - for h:panelGrid -> silent, ignore, no message - for h:panelGrid with duplicate attribute -> Error 500: javax.servlet.ServletException: Error Parsing /pages/client/infoClient.xhtml: Error Traced[line: 57] L'attribut "columns" a d?j? ?t? indiqu? pour l'?l?ment "h:panelGrid". To summarize: 1) an invalid attribute is ignore, server does not stop and no message appears on the console 2) an duplicate valid attribute trigger an HTTP error 500. Line number and attribute name and tag are clearly identified. 3) Note also, from our experience, MyFaces implementation is more strict and reports more errors at the console level. >From my side, I prefer to have a warning message at the console/log for these trivial errors, it helps to maintain a clean code since even the IDE does not detect such error. > a4j:outputPanel - Error message enhancement > ------------------------------------------- > > Key: RF-12028 > URL: https://issues.jboss.org/browse/RF-12028 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Environment: JSF / Mojarra 2.1.6 - cssparser-0.9.6 - guava-11.0.1 - hibernate-validator-4.2.0.Final - springframework 3.0.6.RELEASE - richfaces--4.2.0.Final - sac-1.3 - FireFox 10 - WAS 8.0.0.1 / Windows 7 > Reporter: Jean ANDRE > Labels: waiting_on_user > > When we set an non existing attribute on a4j:outputPanel, for eg. "class" because we have converted a div to a a4j:outputPanel, the error message displayed at the user interface does not inform the developer about the faulty component. The message we got is only : > > Error 500: javax.servlet.ServletException: Setter not found for property class > This error message is not very helpful to debug.... ;) > {code} > layout="block" > class="dark-box" > rendered="#{productBean.expanded eq true}"> > {code} > We should have, as usual, the line of the XHTML file or the component name, the line number, well something more accurate that really help to go faster. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 29 16:08:47 2012 From: jira-events at lists.jboss.org (Jean ANDRE (JIRA)) Date: Thu, 29 Mar 2012 16:08:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12028) a4j:outputPanel - Error message enhancement In-Reply-To: <1368665910.75459.1331155416313.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <168261917.41449.1333051727602.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12680439#comment-12680439 ] Jean ANDRE edited comment on RF-12028 at 3/29/12 4:07 PM: ---------------------------------------------------------- Well, - for a div -> silent, ignore, no message - for a div with duplicate attribute -> Error 500: javax.servlet.ServletException: Error Parsing /pages/client/infoClient.xhtml: Error Traced[line: 30] L'attribut "class" a d?j? ?t? indiqu? pour l'?l?ment "div". - for a h:message -> silent, ignore, no message Error 500: javax.servlet.ServletException: Error Parsing /pages/client/infoClient.xhtml: Error Traced[line: 49] L'attribut "globalOnly" a d?j? ?t? indiqu? pour l'?l?ment "h:messages" - for h:panelGrid -> silent, ignore, no message - for h:panelGrid with duplicate attribute -> Error 500: javax.servlet.ServletException: Error Parsing /pages/client/infoClient.xhtml: Error Traced[line: 57] L'attribut "columns" a d?j? ?t? indiqu? pour l'?l?ment "h:panelGrid". To summarize: 1) an invalid attribute is ignored, server does not stop and no message appears at the console 2) an duplicate valid attribute trigger an HTTP error 500. Line number and attribute name and tag are clearly identified. 3) Note also, from our experience, MyFaces implementation is more strict and reports more errors at the console level. >From my side, I prefer to have a warning message at the console/log for these trivial errors, it helps to maintain a clean code since even the IDE does not detect such error. was (Author: jorelia64): Well, - for a div -> silent, ignore, no message - for a div with duplicate attribute -> Error 500: javax.servlet.ServletException: Error Parsing /pages/client/infoClient.xhtml: Error Traced[line: 30] L'attribut "class" a d?j? ?t? indiqu? pour l'?l?ment "div". - for a h:message -> silent, ignore, no message Error 500: javax.servlet.ServletException: Error Parsing /pages/client/infoClient.xhtml: Error Traced[line: 49] L'attribut "globalOnly" a d?j? ?t? indiqu? pour l'?l?ment "h:messages" - for h:panelGrid -> silent, ignore, no message - for h:panelGrid with duplicate attribute -> Error 500: javax.servlet.ServletException: Error Parsing /pages/client/infoClient.xhtml: Error Traced[line: 57] L'attribut "columns" a d?j? ?t? indiqu? pour l'?l?ment "h:panelGrid". To summarize: 1) an invalid attribute is ignore, server does not stop and no message appears on the console 2) an duplicate valid attribute trigger an HTTP error 500. Line number and attribute name and tag are clearly identified. 3) Note also, from our experience, MyFaces implementation is more strict and reports more errors at the console level. >From my side, I prefer to have a warning message at the console/log for these trivial errors, it helps to maintain a clean code since even the IDE does not detect such error. > a4j:outputPanel - Error message enhancement > ------------------------------------------- > > Key: RF-12028 > URL: https://issues.jboss.org/browse/RF-12028 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Environment: JSF / Mojarra 2.1.6 - cssparser-0.9.6 - guava-11.0.1 - hibernate-validator-4.2.0.Final - springframework 3.0.6.RELEASE - richfaces--4.2.0.Final - sac-1.3 - FireFox 10 - WAS 8.0.0.1 / Windows 7 > Reporter: Jean ANDRE > Labels: waiting_on_user > > When we set an non existing attribute on a4j:outputPanel, for eg. "class" because we have converted a div to a a4j:outputPanel, the error message displayed at the user interface does not inform the developer about the faulty component. The message we got is only : > > Error 500: javax.servlet.ServletException: Setter not found for property class > This error message is not very helpful to debug.... ;) > {code} > layout="block" > class="dark-box" > rendered="#{productBean.expanded eq true}"> > {code} > We should have, as usual, the line of the XHTML file or the component name, the line number, well something more accurate that really help to go faster. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 29 16:10:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Thu, 29 Mar 2012 16:10:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12032) rich:calendar : Ajax request - Error message enhancement - sql.Date In-Reply-To: <1406650855.77949.1331220940774.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1717636535.41467.1333051847470.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12680440#comment-12680440 ] Brian Leathem commented on RF-12032: ------------------------------------ Surely you have access to the server logs in your development and QE application development phases? Have you tried adding an tag to see if any FacesMessages are being queued that are not being displayed? > rich:calendar : Ajax request - Error message enhancement - sql.Date > ------------------------------------------------------------------- > > Key: RF-12032 > URL: https://issues.jboss.org/browse/RF-12032 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Environment: cssparser-0.9.6 - guava-11.0.1 - hibernate-validator-4.2.0.Final - JSF/Mojarra 2.1.6 - springframework-3.0.6.RELEASE - richfaces-4.2.0.Final - sac-1.3.jar - Windows 7, WAS 8.0.0.1, Servlet 2.5 - Java 6. > Reporter: Jean ANDRE > Labels: waiting_on_user > Attachments: rich_calendar_errorMsg_Enhancement.png > > > When a backing-bean have a type of sql.Date which is mapped to a rich:calendar, there is an conversion error due to the rich:calendar component uses util.Date by default. Unfortunately, we do not see any error message at the screen when an ajax request is sent and returned back to us. > What we got, and thanks to Firebug, is the text below as an answer from our Ajax request POST. Nothing is rendered at the screen and the method of the backing bean is not called. > {code} > > class javax.faces.component.UpdateModelException > {code} > Our code looks like this (we remove unecessary field and decoration): > {code} > > > > > value="#{msg['common.command.add.phone']}" > action="#{createClientController.doAddPhone}"> > > > > > > > value="#{phoneBean.effectiveDate}" > popup="true" > showApplyButton="false" > enableManualInput="true" > datePattern="#{msg['client.date.format']}" > inputSize="12" > styleClass="calendar"> > > > > > > > > {code} > Is is possible to have a message returned back to the UI??? or is there a way to handle this error properly? > Other information > ================= > The form is inside a dynamic tab - Fragment are also include dynamically - we use c:if et subView as shown below: > {code} > > > > > > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 29 16:12:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Thu, 29 Mar 2012 16:12:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12040) Multi-form document - command button (submit) does not work after rendering In-Reply-To: <375257168.7025.1331658768095.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <735371204.41484.1333051967322.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem closed RF-12040. ------------------------------ Labels: (was: waiting_on_user) Resolution: Rejected Upstream issue > Multi-form document - command button (submit) does not work after rendering > --------------------------------------------------------------------------- > > Key: RF-12040 > URL: https://issues.jboss.org/browse/RF-12040 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Environment: cssparser-0.9.6 - guava-11.0.1 - hibernate-validator-4.2.0.Final - JSF/Mojarra 2.1.6 - springframework-3.0.6.RELEASE - sac-1.3 - Windows 7 - FireFox 10 - RichFaces 4.2 Final > Reporter: Jean ANDRE > Attachments: NestedWebWithMenu.zip > > > We have one page that contains two forms. The first form contain a menus bar (ajax switchType) while the second contains a tabPanel (also in ajax switchType). When a user select a menu, we select the corresponding tab that contains a submit button. Once the tab is selected, the submit button does not work. We have to click twice for submitting. > # If we move the menu bar inside the second forms, it is working. > # If we set the menu bar in client switchType, selecting the menu doesn't do anything. > # If we set the menu bar in server switchType it's working. > As the rendering is well executed, the submit button should works but is not whatever we set as render="@all, or any valid id". > We have prepared a small application that demonstrates the case. This is a simple but realistic application. Edit the index.xhtml to play with the menu. Let us know if we doing something wrong. > Note also that the JIRA JAVASERVERFACES-2016 was reopened :[JIRA] Reopened: (JAVASERVERFACES-2016) Resources not loaded when using a dynamic ui:inlclude and rendered via ajax > [ http://java.net/jira/browse/JAVASERVERFACES-2016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] > {code:title=Relevant Facelet markup} > > xmlns:ui="http://java.sun.com/jsf/facelets" > xmlns:h="http://java.sun.com/jsf/html" > xmlns:f="http://java.sun.com/jsf/core" > xmlns:rich="http://richfaces.org/rich" > xmlns:a4j="http://richfaces.org/a4j" > xmlns:c="http://java.sun.com/jsp/jstl/core" > template="/templates/basePage.xhtml"> > > > > > > > > > > > > > > > > > > > > > > > label="#{msg['menu.item.one.items.management']}" > action="#{desktopController.doActivateTabItems}" > render="desktopTabs" /> > > > > >
    >
    > > > > > > > > switchType="ajax" > headerPosition="top" > activeItem="#{desktopController.activeTab}" > itemChangeListener="#{desktopController.doItemChangeListener}" > immediate="true"> > > > > > #1 > > > > > > > > > > value="#{msg[desktopController.togglePanelLabel]}" > actionListener="#{desktopController.doToggleTabContent}" > render="toggleTabContent"> > >
    >
    > > > > > > > > > > > > >     >     > > > > > > > > > styleClass="closeButton" > onclick="closeTab('#{tab.id}');event.stopPropagation();" /> > > > > > > > > > >     >     > > > > > > > > > > > > >     > > > >     > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 29 16:14:48 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Thu, 29 Mar 2012 16:14:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12063) rich:notifyMessages not displaying error from valueChangeListener In-Reply-To: <71281469.18246.1332180647276.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1922261422.41502.1333052088162.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678570#comment-12678570 ] Brian Leathem edited comment on RF-12063 at 3/29/12 4:13 PM: ------------------------------------------------------------- Clicking into and out of the input should cause the value change listener to fire, however no message appears on the screen. Simply adding a commandButton, and copying the message generation code from the value change listener into an action= method and clicking the button will cause a notifyMessage to appear on screen. {code} {code} {code:title=Bean.java} @Named @ViewScoped public class Bean implements Serializable { public void testVcl(ValueChangeEvent event) { //Log.log("testVcl"); FacesMessage message = getFacesMessage("helloText"); message.setSeverity(FacesMessage.SEVERITY_ERROR); FacesContext.getCurrentInstance().addMessage(null, message); } public String testAction() { //Log.log("testVcl"); FacesMessage message = getFacesMessage("helloText"); message.setSeverity(FacesMessage.SEVERITY_ERROR); FacesContext.getCurrentInstance().addMessage(null, message); return null; } public static FacesMessage getFacesMessage(String msgKey) { FacesMessage message = Messages.getMessage("messages", msgKey, null); return message; } {code} {code:title=Messages.java} package uk.co.myproj.test; /** * * @author Brendan Healey * copied from Core JSF Geary/Horstmann p249 */ import java.text.MessageFormat; import java.util.Locale; import java.util.MissingResourceException; import java.util.ResourceBundle; import javax.faces.application.Application; import javax.faces.application.FacesMessage; import javax.faces.component.UIViewRoot; import javax.faces.context.FacesContext; public class Messages { public static FacesMessage getMessage(String bundleName, String resourceId, Object[] params) { FacesContext context = FacesContext.getCurrentInstance(); Application app = context.getApplication(); String appBundle = app.getMessageBundle(); Locale locale = getLocale(context); ClassLoader loader = getClassLoader(); String summary = getString(appBundle, bundleName, resourceId, locale, loader, params); if (summary == null) { summary = "???" + resourceId + "???"; } String detail = getString(appBundle, bundleName, resourceId + "_detail", locale, loader, params); return new FacesMessage(summary, detail); } public static String getString(String bundle, String resourceId, Object[] params) { FacesContext context = FacesContext.getCurrentInstance(); Application app = context.getApplication(); String appBundle = app.getMessageBundle(); Locale locale = getLocale(context); ClassLoader loader = getClassLoader(); return getString(appBundle, bundle, resourceId, locale, loader, params); } public static String getString(String bundle1, String bundle2, String resourceId, Locale locale, ClassLoader loader, Object[] params) { String resource = null; ResourceBundle bundle; if (bundle1 != null) { bundle = ResourceBundle.getBundle(bundle1, locale, loader); if (bundle != null) { try { resource = bundle.getString(resourceId); } catch (MissingResourceException ex) { } } } if (resource == null) { bundle = ResourceBundle.getBundle(bundle2, locale, loader); if (bundle != null) { try { resource = bundle.getString(resourceId); } catch (MissingResourceException ex) { } } } if (resource == null) { return null; // no match } if (params == null) { return resource; } MessageFormat formatter = new MessageFormat(resource, locale); return formatter.format(params); } public static Locale getLocale(FacesContext context) { Locale locale = null; UIViewRoot viewRoot = context.getViewRoot(); if (viewRoot != null) { locale = viewRoot.getLocale(); } if (locale == null) { locale = Locale.getDefault(); } return locale; } public static ClassLoader getClassLoader() { ClassLoader loader = Thread.currentThread().getContextClassLoader(); if (loader == null) { loader = ClassLoader.getSystemClassLoader(); } return loader; } } {code} was (Author: healeyb): Clicking into and out of the input should cause the value change listener to fire, however no message appears on the screen. Simply adding a commandButton, and copying the message generation code from the value change listener into an action= method and clicking the button will cause a notifyMessage to appear on screen. Bean.java --------- @Named @ViewScoped public class Bean implements Serializable { public void testVcl(ValueChangeEvent event) { //Log.log("testVcl"); FacesMessage message = getFacesMessage("helloText"); message.setSeverity(FacesMessage.SEVERITY_ERROR); FacesContext.getCurrentInstance().addMessage(null, message); } public String testAction() { //Log.log("testVcl"); FacesMessage message = getFacesMessage("helloText"); message.setSeverity(FacesMessage.SEVERITY_ERROR); FacesContext.getCurrentInstance().addMessage(null, message); return null; } public static FacesMessage getFacesMessage(String msgKey) { FacesMessage message = Messages.getMessage("messages", msgKey, null); return message; } Messages.java ------------- package uk.co.myproj.test; /** * * @author Brendan Healey * copied from Core JSF Geary/Horstmann p249 */ import java.text.MessageFormat; import java.util.Locale; import java.util.MissingResourceException; import java.util.ResourceBundle; import javax.faces.application.Application; import javax.faces.application.FacesMessage; import javax.faces.component.UIViewRoot; import javax.faces.context.FacesContext; public class Messages { public static FacesMessage getMessage(String bundleName, String resourceId, Object[] params) { FacesContext context = FacesContext.getCurrentInstance(); Application app = context.getApplication(); String appBundle = app.getMessageBundle(); Locale locale = getLocale(context); ClassLoader loader = getClassLoader(); String summary = getString(appBundle, bundleName, resourceId, locale, loader, params); if (summary == null) { summary = "???" + resourceId + "???"; } String detail = getString(appBundle, bundleName, resourceId + "_detail", locale, loader, params); return new FacesMessage(summary, detail); } public static String getString(String bundle, String resourceId, Object[] params) { FacesContext context = FacesContext.getCurrentInstance(); Application app = context.getApplication(); String appBundle = app.getMessageBundle(); Locale locale = getLocale(context); ClassLoader loader = getClassLoader(); return getString(appBundle, bundle, resourceId, locale, loader, params); } public static String getString(String bundle1, String bundle2, String resourceId, Locale locale, ClassLoader loader, Object[] params) { String resource = null; ResourceBundle bundle; if (bundle1 != null) { bundle = ResourceBundle.getBundle(bundle1, locale, loader); if (bundle != null) { try { resource = bundle.getString(resourceId); } catch (MissingResourceException ex) { } } } if (resource == null) { bundle = ResourceBundle.getBundle(bundle2, locale, loader); if (bundle != null) { try { resource = bundle.getString(resourceId); } catch (MissingResourceException ex) { } } } if (resource == null) { return null; // no match } if (params == null) { return resource; } MessageFormat formatter = new MessageFormat(resource, locale); return formatter.format(params); } public static Locale getLocale(FacesContext context) { Locale locale = null; UIViewRoot viewRoot = context.getViewRoot(); if (viewRoot != null) { locale = viewRoot.getLocale(); } if (locale == null) { locale = Locale.getDefault(); } return locale; } public static ClassLoader getClassLoader() { ClassLoader loader = Thread.currentThread().getContextClassLoader(); if (loader == null) { loader = ClassLoader.getSystemClassLoader(); } return loader; } } > rich:notifyMessages not displaying error from valueChangeListener > ----------------------------------------------------------------- > > Key: RF-12063 > URL: https://issues.jboss.org/browse/RF-12063 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.2.0.Final > Environment: Mojarra 2.1.7, RF 4.2.0.Final, Windows 7, Glassfish 3.1.2, Chrome browser. > Reporter: Brendan Healey > > I have a global notifyMessages in a template . > I log a global error in the usual way from a value change listener (process validations > phase): > FacesMessage message = getFacesMessage(errKey); > message.setSeverity(FacesMessage.SEVERITY_ERROR); > FacesContext.getCurrentInstance().addMessage(null, message); > but the error never appears. If I have an h:messages on the page which is ajax > rendered the message appears ok. > Regards, > Brendan. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 29 16:14:49 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Thu, 29 Mar 2012 16:14:49 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12063) rich:notifyMessages not displaying error from valueChangeListener In-Reply-To: <71281469.18246.1332180647276.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1346223673.41516.1333052089710.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem reassigned RF-12063: ---------------------------------- Assignee: Luk?? Fry? Lukas, please assess and schedule accordingly > rich:notifyMessages not displaying error from valueChangeListener > ----------------------------------------------------------------- > > Key: RF-12063 > URL: https://issues.jboss.org/browse/RF-12063 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.2.0.Final > Environment: Mojarra 2.1.7, RF 4.2.0.Final, Windows 7, Glassfish 3.1.2, Chrome browser. > Reporter: Brendan Healey > Assignee: Luk?? Fry? > > I have a global notifyMessages in a template . > I log a global error in the usual way from a value change listener (process validations > phase): > FacesMessage message = getFacesMessage(errKey); > message.setSeverity(FacesMessage.SEVERITY_ERROR); > FacesContext.getCurrentInstance().addMessage(null, message); > but the error never appears. If I have an h:messages on the page which is ajax > rendered the message appears ok. > Regards, > Brendan. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 29 16:18:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Thu, 29 Mar 2012 16:18:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12081) Problem with RichEditor RF 4.2.0 In-Reply-To: <1278339548.27975.1332502007395.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1178087141.41541.1333052327306.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12680447#comment-12680447 ] Brian Leathem commented on RF-12081: ------------------------------------ Could you post the facelet file, and the generated html? I suspect you are including some CSS files/rules that are styling the links of the editor. > Problem with RichEditor RF 4.2.0 > -------------------------------- > > Key: RF-12081 > URL: https://issues.jboss.org/browse/RF-12081 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.2.0.Final > Reporter: phelen harg > Labels: waiting_on_user > Attachments: Sem t?tulo.jpg > > > I'm migrating my Application from RF 3.3.3 to RF 4.2.0. But now i'm facing a problem with the richEditor. When I load the the component, all the links in application receive a background like this picture: > Analizing the code with Firebug, I found the problem in the CSS of RichEditor. /org.richfaces.resources/javax.faces.resource/org.richfaces.ckeditor/skins/richfaces/editor.ecss?db=eAHj0yqqAgACGAEl > If I erase the CSS the backgroud disappear. There is some kind of workaround for this? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 29 16:24:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Thu, 29 Mar 2012 16:24:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12084) Richfaces 4.2 when inside dont work and causes 'identifier resolved to null' In-Reply-To: <1382382061.29574.1332701569056.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <986350853.41600.1333052687898.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12084: ------------------------------- Fix Version/s: 4.3-Tracking Forum Reference: https://community.jboss.org/message/723859, https://community.jboss.org/thread/196867 (was: https://community.jboss.org/message/723859, https://community.jboss.org/thread/196867) > Richfaces 4.2 when inside dont work and causes 'identifier resolved to null' > ----------------------------------------------------------------------------------------------------- > > Key: RF-12084 > URL: https://issues.jboss.org/browse/RF-12084 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.2.0.Final > Environment: Windows Vista, Firefox 11, Richfaces 4.2 Final, Mojarra 2.1.7, Tomcat 7.0.26 > Reporter: Ivan Costa > Labels: richfaces > Fix For: 4.3-Tracking > > > a4j:commandLink or a4j:ajax tags inside ui:fragment causes 'identifier resolved to null', > but h:commandLink + f:ajax (both from Mojarra) works perfectly fine! > The problem is described here > https://community.jboss.org/message/723859 > and here: > https://community.jboss.org/thread/196867 > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 29 16:26:48 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Thu, 29 Mar 2012 16:26:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12094) Provide a feature to rich:dataTable that reflects the default sort order on a column (according to the JPQL statement that produced the list items) In-Reply-To: <815335129.33287.1332835127644.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <686654701.41618.1333052808590.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12094: ------------------------------- Fix Version/s: 4.3-Tracking Forum Reference: https://community.jboss.org/thread/197512 (was: https://community.jboss.org/thread/197512) > Provide a feature to rich:dataTable that reflects the default sort order on a column (according to the JPQL statement that produced the list items) > --------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: RF-12094 > URL: https://issues.jboss.org/browse/RF-12094 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-tables > Reporter: Karsten Wutzke > Fix For: 4.3-Tracking > > > A rich:dataTable list is usually sorted by one or several columns according to the JPQL or other statement that produced the list. > I would be worthwhile to have the rich:dataTable reflect the default ordering state by providing an attribute to rich:column that would set the respective up or down sort arrow instead of the default up-down arrow. By default, e.g. on page reload, if nothing was remembered by the browser, rich:dataTable defaults to the dual up-down arrow for all rich:column's. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 29 16:26:48 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Thu, 29 Mar 2012 16:26:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12094) Provide a feature to rich:dataTable that reflects the default sort order on a column (according to the JPQL statement that produced the list items) In-Reply-To: <815335129.33287.1332835127644.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1005111210.41620.1333052808745.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12094: ------------------------------- Component/s: component-tables Forum Reference: https://community.jboss.org/thread/197512 (was: https://community.jboss.org/thread/197512) > Provide a feature to rich:dataTable that reflects the default sort order on a column (according to the JPQL statement that produced the list items) > --------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: RF-12094 > URL: https://issues.jboss.org/browse/RF-12094 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-tables > Reporter: Karsten Wutzke > Fix For: 4.3-Tracking > > > A rich:dataTable list is usually sorted by one or several columns according to the JPQL or other statement that produced the list. > I would be worthwhile to have the rich:dataTable reflect the default ordering state by providing an attribute to rich:column that would set the respective up or down sort arrow instead of the default up-down arrow. By default, e.g. on page reload, if nothing was remembered by the browser, rich:dataTable defaults to the dual up-down arrow for all rich:column's. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 29 16:26:48 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Thu, 29 Mar 2012 16:26:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12096) Push: there is delay between repeated subscribtion In-Reply-To: <298994236.33589.1332842927828.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <940911867.41622.1333052808811.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12096: ------------------------------- Fix Version/s: 4.3-Tracking > Push: there is delay between repeated subscribtion > -------------------------------------------------- > > Key: RF-12096 > URL: https://issues.jboss.org/browse/RF-12096 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Affects Versions: 4.2.0.Final > Reporter: Luk?? Fry? > Fix For: 4.3-Tracking > > > When you have conditionally rendered {{a4j:push}} component and you disable it, > then it stops to receive push events. > Once you enable it, there is delay before it will start to receive events again. > Sample code for reproduction: > {code:xml} > "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> > xmlns:f="http://java.sun.com/jsf/core" xmlns:a4j="http://richfaces.org/a4j"> > > > > > >



    > > > > > > > > > > > > > > > > > >
    > > > #{richBean.date} > > >
    >     >     >     > > {code} > {code:java} > package demo; > import java.util.Date; > import javax.faces.bean.ManagedBean; > import org.richfaces.application.push.MessageException; > import org.richfaces.application.push.TopicKey; > import org.richfaces.application.push.TopicsContext; > @ManagedBean > public class RichBean { > public Date getDate() { > return new Date(); > } > public void push() throws MessageException { > TopicKey topicKey = new TopicKey("sampleAddress"); > TopicsContext topicsContext = TopicsContext.lookup(); > topicsContext.publish(topicKey, new Date().toString()); > System.out.println("push event"); > } > } > {code} > Steps to reproduce: > 1. open the sample page (the "subscribed" message appears) > 2. click on Push! button (the date is changed) > 3. check the checkbox > 4. click on Push! button (the date is not changed anymore) > 5. uncheck the checkbox (the "subscribed" message appears again) > 6. click on Push! > EXPECTED: the date should be changed > ACTUAL: the date is not changed > If you will wait for some seconds, the Push! button will cause change of the date, > but in this delay, client can lose data updates (since "subscribed" event does not show that the client is starting to receive data). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 29 16:28:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Thu, 29 Mar 2012 16:28:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12097) Richfaces 4.2.0 invalid css entry for *.rf-insl-tt In-Reply-To: <771471005.33626.1332844067523.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <772594337.41628.1333052927373.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12097: ------------------------------- Fix Version/s: 4.3-Tracking > Richfaces 4.2.0 invalid css entry for *.rf-insl-tt > -------------------------------------------------- > > Key: RF-12097 > URL: https://issues.jboss.org/browse/RF-12097 > Project: RichFaces > Issue Type: Bug > Components: skinning > Affects Versions: 4.2.0.Final > Environment: Tomcat 6.0.35 > Richfaces 4.2.0 > Windows 7 > Reporter: Stephan Meisinger > Labels: CSS > Fix For: 4.3-Tracking > > > a invalid css syntax for *.rf-insl-tt for PackedCompressed/DEFAULT/packed/packed.css > *.rf-insl-tt{position:absolute;display:none;padding:2px;border:1px solid "#E5973E ";background-color:#FAE6B0;} > should be > *.rf-insl-tt{position:absolute;display:none;padding:2px;border:1px solid #E5973E;background-color:#FAE6B0;} > see http://www.w3.org/TR/CSS1/#border and http://www.w3.org/TR/CSS1/#color-units -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 29 16:30:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Thu, 29 Mar 2012 16:30:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12098) PickList doesn't accept comma in string value In-Reply-To: <1104299453.33800.1332847428203.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1172858391.41631.1333053047387.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12098: ------------------------------- Fix Version/s: 4.3-Tracking > PickList doesn't accept comma in string value > --------------------------------------------- > > Key: RF-12098 > URL: https://issues.jboss.org/browse/RF-12098 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 4.2.0.Final > Reporter: Stefan Risto > Fix For: 4.3-Tracking > > > The rich:pickList Component does not handle values containing commas. > I used a converter and in the getAsString - Method a String containing a comma was returned, such as "You,Me". After selecting this value in the pick list the converters getAsObject method is called twice, once for "You" and once for "Me". > I would expect to get the same value in getAsObject as the converters getAsString returned. Maybe the comma should be escaped by the component and/or the javascript code. > This Bug seems to be related to RF-6026, but that bug is not targeted for RF 4.X -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 29 16:32:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Thu, 29 Mar 2012 16:32:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12107) Kitchensink archetype - comments additions to the generated pom.xml In-Reply-To: <713779216.37241.1332940307373.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <998630343.41633.1333053167588.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12107: ------------------------------- Fix Version/s: 4.2.1.Final > Kitchensink archetype - comments additions to the generated pom.xml > ------------------------------------------------------------------- > > Key: RF-12107 > URL: https://issues.jboss.org/browse/RF-12107 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: archetype > Affects Versions: 4.2.0.Final > Environment: app generated by Kitchensink archetype > Reporter: Juraj Huska > Priority: Optional > Fix For: 4.2.1.Final > > > I would like to suggest some comments additions, to increase user's comprehension. > - _To the comment above arq-jbossas-managed profile:_ > There should be mentioned that you have to provide path to your JBoss instance, by changing the jbossHome property in arquillian.xml, or we can alter the profile to download and unzip JBoss distribution as it is [here|https://github.com/richfaces/qa/blob/master/pom.xml#L559]. > - _In the same comment as mentioned above_ > There should be definitely mentioned the version of JBoss AS it works with, or there should be this version defined explicitly, since it does not work with all AS 7 distributions > - _The comment above arq-jbossas-remote profile_ > There is the same problem with JBoss AS versions as mentioned above. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 29 16:32:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Thu, 29 Mar 2012 16:32:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12099) Kitchensink archetype - mobile demo - loading the about page causes error on the server side In-Reply-To: <1483697602.34497.1332858348789.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <720537931.41635.1333053167789.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12099: ------------------------------- Fix Version/s: 4.2.1.Final > Kitchensink archetype - mobile demo - loading the about page causes error on the server side > -------------------------------------------------------------------------------------------- > > Key: RF-12099 > URL: https://issues.jboss.org/browse/RF-12099 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: archetype > Affects Versions: 4.2.0.Final > Environment: mobile demo for project generated by Kitchensink archetype > Reporter: Juraj Huska > Priority: Minor > Fix For: 4.2.1.Final > > > After clicking on the link(the info button - small blue i in white circle) which should point to the about page, following error is thrown on the server side: > {code} > 16:15:07,894 SEVERE [org.richfaces.log.Context] (http--0.0.0.0-8080-4) /resources/components/memberForm.xhtml @19,62 value="#{cc.attrs.member.name}": Target Unreachable, 'member' returned null: javax.el.PropertyNotFoundException: /resources/components/memberForm.xhtml @19,62 value="#{cc.attrs.member.name}": Target Unreachable, 'member' returned null > at com.sun.faces.facelets.el.TagValueExpression.getType(TagValueExpression.java:100) [jsf-impl-2.1.7-jbossorg-2.jar:] > at com.sun.faces.renderkit.html_basic.HtmlBasicInputRenderer.getConvertedValue(HtmlBasicInputRenderer.java:95) [jsf-impl-2.1.7-jbossorg-2.jar:] > at javax.faces.component.UIInput.getConvertedValue(UIInput.java:1030) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] > at javax.faces.component.UIInput.validate(UIInput.java:960) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] > at javax.faces.component.UIInput.executeValidate(UIInput.java:1233) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] > at javax.faces.component.UIInput.processValidators(UIInput.java:698) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] > at javax.faces.component.UIComponentBase.processValidators(UIComponentBase.java:1214) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] > at javax.faces.component.UIComponentBase.processValidators(UIComponentBase.java:1214) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] > at javax.faces.component.UIComponentBase.processValidators(UIComponentBase.java:1214) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] > at javax.faces.component.UIComponentBase.processValidators(UIComponentBase.java:1214) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] > at javax.faces.component.UIForm.processValidators(UIForm.java:253) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] > at org.richfaces.context.PartialViewExecuteVisitCallback.visit(PartialViewExecuteVisitCallback.java:55) [richfaces-core-impl-4.3.0-20120302.170417-5.jar:4.3.0-SNAPSHOT] > at org.richfaces.context.BaseExtendedVisitContext.invokeVisitCallback(BaseExtendedVisitContext.java:321) [richfaces-core-impl-4.3.0-20120302.170417-5.jar:4.3.0-SNAPSHOT] > at javax.faces.component.UIForm.visitTree(UIForm.java:381) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] > at javax.faces.component.UIComponent.visitTree(UIComponent.java:1623) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] > at javax.faces.component.UIComponent.visitTree(UIComponent.java:1623) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] > at org.richfaces.context.ExtendedPartialViewContextImpl.executeComponents(ExtendedPartialViewContextImpl.java:237) [richfaces-core-impl-4.3.0-20120302.170417-5.jar:4.3.0-SNAPSHOT] > at org.richfaces.context.ExtendedPartialViewContextImpl.processPartialExecutePhase(ExtendedPartialViewContextImpl.java:217) [richfaces-core-impl-4.3.0-20120302.170417-5.jar:4.3.0-SNAPSHOT] > at org.richfaces.context.ExtendedPartialViewContextImpl.processPartial(ExtendedPartialViewContextImpl.java:196) [richfaces-core-impl-4.3.0-20120302.170417-5.jar:4.3.0-SNAPSHOT] > at javax.faces.component.UIViewRoot.processValidators(UIViewRoot.java:1170) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] > at com.sun.faces.lifecycle.ProcessValidationsPhase.execute(ProcessValidationsPhase.java:76) [jsf-impl-2.1.7-jbossorg-2.jar:] > at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) [jsf-impl-2.1.7-jbossorg-2.jar:] > at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118) [jsf-impl-2.1.7-jbossorg-2.jar:] > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:593) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:62) [weld-core-1.1.5.AS71.Final.jar:2012-02-10 15:31] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.13.Final.jar:] > at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.1.1.Final.jar:7.1.1.Final] > at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final] > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.13.Final.jar:] > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.13.Final.jar:] > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.13.Final.jar:] > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.13.Final.jar:] > at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_22] > {code} > The about page is loaded successfully, however after next attempts to click on the same link results in loading blank page. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 29 16:32:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Thu, 29 Mar 2012 16:32:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12100) Kitchensink archetype - mobile demo - adding new member causes rendering blank page In-Reply-To: <2080953888.34709.1332860812065.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1968579288.41637.1333053167944.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12100: ------------------------------- Fix Version/s: 4.2.1.Final > Kitchensink archetype - mobile demo - adding new member causes rendering blank page > ----------------------------------------------------------------------------------- > > Key: RF-12100 > URL: https://issues.jboss.org/browse/RF-12100 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: archetype > Affects Versions: 4.2.0.Final > Environment: mobile demo for Kitchensink archetype > Reporter: Juraj Huska > Fix For: 4.2.1.Final > > Attachments: blank.png > > > When you add new member, either from mobile or from desktop kitchensink demo, *all loaded mobile demos* will be (after retrieving the push from the server) rendering the blank page. > As blank, I mean just the header of the page, please see the screenshot. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 29 16:32:48 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Thu, 29 Mar 2012 16:32:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12102) Kitchensink archetype - shutdown of JBoss AS with project generated from this archetype throws error In-Reply-To: <1394038810.35167.1332868307274.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1588451654.41639.1333053168092.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12102: ------------------------------- Fix Version/s: 4.2.1.Final > Kitchensink archetype - shutdown of JBoss AS with project generated from this archetype throws error > ---------------------------------------------------------------------------------------------------- > > Key: RF-12102 > URL: https://issues.jboss.org/browse/RF-12102 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: archetype > Affects Versions: 4.2.0.Final > Environment: container: JBoss AS 7.1.1.Final > Reporter: Juraj Huska > Priority: Trivial > Fix For: 4.2.1.Final > > > There is the same error thrown as in RF-11905, when shutting down the server. > Kitchensink uses his own DS configuration, and it is enough to add proposed DB_CLOSE_ON_EXIT=FALSE to the connection url, in the file _/src/main/webapp/WEB-INF/kitchensink-quickstart-ds.xml_, in order to workaround the error. > So it will look like: > {code:xml} > jdbc:h2:mem:kitchensink-quickstart;DB_CLOSE_ON_EXIT=FALSE > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 29 16:32:48 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Thu, 29 Mar 2012 16:32:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12101) Kitchensink example - rich:messages does not provide additional info, they are quite misleading In-Reply-To: <1230939528.35068.1332866267338.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1422511658.41641.1333053168186.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12101: ------------------------------- Fix Version/s: 4.2.1.Final > Kitchensink example - rich:messages does not provide additional info, they are quite misleading > ----------------------------------------------------------------------------------------------- > > Key: RF-12101 > URL: https://issues.jboss.org/browse/RF-12101 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: archetype > Affects Versions: 4.2.0.Final > Environment: app generated by the kitchensink archetype > browser: Chrome, Firefox, mobile devices browser(iPhone) > Reporter: Juraj Huska > Priority: Optional > Fix For: 4.2.1.Final > > Attachments: IMG_0038.PNG > > > IMHO the rich:messages tag should be removed, since there is already rich:message generated for every input, and they are not giving additional information, on the contrary they are misleading. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 29 16:34:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Thu, 29 Mar 2012 16:34:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12103) onmouse events dont working on rich:notifyMessage In-Reply-To: <1986202609.36071.1332916247280.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1949029958.41644.1333053287410.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem reassigned RF-12103: ---------------------------------- Assignee: Luk?? Fry? Lukas, please assess and schedule accordingly. > onmouse events dont working on rich:notifyMessage > ------------------------------------------------- > > Key: RF-12103 > URL: https://issues.jboss.org/browse/RF-12103 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.2.0.Final > Reporter: Antonio Rodriguez > Assignee: Luk?? Fry? > Labels: notifyMessage, onclick, onmouseover, richfaces4 > > Hi, im using rich:notifyStack and rich:notifyMessage to show erros of required=true h:inputText. > All goes OK but i need that onclick event over the notifiyMessage, the cursor go focused on the h:inputText associated with the notifyMessage. I noticed that the events (onmouseover, onclick, onmouseout...) doesnt work on notifyMessages. > However, this events goes OK on rich:message. > Does anybody knows why the mouse events dont work with notifyMessages??? > Thanks -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 29 16:34:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Thu, 29 Mar 2012 16:34:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12105) panelToggleListener attribute @listener does not work In-Reply-To: <1942473592.36521.1332923507950.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1941009891.41646.1333053287478.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12105: ------------------------------- Fix Version/s: 4.3-Tracking Component/s: component-panels-layout-themes (was: component-misc) > panelToggleListener attribute @listener does not work > ----------------------------------------------------- > > Key: RF-12105 > URL: https://issues.jboss.org/browse/RF-12105 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.2.0.Final > Environment: RichFaces 4.2.1-SNAPSHOT > Metamer 4.2.1-SNAPSHOT > Mojarra 2.1.5-SNAPSHOT > JBoss AS 7.1.0.Final > OpenJDK Runtime Environment 1.6.0_24-b24 @ Linux > Firefox 11.0 @ Linux x86_64 > Reporter: Ji?? ?tefek > Fix For: 4.3-Tracking > > > # Deploy Metamer. > # Open http://localhost:8080/metamer/faces/components/richPanelToggleListener/collapsiblePanel.xhtml > # Click on chevron to collapse a panel. > # Messages with "* pannelToggleListenerBean panel collapsed" should appear in phases list. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 29 16:34:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Thu, 29 Mar 2012 16:34:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12106) panelToggleListener attribute @for does not work In-Reply-To: <581703508.36545.1332924227837.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1341564360.41647.1333053287519.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12680453#comment-12680453 ] Brian Leathem commented on RF-12106: ------------------------------------ What do you see? What do you expect to see? > panelToggleListener attribute @for does not work > ------------------------------------------------ > > Key: RF-12106 > URL: https://issues.jboss.org/browse/RF-12106 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-misc > Affects Versions: 4.2.0.Final > Environment: RichFaces 4.2.1-SNAPSHOT > Metamer 4.2.1-SNAPSHOT > Mojarra 2.1.5-SNAPSHOT > JBoss AS 7.1.0.Final > OpenJDK Runtime Environment 1.6.0_24-b24 @ Linux > Firefox 11.0 @ Linux x86_64 > Reporter: Ji?? ?tefek > > # Deploy Metamer. > # Open http://localhost:8080/metamer/faces/components/richPanelToggleListener/RF-12106.xhtml -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 29 16:38:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Thu, 29 Mar 2012 16:38:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12108) Components second tab changes are not rendered after performing some ajax action if attribute ajaxRendered="true" inside located on first tab In-Reply-To: <975271229.37623.1332944389491.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <100020479.41655.1333053527646.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-12108. -------------------------------- Resolution: Rejected > Components second tab changes are not rendered after performing some ajax action if attribute ajaxRendered="true" inside located on first tab > --------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: RF-12108 > URL: https://issues.jboss.org/browse/RF-12108 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.2.0.Final > Environment: JDK1.6, > JBoss 6.0.Final, > richfaces 4.1.0.Final/4.2.0.Final > seam 3.1 > IE 9 > Reporter: Artur Mioduszewski > > In case getting 2 tabs (in my case it is primefaces tabs): > {code:title=RENDERING ON SECOND TAB NOT WORKS (after clicking link)} > First tab: > > > > > Second tab (some code with ajax) > Ex. > > > > > {code} > {code:title=RENDERING ON SECOND TAB CORRECTLY WORKS (after clicking link)} > First tab: > > > > > Second tab (some code with ajax) > Ex. > > > > > {code} > When I change tabs order, problem does not exist. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 29 16:38:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Thu, 29 Mar 2012 16:38:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12108) Components second tab changes are not rendered after performing some ajax action if attribute ajaxRendered="true" inside located on first tab In-Reply-To: <975271229.37623.1332944389491.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1420605051.41651.1333053527445.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-12108. -------------------------------- Resolution: Done Primefaces does not use the standardized JSF ajax mechanism for submitting ajax requests, but instead using the jquery ajax mechanism. The two approaches are not compatible. Feel free to re-open this issue if you use components based on the standardized JSF ajax mechanism. > Components second tab changes are not rendered after performing some ajax action if attribute ajaxRendered="true" inside located on first tab > --------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: RF-12108 > URL: https://issues.jboss.org/browse/RF-12108 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.2.0.Final > Environment: JDK1.6, > JBoss 6.0.Final, > richfaces 4.1.0.Final/4.2.0.Final > seam 3.1 > IE 9 > Reporter: Artur Mioduszewski > > In case getting 2 tabs (in my case it is primefaces tabs): > {code:title=RENDERING ON SECOND TAB NOT WORKS (after clicking link)} > First tab: > > > > > Second tab (some code with ajax) > Ex. > > > > > {code} > {code:title=RENDERING ON SECOND TAB CORRECTLY WORKS (after clicking link)} > First tab: > > > > > Second tab (some code with ajax) > Ex. > > > > > {code} > When I change tabs order, problem does not exist. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 29 16:38:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Thu, 29 Mar 2012 16:38:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12108) Components second tab changes are not rendered after performing some ajax action if attribute ajaxRendered="true" inside located on first tab In-Reply-To: <975271229.37623.1332944389491.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <982000619.41654.1333053527551.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem reopened RF-12108: -------------------------------- > Components second tab changes are not rendered after performing some ajax action if attribute ajaxRendered="true" inside located on first tab > --------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: RF-12108 > URL: https://issues.jboss.org/browse/RF-12108 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.2.0.Final > Environment: JDK1.6, > JBoss 6.0.Final, > richfaces 4.1.0.Final/4.2.0.Final > seam 3.1 > IE 9 > Reporter: Artur Mioduszewski > > In case getting 2 tabs (in my case it is primefaces tabs): > {code:title=RENDERING ON SECOND TAB NOT WORKS (after clicking link)} > First tab: > > > > > Second tab (some code with ajax) > Ex. > > > > > {code} > {code:title=RENDERING ON SECOND TAB CORRECTLY WORKS (after clicking link)} > First tab: > > > > > Second tab (some code with ajax) > Ex. > > > > > {code} > When I change tabs order, problem does not exist. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 29 16:40:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Thu, 29 Mar 2012 16:40:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12110) [rich:contextMenu] contextmenu doesn't work anymore if an ajax request is fired while contextmenu is visible In-Reply-To: <2058795180.40029.1333022087624.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1855568664.41660.1333053647384.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12110: ------------------------------- Fix Version/s: 4.3-Tracking Assignee: Brian Leathem Component/s: component-selects > [rich:contextMenu] contextmenu doesn't work anymore if an ajax request is fired while contextmenu is visible > ------------------------------------------------------------------------------------------------------------ > > Key: RF-12110 > URL: https://issues.jboss.org/browse/RF-12110 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 4.2.0.Final > Environment: Tomcat 7, myfaces-2.1.6, richfaces-4.2.0.Final and 4.2.1-SNAPSHOT > Reporter: Rene O > Assignee: Brian Leathem > Fix For: 4.3-Tracking > > > The example shows the problem: > {code:title=example.xhtml} > > xmlns:h="http://java.sun.com/jsf/html" > xmlns:f="http://java.sun.com/jsf/core" > xmlns:ui="http://java.sun.com/jsf/facelets" > xmlns:a4j="http://richfaces.org/a4j" > xmlns:rich="http://richfaces.org/rich"> > > > JSF Test > > > Steps to reproduce the issue: >

    > 1. right click to show context menu >
    > 2. wait till context menu hides >
    > 3. click button 'click me' >
    > 4. right click to show context menu >
    > 5. context menu is visible >

    > Now do the following >
    > 1. right click to show context menu >
    > 2. click button 'click me' before context menu hides >
    > 3. right click to show context menu >
    > 4. context menu doesn't work anymore... >

    > > >
    > > right click for context-menu > > > > Test > > >     >     > > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 29 16:40:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Thu, 29 Mar 2012 16:40:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12113) rich:inputNumberSpinner minValue and maxValue being ignored after second request In-Reply-To: <1286311086.40531.1333034148641.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1397291427.41663.1333053647484.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12113: ------------------------------- Fix Version/s: 4.3-Tracking > rich:inputNumberSpinner minValue and maxValue being ignored after second request > -------------------------------------------------------------------------------- > > Key: RF-12113 > URL: https://issues.jboss.org/browse/RF-12113 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.2.0.Final > Environment: Windows 7 x64, Firefox/Waterfox v10.0.1, Chrome v17.0.963.83 m, IE8 64-bit v8.0.7601.17514 > Reporter: Leo Higgins > Fix For: 4.3-Tracking > > > When setting the value of the component to a value either below the specified minValue or above the specified maxValue, the component correctly sets the value to either the minValue or the maxValue. > On a subsequent request, however, the component does not set the value to the minValue or the maxValue. This bug exists on all above browsers at the Richfaces showcase here: > http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=inputNumberSpinner&skin=blueSky -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 29 16:40:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Thu, 29 Mar 2012 16:40:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12106) panelToggleListener attribute @for does not work In-Reply-To: <581703508.36545.1332924227837.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <440857993.41665.1333053647599.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem reassigned RF-12106: ---------------------------------- Assignee: Ji?? ?tefek > panelToggleListener attribute @for does not work > ------------------------------------------------ > > Key: RF-12106 > URL: https://issues.jboss.org/browse/RF-12106 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-misc > Affects Versions: 4.2.0.Final > Environment: RichFaces 4.2.1-SNAPSHOT > Metamer 4.2.1-SNAPSHOT > Mojarra 2.1.5-SNAPSHOT > JBoss AS 7.1.0.Final > OpenJDK Runtime Environment 1.6.0_24-b24 @ Linux > Firefox 11.0 @ Linux x86_64 > Reporter: Ji?? ?tefek > Assignee: Ji?? ?tefek > > # Deploy Metamer. > # Open http://localhost:8080/metamer/faces/components/richPanelToggleListener/RF-12106.xhtml -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 29 16:51:47 2012 From: jira-events at lists.jboss.org (Jean ANDRE (JIRA)) Date: Thu, 29 Mar 2012 16:51:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12032) rich:calendar : Ajax request - Error message enhancement - sql.Date In-Reply-To: <1406650855.77949.1331220940774.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1507496368.41674.1333054307777.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12680456#comment-12680456 ] Jean ANDRE commented on RF-12032: --------------------------------- 1) Yes of course 2) I do not remember - it is an idea - however, there was a h:messages on the calendar as we got some message (see screen shot) but no message for the conversion error. With the workbench, we can easily test the case has I have add a calendar in one screen and modify the backing bean (controller) for sql.Date type. sql.Date and util.Date are both native standard format to java. Why do not support them as standard. Moreover, most of the time, we received the data from the database/ORM and the date is SQL date. What about having something like "auto-boxing" or automatic conversion when it is feasible for native format? We are not alone for this needs and around. - https://community.jboss.org/thread/10589 - http://stackoverflow.com/questions/7982528/rich-calendar-date-formatting - http://stackoverflow.com/questions/7397096/how-to-check-null-value-for-date-object - http://www.developpez.net/forums/d739236/java/developpement-web-java/frameworks/jsf/probleme-rich-calendar/ - http://www.developpez.net/forums/d967420/java/developpement-web-java/frameworks/jsf/probleme-rich-calendar/ > rich:calendar : Ajax request - Error message enhancement - sql.Date > ------------------------------------------------------------------- > > Key: RF-12032 > URL: https://issues.jboss.org/browse/RF-12032 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Environment: cssparser-0.9.6 - guava-11.0.1 - hibernate-validator-4.2.0.Final - JSF/Mojarra 2.1.6 - springframework-3.0.6.RELEASE - richfaces-4.2.0.Final - sac-1.3.jar - Windows 7, WAS 8.0.0.1, Servlet 2.5 - Java 6. > Reporter: Jean ANDRE > Labels: waiting_on_user > Attachments: rich_calendar_errorMsg_Enhancement.png > > > When a backing-bean have a type of sql.Date which is mapped to a rich:calendar, there is an conversion error due to the rich:calendar component uses util.Date by default. Unfortunately, we do not see any error message at the screen when an ajax request is sent and returned back to us. > What we got, and thanks to Firebug, is the text below as an answer from our Ajax request POST. Nothing is rendered at the screen and the method of the backing bean is not called. > {code} > > class javax.faces.component.UpdateModelException > {code} > Our code looks like this (we remove unecessary field and decoration): > {code} > > > > > value="#{msg['common.command.add.phone']}" > action="#{createClientController.doAddPhone}"> > > > > > > > value="#{phoneBean.effectiveDate}" > popup="true" > showApplyButton="false" > enableManualInput="true" > datePattern="#{msg['client.date.format']}" > inputSize="12" > styleClass="calendar"> > > > > > > > > {code} > Is is possible to have a message returned back to the UI??? or is there a way to handle this error properly? > Other information > ================= > The form is inside a dynamic tab - Fragment are also include dynamically - we use c:if et subView as shown below: > {code} > > > > > > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 29 16:53:47 2012 From: jira-events at lists.jboss.org (Jean ANDRE (JIRA)) Date: Thu, 29 Mar 2012 16:53:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12032) rich:calendar : Ajax request - Error message enhancement - sql.Date In-Reply-To: <1406650855.77949.1331220940774.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <223321497.41679.1333054427685.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12680456#comment-12680456 ] Jean ANDRE edited comment on RF-12032 at 3/29/12 4:52 PM: ---------------------------------------------------------- 1) Yes of course 2) I do not remember - it is an idea - however, there was a h:messages on the calendar as we got some message (see screen shot) but no message for the conversion error. With the workbench, we can easily test the case as I have added a calendar in one screen by default - We just need to modify the backing bean (controller) for sql.Date type and see what is appening. sql.Date and util.Date are both native standard format to java. Why do not support them as standard. Moreover, most of the time, we received the data from the database/ORM and the date is SQL date. What about having something like "auto-boxing" or automatic conversion when it is feasible for native format? We are not alone for this needs and around. - https://community.jboss.org/thread/10589 - http://stackoverflow.com/questions/7982528/rich-calendar-date-formatting - http://stackoverflow.com/questions/7397096/how-to-check-null-value-for-date-object - http://www.developpez.net/forums/d739236/java/developpement-web-java/frameworks/jsf/probleme-rich-calendar/ - http://www.developpez.net/forums/d967420/java/developpement-web-java/frameworks/jsf/probleme-rich-calendar/ was (Author: jorelia64): 1) Yes of course 2) I do not remember - it is an idea - however, there was a h:messages on the calendar as we got some message (see screen shot) but no message for the conversion error. With the workbench, we can easily test the case has I have add a calendar in one screen and modify the backing bean (controller) for sql.Date type. sql.Date and util.Date are both native standard format to java. Why do not support them as standard. Moreover, most of the time, we received the data from the database/ORM and the date is SQL date. What about having something like "auto-boxing" or automatic conversion when it is feasible for native format? We are not alone for this needs and around. - https://community.jboss.org/thread/10589 - http://stackoverflow.com/questions/7982528/rich-calendar-date-formatting - http://stackoverflow.com/questions/7397096/how-to-check-null-value-for-date-object - http://www.developpez.net/forums/d739236/java/developpement-web-java/frameworks/jsf/probleme-rich-calendar/ - http://www.developpez.net/forums/d967420/java/developpement-web-java/frameworks/jsf/probleme-rich-calendar/ > rich:calendar : Ajax request - Error message enhancement - sql.Date > ------------------------------------------------------------------- > > Key: RF-12032 > URL: https://issues.jboss.org/browse/RF-12032 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Environment: cssparser-0.9.6 - guava-11.0.1 - hibernate-validator-4.2.0.Final - JSF/Mojarra 2.1.6 - springframework-3.0.6.RELEASE - richfaces-4.2.0.Final - sac-1.3.jar - Windows 7, WAS 8.0.0.1, Servlet 2.5 - Java 6. > Reporter: Jean ANDRE > Labels: waiting_on_user > Attachments: rich_calendar_errorMsg_Enhancement.png > > > When a backing-bean have a type of sql.Date which is mapped to a rich:calendar, there is an conversion error due to the rich:calendar component uses util.Date by default. Unfortunately, we do not see any error message at the screen when an ajax request is sent and returned back to us. > What we got, and thanks to Firebug, is the text below as an answer from our Ajax request POST. Nothing is rendered at the screen and the method of the backing bean is not called. > {code} > > class javax.faces.component.UpdateModelException > {code} > Our code looks like this (we remove unecessary field and decoration): > {code} > > > > > value="#{msg['common.command.add.phone']}" > action="#{createClientController.doAddPhone}"> > > > > > > > value="#{phoneBean.effectiveDate}" > popup="true" > showApplyButton="false" > enableManualInput="true" > datePattern="#{msg['client.date.format']}" > inputSize="12" > styleClass="calendar"> > > > > > > > > {code} > Is is possible to have a message returned back to the UI??? or is there a way to handle this error properly? > Other information > ================= > The form is inside a dynamic tab - Fragment are also include dynamically - we use c:if et subView as shown below: > {code} > > > > > > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 29 16:53:48 2012 From: jira-events at lists.jboss.org (Jean ANDRE (JIRA)) Date: Thu, 29 Mar 2012 16:53:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12032) rich:calendar : Ajax request - Error message enhancement - sql.Date In-Reply-To: <1406650855.77949.1331220940774.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1597471984.41686.1333054428041.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12680456#comment-12680456 ] Jean ANDRE edited comment on RF-12032 at 3/29/12 4:53 PM: ---------------------------------------------------------- 1) Yes of course 2) I do not remember - it is an idea - however, there was a h:messages on the calendar as we got some message (see screen shot) but no message for the conversion error. With the workbench, we can easily test the case as I have added a calendar in one screen by default - We just need to modify the backing bean (controller) for sql.Date type and see what is appening. sql.Date and util.Date are both native standard format to java. Why do not support them as standard. Moreover, most of the time, we received the data from the database/ORM and the date is SQL date. What about having something like "auto-boxing" or automatic conversion when it is feasible for native format? We are not alone for this need and around. - https://community.jboss.org/thread/10589 - http://stackoverflow.com/questions/7982528/rich-calendar-date-formatting - http://stackoverflow.com/questions/7397096/how-to-check-null-value-for-date-object - http://www.developpez.net/forums/d739236/java/developpement-web-java/frameworks/jsf/probleme-rich-calendar/ - http://www.developpez.net/forums/d967420/java/developpement-web-java/frameworks/jsf/probleme-rich-calendar/ was (Author: jorelia64): 1) Yes of course 2) I do not remember - it is an idea - however, there was a h:messages on the calendar as we got some message (see screen shot) but no message for the conversion error. With the workbench, we can easily test the case as I have added a calendar in one screen by default - We just need to modify the backing bean (controller) for sql.Date type and see what is appening. sql.Date and util.Date are both native standard format to java. Why do not support them as standard. Moreover, most of the time, we received the data from the database/ORM and the date is SQL date. What about having something like "auto-boxing" or automatic conversion when it is feasible for native format? We are not alone for this needs and around. - https://community.jboss.org/thread/10589 - http://stackoverflow.com/questions/7982528/rich-calendar-date-formatting - http://stackoverflow.com/questions/7397096/how-to-check-null-value-for-date-object - http://www.developpez.net/forums/d739236/java/developpement-web-java/frameworks/jsf/probleme-rich-calendar/ - http://www.developpez.net/forums/d967420/java/developpement-web-java/frameworks/jsf/probleme-rich-calendar/ > rich:calendar : Ajax request - Error message enhancement - sql.Date > ------------------------------------------------------------------- > > Key: RF-12032 > URL: https://issues.jboss.org/browse/RF-12032 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Environment: cssparser-0.9.6 - guava-11.0.1 - hibernate-validator-4.2.0.Final - JSF/Mojarra 2.1.6 - springframework-3.0.6.RELEASE - richfaces-4.2.0.Final - sac-1.3.jar - Windows 7, WAS 8.0.0.1, Servlet 2.5 - Java 6. > Reporter: Jean ANDRE > Labels: waiting_on_user > Attachments: rich_calendar_errorMsg_Enhancement.png > > > When a backing-bean have a type of sql.Date which is mapped to a rich:calendar, there is an conversion error due to the rich:calendar component uses util.Date by default. Unfortunately, we do not see any error message at the screen when an ajax request is sent and returned back to us. > What we got, and thanks to Firebug, is the text below as an answer from our Ajax request POST. Nothing is rendered at the screen and the method of the backing bean is not called. > {code} > > class javax.faces.component.UpdateModelException > {code} > Our code looks like this (we remove unecessary field and decoration): > {code} > > > > > value="#{msg['common.command.add.phone']}" > action="#{createClientController.doAddPhone}"> > > > > > > > value="#{phoneBean.effectiveDate}" > popup="true" > showApplyButton="false" > enableManualInput="true" > datePattern="#{msg['client.date.format']}" > inputSize="12" > styleClass="calendar"> > > > > > > > > {code} > Is is possible to have a message returned back to the UI??? or is there a way to handle this error properly? > Other information > ================= > The form is inside a dynamic tab - Fragment are also include dynamically - we use c:if et subView as shown below: > {code} > > > > > > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Mar 29 21:03:47 2012 From: jira-events at lists.jboss.org (Ivan Costa (JIRA)) Date: Thu, 29 Mar 2012 21:03:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12114) Richfaces 4.2 rich:autocomplete don't fire ajax on blur event Message-ID: <1022471400.42032.1333069427412.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Ivan Costa created RF-12114: ------------------------------- Summary: Richfaces 4.2 rich:autocomplete don't fire ajax on blur event Key: RF-12114 URL: https://issues.jboss.org/browse/RF-12114 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-a4j-core, component-input Affects Versions: 4.2.0.Final Environment: Richfaces 4.2 Final, Mojarra 2.1.7, Tomcat 7.0.26 Reporter: Ivan Costa rich:autocomplete don?t call actionListener on blur event -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 30 01:31:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Fri, 30 Mar 2012 01:31:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12091) rich:dataScroller scrollListener not documented In-Reply-To: <1487113708.31251.1332772548274.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <782771300.42116.1333085507675.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12091: ------------------------------- Comment: was deleted (was: Looks like the method: {code} public DataScrollListener[] getScrollListeners() { return (DataScrollListener[]) getFacesListeners(DataScrollListener.class); } {code} is missing the @Attribute annotation. It should be added, with generate=false.) > rich:dataScroller scrollListener not documented > ----------------------------------------------- > > Key: RF-12091 > URL: https://issues.jboss.org/browse/RF-12091 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: 4.2.0.Final > Reporter: Dupont Dupont > Assignee: Brian Leathem > Fix For: 4.2.1.CR1 > > > rich:dataScroller has a scrollListener attribute, but it's not documented (no occurence in component reference or in taglib.xml). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 30 09:35:48 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 30 Mar 2012 09:35:48 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-9443) switchable panels: It should be possible to iterate child panels using a4j:repeat component In-Reply-To: <1010028052.19325.1286380239792.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <845949686.43353.1333114548454.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-9443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12680621#comment-12680621 ] Luk?? Fry? commented on RF-9443: -------------------------------- This issue has been discussed on team meeting, the minutes are here: 4. Dynamic switchable panels (bleathem, 14:50:46) http://transcripts.jboss.org/meeting/irc.freenode.org/richfaces/2012/richfaces.2012-03-20-14.01.html This issue is concurrent request for RF-12029. However this solution allows bigger variability, since you could combine dynamic and static parts. > switchable panels: It should be possible to iterate child panels using a4j:repeat component > ------------------------------------------------------------------------------------------- > > Key: RF-9443 > URL: https://issues.jboss.org/browse/RF-9443 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.0.0.Milestone2 > Reporter: Ilya Shaikovsky > Fix For: 4.Future > > > requirement present there - http://community.jboss.org/wiki/RichFaces4xswitchablepanels > Alex, consider this issue to implementation only after all the new components tasks for M4. If will not fit - postpone to next one as it has workaround. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 30 09:35:49 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 30 Mar 2012 09:35:49 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12029) AbstractTogglePanel should extend UIRepeat, instead of UIOutput In-Reply-To: <1430073926.75557.1331161056577.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <366336221.43360.1333114549712.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12680622#comment-12680622 ] Luk?? Fry? commented on RF-12029: --------------------------------- This issue has been discussed on team meeting, the minutes are here: 4. Dynamic switchable panels (bleathem, 14:50:46) http://transcripts.jboss.org/meeting/irc.freenode.org/richfaces/2012/richfaces.2012-03-20-14.01.html This issue is concurrent request for RF-9443. > AbstractTogglePanel should extend UIRepeat, instead of UIOutput > --------------------------------------------------------------- > > Key: RF-12029 > URL: https://issues.jboss.org/browse/RF-12029 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-output > Reporter: Brian Leathem > Assignee: Bernard Labno > > Valid uses exist for dynamically generating rich:tab, rich:togglePanelItem, rich:accordionItem. Current techniques for supporting this use case involve using c:forEach, which is a problem since c: tags are processed too early to nicely support dynamic use cases. > One idea to support this use case, is to have AbstractTogglePanel extend UIRepeat, instead of UIOutput to better dynamic child components. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 30 09:55:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 30 Mar 2012 09:55:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11833) Label for calendar results in non-valid markup In-Reply-To: <1824573501.21859.1324327990123.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1173473290.43487.1333115747929.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12680639#comment-12680639 ] Luk?? Fry? commented on RF-11833: --------------------------------- Filed spec issue: http://java.net/jira/browse/JAVASERVERFACES_SPEC_PUBLIC-1086 > Label for calendar results in non-valid markup > ---------------------------------------------- > > Key: RF-11833 > URL: https://issues.jboss.org/browse/RF-11833 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.1.0.Final > Reporter: Pavol Pitonak > Assignee: Luk?? Fry? > > The code in first code snippet results in markup below which is not valid. The for attribute of the label element must refer to a form control, e.g. the actual input inside calendar (that with ID dateForm:fromDateInputDate). > {code:xml} > > > {code} > {code:xml} > > > > > ... > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 30 09:57:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 30 Mar 2012 09:57:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11833) Label for calendar results in non-valid markup In-Reply-To: <1824573501.21859.1324327990123.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <605340444.43491.1333115867310.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved RF-11833. ----------------------------- Resolution: Rejected Rejected as spec issue. > Label for calendar results in non-valid markup > ---------------------------------------------- > > Key: RF-11833 > URL: https://issues.jboss.org/browse/RF-11833 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.1.0.Final > Reporter: Pavol Pitonak > Assignee: Luk?? Fry? > > The code in first code snippet results in markup below which is not valid. The for attribute of the label element must refer to a form control, e.g. the actual input inside calendar (that with ID dateForm:fromDateInputDate). > {code:xml} > > > {code} > {code:xml} > > > > > ... > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 30 10:07:47 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 30 Mar 2012 10:07:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12044) Metamer: @preventDefault attribute of rich:hotKey component doesn't work in IE 9 and Google Chrome In-Reply-To: <283065864.9549.1331739467659.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <458212685.43505.1333116467498.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12680642#comment-12680642 ] Luk?? Fry? commented on RF-12044: --------------------------------- Added page for known limitations: https://community.jboss.org/wiki/RichhotKey-PreventDefault-KnownLimitations > Metamer: @preventDefault attribute of rich:hotKey component doesn't work in IE 9 and Google Chrome > -------------------------------------------------------------------------------------------------- > > Key: RF-12044 > URL: https://issues.jboss.org/browse/RF-12044 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-misc > Affects Versions: 4.2.0.Final > Environment: RichFaces 4.2.1-SNAPSHOT > Metamer 4.2.1-SNAPSHOT > Mojarra 2.1.5-SNAPSHOT > JBoss AS 7.1.0.Final > Java(TM) SE Runtime Environment 1.6.0_31-b04 @ Linux > Chrome 17.0.963.78 @ Linux i686 > ?RichFaces 4.2.1-SNAPSHOT > ?Metamer 4.2.1-SNAPSHOT > ?Mojarra 2.1.5-SNAPSHOT > ?JBoss AS 7.1.0.Final > ?Java(TM) SE Runtime Environment 1.6.0_31-b04 @ Linux > ?Internet Explorer 9.0 @ Win32 > Reporter: Jan Papousek > Assignee: Luk?? Fry? > Labels: Chrome, IE9 > > It's working correctly in Firefox 10. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 30 13:07:47 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Fri, 30 Mar 2012 13:07:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12115) Consider a method for attaching RF events via a jQuery selector Message-ID: <157141177.44170.1333127267982.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Brian Leathem created RF-12115: ---------------------------------- Summary: Consider a method for attaching RF events via a jQuery selector Key: RF-12115 URL: https://issues.jboss.org/browse/RF-12115 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Components: component-a4j-core Reporter: Brian Leathem Write now we can attach events either by Id, or by element. We could achieve more flexibility by attaching events directly by jQuery selector. Something like rf.Event.bindByJquerySelector (name TBD) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 30 14:17:47 2012 From: jira-events at lists.jboss.org (Adrien Adrien (JIRA)) Date: Fri, 30 Mar 2012 14:17:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12116) RF 4.2 : jquery not generated for function Message-ID: <880788296.44278.1333131467294.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Adrien Adrien created RF-12116: ---------------------------------- Summary: RF 4.2 : jquery not generated for function Key: RF-12116 URL: https://issues.jboss.org/browse/RF-12116 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.2.0.Final Environment: JBoss 7.1 /RF4.2 Reporter: Adrien Adrien This code doesn t generate javascript expected Code generated in html page Expected something like : -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 30 17:07:47 2012 From: jira-events at lists.jboss.org (phelen harg (JIRA)) Date: Fri, 30 Mar 2012 17:07:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12081) Problem with RichEditor RF 4.2.0 In-Reply-To: <1278339548.27975.1332502007395.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <2071596362.44471.1333141667485.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] phelen harg updated RF-12081: ----------------------------- Attachment: page.xhtml Page.rar > Problem with RichEditor RF 4.2.0 > -------------------------------- > > Key: RF-12081 > URL: https://issues.jboss.org/browse/RF-12081 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.2.0.Final > Reporter: phelen harg > Labels: waiting_on_user > Attachments: Page.rar, page.xhtml, Sem t?tulo.jpg > > > I'm migrating my Application from RF 3.3.3 to RF 4.2.0. But now i'm facing a problem with the richEditor. When I load the the component, all the links in application receive a background like this picture: > Analizing the code with Firebug, I found the problem in the CSS of RichEditor. /org.richfaces.resources/javax.faces.resource/org.richfaces.ckeditor/skins/richfaces/editor.ecss?db=eAHj0yqqAgACGAEl > If I erase the CSS the backgroud disappear. There is some kind of workaround for this? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 30 17:09:47 2012 From: jira-events at lists.jboss.org (phelen harg (JIRA)) Date: Fri, 30 Mar 2012 17:09:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12081) Problem with RichEditor RF 4.2.0 In-Reply-To: <1278339548.27975.1332502007395.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <2142502826.44474.1333141787341.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12680742#comment-12680742 ] phelen harg commented on RF-12081: ---------------------------------- I've attach the page.xhtml and the page and css in the page.rar > Problem with RichEditor RF 4.2.0 > -------------------------------- > > Key: RF-12081 > URL: https://issues.jboss.org/browse/RF-12081 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.2.0.Final > Reporter: phelen harg > Labels: waiting_on_user > Attachments: Page.rar, page.xhtml, Sem t?tulo.jpg > > > I'm migrating my Application from RF 3.3.3 to RF 4.2.0. But now i'm facing a problem with the richEditor. When I load the the component, all the links in application receive a background like this picture: > Analizing the code with Firebug, I found the problem in the CSS of RichEditor. /org.richfaces.resources/javax.faces.resource/org.richfaces.ckeditor/skins/richfaces/editor.ecss?db=eAHj0yqqAgACGAEl > If I erase the CSS the backgroud disappear. There is some kind of workaround for this? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 30 17:32:47 2012 From: jira-events at lists.jboss.org (Ivan Costa (JIRA)) Date: Fri, 30 Mar 2012 17:32:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12117) No showcase at http://showcase.richfaces.org/ - "welcome to Grails" salute Message-ID: <1870074657.44485.1333143167282.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Ivan Costa created RF-12117: ------------------------------- Summary: No showcase at http://showcase.richfaces.org/ - "welcome to Grails" salute Key: RF-12117 URL: https://issues.jboss.org/browse/RF-12117 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: showcase Affects Versions: 4.2.0.Final Reporter: Ivan Costa Priority: Blocker Since yesterday showcase at url http://showcase.richfaces.org/ shows a "Welcome to Grails" page. No showcase at all. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Mar 30 22:43:47 2012 From: jira-events at lists.jboss.org (Ivan Costa (JIRA)) Date: Fri, 30 Mar 2012 22:43:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12117) No showcase at http://showcase.richfaces.org/ - "welcome to Grails" salute In-Reply-To: <1870074657.44485.1333143167282.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <761924912.44608.1333161827429.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-12117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Costa closed RF-12117. --------------------------- Resolution: Done It seems ok now. > No showcase at http://showcase.richfaces.org/ - "welcome to Grails" salute > --------------------------------------------------------------------------- > > Key: RF-12117 > URL: https://issues.jboss.org/browse/RF-12117 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: showcase > Affects Versions: 4.2.0.Final > Reporter: Ivan Costa > Priority: Blocker > > Since yesterday showcase at url http://showcase.richfaces.org/ shows a "Welcome to Grails" page. No showcase at all. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira