From jira-events at lists.jboss.org Mon Jan 2 06:01:12 2012 From: jira-events at lists.jboss.org (Milo van der Zee (Commented) (JIRA)) Date: Mon, 2 Jan 2012 06:01:12 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11803) render of 'c:' and 'fn:' is one click behind In-Reply-To: <1412990328.81640.1323338620636.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1365041986.34456.1325502072551.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12653320#comment-12653320 ] Milo van der Zee commented on RF-11803: --------------------------------------- Myfaces: https://issues.apache.org/jira/browse/MYFACES-3436 > render of 'c:' and 'fn:' is one click behind > -------------------------------------------- > > Key: RF-11803 > URL: https://issues.jboss.org/browse/RF-11803 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Environment: MyFaces 2.1.5, Tomcat 7.0.22, 4.1.0-20111204 from showcase > Reporter: Milo van der Zee > Assignee: Luk?? Fry? > Priority: Minor > Labels: render, waiting_on_user > > 'c:' and 'fn:' is rendered differently from previous versions. > When clicking the inc and dec buttons in the example you can see that the field contents are updates each click but the number of fields is not (comma at the end when pressing 'dec'. Pressing 'render' then fixes the output. > When using a function to render it works fine. Even though the function does not do much. > MAG, > Milo > {code:title="testje4.xhtml"} > > xmlns="http://www.w3.org/1999/xhtml" > xmlns:h="http://java.sun.com/jsf/html" > xmlns:a4j="http://richfaces.org/a4j" > xmlns:rich="http://richfaces.org/rich" > xmlns:fn="http://java.sun.com/jsp/jstl/functions" > xmlns:c="http://java.sun.com/jsp/jstl/core" > > > > > > > > > > Counter: #{testBean.counter}
> > >
> > > > > > > #{status+1}: '#{field}', '#{fields}'
> > >
> > Direct render: > > >
> With function to render: > > >
> Manual render: > > > > > {code} > {code:title="testBean.java"} > package com.test; > import java.util.Arrays; > import java.util.List; > import javax.faces.bean.ManagedBean; > import javax.faces.bean.SessionScoped; > @ManagedBean > @SessionScoped > public class TestBean { > private int counter = 5; > public String getFieldsString() { > StringBuilder builder = new StringBuilder(); > boolean firstField = true; > for (int i = 0; i < counter; i++) { > if (!firstField) builder.append(','); > firstField = false; > char[] fill = new char[i + 1]; > Arrays.fill(fill, Character.forDigit(counter, 10)); > String fieldName = new String(fill); > builder.append(fieldName); > } > return builder.toString(); > } > public List getFieldsList() { > String string = getFieldsString(); > List list = Arrays.asList(string.split(",")); > return list; > } > public void decCounter() { > counter--; > if (counter < 1) counter = 1; > } > public void incCounter() { > counter++; > if (counter > 9) counter = 9; > } > public int getCounter() { > return counter; > } > public void setCounter(int counter) { > this.counter = counter; > } > } > {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 Jan 2 07:37:09 2012 From: jira-events at lists.jboss.org (Pavol Pitonak (Assigned) (JIRA)) Date: Mon, 2 Jan 2012 07:37:09 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11814) a4j:commandLink in tabPanel disabled if switchtype = ajax In-Reply-To: <796306910.9115.1323859989475.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1500282964.34590.1325507829387.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavol Pitonak reassigned RF-11814: ---------------------------------- Assignee: J?n Jamrich (was: Pavol Pitonak) > a4j:commandLink in tabPanel disabled if switchtype = ajax > --------------------------------------------------------- > > Key: RF-11814 > URL: https://issues.jboss.org/browse/RF-11814 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core, component-panels-layout-themes > Affects Versions: 4.1.0.CR2 > Environment: Win 7 64 Bit, Tomcat 7.0.23, Mojarra 2.1.3 > Reporter: Friedhelm Kuehn > Assignee: J?n Jamrich > > In the following constellation (=extract from real page) the a4j:commandlink action method > is correctly triggered on clicking when tabPanels switchType = "client" but not when switchType = "ajax" > {code} > > > > > ..... > > > > > > > Logging out, please wait ! > > > {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 Jan 2 07:45:09 2012 From: jira-events at lists.jboss.org (Pavol Pitonak (Assigned) (JIRA)) Date: Mon, 2 Jan 2012 07:45:09 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11825) rich:fileUpload - File selected for upload is duplicated in IE 8 when placed in composite component In-Reply-To: <723368030.20345.1324296789427.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1623840396.34600.1325508309769.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavol Pitonak reassigned RF-11825: ---------------------------------- Assignee: J?n Jamrich (was: Pavol Pitonak) > rich:fileUpload - File selected for upload is duplicated in IE 8 when placed in composite component > --------------------------------------------------------------------------------------------------- > > Key: RF-11825 > URL: https://issues.jboss.org/browse/RF-11825 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.1.0.Final > Environment: Apache Tomcat 6.0 > Java 1.6.0_24 > Mojarra 2.1.2 > Reporter: Pavel Hofr?k > Assignee: J?n Jamrich > Labels: composite_component, fileUpload, richfaces > > When rich:fileUpload is part of composite component, and this component is placed in page, than when file is selected from system dialog, it is added twice in list of files. > This fault occurs in IE 8. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 2 08:00:09 2012 From: jira-events at lists.jboss.org (Pavol Pitonak (Assigned) (JIRA)) Date: Mon, 2 Jan 2012 08:00:09 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11846) rich:validator ignores @NotEmpty In-Reply-To: <651588956.26878.1324469409370.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1225603833.34632.1325509209734.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavol Pitonak reassigned RF-11846: ---------------------------------- Assignee: J?n Jamrich (was: Pavol Pitonak) > rich:validator ignores @NotEmpty > -------------------------------- > > Key: RF-11846 > URL: https://issues.jboss.org/browse/RF-11846 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-validators > Affects Versions: 4.1.0.Final > Environment: Maven 3, Tomcat 6.0.x, Ubuntu 11.10 x64, Glassfish jsf 2.x implementation, Hibernate validator 4.1.0.Final > Reporter: Mercer Traieste > Assignee: J?n Jamrich > > I want to have [client-side validation|http://richfaces-showcase.appspot.com/richfaces/component-sample.jsf?demo=clientValidation&sample=jsr303&skin=blueSky] using rich:validator in Richfaces 4.1, but @NotEmpty is ignored. > {code:xml} > > > > > > {code} > {code:java} > import org.hibernate.validator.constraints.NotEmpty; > import javax.faces.bean.ManagedBean; > import javax.faces.bean.SessionScoped; > import java.io.Serializable; > @ManagedBean > @SessionScoped > public class RichBean implements Serializable { > private static final long serialVersionUID = -2403138958014741653L; > @NotEmpty > private String firstName; > public String getFirstName() { > return firstName; > } > public void setFirstName(String firstName) { > this.firstName = firstName; > } > } > {code} > @Email, another specific Hibernate validator 4.1 annotation works 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 Mon Jan 2 08:00:09 2012 From: jira-events at lists.jboss.org (Pavol Pitonak (Assigned) (JIRA)) Date: Mon, 2 Jan 2012 08:00:09 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11850) RF 4.1.0.Final: Problem using columnResize with more than one extendedDataTable on the same page. In-Reply-To: <1719236551.29235.1324550769802.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <130165323.34635.1325509209848.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavol Pitonak reassigned RF-11850: ---------------------------------- Assignee: J?n Jamrich (was: Pavol Pitonak) > RF 4.1.0.Final: Problem using columnResize with more than one extendedDataTable on the same page. > ------------------------------------------------------------------------------------------------- > > Key: RF-11850 > URL: https://issues.jboss.org/browse/RF-11850 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.1.0.Final > Environment: Windows 7 x64 or arch linux x86 > JBoss 7.0.1 Final or Glassfish 3.1 > Reporter: Christian Peter > Assignee: J?n Jamrich > Priority: Minor > > Hello, > I've encountered some problems using richfaces extendedDataTables in RichFace 4.1.0.Final > Here is the facelet: > {code:title=facelet} > > > > Header7 > #{item.name} > > > > Header8 > #{item.uuid} > > > > Header9 > #{item.uuid} > > > > Header10 > #{item.uuid} > > > > > > > > > > Header7 > #{item.name} > > > > Header8 > #{item.uuid} > > > Header9 > #{item.uuid} > > > > Header10 > #{item.uuid} > > > > > > {code} > > Resizing the columns on the first table works perfectly, but if someone tries to resize the second tables' columns as well, I've got NullPointer exceptions like: > {code:title=stacktrace} > java.lang.NullPointerException > at org.richfaces.renderkit.SortingFilteringRowsRenderer.updateAttribute(SortingFilteringRowsRenderer.java:135) [richfaces-components-ui-4.1.0.Final.jar: > at org.richfaces.renderkit.ExtendedDataTableRenderer.updateWidthOfColumns(ExtendedDataTableRenderer.java:825) [richfaces-components-ui-4.1.0.Final.jar:] > at org.richfaces.renderkit.ExtendedDataTableRenderer.doDecode(ExtendedDataTableRenderer.java:808) [richfaces-components-ui-4.1.0.Final.jar:] > at org.richfaces.renderkit.RendererBase.decode(RendererBase.java:80) [richfaces-components-ui-4.1.0.Final.jar:] > at javax.faces.component.UIComponentBase.decode(UIComponentBase.java:787) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at org.richfaces.component.UIDataAdaptor.processDecodes(UIDataAdaptor.java:819) [richfaces-components-ui-4.1.0.Final.jar:] > at org.richfaces.context.PartialViewExecuteVisitCallback.visit(PartialViewExecuteVisitCallback.java:53) [richfaces-core-impl-4.1.0.Final.jar:] > at org.richfaces.context.BaseExtendedVisitContext.invokeVisitCallback(BaseExtendedVisitContext.java:321) [richfaces-core-impl-4.1.0.Final.jar:] > at org.richfaces.component.UIDataAdaptor.visitTree(UIDataAdaptor.java:1319) [richfaces-components-ui-4.1.0.Final.jar:] > at javax.faces.component.UIComponent.visitTree(UIComponent.java:1600) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at javax.faces.component.UIForm.visitTree(UIForm.java:344) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at javax.faces.component.UIComponent.visitTree(UIComponent.java:1600) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at javax.faces.component.UIComponent.visitTree(UIComponent.java:1600) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at org.richfaces.context.ExtendedPartialViewContextImpl.executeComponents(ExtendedPartialViewContextImpl.java:237) [richfaces-core-impl-4.1.0.Final.jar: > at org.richfaces.context.ExtendedPartialViewContextImpl.processPartialExecutePhase(ExtendedPartialViewContextImpl.java:217) [richfaces-core-impl-4.1.0.F > at org.richfaces.context.ExtendedPartialViewContextImpl.processPartial(ExtendedPartialViewContextImpl.java:196) [richfaces-core-impl-4.1.0.Final.jar:] > at javax.faces.component.UIViewRoot.processDecodes(UIViewRoot.java:931) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at com.sun.faces.lifecycle.ApplyRequestValuesPhase.execute(ApplyRequestValuesPhase.java:78) [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 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] > {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 Jan 2 10:12:10 2012 From: jira-events at lists.jboss.org (Marek Novotny (Commented) (JIRA)) Date: Mon, 2 Jan 2012 10:12:10 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11615) Upgrade to JBoss Parent version 7 In-Reply-To: <1714858172.39799.1320059745985.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <79357.34915.1325517130212.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12653352#comment-12653352 ] Marek Novotny commented on RF-11615: ------------------------------------ Please upgrade to JBoss Parent 8, which JBoss AS 7.1 uses. > Upgrade to JBoss Parent version 7 > --------------------------------- > > Key: RF-11615 > URL: https://issues.jboss.org/browse/RF-11615 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 4.1.0.Milestone4 > Reporter: Luk?? Fry? > Priority: Minor > Fix For: 4.2-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 Mon Jan 2 10:16:09 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28Updated=29_=28JIRA=29?=) Date: Mon, 2 Jan 2012 10:16:09 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11615) Upgrade to JBoss Parent version 8 In-Reply-To: <1714858172.39799.1320059745985.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1198325749.34965.1325517369757.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated RF-11615: ---------------------------- Summary: Upgrade to JBoss Parent version 8 (was: Upgrade to JBoss Parent version 7) Assignee: Brian Leathem Fix Version/s: (was: 4.2-Tracking) Brian, please review for addition to {{4.1.1}}. > Upgrade to JBoss Parent version 8 > --------------------------------- > > Key: RF-11615 > URL: https://issues.jboss.org/browse/RF-11615 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 4.1.0.Milestone4 > Reporter: Luk?? Fry? > Assignee: Brian Leathem > Priority: Minor > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 2 10:18:10 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28Issue_Comment_Edited=29_=28JIRA=29?=) Date: Mon, 2 Jan 2012 10:18:10 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11615) Upgrade to JBoss Parent version 8 In-Reply-To: <1714858172.39799.1320059745985.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <211682005.34989.1325517490554.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12653354#comment-12653354 ] Luk?? Fry? edited comment on RF-11615 at 1/2/12 10:17 AM: ---------------------------------------------------------- Brian, please review for addition to {{4.1.1}}. Diff 7~8: https://github.com/jboss/jboss-parent-pom/compare/7...8 was (Author: lfryc): Brian, please review for addition to {{4.1.1}}. > Upgrade to JBoss Parent version 8 > --------------------------------- > > Key: RF-11615 > URL: https://issues.jboss.org/browse/RF-11615 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 4.1.0.Milestone4 > Reporter: Luk?? Fry? > Assignee: Brian Leathem > Priority: Minor > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 2 10:46:09 2012 From: jira-events at lists.jboss.org (Pavol Pitonak (Closed) (JIRA)) Date: Mon, 2 Jan 2012 10:46:09 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11813) Drop down menu generates non-valid HTML In-Reply-To: <35971641.7524.1323808689819.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1973760510.35067.1325519169969.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavol Pitonak closed RF-11813. ------------------------------ > Drop down menu generates non-valid HTML > --------------------------------------- > > Key: RF-11813 > URL: https://issues.jboss.org/browse/RF-11813 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-menu > Affects Versions: 4.1.0.CR2 > Reporter: Pavol Pitonak > Assignee: Brian Leathem > Priority: Trivial > Fix For: 4.1.1.Final > > > The following code snippet generates non-valid XHTML (it contains a div inside span): > {code:xml} > > {code} > {code:xml} >
> >
> > Chart > >
> {code} > Menu items with icon are 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 Jan 2 11:15:09 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28Commented=29_=28JIRA=29?=) Date: Mon, 2 Jan 2012 11:15:09 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11666) Manage dependencies across whole framework In-Reply-To: <1076602405.71397.1320851805815.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <189518901.35089.1325520909988.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12653364#comment-12653364 ] Luk?? Fry? commented on RF-11666: --------------------------------- After review with Marek, we have decided for further changes: #. remove {{${version.richfaces}}} from {{richfaces-root-parent}} #. remove all other {{${version.richfaces}}} occurences #. do not import {{richfaces-bom}} in examples which relies on {{richfaces-root-parent}} > Manage dependencies across whole framework > ------------------------------------------ > > Key: RF-11666 > URL: https://issues.jboss.org/browse/RF-11666 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 4.1.0.CR1 > Reporter: Luk?? Fry? > Assignee: Marek Novotny > Fix For: 4.1.1.Final, 4.2-Tracking > > > (Issue originally requested by Marek Novotny) > There are lot of dependencies with versions managed on low-level POMs, e.g.: > Search across project has found following (approximately, includes false positives): > {code} > ./checkstyle/pom.xml > ./shade-transformers/pom.xml > ./core/impl/pom.xml > ./core/api/pom.xml > ./build/dist/pom.xml > ./dev-examples/dnd-demo/pom.xml > ./dev-examples/input-demo/pom.xml > ./dev-examples/iteration-demo/pom.xml > ./dev-examples/output-demo/pom.xml > ./dev-examples/parent/pom.xml > ./dev-examples/irc-client/pom.xml > ./dev-examples/push-demo/pom.xml > ./components/output/ui/pom.xml > ./components/dnd/ui/pom.xml > ./components/dnd/api/pom.xml > ./components/validator/ui/pom.xml > ./components/dist/static-resources/pom.xml > ./components/dist/richfaces-components-ui/pom.xml > ./components/input/ui/pom.xml > ./components/parent/pom.xml > ./components/pom.xml > ./showcase/pom.xml > ./archetype-simpleapp/src/main/resources/archetype-resources/pom.xml > ./archetype-simpleapp/pom.xml > ./cdk/maven-javascript-plugin/pom.xml > ./cdk/maven-cdk-plugin/pom.xml > ./cdk/generator/pom.xml > {code} > For {{jsf-test}}: > {code} > ./jsf-test/jsf-mockito/pom.xml > ./jsf-test/stage/pom.xml > ./jsf-test/mock/pom.xml > ./jsf-test/maven-mockgenerator-plugin/pom.xml > ./jsf-test/jsf-test-htmlunit/pom.xml > ./jsf-test/scriptunit/pom.xml > ./jsf-test/jetty/pom.xml > {code} > It would be beneficial having one place managing these dependencies. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 2 11:54:09 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28Assigned=29_=28JIRA=29?=) Date: Mon, 2 Jan 2012 11:54:09 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11666) Manage dependencies across whole framework In-Reply-To: <1076602405.71397.1320851805815.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <847307740.35148.1325523249668.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? reassigned RF-11666: ------------------------------- Assignee: Luk?? Fry? (was: Marek Novotny) > Manage dependencies across whole framework > ------------------------------------------ > > Key: RF-11666 > URL: https://issues.jboss.org/browse/RF-11666 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 4.1.0.CR1 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 4.1.1.Final, 4.2-Tracking > > > (Issue originally requested by Marek Novotny) > There are lot of dependencies with versions managed on low-level POMs, e.g.: > Search across project has found following (approximately, includes false positives): > {code} > ./checkstyle/pom.xml > ./shade-transformers/pom.xml > ./core/impl/pom.xml > ./core/api/pom.xml > ./build/dist/pom.xml > ./dev-examples/dnd-demo/pom.xml > ./dev-examples/input-demo/pom.xml > ./dev-examples/iteration-demo/pom.xml > ./dev-examples/output-demo/pom.xml > ./dev-examples/parent/pom.xml > ./dev-examples/irc-client/pom.xml > ./dev-examples/push-demo/pom.xml > ./components/output/ui/pom.xml > ./components/dnd/ui/pom.xml > ./components/dnd/api/pom.xml > ./components/validator/ui/pom.xml > ./components/dist/static-resources/pom.xml > ./components/dist/richfaces-components-ui/pom.xml > ./components/input/ui/pom.xml > ./components/parent/pom.xml > ./components/pom.xml > ./showcase/pom.xml > ./archetype-simpleapp/src/main/resources/archetype-resources/pom.xml > ./archetype-simpleapp/pom.xml > ./cdk/maven-javascript-plugin/pom.xml > ./cdk/maven-cdk-plugin/pom.xml > ./cdk/generator/pom.xml > {code} > For {{jsf-test}}: > {code} > ./jsf-test/jsf-mockito/pom.xml > ./jsf-test/stage/pom.xml > ./jsf-test/mock/pom.xml > ./jsf-test/maven-mockgenerator-plugin/pom.xml > ./jsf-test/jsf-test-htmlunit/pom.xml > ./jsf-test/scriptunit/pom.xml > ./jsf-test/jetty/pom.xml > {code} > It would be beneficial having one place managing these dependencies. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 2 23:13:09 2012 From: jira-events at lists.jboss.org (Dave Chen (Created) (JIRA)) Date: Mon, 2 Jan 2012 23:13:09 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11859) Many script/css added when not needed Message-ID: <872670898.35681.1325563989373.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Many script/css added when not needed ------------------------------------- Key: RF-11859 URL: https://issues.jboss.org/browse/RF-11859 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 3.3.3.Final Environment: JBoss 5.1 Reporter: Dave Chen Richfaces filter always adds many scripts/css even when a page does not need them, causing slow page loading for website, and not search engine friendly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 3 04:45:09 2012 From: jira-events at lists.jboss.org (Pavol Pitonak (Closed) (JIRA)) Date: Tue, 3 Jan 2012 04:45:09 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11830) Toolbar: attribute width is always generated In-Reply-To: <19764319.21785.1324325349860.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1348098187.35862.1325583909607.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavol Pitonak closed RF-11830. ------------------------------ > Toolbar: attribute width is always generated > -------------------------------------------- > > Key: RF-11830 > URL: https://issues.jboss.org/browse/RF-11830 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-menu > Affects Versions: 4.1.0.Final > Reporter: Pavol Pitonak > Assignee: Brian Leathem > Priority: Trivial > Fix For: 4.1.1.Final > > > Toolbar generates width attribute even if width is set in CSS. > {code:xml} > > > > > {code} > The code above generates the following markup (width is set twice): > {code:xml} > > ... >
> {code} > Only CSS should be used. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 3 04:47:09 2012 From: jira-events at lists.jboss.org (Pavol Pitonak (Closed) (JIRA)) Date: Tue, 3 Jan 2012 04:47:09 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11829) Toolbar: cellspacing and cellpadding should be implemented using CSS In-Reply-To: <1368421696.21763.1324324870064.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <813417665.35864.1325584029493.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavol Pitonak closed RF-11829. ------------------------------ > Toolbar: cellspacing and cellpadding should be implemented using CSS > -------------------------------------------------------------------- > > Key: RF-11829 > URL: https://issues.jboss.org/browse/RF-11829 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-menu > Affects Versions: 4.1.0.Final > Reporter: Pavol Pitonak > Assignee: Brian Leathem > Priority: Trivial > Fix For: 4.1.1.Final > > > Replace attributes cellpadding and cellspacing with rich:toolbar with CSS (border-collapse: collapse). Cellspacing and cellpadding are not valid in HTML5. > For example, see RichFaces Showcase: > http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=toolBar&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 Tue Jan 3 04:49:09 2012 From: jira-events at lists.jboss.org (Pavol Pitonak (Closed) (JIRA)) Date: Tue, 3 Jan 2012 04:49:09 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11831) Toolbar: col elements should use CSS for width In-Reply-To: <1706606323.21791.1324325949521.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1432520721.35869.1325584149640.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavol Pitonak closed RF-11831. ------------------------------ > Toolbar: col elements should use CSS for width > ---------------------------------------------- > > Key: RF-11831 > URL: https://issues.jboss.org/browse/RF-11831 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-menu > Affects Versions: 4.1.0.Final > Reporter: Pavol Pitonak > Assignee: Brian Leathem > Priority: Trivial > Labels: needs-qe > Fix For: 4.1.1.Final > > > Toolbar generates elements with attribute "width" which should be replaced with CSS. Attribute width is obsolete in HTML5. > {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 Tue Jan 3 04:49:09 2012 From: jira-events at lists.jboss.org (Pavol Pitonak (Closed) (JIRA)) Date: Tue, 3 Jan 2012 04:49:09 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11832) Toolbar: attribute border should be replaced with CSS In-Reply-To: <1851411769.21834.1324327389425.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <440772808.35868.1325584149541.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavol Pitonak closed RF-11832. ------------------------------ > Toolbar: attribute border should be replaced with CSS > ----------------------------------------------------- > > Key: RF-11832 > URL: https://issues.jboss.org/browse/RF-11832 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-menu > Affects Versions: 4.1.0.Final > Reporter: Pavol Pitonak > Assignee: Brian Leathem > Priority: Trivial > Fix For: 4.1.1.Final > > > Toolbar generates border="0" in top table element. Instead, CSS property *border: none;* should be set in following classes: > * rf-tb-itm > * rf-tb-sep > * rf-tb-emp -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 3 06:09:09 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28Updated=29_=28JIRA=29?=) Date: Tue, 3 Jan 2012 06:09:09 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11666) Manage dependencies across whole framework In-Reply-To: <1076602405.71397.1320851805815.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1275782964.36035.1325588949790.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated RF-11666: ---------------------------- Fix Version/s: (was: 4.2-Tracking) Priority: Critical (was: Major) > Manage dependencies across whole framework > ------------------------------------------ > > Key: RF-11666 > URL: https://issues.jboss.org/browse/RF-11666 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 4.1.0.CR1 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Priority: Critical > Fix For: 4.1.1.Final > > > (Issue originally requested by Marek Novotny) > There are lot of dependencies with versions managed on low-level POMs, e.g.: > Search across project has found following (approximately, includes false positives): > {code} > ./checkstyle/pom.xml > ./shade-transformers/pom.xml > ./core/impl/pom.xml > ./core/api/pom.xml > ./build/dist/pom.xml > ./dev-examples/dnd-demo/pom.xml > ./dev-examples/input-demo/pom.xml > ./dev-examples/iteration-demo/pom.xml > ./dev-examples/output-demo/pom.xml > ./dev-examples/parent/pom.xml > ./dev-examples/irc-client/pom.xml > ./dev-examples/push-demo/pom.xml > ./components/output/ui/pom.xml > ./components/dnd/ui/pom.xml > ./components/dnd/api/pom.xml > ./components/validator/ui/pom.xml > ./components/dist/static-resources/pom.xml > ./components/dist/richfaces-components-ui/pom.xml > ./components/input/ui/pom.xml > ./components/parent/pom.xml > ./components/pom.xml > ./showcase/pom.xml > ./archetype-simpleapp/src/main/resources/archetype-resources/pom.xml > ./archetype-simpleapp/pom.xml > ./cdk/maven-javascript-plugin/pom.xml > ./cdk/maven-cdk-plugin/pom.xml > ./cdk/generator/pom.xml > {code} > For {{jsf-test}}: > {code} > ./jsf-test/jsf-mockito/pom.xml > ./jsf-test/stage/pom.xml > ./jsf-test/mock/pom.xml > ./jsf-test/maven-mockgenerator-plugin/pom.xml > ./jsf-test/jsf-test-htmlunit/pom.xml > ./jsf-test/scriptunit/pom.xml > ./jsf-test/jetty/pom.xml > {code} > It would be beneficial having one place managing these dependencies. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 3 06:11:11 2012 From: jira-events at lists.jboss.org (Pavol Pitonak (Assigned) (JIRA)) Date: Tue, 3 Jan 2012 06:11:11 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-10197) Right click menu - rich:contextMenu - should be ported from RF 3 In-Reply-To: <1371525318.9293.1294869109676.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <701955715.36058.1325589071442.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-10197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavol Pitonak reassigned RF-10197: ---------------------------------- Assignee: J?n Jamrich (was: Pavol Pitonak) > Right click menu - rich:contextMenu - should be ported from RF 3 > ---------------------------------------------------------------- > > Key: RF-10197 > URL: https://issues.jboss.org/browse/RF-10197 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-menu > Affects Versions: 4.0.0.Milestone5 > Environment: Windows > Reporter: Devinder Singh > Assignee: J?n Jamrich > Priority: Blocker > Labels: sandbox > Fix For: 4.1.1.Final > > > rich:contextMenu is available in 3.x release but not yet supported in 4.0. > As it enables right click menus on JSF components, it's a very useful feature that can be used in wide variety of applications -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 3 06:50:09 2012 From: jira-events at lists.jboss.org (Pavol Pitonak (Created) (JIRA)) Date: Tue, 3 Jan 2012 06:50:09 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11860) Data table: The scope attribute on the td element is obsolete Message-ID: <207304981.36098.1325591409412.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Data table: The scope attribute on the td element is obsolete ------------------------------------------------------------- Key: RF-11860 URL: https://issues.jboss.org/browse/RF-11860 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: compatibility, component-tables Affects Versions: 4.1.0.Final Environment: RichFaces 4.1.1-SNAPSHOT Metamer 4.1.1-SNAPSHOT r.23118 Mojarra 2.1.5 JBoss AS 7.1.0.CR1 OpenJDK Runtime Environment 1.6.0_22-b22 @ Linux Chrome 16.0.912.63 @ Linux i686 Reporter: Pavol Pitonak The column footer is rendered as in following code snippet (can be reproduced in Metamer http://localhost:8080/metamer/faces/components/richDataTable/facets.xhtml): {code:xml} {code} Attribute *scope* on element td is obsolete in HTML5 and should be set on th element instead. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 3 07:33:10 2012 From: jira-events at lists.jboss.org (RH Bugzilla Integration (Commented) (JIRA)) Date: Tue, 3 Jan 2012 07:33:10 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11544) Unify JSF API dependencies usage + introduce JBoss-specific profile In-Reply-To: <802301686.33181.1318582636150.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <688623924.36222.1325593990186.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12653477#comment-12653477 ] RH Bugzilla Integration commented on RF-11544: ---------------------------------------------- Karel Piwko changed the Status of [bug 746177|https://bugzilla.redhat.com/show_bug.cgi?id=746177] from ON_QA to VERIFIED > Unify JSF API dependencies usage + introduce JBoss-specific profile > ------------------------------------------------------------------- > > Key: RF-11544 > URL: https://issues.jboss.org/browse/RF-11544 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 4.1.0.Milestone2 > Reporter: Karel Piwko > Assignee: Luk?? Fry? > Fix For: 4.1.0.Milestone4 > > > Description of problem: > RichFaces bom contains com.sun.faces for jsf-api definition. > Version-Release number of selected component (if applicable): > 4.1.0-20110910-M2-redhat-1 > How reproducible: > Always. > Steps to Reproduce: > 1. Import org.richfaces:richfaces-bom > Actual results: > There is com.sun.faces:jsf-api and com.sun.faces:jsf-impl > Expected results: > There should be javax.faces:jsf-api and com.sun.faces:jsf-impl -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 3 09:05:09 2012 From: jira-events at lists.jboss.org (Peter B (Created) (JIRA)) Date: Tue, 3 Jan 2012 09:05:09 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11861) richfaces 4.1.Final showcase: Non-resolvable parent POM: Could not find artifact org.richfaces:richfaces-root-parent:pom:4.1.0.Final Message-ID: <1704236441.36501.1325599509914.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> richfaces 4.1.Final showcase: Non-resolvable parent POM: Could not find artifact org.richfaces:richfaces-root-parent:pom:4.1.0.Final ------------------------------------------------------------------------------------------------------------------------------------ Key: RF-11861 URL: https://issues.jboss.org/browse/RF-11861 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Peter B richfaces showcase for Richfaces 4.1 Final doesn't build. Problem is that: org.richfaces richfaces-root-parent 4.1.0.Final is not in central maven repository. Console output: [INFO] Scanning for projects... Downloading: http://repo1.maven.org/maven2/org/richfaces/richfaces-root-parent/4.1.0.Final/richfaces-root-parent-4.1.0.F inal.pom [ERROR] The build could not read 1 project -> [Help 1] [ERROR] [ERROR] The project org.richfaces.examples:richfaces-showcase:4.1.0.Final (D:\tmp\richfaces-showcase-77c6701\pom.xml) has 1 error [ERROR] Non-resolvable parent POM: Could not find artifact org.richfaces:richfaces-root-parent:pom:4.1.0.Final in ce ntral (http://repo1.maven.org/maven2) and 'parent.relativePath' points at wrong local POM @ line 8, column 13 -> [Help 2 ] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException [ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 3 09:40:09 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28Resolved=29_=28JIRA=29?=) Date: Tue, 3 Jan 2012 09:40:09 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11666) Manage dependencies across whole framework In-Reply-To: <1076602405.71397.1320851805815.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1880821888.36622.1325601609816.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved RF-11666. ----------------------------- Resolution: Done Changes has been integrated to {{develop}}. > Manage dependencies across whole framework > ------------------------------------------ > > Key: RF-11666 > URL: https://issues.jboss.org/browse/RF-11666 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 4.1.0.CR1 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Priority: Critical > Fix For: 4.1.1.Final > > > (Issue originally requested by Marek Novotny) > There are lot of dependencies with versions managed on low-level POMs, e.g.: > Search across project has found following (approximately, includes false positives): > {code} > ./checkstyle/pom.xml > ./shade-transformers/pom.xml > ./core/impl/pom.xml > ./core/api/pom.xml > ./build/dist/pom.xml > ./dev-examples/dnd-demo/pom.xml > ./dev-examples/input-demo/pom.xml > ./dev-examples/iteration-demo/pom.xml > ./dev-examples/output-demo/pom.xml > ./dev-examples/parent/pom.xml > ./dev-examples/irc-client/pom.xml > ./dev-examples/push-demo/pom.xml > ./components/output/ui/pom.xml > ./components/dnd/ui/pom.xml > ./components/dnd/api/pom.xml > ./components/validator/ui/pom.xml > ./components/dist/static-resources/pom.xml > ./components/dist/richfaces-components-ui/pom.xml > ./components/input/ui/pom.xml > ./components/parent/pom.xml > ./components/pom.xml > ./showcase/pom.xml > ./archetype-simpleapp/src/main/resources/archetype-resources/pom.xml > ./archetype-simpleapp/pom.xml > ./cdk/maven-javascript-plugin/pom.xml > ./cdk/maven-cdk-plugin/pom.xml > ./cdk/generator/pom.xml > {code} > For {{jsf-test}}: > {code} > ./jsf-test/jsf-mockito/pom.xml > ./jsf-test/stage/pom.xml > ./jsf-test/mock/pom.xml > ./jsf-test/maven-mockgenerator-plugin/pom.xml > ./jsf-test/jsf-test-htmlunit/pom.xml > ./jsf-test/scriptunit/pom.xml > ./jsf-test/jetty/pom.xml > {code} > It would be beneficial having one place managing these dependencies. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 3 09:40:10 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28Resolved=29_=28JIRA=29?=) Date: Tue, 3 Jan 2012 09:40:10 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11760) Remove parent section from richfaces-bom In-Reply-To: <873400509.55474.1322668960858.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <346071380.36636.1325601610969.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved RF-11760. ----------------------------- Resolution: Done > Remove parent section from richfaces-bom > ---------------------------------------- > > Key: RF-11760 > URL: https://issues.jboss.org/browse/RF-11760 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 4.1.0.CR1 > Reporter: Karel Piwko > Assignee: Luk?? Fry? > Priority: Blocker > Fix For: 4.1.1.Final > > > Having element in the BOM file is fundamentally wrong. > If user imports dependencyManagement of the BOM file, it imports even the dependencies from its parent and upper ancestors. Since the ancestor is jboss-parent, it includes virtually the whole world. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 3 09:42:09 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28Resolved=29_=28JIRA=29?=) Date: Tue, 3 Jan 2012 09:42:09 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11791) Upgrade build version of JSF RI to 2.1.5 In-Reply-To: <1733474985.72661.1323163180651.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <2059633012.36640.1325601729964.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved RF-11791. ----------------------------- Resolution: Done > Upgrade build version of JSF RI to 2.1.5 > ---------------------------------------- > > Key: RF-11791 > URL: https://issues.jboss.org/browse/RF-11791 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 4.1.0.CR2 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 4.1.1.Final > > > The {{2.1.5}} fixes the security issue: > [includeViewParameters re-evaluates param/model values as EL expressions|http://java.net/jira/browse/JAVASERVERFACES-2247] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 3 09:42:10 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28Resolved=29_=28JIRA=29?=) Date: Tue, 3 Jan 2012 09:42:10 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11788) Update build version of MyFaces to 2.1.5 In-Reply-To: <2142901077.70509.1323104320664.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1088576509.36653.1325601730615.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved RF-11788. ----------------------------- Resolution: Done > Update build version of MyFaces to 2.1.5 > ----------------------------------------- > > Key: RF-11788 > URL: https://issues.jboss.org/browse/RF-11788 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 4.1.0.CR1 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Labels: myfaces > Fix For: 4.1.1.Final > > > In {{richfaces-bom}}, we are using {{2.1.1}}, but documented version is {{2.1.4}}. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 3 09:51:10 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28Resolved=29_=28JIRA=29?=) Date: Tue, 3 Jan 2012 09:51:10 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11835) Remove repositories and pluginRepositories sections from richfaces-parent In-Reply-To: <1310408444.24263.1324385949362.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1263989600.36686.1325602270040.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved RF-11835. ----------------------------- Resolution: Done Framework has been upgraded to {{richfaces-parent:12-SNAPSHOT}}, which does not contain these sections anymore. > Remove repositories and pluginRepositories sections from richfaces-parent > ------------------------------------------------------------------------- > > Key: RF-11835 > URL: https://issues.jboss.org/browse/RF-11835 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: architectural, clean-up > Affects Versions: 4.1.0.Final > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 4.1.1.Final > > > Since we are uploading richfaces to Maven Central, we don't want to include project specific repositories in build. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 3 09:51:10 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28Resolved=29_=28JIRA=29?=) Date: Tue, 3 Jan 2012 09:51:10 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11826) Parent: upgrade maven-plugin-plugin to 2.9 and setup project to use richfaces-parent:12-SNAPSHOT In-Reply-To: <1306404369.21376.1324313889478.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <497719097.36688.1325602270118.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved RF-11826. ----------------------------- Resolution: Done > Parent: upgrade maven-plugin-plugin to 2.9 and setup project to use richfaces-parent:12-SNAPSHOT > ------------------------------------------------------------------------------------------------ > > Key: RF-11826 > URL: https://issues.jboss.org/browse/RF-11826 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 4.1.1.Final > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 4.1.1.Final > > > Issue with plugin dep version on {{jboss-parent}} side (JBBUILD-709) lead into local update [2]. > we should upgrade it in {{richfaces-parent}} before JBoss Parent will be released. > [1] https://github.com/richfaces/cdk/commit/642ec7a81075aec334d6692cc6077f69bce2572d#L0R104 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 3 09:53:10 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28Commented=29_=28JIRA=29?=) Date: Tue, 3 Jan 2012 09:53:10 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11836) Replace ${project.version} definitions in the poms with actual version In-Reply-To: <150403957.24272.1324386369523.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <843853492.36721.1325602390438.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12653525#comment-12653525 ] Luk?? Fry? commented on RF-11836: --------------------------------- >From the message from Maven Central guys, we it appeared we should not use ${project.version} at all, but the project which should be affected are not listed, we would need to investigate more what variables exactly should not be used. > Replace ${project.version} definitions in the poms with actual version > ---------------------------------------------------------------------- > > Key: RF-11836 > URL: https://issues.jboss.org/browse/RF-11836 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 4.1.0.Final > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 4.1.1.Final > > > This is requirement for uploading to Maven Central. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 3 10:02:09 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28Closed=29_=28JIRA=29?=) Date: Tue, 3 Jan 2012 10:02:09 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11767) Archetype: cannot build generated project because of missing JSF impl In-Reply-To: <210769580.60461.1322740300710.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <366436014.36761.1325602929889.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? closed RF-11767. --------------------------- Assignee: Luk?? Fry? Fix Version/s: (was: 4.1.1.Final) Resolution: Rejected Rejected as there are no changes necessary in archetype. > Archetype: cannot build generated project because of missing JSF impl > --------------------------------------------------------------------- > > Key: RF-11767 > URL: https://issues.jboss.org/browse/RF-11767 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: archetype > Affects Versions: 4.1.0.CR1 > Reporter: Pavol Pitonak > Assignee: Luk?? Fry? > > It's not possible to build a project generated using richfaces-archetype-simpleapp with enterprise=true because of missing JSF implementation artifact. > RichFaces BOM contains following version but EAP repository contains 2.1.3-b02-redhat-0-todo. > {code:xml} > > com.sun.faces > jsf-impl > 2.1.3-b02-jbossorg-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 Tue Jan 3 10:04:09 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28Assigned=29_=28JIRA=29?=) Date: Tue, 3 Jan 2012 10:04:09 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11816) Notify stack: names of CSS classes do not follow naming conventions In-Reply-To: <1667763817.10485.1323880569406.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <328678491.36765.1325603049557.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? reassigned RF-11816: ------------------------------- Assignee: Luk?? Fry? > Notify stack: names of CSS classes do not follow naming conventions > ------------------------------------------------------------------- > > Key: RF-11816 > URL: https://issues.jboss.org/browse/RF-11816 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-validators > Affects Versions: 4.1.0.Final > Reporter: Pavol Pitonak > Assignee: Luk?? Fry? > Priority: Minor > Fix For: 4.1.1.Final > > > Notify stack has 4 CSS classes that do not follow naming conventions: > * rf-ntf-pos-topLeft > * rf-ntf-pos-topRight > * rf-ntf-pos-bottomLeft > * rf-ntf-pos-bottomRight > Compare with similar classes of popup panel: > * rf-pp-hndlr-tl > * rf-pp-hndlr-tr > * rf-pp-hndlr-bl > * rf-pp-hndlr-br -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 3 10:04:09 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28Assigned=29_=28JIRA=29?=) Date: Tue, 3 Jan 2012 10:04:09 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11839) Hot key doesn't work when focus in on editor In-Reply-To: <334225743.24536.1324390329689.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <2143284697.36768.1325603049677.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? reassigned RF-11839: ------------------------------- Assignee: Luk?? Fry? > Hot key doesn't work when focus in on editor > -------------------------------------------- > > Key: RF-11839 > URL: https://issues.jboss.org/browse/RF-11839 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input, component-misc > Affects Versions: 4.1.0.Final > Environment: RichFaces 4.1.1-SNAPSHOT > Metamer 4.1.1-SNAPSHOT > Mojarra 2.1.3 > JBoss AS 7.1.0.Beta1 > OpenJDK Runtime Environment 1.6.0_22-b22 @ Linux > Chrome 16.0.912.63 @ Linux x86_64, Firefox 8.0 @ Linux x86_64 > Reporter: Pavol Pitonak > Assignee: Luk?? Fry? > Fix For: 4.1.1.Final > > > # deploy Metamer and open http://localhost:8080/metamer/faces/components/richHotKey/editor.xhtml > # press Ctrl+X (to focus on editor) > # press Alt+X (to blur from editor) > result: > * when Ctrl+X is pressed, focus is in editor > * when Alt+X is pressed, nothing happens (editor should no longer be focused) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 3 10:04:09 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28Assigned=29_=28JIRA=29?=) Date: Tue, 3 Jan 2012 10:04:09 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11808) Archetypes : remove the generation of *-source jars plumbing In-Reply-To: <1095649657.3045.1323708909608.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <879082206.36770.1325603049806.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? reassigned RF-11808: ------------------------------- Assignee: Luk?? Fry? > Archetypes : remove the generation of *-source jars plumbing > ------------------------------------------------------------ > > Key: RF-11808 > URL: https://issues.jboss.org/browse/RF-11808 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: archetype > Affects Versions: 4.1.0.CR2 > Reporter: Fred Bricon > Assignee: Luk?? Fry? > Priority: Minor > Fix For: 4.1.1.Final > > > The RF archetypes have some configuration to create *-source jars. Since the sources are already packaged in the actual archetype, this seems unnecessary, clutters the pom.xml and adds extra overhead to maintain the maven-assembly-plugin configuration. > Unless there's a good reason to keep that boilerplate, my suggestion is to stop generating the *-source packages and clean up the pom.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 Jan 3 10:08:09 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28Updated=29_=28JIRA=29?=) Date: Tue, 3 Jan 2012 10:08:09 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11824) rich:hotKey - add option to prevent default event handling In-Reply-To: <2043524135.17961.1324056189409.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1453263451.36787.1325603289481.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated RF-11824: ---------------------------- Fix Version/s: 4.1.1.Final > rich:hotKey - add option to prevent default event handling > ---------------------------------------------------------- > > Key: RF-11824 > URL: https://issues.jboss.org/browse/RF-11824 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-misc > Affects Versions: 4.1.1.Final > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Priority: Critical > Fix For: 4.1.1.Final > > > Some hot-keys are triggering default event handling ({{ctrl+a}}, {{page-up}}, etc.), > we may try to prevent this behavior, however it is not as simple as {{event.preventDefault()}} or {{return false;}}. > *_Please vote on issue if you would like to having this issue 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 Tue Jan 3 10:10:09 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28Updated=29_=28JIRA=29?=) Date: Tue, 3 Jan 2012 10:10:09 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11471) Upgrade to latest version of Atmosphere In-Reply-To: <1090154337.14335.1318029736037.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1018205292.36790.1325603409964.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated RF-11471: ---------------------------- Summary: Upgrade to latest version of Atmosphere (was: Upgrade to Atmosphere 0.8.0-RC3) > Upgrade to latest version of Atmosphere > --------------------------------------- > > Key: RF-11471 > URL: https://issues.jboss.org/browse/RF-11471 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 4.1.0.Milestone3 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Priority: Critical > Fix For: 4.2-Tracking > > > Atmosphere 0.8.0-RC2 is planned to be released [1] on right on 4.1.0.M3 code-freeze, we will wait before start of QE cycle to grab this release. > [1] http://groups.google.com/group/atmosphere-framework/browse_thread/thread/caffae0c616c250a -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 3 10:22:11 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28Commented=29_=28JIRA=29?=) Date: Tue, 3 Jan 2012 10:22:11 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11803) render of 'c:' and 'fn:' is one click behind In-Reply-To: <1412990328.81640.1323338620636.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <88319743.36825.1325604131900.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12653533#comment-12653533 ] Luk?? Fry? commented on RF-11803: --------------------------------- Thanks Milo, in respect to records, I'm rejecting this issue as upstream issue. > render of 'c:' and 'fn:' is one click behind > -------------------------------------------- > > Key: RF-11803 > URL: https://issues.jboss.org/browse/RF-11803 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Environment: MyFaces 2.1.5, Tomcat 7.0.22, 4.1.0-20111204 from showcase > Reporter: Milo van der Zee > Assignee: Luk?? Fry? > Priority: Minor > Labels: render > > 'c:' and 'fn:' is rendered differently from previous versions. > When clicking the inc and dec buttons in the example you can see that the field contents are updates each click but the number of fields is not (comma at the end when pressing 'dec'. Pressing 'render' then fixes the output. > When using a function to render it works fine. Even though the function does not do much. > MAG, > Milo > {code:title="testje4.xhtml"} > > xmlns="http://www.w3.org/1999/xhtml" > xmlns:h="http://java.sun.com/jsf/html" > xmlns:a4j="http://richfaces.org/a4j" > xmlns:rich="http://richfaces.org/rich" > xmlns:fn="http://java.sun.com/jsp/jstl/functions" > xmlns:c="http://java.sun.com/jsp/jstl/core" > > > > > > > > > > Counter: #{testBean.counter}
> > >
> > > > > > > #{status+1}: '#{field}', '#{fields}'
> > >
> > Direct render: > > >
> With function to render: > > >
> Manual render: > > > > > {code} > {code:title="testBean.java"} > package com.test; > import java.util.Arrays; > import java.util.List; > import javax.faces.bean.ManagedBean; > import javax.faces.bean.SessionScoped; > @ManagedBean > @SessionScoped > public class TestBean { > private int counter = 5; > public String getFieldsString() { > StringBuilder builder = new StringBuilder(); > boolean firstField = true; > for (int i = 0; i < counter; i++) { > if (!firstField) builder.append(','); > firstField = false; > char[] fill = new char[i + 1]; > Arrays.fill(fill, Character.forDigit(counter, 10)); > String fieldName = new String(fill); > builder.append(fieldName); > } > return builder.toString(); > } > public List getFieldsList() { > String string = getFieldsString(); > List list = Arrays.asList(string.split(",")); > return list; > } > public void decCounter() { > counter--; > if (counter < 1) counter = 1; > } > public void incCounter() { > counter++; > if (counter > 9) counter = 9; > } > public int getCounter() { > return counter; > } > public void setCounter(int counter) { > this.counter = counter; > } > } > {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 Jan 3 10:22:12 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28Resolved=29_=28JIRA=29?=) Date: Tue, 3 Jan 2012 10:22:12 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11803) render of 'c:' and 'fn:' is one click behind In-Reply-To: <1412990328.81640.1323338620636.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <2116376161.36829.1325604132106.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved RF-11803. ----------------------------- Resolution: Rejected > render of 'c:' and 'fn:' is one click behind > -------------------------------------------- > > Key: RF-11803 > URL: https://issues.jboss.org/browse/RF-11803 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Environment: MyFaces 2.1.5, Tomcat 7.0.22, 4.1.0-20111204 from showcase > Reporter: Milo van der Zee > Assignee: Luk?? Fry? > Priority: Minor > Labels: render > > 'c:' and 'fn:' is rendered differently from previous versions. > When clicking the inc and dec buttons in the example you can see that the field contents are updates each click but the number of fields is not (comma at the end when pressing 'dec'. Pressing 'render' then fixes the output. > When using a function to render it works fine. Even though the function does not do much. > MAG, > Milo > {code:title="testje4.xhtml"} > > xmlns="http://www.w3.org/1999/xhtml" > xmlns:h="http://java.sun.com/jsf/html" > xmlns:a4j="http://richfaces.org/a4j" > xmlns:rich="http://richfaces.org/rich" > xmlns:fn="http://java.sun.com/jsp/jstl/functions" > xmlns:c="http://java.sun.com/jsp/jstl/core" > > > > > > > > > > Counter: #{testBean.counter}
> > >
> > > > > > > #{status+1}: '#{field}', '#{fields}'
> > >
> > Direct render: > > >
> With function to render: > > >
> Manual render: > > > > > {code} > {code:title="testBean.java"} > package com.test; > import java.util.Arrays; > import java.util.List; > import javax.faces.bean.ManagedBean; > import javax.faces.bean.SessionScoped; > @ManagedBean > @SessionScoped > public class TestBean { > private int counter = 5; > public String getFieldsString() { > StringBuilder builder = new StringBuilder(); > boolean firstField = true; > for (int i = 0; i < counter; i++) { > if (!firstField) builder.append(','); > firstField = false; > char[] fill = new char[i + 1]; > Arrays.fill(fill, Character.forDigit(counter, 10)); > String fieldName = new String(fill); > builder.append(fieldName); > } > return builder.toString(); > } > public List getFieldsList() { > String string = getFieldsString(); > List list = Arrays.asList(string.split(",")); > return list; > } > public void decCounter() { > counter--; > if (counter < 1) counter = 1; > } > public void incCounter() { > counter++; > if (counter > 9) counter = 9; > } > public int getCounter() { > return counter; > } > public void setCounter(int counter) { > this.counter = counter; > } > } > {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 Jan 3 10:22:12 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28Updated=29_=28JIRA=29?=) Date: Tue, 3 Jan 2012 10:22:12 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11840) Hot key: arrow keys do not work in pick/ordering list when hot key is on page In-Reply-To: <1746550578.24557.1324390689563.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <781775710.36837.1325604132455.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated RF-11840: ---------------------------- Fix Version/s: 4.1.1.Final > Hot key: arrow keys do not work in pick/ordering list when hot key is on page > ----------------------------------------------------------------------------- > > Key: RF-11840 > URL: https://issues.jboss.org/browse/RF-11840 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-misc, component-selects > Affects Versions: 4.1.0.Final > Environment: RichFaces 4.1.1-SNAPSHOT > Metamer 4.1.1-SNAPSHOT > Mojarra 2.1.3-b02 > JBoss AS 7.1.0.Beta1 > OpenJDK Runtime Environment 1.6.0_22-b22 @ Linux > Chrome 16.0.912.63 @ Linux i686 > Reporter: Pavol Pitonak > Assignee: Luk?? Fry? > Fix For: 4.1.1.Final > > > # deploy Metamer and open http://localhost:8080/metamer/faces/components/richHotKey/pickList.xhtml > # click into pick list to select third item (Phoenix, Arizona) > # press arrow down > result: > * the following item in pick list should be selected (Little Rock, Arkansas) but browser scrolls the page instead > * when rich:hotKey is removed from page, arrows down/up start working again > * there is the same problem with *ordering 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 Tue Jan 3 10:25:09 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28Commented=29_=28JIRA=29?=) Date: Tue, 3 Jan 2012 10:25:09 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11837) Hot key: type attribute doesn't work when set to keypress In-Reply-To: <1275549371.24421.1324389250026.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1957290938.36841.1325604309566.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12653535#comment-12653535 ] Luk?? Fry? commented on RF-11837: --------------------------------- @type attribute are going to be reimplemented in scope of RF-11851. Let's reject this one once implemented. > Hot key: type attribute doesn't work when set to keypress > --------------------------------------------------------- > > Key: RF-11837 > URL: https://issues.jboss.org/browse/RF-11837 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-misc > Affects Versions: 4.1.0.Final > Environment: RichFaces 4.1.1-SNAPSHOT > Metamer 4.1.1-SNAPSHOT > Mojarra 2.1.3 > JBoss AS 7.1.0.Beta1 > OpenJDK Runtime Environment 1.6.0_22-b22 @ Linux > Chrome 16.0.912.63 @ Linux i686 > Reporter: Pavol Pitonak > Assignee: Luk?? Fry? > Fix For: 4.1.1.Final > > > # deploy Metamer and open http://localhost:8080/metamer/faces/components/richHotKey/simple.xhtml > # press Ctrl+X > # set attribute type=keypress > # press Ctrl+X > result: > * first action is executed, second 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 Tue Jan 3 10:25:09 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28Updated=29_=28JIRA=29?=) Date: Tue, 3 Jan 2012 10:25:09 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11837) Hot key: type attribute doesn't work when set to keypress In-Reply-To: <1275549371.24421.1324389250026.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <253000606.36843.1325604309828.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated RF-11837: ---------------------------- Fix Version/s: 4.1.1.Final > Hot key: type attribute doesn't work when set to keypress > --------------------------------------------------------- > > Key: RF-11837 > URL: https://issues.jboss.org/browse/RF-11837 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-misc > Affects Versions: 4.1.0.Final > Environment: RichFaces 4.1.1-SNAPSHOT > Metamer 4.1.1-SNAPSHOT > Mojarra 2.1.3 > JBoss AS 7.1.0.Beta1 > OpenJDK Runtime Environment 1.6.0_22-b22 @ Linux > Chrome 16.0.912.63 @ Linux i686 > Reporter: Pavol Pitonak > Assignee: Luk?? Fry? > Fix For: 4.1.1.Final > > > # deploy Metamer and open http://localhost:8080/metamer/faces/components/richHotKey/simple.xhtml > # press Ctrl+X > # set attribute type=keypress > # press Ctrl+X > result: > * first action is executed, second 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 Tue Jan 3 10:27:09 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28Commented=29_=28JIRA=29?=) Date: Tue, 3 Jan 2012 10:27:09 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11851) rich:hotKey - add support for onkeypress, onkeydown and onkeyup In-Reply-To: <2116883574.29436.1324557550117.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <471153882.36846.1325604429391.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12653536#comment-12653536 ] Luk?? Fry? commented on RF-11851: --------------------------------- Reject RF-11837 once this issue will be solved. > rich:hotKey - add support for onkeypress, onkeydown and onkeyup > --------------------------------------------------------------- > > Key: RF-11851 > URL: https://issues.jboss.org/browse/RF-11851 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: component-misc > Affects Versions: 4.1.1.Final > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Priority: Critical > Fix For: 4.1.1.Final > > > The binding will be done only for such types which have defined some handler. > This will mean removing {{@type}} 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 Tue Jan 3 10:41:09 2012 From: jira-events at lists.jboss.org (Pavol Pitonak (Created) (JIRA)) Date: Tue, 3 Jan 2012 10:41:09 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11862) BOM cannot be build Message-ID: <1844936912.36863.1325605269564.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> BOM cannot be build ------------------- Key: RF-11862 URL: https://issues.jboss.org/browse/RF-11862 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: build/distribution Affects Versions: 4.1.0.Final Reporter: Pavol Pitonak Priority: Blocker RichFaces BOM cannot be build (https://hudson.qa.jboss.com/hudson/view/RF-4.0/job/richfaces-4.1-build/84/console). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 3 13:47:09 2012 From: jira-events at lists.jboss.org (Brian Leathem (Resolved) (JIRA)) Date: Tue, 3 Jan 2012 13:47:09 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11856) Restore IE7 Support (dropped in RF 4.1.0.Final) In-Reply-To: <1285828427.30856.1324626849381.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1681843144.37632.1325616429395.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-11856. -------------------------------- Assignee: Brian Leathem Resolution: Won't Fix We've removed IE 7 from the list of supported browsers, as it's no longer a focus for the project moving forward. If you experience any specific issues with IE 7, please file jira issues, and we can assess them on a case-by-case basis. > Restore IE7 Support (dropped in RF 4.1.0.Final) > ----------------------------------------------- > > Key: RF-11856 > URL: https://issues.jboss.org/browse/RF-11856 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Dupont Dupont > Assignee: Brian Leathem > > IE 7 support was dropped in RF 4.1 > Links : > * http://community.jboss.org/wiki/PrioritizedRichFacesBrowsersCompatibilityMatrix > * http://docs.jboss.org/richfaces/latest_4_1_X/Developer_Guide/en-US/html/chap-Developer_Guide-RichFaces_overview.html#sect-Component_Reference-RichFaces_overview-Client_requirements > > IE 7 usage is 6.7% (from http://www.w3counter.com/globalstats.php) - RF 4.1 isn't usable for us as of now for internet purposes. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 4 04:10:17 2012 From: jira-events at lists.jboss.org (Lutz Ulrich (Commented) (JIRA)) Date: Wed, 4 Jan 2012 04:10:17 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11777) PopupPanelBaseRenderer is missing ResourceDependency on jquery.js In-Reply-To: <931847243.65657.1322832580703.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <926298812.38695.1325668217718.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12653715#comment-12653715 ] Lutz Ulrich commented on RF-11777: ---------------------------------- Sorry, in our case, the problem resulted from using PrimeFaces along with RichFaces. PrimeFaces has a special HeadRenderer (for HTML ) which only interprets resources which end with '.js' as script resources. Thus, RichFaces special script resources 'ajax.reslib' and 'base-component.reslib' are not treated as script resources and the related resource UIComponents are probably not rendered at all. > PopupPanelBaseRenderer is missing ResourceDependency on jquery.js > ----------------------------------------------------------------- > > Key: RF-11777 > URL: https://issues.jboss.org/browse/RF-11777 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.0.0.Final > Environment: Java7, Tomcat 7.0.22, Mojarra 2.1.2 > Reporter: Lutz Ulrich > Assignee: Brian Leathem > Priority: Minor > Original Estimate: 5 minutes > Remaining Estimate: 5 minutes > > PopupPanelBaseRenderer is missing ResourceDependency on jquery.js and maybe other script library files. > If the page does not contain any components which declare to require jquery.js or if such components are located after popupPanel, the missing jQuery library causes script errors and the popupPanel 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 Jan 4 04:12:10 2012 From: jira-events at lists.jboss.org (Juraj Huska (Commented) (JIRA)) Date: Wed, 4 Jan 2012 04:12:10 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11827) showcase - all rich:autocomplete demos do not work on 4.1.1-SNAPSHOT In-Reply-To: <945549203.21383.1324314009775.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1742441236.38700.1325668330686.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12653716#comment-12653716 ] Juraj Huska commented on RF-11827: ---------------------------------- The affect by was wrong, sorry, the version from title is the one where the issue occurs. > showcase - all rich:autocomplete demos do not work on 4.1.1-SNAPSHOT > -------------------------------------------------------------------- > > Key: RF-11827 > URL: https://issues.jboss.org/browse/RF-11827 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input, showcase > Affects Versions: 4.1.1.Final > Environment: richfaces showcase 4.1.1-SNAPSHOT > all containers > all brosers > Reporter: Juraj Huska > Assignee: Juraj Huska > > Demos for rich:autocomplete do not work, *whole functionality of autocomplete is broken somehow*. > It is noticeable on *all containers* and on *all browsers*. > It works fine on 4.1.0-SNAPSHOT showcase wars. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 4 04:12:11 2012 From: jira-events at lists.jboss.org (Juraj Huska (Updated) (JIRA)) Date: Wed, 4 Jan 2012 04:12:11 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11827) showcase - all rich:autocomplete demos do not work on 4.1.1-SNAPSHOT In-Reply-To: <945549203.21383.1324314009775.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <864858531.38703.1325668331270.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj Huska updated RF-11827: ----------------------------- Assignee: (was: Juraj Huska) Affects Version/s: 4.1.1.Final (was: 4.1.0.Final) > showcase - all rich:autocomplete demos do not work on 4.1.1-SNAPSHOT > -------------------------------------------------------------------- > > Key: RF-11827 > URL: https://issues.jboss.org/browse/RF-11827 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input, showcase > Affects Versions: 4.1.1.Final > Environment: richfaces showcase 4.1.1-SNAPSHOT > all containers > all brosers > Reporter: Juraj Huska > > Demos for rich:autocomplete do not work, *whole functionality of autocomplete is broken somehow*. > It is noticeable on *all containers* and on *all browsers*. > It works fine on 4.1.0-SNAPSHOT showcase wars. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 4 04:36:11 2012 From: jira-events at lists.jboss.org (Lutz Ulrich (Commented) (JIRA)) Date: Wed, 4 Jan 2012 04:36:11 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11144) Add the possibility to configure which jquery version RF will use. In-Reply-To: <1736166369.80509.1311615563710.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <416810072.38759.1325669771036.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12653718#comment-12653718 ] Lutz Ulrich commented on RF-11144: ---------------------------------- I'm using PrimeFaces along with RichFaces, too, and have the same problem. In order to avoid such conflicts, RichFaces' jquery.js (and all jquery.js files of other JSF libraries) should contain a test which checks if jquery has already been initialized. That is, check for example, if the variables window.$ or window.jquery are already defined. A workaround is to 'override' RichFaces' version of jquery.js. RichFaces jquery.js is integrated into the HTML document via: It is loaded from richfaces-core-impl-.jar/META-INF/resources/jquery.js . If the web app's folder resources/ contains a file with the same name, that resource file will be loaded instead of the one in richfaces-core-impl-.jar, because files in the web app's resources folder have a higher priority than files in JARs. One can copy RichFaces jquery.js from richfaces-core-impl-.jar into the web app's resources/ folder. In that copy, one can add additional code which checks if jquery has already been initialized: (function( window, undefined ) { // THE TEST: if (!window.$) { // ... window.jQuery = window.$ = jQuery; } // end test if window.$ })(window); > Add the possibility to configure which jquery version RF will use. > ------------------------------------------------------------------ > > Key: RF-11144 > URL: https://issues.jboss.org/browse/RF-11144 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: compatibility, third-party > Reporter: Jos? Freitas > Labels: integration, jquery, primefaces > Fix For: 4.Future > > > This feature would be awesome cause it could easy integration with others components suites like primefaces. > if we could say to richfaces where it could find its jquery reference, we could config it to use jquery from primefaces for example. > > avoiding jquery double loading and conflicts between libs. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 4 05:27:10 2012 From: jira-events at lists.jboss.org (Juraj Huska (Created) (JIRA)) Date: Wed, 4 Jan 2012 05:27:10 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11863) showcase - rich:hotKey - mistake in demo description Message-ID: <1960056587.38881.1325672830689.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> showcase - rich:hotKey - mistake in demo description ---------------------------------------------------- Key: RF-11863 URL: https://issues.jboss.org/browse/RF-11863 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-misc, examples, showcase Affects Versions: 4.1.1.Final Environment: showcase 4.1.1-SNAPSHOT Reporter: Juraj Huska Priority: Trivial In the text description is said: ??Press Home or End buttons in order to move all items between lists.?? However, for this action (moving all items), the 'ctrl+right' and 'ctrl+left' shortcuts are bound. The demo description should be updated according to current bindings. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 4 05:29:09 2012 From: jira-events at lists.jboss.org (Juraj Huska (Updated) (JIRA)) Date: Wed, 4 Jan 2012 05:29:09 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11863) showcase - rich:hotKey - mistake in demo description In-Reply-To: <1960056587.38881.1325672830689.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1005233890.38884.1325672949733.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj Huska updated RF-11863: ----------------------------- Description: In the demo description is said: ??Press Home or End buttons in order to move all items between lists.?? However, for this action (moving all items), the 'ctrl+right' and 'ctrl+left' shortcuts are bound. The demo description should be updated according to current bindings. was: In the text description is said: ??Press Home or End buttons in order to move all items between lists.?? However, for this action (moving all items), the 'ctrl+right' and 'ctrl+left' shortcuts are bound. The demo description should be updated according to current bindings. > showcase - rich:hotKey - mistake in demo description > ---------------------------------------------------- > > Key: RF-11863 > URL: https://issues.jboss.org/browse/RF-11863 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-misc, examples, showcase > Affects Versions: 4.1.1.Final > Environment: showcase 4.1.1-SNAPSHOT > Reporter: Juraj Huska > Priority: Trivial > > In the demo description is said: ??Press Home or End buttons in order to move all items between lists.?? > However, for this action (moving all items), the 'ctrl+right' and 'ctrl+left' shortcuts are bound. > The demo description should be updated according to current bindings. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 4 22:21:09 2012 From: jira-events at lists.jboss.org (Brian Leathem (Updated) (JIRA)) Date: Wed, 4 Jan 2012 22:21:09 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11827) showcase - all rich:autocomplete demos do not work on 4.1.1-SNAPSHOT In-Reply-To: <945549203.21383.1324314009775.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <23703375.41098.1325733669361.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-11827: ------------------------------- Fix Version/s: 4.1.1.Final Assignee: Luk?? Fry? Affects Version/s: (was: 4.1.1.Final) Errors in the javascript console show a problem with the hotkey jquery functionality (in packed.js). Possibly a resource ordering issue? > showcase - all rich:autocomplete demos do not work on 4.1.1-SNAPSHOT > -------------------------------------------------------------------- > > Key: RF-11827 > URL: https://issues.jboss.org/browse/RF-11827 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input, showcase > Environment: richfaces showcase 4.1.1-SNAPSHOT > all containers > all brosers > Reporter: Juraj Huska > Assignee: Luk?? Fry? > Fix For: 4.1.1.Final > > > Demos for rich:autocomplete do not work, *whole functionality of autocomplete is broken somehow*. > It is noticeable on *all containers* and on *all browsers*. > It works fine on 4.1.0-SNAPSHOT showcase wars. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 4 22:23:09 2012 From: jira-events at lists.jboss.org (Brian Leathem (Updated) (JIRA)) Date: Wed, 4 Jan 2012 22:23:09 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11858) Upgrade to Guava 10.0 (or even 11.0) as provided by JBossAS 7.1.CR1b In-Reply-To: <1099871218.32163.1324892709514.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <67026348.41101.1325733789471.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-11858: ------------------------------- Fix Version/s: 4.1-Tracking Priority: Critical (was: Major) Assignee: Brian Leathem Marking as critical, as this must be done early in the dev process if it is to be included in 4.1.1.Final > Upgrade to Guava 10.0 (or even 11.0) as provided by JBossAS 7.1.CR1b > -------------------------------------------------------------------- > > Key: RF-11858 > URL: https://issues.jboss.org/browse/RF-11858 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Reporter: Juergen Zimmermann > Assignee: Brian Leathem > Priority: Critical > Fix For: 4.1.1.Final > > > JBossAS 7.1.CR1b is using Guava 10.0. To prohibit compatibility issues I'd appreciate if you'd also upgrade to 10.0 (or even 11.0). Please see http://repo1.maven.org/maven2/com/google/guava/guava/ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 4 22:23:09 2012 From: jira-events at lists.jboss.org (Brian Leathem (Updated) (JIRA)) Date: Wed, 4 Jan 2012 22:23:09 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11858) Upgrade to Guava 10.0 (or even 11.0) as provided by JBossAS 7.1.CR1b In-Reply-To: <1099871218.32163.1324892709514.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1738285248.41103.1325733789560.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-11858: ------------------------------- Fix Version/s: 4.1.1.Final (was: 4.1-Tracking) > Upgrade to Guava 10.0 (or even 11.0) as provided by JBossAS 7.1.CR1b > -------------------------------------------------------------------- > > Key: RF-11858 > URL: https://issues.jboss.org/browse/RF-11858 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Reporter: Juergen Zimmermann > Assignee: Brian Leathem > Priority: Critical > Fix For: 4.1.1.Final > > > JBossAS 7.1.CR1b is using Guava 10.0. To prohibit compatibility issues I'd appreciate if you'd also upgrade to 10.0 (or even 11.0). Please see http://repo1.maven.org/maven2/com/google/guava/guava/ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 4 22:23:09 2012 From: jira-events at lists.jboss.org (Brian Leathem (Updated) (JIRA)) Date: Wed, 4 Jan 2012 22:23:09 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11859) Many script/css added when not needed In-Reply-To: <872670898.35681.1325563989373.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1771055944.41105.1325733789636.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-11859: ------------------------------- Fix Version/s: 3.Future Forum Reference: http://community.jboss.org/message/643264#643264 (was: http://community.jboss.org/message/643264#643264) > Many script/css added when not needed > ------------------------------------- > > Key: RF-11859 > URL: https://issues.jboss.org/browse/RF-11859 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 3.3.3.Final > Environment: JBoss 5.1 > Reporter: Dave Chen > Fix For: 3.Future > > > Richfaces filter always adds many scripts/css even when a page does not need them, causing slow page loading for website, and not search engine friendly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 4 22:25:44 2012 From: jira-events at lists.jboss.org (Brian Leathem (Updated) (JIRA)) Date: Wed, 4 Jan 2012 22:25:44 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11860) Data table: The scope attribute on the td element is obsolete In-Reply-To: <207304981.36098.1325591409412.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1090331936.41372.1325733944903.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-11860: ------------------------------- Fix Version/s: 4.1.1.Final Priority: Minor (was: Major) Assignee: Brian Leathem > Data table: The scope attribute on the td element is obsolete > ------------------------------------------------------------- > > Key: RF-11860 > URL: https://issues.jboss.org/browse/RF-11860 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: compatibility, component-tables > Affects Versions: 4.1.0.Final > Environment: RichFaces 4.1.1-SNAPSHOT > Metamer 4.1.1-SNAPSHOT r.23118 > Mojarra 2.1.5 > JBoss AS 7.1.0.CR1 > OpenJDK Runtime Environment 1.6.0_22-b22 @ Linux > Chrome 16.0.912.63 @ Linux i686 > Reporter: Pavol Pitonak > Assignee: Brian Leathem > Priority: Minor > Fix For: 4.1.1.Final > > > The column footer is rendered as in following code snippet (can be reproduced in Metamer http://localhost:8080/metamer/faces/components/richDataTable/facets.xhtml): > {code:xml} > > > > > > > > > > {code} > Attribute *scope* on element td is obsolete in HTML5 and should be set on th element instead. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 4 22:25:44 2012 From: jira-events at lists.jboss.org (Brian Leathem (Updated) (JIRA)) Date: Wed, 4 Jan 2012 22:25:44 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11861) richfaces 4.1.Final showcase: Non-resolvable parent POM: Could not find artifact org.richfaces:richfaces-root-parent:pom:4.1.0.Final In-Reply-To: <1704236441.36501.1325599509914.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <992088357.41374.1325733944967.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-11861: ------------------------------- Description: richfaces showcase for Richfaces 4.1 Final doesn't build. Problem is that: {code} org.richfacesrichfaces-root-parent4.1.0.Final {code} is not in central maven repository. Console output: {code} [INFO] Scanning for projects... Downloading: http://repo1.maven.org/maven2/org/richfaces/richfaces-root-parent/4.1.0.Final/richfaces-root-parent-4.1.0.F inal.pom [ERROR] The build could not read 1 project -> [Help 1] [ERROR] [ERROR] The project org.richfaces.examples:richfaces-showcase:4.1.0.Final (D:\tmp\richfaces-showcase-77c6701\pom.xml) has 1 error [ERROR] Non-resolvable parent POM: Could not find artifact org.richfaces:richfaces-root-parent:pom:4.1.0.Final in ce ntral (http://repo1.maven.org/maven2) and 'parent.relativePath' points at wrong local POM @ line 8, column 13 -> [Help 2 ] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException [ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException {code} was: richfaces showcase for Richfaces 4.1 Final doesn't build. Problem is that: org.richfacesrichfaces-root-parent4.1.0.Final is not in central maven repository. Console output: [INFO] Scanning for projects... Downloading: http://repo1.maven.org/maven2/org/richfaces/richfaces-root-parent/4.1.0.Final/richfaces-root-parent-4.1.0.F inal.pom [ERROR] The build could not read 1 project -> [Help 1] [ERROR] [ERROR] The project org.richfaces.examples:richfaces-showcase:4.1.0.Final (D:\tmp\richfaces-showcase-77c6701\pom.xml) has 1 error [ERROR] Non-resolvable parent POM: Could not find artifact org.richfaces:richfaces-root-parent:pom:4.1.0.Final in ce ntral (http://repo1.maven.org/maven2) and 'parent.relativePath' points at wrong local POM @ line 8, column 13 -> [Help 2 ] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException [ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException Workaround Description: One of the possible workarounds is to add relevant jboss repository to pom.xml file, I added following to make it running: {code} jboss-public-repository-group https://repository.jboss.org/nexus/content/groups/public-jboss/ default true never {code} But I believe it should work out of the box for anyone willing to build showcase => should be part of pom.xml as default, or it should be mentioned in the readme file as a prerequisite. was: One of the possible workarounds is to add relevant jboss repository to pom.xml file, I added following to make it running: jboss-public-repository-group https://repository.jboss.org/nexus/content/groups/public-jboss/ default true never But I believe it should work out of the box for anyone willing to build showcase => should be part of pom.xml as default, or it should be mentioned in the readme file as a prerequisite. > richfaces 4.1.Final showcase: Non-resolvable parent POM: Could not find artifact org.richfaces:richfaces-root-parent:pom:4.1.0.Final > ------------------------------------------------------------------------------------------------------------------------------------ > > Key: RF-11861 > URL: https://issues.jboss.org/browse/RF-11861 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Peter B > Labels: richfaces > > richfaces showcase for Richfaces 4.1 Final doesn't build. > Problem is that: > {code} > org.richfaces > richfaces-root-parent > 4.1.0.Final > {code} > is not in central maven repository. > Console output: > {code} > [INFO] Scanning for projects... > Downloading: http://repo1.maven.org/maven2/org/richfaces/richfaces-root-parent/4.1.0.Final/richfaces-root-parent-4.1.0.F > inal.pom > [ERROR] The build could not read 1 project -> [Help 1] > [ERROR] > [ERROR] The project org.richfaces.examples:richfaces-showcase:4.1.0.Final (D:\tmp\richfaces-showcase-77c6701\pom.xml) > has 1 error > [ERROR] Non-resolvable parent POM: Could not find artifact org.richfaces:richfaces-root-parent:pom:4.1.0.Final in ce > ntral (http://repo1.maven.org/maven2) and 'parent.relativePath' points at wrong local POM @ line 8, column 13 -> [Help 2 > ] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please read the following articles: > [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException > [ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException > {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 Jan 4 22:27:10 2012 From: jira-events at lists.jboss.org (Brian Leathem (Updated) (JIRA)) Date: Wed, 4 Jan 2012 22:27:10 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11862) BOM cannot be build In-Reply-To: <1844936912.36863.1325605269564.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <730801843.41385.1325734030121.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-11862: ------------------------------- Fix Version/s: 4.1.1.Final Assignee: Luk?? Fry? Indeed a blocker, probably introduced with the recent BOM/parent cleanup. > BOM cannot be build > ------------------- > > Key: RF-11862 > URL: https://issues.jboss.org/browse/RF-11862 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 4.1.0.Final > Reporter: Pavol Pitonak > Assignee: Luk?? Fry? > Priority: Blocker > Fix For: 4.1.1.Final > > > RichFaces BOM cannot be build (https://hudson.qa.jboss.com/hudson/view/RF-4.0/job/richfaces-4.1-build/84/console). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 4 22:29:09 2012 From: jira-events at lists.jboss.org (Brian Leathem (Updated) (JIRA)) Date: Wed, 4 Jan 2012 22:29:09 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11863) showcase - rich:hotKey - mistake in demo description In-Reply-To: <1960056587.38881.1325672830689.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1158439907.41388.1325734149381.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-11863: ------------------------------- Fix Version/s: 4.1.1.Final Assignee: Luk?? Fry? > showcase - rich:hotKey - mistake in demo description > ---------------------------------------------------- > > Key: RF-11863 > URL: https://issues.jboss.org/browse/RF-11863 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-misc, examples, showcase > Affects Versions: 4.1.1.Final > Environment: showcase 4.1.1-SNAPSHOT > Reporter: Juraj Huska > Assignee: Luk?? Fry? > Priority: Trivial > Fix For: 4.1.1.Final > > > In the demo description is said: ??Press Home or End buttons in order to move all items between lists.?? > However, for this action (moving all items), the 'ctrl+right' and 'ctrl+left' shortcuts are bound. > The demo description should be updated according to current bindings. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 5 04:32:09 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28Commented=29_=28JIRA=29?=) Date: Thu, 5 Jan 2012 04:32:09 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11862) BOM cannot be build In-Reply-To: <1844936912.36863.1325605269564.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <339871588.41968.1325755929422.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12653988#comment-12653988 ] Luk?? Fry? commented on RF-11862: --------------------------------- Fixed in https://github.com/richfaces/build/commit/fc302d8c4a616dafb67c53d8d5b9fcc521e65d55 > BOM cannot be build > ------------------- > > Key: RF-11862 > URL: https://issues.jboss.org/browse/RF-11862 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 4.1.0.Final > Reporter: Pavol Pitonak > Assignee: Luk?? Fry? > Priority: Blocker > > RichFaces BOM cannot be build (https://hudson.qa.jboss.com/hudson/view/RF-4.0/job/richfaces-4.1-build/84/console). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 5 04:32:09 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28Resolved=29_=28JIRA=29?=) Date: Thu, 5 Jan 2012 04:32:09 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11862) BOM cannot be build In-Reply-To: <1844936912.36863.1325605269564.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1111016990.41970.1325755929546.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved RF-11862. ----------------------------- Fix Version/s: (was: 4.1.1.Final) Resolution: Duplicate Issue > BOM cannot be build > ------------------- > > Key: RF-11862 > URL: https://issues.jboss.org/browse/RF-11862 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 4.1.0.Final > Reporter: Pavol Pitonak > Assignee: Luk?? Fry? > Priority: Blocker > > RichFaces BOM cannot be build (https://hudson.qa.jboss.com/hudson/view/RF-4.0/job/richfaces-4.1-build/84/console). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 5 09:06:09 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28Assigned=29_=28JIRA=29?=) Date: Thu, 5 Jan 2012 09:06:09 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11836) Replace ${project.version} definitions in the poms with actual version In-Reply-To: <150403957.24272.1324386369523.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <941005960.42908.1325772369962.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? reassigned RF-11836: ------------------------------- Assignee: Brian Leathem (was: Luk?? Fry?) > Replace ${project.version} definitions in the poms with actual version > ---------------------------------------------------------------------- > > Key: RF-11836 > URL: https://issues.jboss.org/browse/RF-11836 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 4.1.0.Final > Reporter: Luk?? Fry? > Assignee: Brian Leathem > Fix For: 4.1.1.Final > > > This is requirement for uploading to Maven Central. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 5 09:08:09 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28Commented=29_=28JIRA=29?=) Date: Thu, 5 Jan 2012 09:08:09 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11836) Replace ${project.version} definitions in the poms with actual version In-Reply-To: <150403957.24272.1324386369523.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <2106668050.42911.1325772489873.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12654044#comment-12654044 ] Luk?? Fry? commented on RF-11836: --------------------------------- It needs to be determined if we are able to sync only 4.1.x artifacts with Maven Central. > Replace ${project.version} definitions in the poms with actual version > ---------------------------------------------------------------------- > > Key: RF-11836 > URL: https://issues.jboss.org/browse/RF-11836 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 4.1.0.Final > Reporter: Luk?? Fry? > Assignee: Brian Leathem > Fix For: 4.1.1.Final > > > This is requirement for uploading to Maven Central. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 5 10:44:09 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28Resolved=29_=28JIRA=29?=) Date: Thu, 5 Jan 2012 10:44:09 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11858) Upgrade to Guava 10.0 (or even 11.0) as provided by JBossAS 7.1.CR1b In-Reply-To: <1099871218.32163.1324892709514.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1124803210.43296.1325778249545.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved RF-11858. ----------------------------- Fix Version/s: (was: 4.1.1.Final) Resolution: Duplicate Issue Guava already upgraded in RF-11666. > Upgrade to Guava 10.0 (or even 11.0) as provided by JBossAS 7.1.CR1b > -------------------------------------------------------------------- > > Key: RF-11858 > URL: https://issues.jboss.org/browse/RF-11858 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Reporter: Juergen Zimmermann > Assignee: Brian Leathem > Priority: Critical > > JBossAS 7.1.CR1b is using Guava 10.0. To prohibit compatibility issues I'd appreciate if you'd also upgrade to 10.0 (or even 11.0). Please see http://repo1.maven.org/maven2/com/google/guava/guava/ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 5 10:48:10 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28Updated=29_=28JIRA=29?=) Date: Thu, 5 Jan 2012 10:48:10 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11615) Upgrade to JBoss Parent version 8 In-Reply-To: <1714858172.39799.1320059745985.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <264922394.43301.1325778490121.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated RF-11615: ---------------------------- Assignee: Luk?? Fry? (was: Brian Leathem) Fix Version/s: 4.1.1.Final > Upgrade to JBoss Parent version 8 > --------------------------------- > > Key: RF-11615 > URL: https://issues.jboss.org/browse/RF-11615 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 4.1.0.Milestone4 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Priority: Minor > Fix For: 4.1.1.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 Thu Jan 5 12:27:09 2012 From: jira-events at lists.jboss.org (Brian Leathem (Updated) (JIRA)) Date: Thu, 5 Jan 2012 12:27:09 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11657) Better integration with JBossAS 7.1 In-Reply-To: <1860495351.67654.1320759705458.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1170260844.43602.1325784429561.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-11657: ------------------------------- Fix Version/s: 4.1.1.Final (was: 4.2-Tracking) Priority: Trivial (was: Major) Assignee: Brian Leathem > Better integration with JBossAS 7.1 > ----------------------------------- > > Key: RF-11657 > URL: https://issues.jboss.org/browse/RF-11657 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build/distribution, compatibility > Affects Versions: 4.1.0.Milestone4 > Reporter: Juergen Zimmermann > Assignee: Brian Leathem > Priority: Trivial > Fix For: 4.1.1.Final > > > JBossAS 7.1 contains Google Guava 10.0.x (in addition to sac-1.3.jar and cssparser-0.9.5.jar). Guava can be reused in RichFaces instead of doubling it in WEB-INF/lib. The solution is pretty simple: > In richfaces-core-impl-VERSION.jar the file META-INF/MANIFEST.MF already contains the line "Dependencies: ...". This line has to be extended by just ",com.google.guava" as follows: > Dependencies: org.w3c.css.sac,net.sourceforge.cssparser,com.google.guava > That's all and from now on RichFaces doesn't require the distribution of Google Guava in WEB-INF/lib when the platform is JBossAS 7.1. Please see also https://issues.jboss.org/browse/AS7-1809. > Be aware that there is no blank after the comma between net.sourceforge.cssparser and com.google.guava. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 5 14:26:09 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28Updated=29_=28JIRA=29?=) Date: Thu, 5 Jan 2012 14:26:09 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11810) Fix the richfaces-components-ui build to do not overwrite assemblied JAR In-Reply-To: <1133407192.4657.1323764289624.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <2009312638.43799.1325791569836.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated RF-11810: ---------------------------- Complexity: Low > Fix the richfaces-components-ui build to do not overwrite assemblied JAR > ------------------------------------------------------------------------ > > Key: RF-11810 > URL: https://issues.jboss.org/browse/RF-11810 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 4.1.0.Final > Reporter: Marek Novotny > Assignee: Luk?? Fry? > Fix For: 4.1.1.Final > > > (Issue reported by Lukas Fryc) > Marek Novotny (manaRH) has recently reported that sometimes RF build fails for him since {{richfaces-components-ui}} module is generating JAR using {{maven-assembly-plugin}} which has the same name as the standard {{maven-jar-plugin}} artifact would be called. > This may lead into potential clash for bad timings, especially when these plugins are ran on the same lifecycle phase. > The symptoms are failing applications (and functional tests) which are not able to use any UI implementation classes. > We should either: > # change lifecycle mapping of plugins > # modify {{maven-jar-plugin}} settings > {code:title=Log from Hudson console http://hudson.qa.jboss.com/hudson/job/richfaces-4.1-all-jboss/62/console} > [INFO] ------------------------------------------------------------------------ > [INFO] Building RichFaces Examples Aggregator 4.1.0-SNAPSHOT > [INFO] ------------------------------------------------------------------------ > [INFO] > [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ examples-aggregator --- > [INFO] > [INFO] --- maven-enforcer-plugin:1.0:enforce (enforce-java-version) @ examples-aggregator --- > [INFO] > [INFO] --- maven-enforcer-plugin:1.0:enforce (enforce-maven-version) @ examples-aggregator --- > [INFO] > [INFO] --- maven-source-plugin:2.1.2:jar-no-fork (attach-sources) @ examples-aggregator --- > projectSucceeded org.richfaces.examples:examples-aggregator:4.1.0-SNAPSHOT > [JENKINS] Archiving /mnt/hudson_workspace/workspace/richfaces-4.1-all-jboss/dev-examples/pom.xml to /qa/hudson_master/hudson_home/hudson_workspace/jobs/richfaces-4.1-all-jboss/modules/org.richfaces.examples$examples-aggregator/builds/2011-12-09_06-01-08/archive/org.richfaces.examples/examples-aggregator/4.1.0-SNAPSHOT/examples-aggregator-4.1.0-SNAPSHOT.pom > [INFO] > [INFO] ------------------------------------------------------------------------ > [INFO] Building RichFaces Showcase 4.1.0-SNAPSHOT > [INFO] ------------------------------------------------------------------------ > [INFO] > [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ richfaces-showcase --- > [INFO] Deleting /mnt/hudson_workspace/workspace/richfaces-4.1-all-jboss/showcase/target > [INFO] > [INFO] --- maven-enforcer-plugin:1.0:enforce (enforce-java-version) @ richfaces-showcase --- > [INFO] > [INFO] --- maven-enforcer-plugin:1.0:enforce (enforce-maven-version) @ richfaces-showcase --- > [INFO] > [INFO] --- maven-checkstyle-plugin:2.5:check (richfaces-checkstyle-report) @ richfaces-showcase --- > [INFO] > [INFO] [debug] execute contextualize > [INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ richfaces-showcase --- > [INFO] Using 'UTF-8' encoding to copy filtered resources. > [INFO] Copying 9 resources > [INFO] Copying 0 resource > [INFO] > [INFO] --- maven-compiler-plugin:2.3.1:compile (default-compile) @ richfaces-showcase --- > [INFO] Compiling 97 source files to /mnt/hudson_workspace/workspace/richfaces-4.1-all-jboss/showcase/target/classes > [INFO] ------------------------------------------------------------- > [ERROR] COMPILATION ERROR : > [INFO] ------------------------------------------------------------- > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.1-all-jboss/showcase/src/main/java/org/richfaces/demo/calendar/model/CalendarModelItem.java:[3,26] cannot find symbol > symbol : class CalendarDataModelItem > location: package org.richfaces.model > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.1-all-jboss/showcase/src/main/java/org/richfaces/demo/calendar/model/CalendarModelItem.java:[5,42] cannot find symbol > symbol: class CalendarDataModelItem > public class CalendarModelItem implements CalendarDataModelItem { > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.1-all-jboss/showcase/src/main/java/org/richfaces/demo/tree/TreeBean.java:[36,30] cannot find symbol > symbol : class UITree > location: package org.richfaces.component > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.1-all-jboss/showcase/src/main/java/org/richfaces/demo/tables/ExtTableSelectionBean.java:[13,30] cannot find symbol > symbol : class UIExtendedDataTable > location: package org.richfaces.component > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.1-all-jboss/showcase/src/main/java/org/richfaces/demo/calendar/model/CalendarModel.java:[10,26] cannot find symbol > symbol : class CalendarDataModel > location: package org.richfaces.model > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.1-all-jboss/showcase/src/main/java/org/richfaces/demo/calendar/model/CalendarModel.java:[11,26] cannot find symbol > symbol : class CalendarDataModelItem > location: package org.richfaces.model > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.1-all-jboss/showcase/src/main/java/org/richfaces/demo/calendar/model/CalendarModel.java:[15,38] cannot find symbol > symbol: class CalendarDataModel > public class CalendarModel implements CalendarDataModel { > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.1-all-jboss/showcase/src/main/java/org/richfaces/demo/calendar/model/CalendarModel.java:[28,11] cannot find symbol > symbol : class CalendarDataModelItem > location: class org.richfaces.demo.calendar.model.CalendarModel > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.1-all-jboss/showcase/src/main/java/org/richfaces/demo/tree/TreeBean.java:[72,8] cannot find symbol > symbol : class UITree > location: class org.richfaces.demo.tree.TreeBean > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.1-all-jboss/showcase/src/main/java/org/richfaces/demo/tree/TreeBean.java:[72,23] cannot find symbol > symbol : class UITree > location: class org.richfaces.demo.tree.TreeBean > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.1-all-jboss/showcase/src/main/java/org/richfaces/demo/tables/ExtTableSelectionBean.java:[26,8] cannot find symbol > symbol : class UIExtendedDataTable > location: class org.richfaces.demo.tables.ExtTableSelectionBean > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.1-all-jboss/showcase/src/main/java/org/richfaces/demo/tables/ExtTableSelectionBean.java:[26,41] cannot find symbol > symbol : class UIExtendedDataTable > location: class org.richfaces.demo.tables.ExtTableSelectionBean > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.1-all-jboss/showcase/src/main/java/org/richfaces/demo/calendar/model/CalendarModel.java:[29,8] cannot find symbol > symbol : class CalendarDataModelItem > location: class org.richfaces.demo.calendar.model.CalendarModel > [INFO] 13 errors > [INFO] ------------------------------------------------------------- > mojoFailed org.apache.maven.plugins:maven-compiler-plugin:2.3.1(default-compile) > projectFailed org.richfaces.examples:richfaces-showcase:4.1.0-SNAPSHOT > [JENKINS] Archiving /mnt/hudson_workspace/workspace/richfaces-4.1-all-jboss/showcase/pom.xml to /qa/hudson_master/hudson_home/hudson_workspace/jobs/richfaces-4.1-all-jboss/modules/org.richfaces.examples$richfaces-showcase/builds/2011-12-09_06-01-09/archive/org.richfaces.examples/richfaces-showcase/4.1.0-SNAPSHOT/richfaces-showcase-4.1.0-SNAPSHOT.pom > sessionEnded > [INFO] ------------------------------------------------------------------------ > [INFO] Reactor Summary: > [INFO] > [INFO] RichFaces BOM ..................................... SUCCESS [5.347s] > [INFO] RichFaces Root Parent ............................. SUCCESS [3.868s] > [INFO] RichFaces Core Parent ............................. SUCCESS [0.434s] > [INFO] RichFaces Core API ................................ SUCCESS [55.658s] > [INFO] RichFaces Core Implementation ..................... SUCCESS [5:34.292s] > [INFO] RichFaces Core Aggregator ......................... SUCCESS [0.269s] > [INFO] RichFaces CDK Parent .............................. SUCCESS [0.423s] > [INFO] RichFaces CDK Commons ............................. SUCCESS [14.724s] > [INFO] RichFaces CDK Annotations ......................... SUCCESS [13.308s] > [INFO] RichFaces CDK Attributes .......................... SUCCESS [16.929s] > [INFO] RichFaces CDK XInclude Transformer ................ SUCCESS [24.699s] > [INFO] RichFaces CDK Generator ........................... SUCCESS [2:09.707s] > [INFO] RichFaces CDK Generator Maven Plugin .............. SUCCESS [26.485s] > [INFO] RichFaces CDK Resources Maven Plugin .............. SUCCESS [32.530s] > [INFO] RichFaces CDK Distribution ........................ SUCCESS [29.946s] > [INFO] RichFaces CDK Aggregator .......................... SUCCESS [0.244s] > [INFO] RichFaces UI Components Parent .................... SUCCESS [1.515s] > [INFO] RichFaces UI Components: Common API ............... SUCCESS [20.304s] > [INFO] RichFaces UI Components: Common UI ................ SUCCESS [1:07.241s] > [INFO] RichFaces UI Components: Common Aggregator ........ SUCCESS [0.417s] > [INFO] RichFaces UI Components: Core API ................. SUCCESS [10.942s] > [INFO] RichFaces UI Components: Core UI .................. SUCCESS [2:25.334s] > [INFO] RichFaces UI Components: Core Aggregator .......... SUCCESS [0.368s] > [INFO] RichFaces UI Components: Iteration API ............ SUCCESS [18.222s] > [INFO] RichFaces UI Components: Iteration UI ............. SUCCESS [3:02.748s] > [INFO] RichFaces UI Components: Iteration Aggregator ..... SUCCESS [0.401s] > [INFO] RichFaces UI Components: Miscellanous UI .......... SUCCESS [33.776s] > [INFO] RichFaces UI Components: Miscellanous Aggregator .. SUCCESS [0.366s] > [INFO] RichFaces UI Components: Output API ............... SUCCESS [14.140s] > [INFO] RichFaces UI Components: Output UI ................ SUCCESS [3:05.517s] > [INFO] RichFaces UI Components: Output Aggregator ........ SUCCESS [0.390s] > [INFO] RichFaces UI Components: Input API ................ SUCCESS [13.374s] > [INFO] RichFaces UI Components: Input UI ................. SUCCESS [4:40.374s] > [INFO] RichFaces UI Components: Input Aggregator ......... SUCCESS [0.371s] > [INFO] RichFaces UI Components: Drag-n-Drop API .......... SUCCESS [12.126s] > [INFO] RichFaces UI Components: Drag-n-Drop UI ........... SUCCESS [30.145s] > [INFO] RichFaces UI Components: Drag-n-Drop Aggregator ... SUCCESS [0.406s] > [INFO] RichFaces UI Components: Validator api ............ SUCCESS [15.710s] > [INFO] RichFaces UI Components: Validator ui ............. SUCCESS [2:46.216s] > [INFO] RichFaces UI Components: validator-aggregator ..... SUCCESS [0.372s] > [INFO] Richfaces UI Components API ....................... SUCCESS [23.604s] > [INFO] RichFaces UI Components Static Resources .......... SUCCESS [1:47.298s] > [INFO] RichFaces UI Components UI ........................ SUCCESS [2:01.812s] > [INFO] RichFaces UI Distribution ......................... SUCCESS [0.369s] > [INFO] RichFaces UI Components Aggregator ................ SUCCESS [0.269s] > [INFO] RichFaces Archetypes Simple Application ........... SUCCESS [7.277s] > [INFO] RichFaces Archetypes Component .................... SUCCESS [3.212s] > [INFO] RichFaces Archetypes Component Short .............. SUCCESS [1.981s] > [INFO] RichFaces Archetypes Components Aggregator ........ SUCCESS [2.562s] > [INFO] RichFaces Archetypes GAE Application .............. SUCCESS [2.730s] > [INFO] RichFaces Archetypes Aggregator ................... SUCCESS [0.264s] > [INFO] RichFaces Examples Parent ......................... SUCCESS [0.411s] > [INFO] RichFaces Examples Template ....................... SUCCESS [15.603s] > [INFO] RichFaces Examples Core ........................... SUCCESS [16.374s] > [INFO] RichFaces Examples Miscellanous ................... SUCCESS [12.221s] > [INFO] RichFaces Examples Outputs ........................ SUCCESS [14.603s] > [INFO] RichFaces Examples Inputs ......................... SUCCESS [19.791s] > [INFO] RichFaces Examples Repeater ....................... SUCCESS [26.964s] > [INFO] RichFaces Examples Iteration ...................... SUCCESS [30.285s] > [INFO] RichFaces Examples Push ........................... SUCCESS [18.215s] > [INFO] RichFaces Examples Validators ..................... SUCCESS [19.452s] > [INFO] RichFaces Examples DND ............................ SUCCESS [13.337s] > [INFO] RichFaces Examples Richfaces IRC Client Application SUCCESS [14.630s] > [INFO] RichFaces Examples Aggregator ..................... SUCCESS [0.241s] > [INFO] RichFaces Showcase ................................ FAILURE [12.109s] > [INFO] RichFaces Distribution Assembler .................. SKIPPED > [INFO] RichFaces Aggregator .............................. SKIPPED > [INFO] ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 41:12.509s > [INFO] Finished at: Fri Dec 09 06:42:33 EST 2011 > [INFO] Final Memory: 312M/708M > [INFO] ------------------------------------------------------------------------ > maven builder waiting > mavenExecutionResult exceptions not empty > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.3.1:compile (default-compile) on project richfaces-showcase: Compilation failure > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) > at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) > at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) > at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) > at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) > at org.jvnet.hudson.maven3.launcher.Maven3Launcher.main(Maven3Launcher.java:79) > 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.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:329) > at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:239) > at org.jvnet.hudson.maven3.agent.Maven3Main.launch(Maven3Main.java:146) > at hudson.maven.Maven3Builder.call(Maven3Builder.java:127) > at hudson.maven.Maven3Builder.call(Maven3Builder.java:74) > at hudson.remoting.UserRequest.perform(UserRequest.java:114) > at hudson.remoting.UserRequest.perform(UserRequest.java:48) > at hudson.remoting.Request$2.run(Request.java:270) > 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:660) > Caused by: org.apache.maven.plugin.CompilationFailureException: Compilation failure > at org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:656) > at org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:128) > at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) > ... 27 more > channel stopped > Email was triggered for: Failure > Sending email for trigger: Failure > ERROR: Ignore Problem expanding maven opts macros org.jenkinsci.plugins.tokenmacro.TokenMacro > Sending email to: richfaces-builds at lists.jboss.org > Finished: FAILURE > {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 Jan 5 14:57:09 2012 From: jira-events at lists.jboss.org (Jean ANDRE (Updated) (JIRA)) Date: Thu, 5 Jan 2012 14:57:09 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11855) error@malformedXML on inputText files - Ajax Validation on event change - RichFaces 4.1 Final In-Reply-To: <26805713.30230.1324582930232.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <153728527.43845.1325793429495.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean ANDRE updated RF-11855: ---------------------------- Workaround Description: If you use the tag f:ajax instead of tag a4j:ajax, it works much better, however, this way seems not working with calendar (needs more investigations on it). Workaround: Workaround Exists Description: We got a error at malformedXML message when we want to apply an ajax validation on imput text. The field is include inside a tab in mode "server" - What ever the mode, we getting the error. Tab content is built by including some xhtml. See attachment. {code} < event="change" bypassUpdates="true" execute="@this" render="@this" /> {code} was: We got a error at malformedXML message when we want to apply an ajax validation on imput text. The field is include inside a tab in mode "server" - What ever the mode, we getting the error. Tab content is built by including some xhtml. See attachment. {code} {code} Steps to Reproduce: Well, difficult to reproduce by a simple example - See attachment, that give you an idea of the page structure and complexity. (was: Well, difficult to reproduce as is - See attachment.) > error at malformedXML on inputText files - Ajax Validation on event change - RichFaces 4.1 Final > ---------------------------------------------------------------------------------------------- > > Key: RF-11855 > URL: https://issues.jboss.org/browse/RF-11855 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.1.0.Final > Environment: Websphere 8.0.0.1 - RAD 8.0.0.4 - JSF Mojorra 2.1.4 - Spring 3.0.6 Final - Hibernate Validator 4.2. - Java 6 > Reporter: Jean ANDRE > Labels: INPUT, MALFORMED, UI, XML, waiting_on_user > Attachments: createClient1.xhtml, CreateClientController1.java, error at malformedXML-ScreenShot-1.jpg, error at malformedXML.debug.txt, error at malformedXML.viewSource.html, index.xhtml > > > We got a error at malformedXML message when we want to apply an ajax validation on imput text. > The field is include inside a tab in mode "server" - What ever the mode, we getting the error. Tab content is built by including some xhtml. See attachment. > {code} > > xmlns:h="http://java.sun.com/jsf/html" > xmlns:f="http://java.sun.com/jsf/core" > xmlns:rich="http://richfaces.org/rich" > xmlns:c="http://java.sun.com/jsp/jstl/core" > xmlns:a4j="http://richfaces.org/a4j"> > > > > > > > > > < event="change" bypassUpdates="true" execute="@this" render="@this" /> > > > > > > > {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 Jan 5 14:59:09 2012 From: jira-events at lists.jboss.org (Jean ANDRE (Updated) (JIRA)) Date: Thu, 5 Jan 2012 14:59:09 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11855) error@malformedXML on inputText files - Ajax Validation on event change - RichFaces 4.1 Final In-Reply-To: <26805713.30230.1324582930232.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1144567512.43863.1325793549771.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean ANDRE updated RF-11855: ---------------------------- Workaround Description: If you use the tag *f:ajax* instead of tag *a4j:ajax*, it works much better, however, this way seems not working with calendar (needs more investigations on it). (was: If you use the tag f:ajax instead of tag a4j:ajax, it works much better, however, this way seems not working with calendar (needs more investigations on it).) Description: We got a error at malformedXML message when we want to apply an ajax validation on imput text. The field is include inside a tab in mode "server" - What ever the mode, we getting the error. Tab content is built by including some xhtml. See attachment. {code} {code} was: We got a error at malformedXML message when we want to apply an ajax validation on imput text. The field is include inside a tab in mode "server" - What ever the mode, we getting the error. Tab content is built by including some xhtml. See attachment. {code} < event="change" bypassUpdates="true" execute="@this" render="@this" /> {code} > error at malformedXML on inputText files - Ajax Validation on event change - RichFaces 4.1 Final > ---------------------------------------------------------------------------------------------- > > Key: RF-11855 > URL: https://issues.jboss.org/browse/RF-11855 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.1.0.Final > Environment: Websphere 8.0.0.1 - RAD 8.0.0.4 - JSF Mojorra 2.1.4 - Spring 3.0.6 Final - Hibernate Validator 4.2. - Java 6 > Reporter: Jean ANDRE > Labels: INPUT, MALFORMED, UI, XML, waiting_on_user > Attachments: createClient1.xhtml, CreateClientController1.java, error at malformedXML-ScreenShot-1.jpg, error at malformedXML.debug.txt, error at malformedXML.viewSource.html, index.xhtml > > > We got a error at malformedXML message when we want to apply an ajax validation on imput text. > The field is include inside a tab in mode "server" - What ever the mode, we getting the error. Tab content is built by including some xhtml. See attachment. > {code} > > xmlns:h="http://java.sun.com/jsf/html" > xmlns:f="http://java.sun.com/jsf/core" > xmlns:rich="http://richfaces.org/rich" > xmlns:c="http://java.sun.com/jsp/jstl/core" > xmlns:a4j="http://richfaces.org/a4j"> > > > > > > > > > > > > > > > > {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 Jan 5 16:36:12 2012 From: jira-events at lists.jboss.org (Jean ANDRE (Issue Comment Edited) (JIRA)) Date: Thu, 5 Jan 2012 16:36:12 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11764) Problems with packed resources In-Reply-To: <1531552132.56496.1322674962554.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <777785947.44082.1325799372656.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12650475#comment-12650475 ] Jean ANDRE edited comment on RF-11764 at 1/5/12 4:34 PM: --------------------------------------------------------- Well, do you prefer having a ear file to be deployed because unfortunately this is the best sample I can give you - It is a standalone application, no db access, no back-end, only pure GUI. The given file is a perfect example how a page can be complex by having multiple includes and nested tabs. Most of the bugs reported are related to resource and tabs can be reproduced easily by playing with the application. The complexity of the page is a part of the problem and making it more simple might not reproduce the bug. If you have any difficulty to run the application, let me know - AspectJ can be disable by removing aspectJ classes - AspectJ is solely used for logging purpose. Libraries needed are : - RichFaces 4.1.0 et dependency - hibernate-validator-4.2.0.Final.jar - org.springframework.asm-3.0.6.RELEASE.jar - org.springframework.beans-3.0.6.RELEASE.jar - org.springframework.context-3.0.6.RELEASE.jar - org.springframework.core-3.0.6.RELEASE.jar - org.springframework.expression-3.0.6.RELEASE.jar - org.springframework.web-3.0.6.RELEASE.jar - slf4j-api-1.6.1.jar - slf4j-log4j12-1.6.1.jar - JSF Mojorra 2.1.4 Please, take the time to setup the application and I will assist you to pinpoint the bugs for : - RF-11764 - RF-11763 - RF-11750 - RF-11730 - RF-10989 - RF-11694 - RF-11427 - RF-11054 - RF-11669 - RF-11855 Then... by setting the application, there is a lot to win as you will easily reproduce those bugs... was (Author: jorelia64): Well, do you prefer having a ear file to be deployed because unfortunately this is the best sample I can give you - It is a standalone application, no db access, no back-end, only pure GUI. The given file is a perfect example how a page can be complex by having multiple includes and nested tabs. Most of the bugs reported are related to resource and tabs can be reproduced easily by playing with the application. The complexity of the page is a part of the problem and making it more simple might not reproduce the bug. If you have any difficulty to run the application, let me know - AspectJ can be disable by removing aspectJ classes - AspectJ is solely used for logging purpose. Libraries needed are : - RichFaces 4.1.0 et dependency - hibernate-validator-4.2.0.Final.jar - org.springframework.asm-3.0.6.RELEASE.jar - org.springframework.beans-3.0.6.RELEASE.jar - org.springframework.context-3.0.6.RELEASE.jar - org.springframework.core-3.0.6.RELEASE.jar - org.springframework.expression-3.0.6.RELEASE.jar - org.springframework.web-3.0.6.RELEASE.jar - slf4j-api-1.6.1.jar - slf4j-log4j12-1.6.1.jar - JSF Mojorra 2.1.4 Please, take the time to setup the application and I will assist you to pinpoint the bugs for : - RF-11764 - RF-11763 - RF-11750 - RF-11730 - RF-10989 - RF-11694 - RF-11427 - RF-11054 - RF-11669 Then... by setting the application, there is a lot to win as you will easily reproduce those bugs... > Problems with packed resources > ------------------------------ > > Key: RF-11764 > URL: https://issues.jboss.org/browse/RF-11764 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.1.0.CR1 > Reporter: Jean ANDRE > Labels: material-sent > > *Follow up RF-11694.* > We tested the solution by updating the web.xml. We put following code : > {code} > > org.richfaces.resourceMapping.enabled > true > > > org.richfaces.resourceMapping.packedStages > All > > {code} > The workaround does not work well because it triggers many javacript erreur - User Interface seem to be frozen, hanged. > Here are the errors catch under firebug / Mozilla > {code} > jsf is not defined > [Stopper sur une erreur] }(jQuery,RichFaces,jsf));;(function(C,B,D){B.blankFunction=function(){}; > packed.js (ligne 3040) > RichFaces.ui is undefined > [Stopper sur une erreur] > {code} > My style left is applied but the header is one level lower and has rf-edt-hdr-c-cnt style which will always make it center -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 24 09:43:18 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Tue, 24 Jan 2012 09:43:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11588) HeaderClass is ignored on ExtendedDataTable column In-Reply-To: <1427004328.27237.1319584545776.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1208593971.19216.1327416198461.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-11588: ------------------------------- Fix Version/s: 4.2.0.CR1 (was: 4.Future) Priority: Trivial (was: Minor) Assignee: Brian Leathem > HeaderClass is ignored on ExtendedDataTable column > -------------------------------------------------- > > Key: RF-11588 > URL: https://issues.jboss.org/browse/RF-11588 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.1.0.Milestone3 > Reporter: Cody Lerum > Assignee: Brian Leathem > Priority: Trivial > Fix For: 4.2.0.CR1 > > > When a header class is defined on a rich:column inside an rich:extendedDataTable it is ignored > Assume > {code} > > Foo > > > {code} > What is rendered is > {code} > > {code} > My style left is applied but the header is one level lower and has rf-edt-hdr-c-cnt style which will always make it center -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 24 14:24:18 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Tue, 24 Jan 2012 14:24:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11588) HeaderClass is ignored on ExtendedDataTable column In-Reply-To: <1427004328.27237.1319584545776.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1162394222.19828.1327433058250.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12661516#comment-12661516 ] Brian Leathem commented on RF-11588: ------------------------------------ Looking into the code, it's convoluted and not as trivial to change as I would have expected. Would you find it acceptable to repeat the custom css class on the interior div? It would mean the css class would show up twice, which is unfortunate, but would result in your style being applied as expected. > HeaderClass is ignored on ExtendedDataTable column > -------------------------------------------------- > > Key: RF-11588 > URL: https://issues.jboss.org/browse/RF-11588 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.1.0.Milestone3 > Reporter: Cody Lerum > Assignee: Brian Leathem > Priority: Trivial > Fix For: 4.2.0.CR1 > > > When a header class is defined on a rich:column inside an rich:extendedDataTable it is ignored > Assume > {code} > > Foo > > > {code} > What is rendered is > {code} > > {code} > My style left is applied but the header is one level lower and has rf-edt-hdr-c-cnt style which will always make it center -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 24 15:12:18 2012 From: jira-events at lists.jboss.org (Cody Lerum (JIRA)) Date: Tue, 24 Jan 2012 15:12:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11588) HeaderClass is ignored on ExtendedDataTable column In-Reply-To: <1427004328.27237.1319584545776.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1676737296.19902.1327435938290.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12661527#comment-12661527 ] Cody Lerum commented on RF-11588: --------------------------------- That works for me with maybe a long term JIRA to look at improving impl > HeaderClass is ignored on ExtendedDataTable column > -------------------------------------------------- > > Key: RF-11588 > URL: https://issues.jboss.org/browse/RF-11588 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.1.0.Milestone3 > Reporter: Cody Lerum > Assignee: Brian Leathem > Priority: Trivial > Fix For: 4.2.0.CR1 > > > When a header class is defined on a rich:column inside an rich:extendedDataTable it is ignored > Assume > {code} > > Foo > > > {code} > What is rendered is > {code} > > {code} > My style left is applied but the header is one level lower and has rf-edt-hdr-c-cnt style which will always make it center -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 24 15:43:18 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Tue, 24 Jan 2012 15:43:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11850) RF 4.1.0.Final: Problem using columnResize with more than one extendedDataTable on the same page. In-Reply-To: <1719236551.29235.1324550769802.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1508661572.19931.1327437798554.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-11850. -------------------------------- Resolution: Done Initialized the newWidths property of the EDT js initializer. > RF 4.1.0.Final: Problem using columnResize with more than one extendedDataTable on the same page. > ------------------------------------------------------------------------------------------------- > > Key: RF-11850 > URL: https://issues.jboss.org/browse/RF-11850 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.1.0.Final > Environment: Windows 7 x64 or arch linux x86 > JBoss 7.0.1 Final or Glassfish 3.1 > Reporter: Christian Peter > Assignee: Brian Leathem > Priority: Minor > Fix For: 4.2.0.CR1 > > > Hello, > I've encountered some problems using richfaces extendedDataTables in RichFace 4.1.0.Final > Here is the facelet: > {code:title=facelet} > > > > Header7 > #{item.name} > > > > Header8 > #{item.uuid} > > > > Header9 > #{item.uuid} > > > > Header10 > #{item.uuid} > > > > > > > > > > Header7 > #{item.name} > > > > Header8 > #{item.uuid} > > > Header9 > #{item.uuid} > > > > Header10 > #{item.uuid} > > > > > > {code} > > Resizing the columns on the first table works perfectly, but if someone tries to resize the second tables' columns as well, I've got NullPointer exceptions like: > {code:title=stacktrace} > java.lang.NullPointerException > at org.richfaces.renderkit.SortingFilteringRowsRenderer.updateAttribute(SortingFilteringRowsRenderer.java:135) [richfaces-components-ui-4.1.0.Final.jar: > at org.richfaces.renderkit.ExtendedDataTableRenderer.updateWidthOfColumns(ExtendedDataTableRenderer.java:825) [richfaces-components-ui-4.1.0.Final.jar:] > at org.richfaces.renderkit.ExtendedDataTableRenderer.doDecode(ExtendedDataTableRenderer.java:808) [richfaces-components-ui-4.1.0.Final.jar:] > at org.richfaces.renderkit.RendererBase.decode(RendererBase.java:80) [richfaces-components-ui-4.1.0.Final.jar:] > at javax.faces.component.UIComponentBase.decode(UIComponentBase.java:787) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at org.richfaces.component.UIDataAdaptor.processDecodes(UIDataAdaptor.java:819) [richfaces-components-ui-4.1.0.Final.jar:] > at org.richfaces.context.PartialViewExecuteVisitCallback.visit(PartialViewExecuteVisitCallback.java:53) [richfaces-core-impl-4.1.0.Final.jar:] > at org.richfaces.context.BaseExtendedVisitContext.invokeVisitCallback(BaseExtendedVisitContext.java:321) [richfaces-core-impl-4.1.0.Final.jar:] > at org.richfaces.component.UIDataAdaptor.visitTree(UIDataAdaptor.java:1319) [richfaces-components-ui-4.1.0.Final.jar:] > at javax.faces.component.UIComponent.visitTree(UIComponent.java:1600) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at javax.faces.component.UIForm.visitTree(UIForm.java:344) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at javax.faces.component.UIComponent.visitTree(UIComponent.java:1600) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at javax.faces.component.UIComponent.visitTree(UIComponent.java:1600) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at org.richfaces.context.ExtendedPartialViewContextImpl.executeComponents(ExtendedPartialViewContextImpl.java:237) [richfaces-core-impl-4.1.0.Final.jar: > at org.richfaces.context.ExtendedPartialViewContextImpl.processPartialExecutePhase(ExtendedPartialViewContextImpl.java:217) [richfaces-core-impl-4.1.0.F > at org.richfaces.context.ExtendedPartialViewContextImpl.processPartial(ExtendedPartialViewContextImpl.java:196) [richfaces-core-impl-4.1.0.Final.jar:] > at javax.faces.component.UIViewRoot.processDecodes(UIViewRoot.java:931) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at com.sun.faces.lifecycle.ApplyRequestValuesPhase.execute(ApplyRequestValuesPhase.java:78) [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 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] > {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 Jan 24 16:37:18 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Tue, 24 Jan 2012 16:37:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11860) Data table: The scope attribute on the td element is obsolete In-Reply-To: <207304981.36098.1325591409412.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1642129572.20047.1327441038316.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-11860. -------------------------------- Resolution: Done It seems __ renders with __ renders with __ to render with _ > > > > > > > > > {code} > Attribute *scope* on element td is obsolete in HTML5 and should be set on th element instead. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 24 17:04:18 2012 From: jira-events at lists.jboss.org (Tom Giberius (JIRA)) Date: Tue, 24 Jan 2012 17:04:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11916) extendedDataTable partial update => extend the functionality with INSERT and DELETE row where scroll position does not go up. Message-ID: <1922325197.20094.1327442658256.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Tom Giberius created RF-11916: --------------------------------- Summary: extendedDataTable partial update => extend the functionality with INSERT and DELETE row where scroll position does not go up. Key: RF-11916 URL: https://issues.jboss.org/browse/RF-11916 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Tom Giberius Situation: 1) extendDataTable with a verticall ScrollBar 2) Insert or delete record by insert/delete in myBean and by a re-render of the table. 3) The re-render causes a full rebuild of the table in the DOM and the effect is that the scrollbar goes up to the beginning.In fact this makes a scrollable extendedDataTable not useful for inserting/deleting records. Partial Table Render for extendedDataTable is available in RF 4.1 with a construction like: render="myTable at rows(myBean.listOfUpdateRows):myColumn" This works fine for already available rows and indeed it is an UPDATE. Also @body, @header and @footer are available for partial table update. I would like to hava a kind of partitial table INSERT and UPDATE where not the whole table is "re-draw" by only the record(s) are INSERTED or DELETED and where the scroll position for the user visually stays the same. It could look like: render="myTable at insert(myBean.Row) render="myTable at delete(myBean.RowKey) If you have questions I will gladly elaborate on 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 Tue Jan 24 17:06:18 2012 From: jira-events at lists.jboss.org (Tom Giberius (JIRA)) Date: Tue, 24 Jan 2012 17:06:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11916) extendedDataTable partial update => extend the functionality with INSERT and DELETE row where scroll position does not go up. In-Reply-To: <1922325197.20094.1327442658256.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1025803995.20105.1327442778763.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Giberius updated RF-11916: ------------------------------ Description: Situation: 1) extendDataTable with a verticall ScrollBar 2) Insert or delete record by insert/delete in myBean and by a re-render of the table. 3) The re-render causes a full rebuild of the table in the DOM and the effect is that the scrollbar goes up to the beginning.In fact this makes a scrollable extendedDataTable not useful for inserting/deleting records. Partial Table Render for extendedDataTable is available in RF 4.1 with a construction like: render="myTable at rows(myBean.listOfUpdateRows):myColumn" This works fine for already available rows and indeed it is an UPDATE. Also @body, @header and @footer are available for partial table update. I would like to have a kind of partitial table INSERT and UPDATE where not the whole table is "re-draw", only the record(s) are INSERTED or DELETED and where the scroll position for the user visually stays the same. Maintaining the scroll position is the reason for this request, a user should be able to insert/delete rows any where in a scrollalbe table larger then the table height. It could look like: render="myTable at insert(myBean.Row) render="myTable at delete(myBean.RowKey) If you have questions I will gladly elaborate on above. was: Situation: 1) extendDataTable with a verticall ScrollBar 2) Insert or delete record by insert/delete in myBean and by a re-render of the table. 3) The re-render causes a full rebuild of the table in the DOM and the effect is that the scrollbar goes up to the beginning.In fact this makes a scrollable extendedDataTable not useful for inserting/deleting records. Partial Table Render for extendedDataTable is available in RF 4.1 with a construction like: render="myTable at rows(myBean.listOfUpdateRows):myColumn" This works fine for already available rows and indeed it is an UPDATE. Also @body, @header and @footer are available for partial table update. I would like to hava a kind of partitial table INSERT and UPDATE where not the whole table is "re-draw" by only the record(s) are INSERTED or DELETED and where the scroll position for the user visually stays the same. It could look like: render="myTable at insert(myBean.Row) render="myTable at delete(myBean.RowKey) If you have questions I will gladly elaborate on above. > extendedDataTable partial update => extend the functionality with INSERT and DELETE row where scroll position does not go up. > ----------------------------------------------------------------------------------------------------------------------------- > > Key: RF-11916 > URL: https://issues.jboss.org/browse/RF-11916 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Tom Giberius > > Situation: > 1) extendDataTable with a verticall ScrollBar > 2) Insert or delete record by insert/delete in myBean and by a re-render of the table. > 3) The re-render causes a full rebuild of the table in the DOM and the effect is that the scrollbar goes up to the beginning.In fact this makes a scrollable extendedDataTable not useful for inserting/deleting records. > Partial Table Render for extendedDataTable is available in RF 4.1 with a construction like: > render="myTable at rows(myBean.listOfUpdateRows):myColumn" > This works fine for already available rows and indeed it is an UPDATE. > Also @body, @header and @footer are available for partial table update. > I would like to have a kind of partitial table INSERT and UPDATE where not the whole table is "re-draw", only the record(s) are INSERTED or DELETED and where the scroll position for the user visually stays the same. Maintaining the scroll position is the reason for this request, a user should be able to insert/delete rows any where in a scrollalbe table larger then the table height. > It could look like: > render="myTable at insert(myBean.Row) > render="myTable at delete(myBean.RowKey) > If you have questions I will gladly elaborate on 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 Tue Jan 24 17:08:18 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Tue, 24 Jan 2012 17:08:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11765) Datatable footer cell doesn't use all columns (wrong colspan generated) In-Reply-To: <249178125.59139.1322705200743.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1554635782.20108.1327442898718.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-11765. -------------------------------- Fix Version/s: (was: 4.2.0.CR1) Resolution: Won't Fix On analysing the provided code sample I've concluded that the current behaviour is correct. Consider the state while trying to count the number of columns while rendering the footer: While rendering the footer, no row is active, hence rowNbr cannot return 0 (that would imply the 0th row is active). It counts the number of rendered columns to determine what to use for the colspan - if a column is not rendered, it should not be included in the count. Hence the appropriate solution is indeed to alter the render logic of the column, so that it is counted while rendering the footer. > Datatable footer cell doesn't use all columns (wrong colspan generated) > ----------------------------------------------------------------------- > > Key: RF-11765 > URL: https://issues.jboss.org/browse/RF-11765 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.1.0.CR1 > Reporter: Karsten Wutzke > Assignee: Brian Leathem > Labels: colspan, dataTable, footer > > When specifying a datatable's header with rich:columnGroup and a rich:column in the tbody that has rendered="#{rowKeyNbr eq 0}" the wrong colspan for the table footer cell is generated. > For more details, code, and images please see the forum thread: > http://community.jboss.org/message/639211 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 24 17:20:18 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Tue, 24 Jan 2012 17:20:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11901) Review the "new" label on showcase compnents In-Reply-To: <1378292109.9479.1326930259921.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <596357424.20135.1327443618199.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-11901. -------------------------------- Resolution: Done > Review the "new" label on showcase compnents > -------------------------------------------- > > Key: RF-11901 > URL: https://issues.jboss.org/browse/RF-11901 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: showcase > Reporter: Brian Leathem > Assignee: Brian Leathem > Priority: Trivial > Fix For: 4.2.0.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 Tue Jan 24 17:24:18 2012 From: jira-events at lists.jboss.org (Tom Giberius (JIRA)) Date: Tue, 24 Jan 2012 17:24:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11916) extendedDataTable partial update => extend the functionality with INSERT and DELETE row where scroll position does not go up. In-Reply-To: <1922325197.20094.1327442658256.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <673533044.20140.1327443858384.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Giberius updated RF-11916: ------------------------------ Description: Situation: 1) extendDataTable with a verticall ScrollBar 2) Insert or delete record by insert/delete in myBean and by a re-render of the table. 3) The re-render causes a full rebuild of the table in the DOM and the effect is that the scrollbar goes up to the beginning.In fact this makes a scrollable extendedDataTable not useful for inserting/deleting records. Partial Table Render for extendedDataTable is available in RF 4.1 with a construction like: render="myTable at rows(myBean.listOfUpdateRows):myColumn" This works fine for already available rows and indeed it is an UPDATE. Also @body, @header and @footer are available for partial table update. I would like to have a kind of partitial table INSERT and UPDATE where not the whole table is "re-draw", only the record(s) are INSERTED or DELETED and where the scroll position for the user visually stays the same. Maintaining the scroll position is the reason for this request, a user should be able to insert/delete rows any where in a scrollalbe table larger then the table height. It could look like: render="myTable at insert(myBean.Row) render="myTable at delete(myBean.RowKey) Also take care of the "selected" row: * For deletes the RowKey is passed, so no problem * For inserts one could consider: - Pass RowKey as parameter and insert before/after the given RowKey - Use the current "selected record" E.g.current selected record: * No record - then insert in first position * A record selected - insert after selected records The inserted record is anyway the new "selected row" Also with a delete you should consider what the "selected record" should be if a selected record is deleted. I use the selected record (single selection mode) in insert/delete. For that I made some changes to the JavaScript of the extendenDataTable. If you have questions I will gladly elaborate on above. was: Situation: 1) extendDataTable with a verticall ScrollBar 2) Insert or delete record by insert/delete in myBean and by a re-render of the table. 3) The re-render causes a full rebuild of the table in the DOM and the effect is that the scrollbar goes up to the beginning.In fact this makes a scrollable extendedDataTable not useful for inserting/deleting records. Partial Table Render for extendedDataTable is available in RF 4.1 with a construction like: render="myTable at rows(myBean.listOfUpdateRows):myColumn" This works fine for already available rows and indeed it is an UPDATE. Also @body, @header and @footer are available for partial table update. I would like to have a kind of partitial table INSERT and UPDATE where not the whole table is "re-draw", only the record(s) are INSERTED or DELETED and where the scroll position for the user visually stays the same. Maintaining the scroll position is the reason for this request, a user should be able to insert/delete rows any where in a scrollalbe table larger then the table height. It could look like: render="myTable at insert(myBean.Row) render="myTable at delete(myBean.RowKey) If you have questions I will gladly elaborate on above. > extendedDataTable partial update => extend the functionality with INSERT and DELETE row where scroll position does not go up. > ----------------------------------------------------------------------------------------------------------------------------- > > Key: RF-11916 > URL: https://issues.jboss.org/browse/RF-11916 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Tom Giberius > > Situation: > 1) extendDataTable with a verticall ScrollBar > 2) Insert or delete record by insert/delete in myBean and by a re-render of the table. > 3) The re-render causes a full rebuild of the table in the DOM and the effect is that the scrollbar goes up to the beginning.In fact this makes a scrollable extendedDataTable not useful for inserting/deleting records. > Partial Table Render for extendedDataTable is available in RF 4.1 with a construction like: > render="myTable at rows(myBean.listOfUpdateRows):myColumn" > This works fine for already available rows and indeed it is an UPDATE. > Also @body, @header and @footer are available for partial table update. > I would like to have a kind of partitial table INSERT and UPDATE where not the whole table is "re-draw", only the record(s) are INSERTED or DELETED and where the scroll position for the user visually stays the same. Maintaining the scroll position is the reason for this request, a user should be able to insert/delete rows any where in a scrollalbe table larger then the table height. > It could look like: > render="myTable at insert(myBean.Row) > render="myTable at delete(myBean.RowKey) > Also take care of the "selected" row: > * For deletes the RowKey is passed, so no problem > * For inserts one could consider: > - Pass RowKey as parameter and insert before/after the given RowKey > - Use the current "selected record" > E.g.current selected record: > * No record - then insert in first position > * A record selected - insert after selected records > The inserted record is anyway the new "selected row" > Also with a delete you should consider what the "selected record" should be if a selected record is deleted. > I use the selected record (single selection mode) in insert/delete. For that I made some changes to the JavaScript of the extendenDataTable. > If you have questions I will gladly elaborate on 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 Tue Jan 24 18:06:19 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Tue, 24 Jan 2012 18:06:19 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11917) Multiselect in pickList broken Message-ID: <225210152.20244.1327446379363.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Brian Leathem created RF-11917: ---------------------------------- Summary: Multiselect in pickList broken Key: RF-11917 URL: https://issues.jboss.org/browse/RF-11917 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-selects Reporter: Brian Leathem Assignee: Brian Leathem Priority: Critical Fix For: 4.2.0.CR1 Holding down the ctrl key while selecting values in the pickList no longer slects multiple values. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 24 18:06:19 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Tue, 24 Jan 2012 18:06:19 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11917) Multiselect in pickList broken In-Reply-To: <225210152.20244.1327446379363.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <813271807.20245.1327446379393.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12661576#comment-12661576 ] Brian Leathem commented on RF-11917: ------------------------------------ The event.metakey semantics were changed in jQuery 1.7 (see: http://bugs.jquery.com/ticket/10666). > Multiselect in pickList broken > ------------------------------ > > Key: RF-11917 > URL: https://issues.jboss.org/browse/RF-11917 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects > Reporter: Brian Leathem > Assignee: Brian Leathem > Priority: Critical > Fix For: 4.2.0.CR1 > > > Holding down the ctrl key while selecting values in the pickList no longer slects multiple values. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 24 18:12:18 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Tue, 24 Jan 2012 18:12:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11917) Multiselect in pickList broken In-Reply-To: <225210152.20244.1327446379363.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <706992412.20246.1327446738207.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-11917. -------------------------------- Resolution: Done Replaced e.metaKey usage with e.metaKey || e.ctrlKey > Multiselect in pickList broken > ------------------------------ > > Key: RF-11917 > URL: https://issues.jboss.org/browse/RF-11917 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects > Reporter: Brian Leathem > Assignee: Brian Leathem > Priority: Critical > Fix For: 4.2.0.CR1 > > > Holding down the ctrl key while selecting values in the pickList no longer slects multiple values. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 24 18:41:18 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Tue, 24 Jan 2012 18:41:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11834) [RF4.1.final] rich:picklist don't support @RequestScope In-Reply-To: <823611390.23103.1324374549401.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <904412264.20345.1327448478766.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-11834. -------------------------------- Fix Version/s: (was: 4.2.0.CR1) Resolution: Cannot Reproduce Bug Works for me, see the pickList dev-example: https://github.com/richfaces/dev-examples/blob/develop/input-demo/src/main/webapp/examples/pickList.xhtml Note: you must implement the equals method for the model object used with the pickList. > [RF4.1.final] rich:picklist don't support @RequestScope > ------------------------------------------------------- > > Key: RF-11834 > URL: https://issues.jboss.org/browse/RF-11834 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 4.1.0.Final > Environment: JBoss 7 / RF4.1.final jdk 1.6_u27 > Reporter: Adrien Adrien > Assignee: Brian Leathem > Labels: picklist, scope > > picklist don't works if backbean is @requestScope. > (it worked in RF 3.3.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 Jan 24 18:45:18 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Tue, 24 Jan 2012 18:45:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11657) Better integration with JBossAS 7.1 In-Reply-To: <1860495351.67654.1320759705458.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1649398193.20356.1327448718881.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-11657. -------------------------------- Resolution: Done Added com.google.com to the manifest.mf Dependencies property > Better integration with JBossAS 7.1 > ----------------------------------- > > Key: RF-11657 > URL: https://issues.jboss.org/browse/RF-11657 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build/distribution, compatibility > Affects Versions: 4.1.0.Milestone4 > Reporter: Juergen Zimmermann > Assignee: Brian Leathem > Priority: Trivial > Fix For: 4.2.0.CR1 > > > JBossAS 7.1 contains Google Guava 10.0.x (in addition to sac-1.3.jar and cssparser-0.9.5.jar). Guava can be reused in RichFaces instead of doubling it in WEB-INF/lib. The solution is pretty simple: > In richfaces-core-impl-VERSION.jar the file META-INF/MANIFEST.MF already contains the line "Dependencies: ...". This line has to be extended by just ",com.google.guava" as follows: > Dependencies: org.w3c.css.sac,net.sourceforge.cssparser,com.google.guava > That's all and from now on RichFaces doesn't require the distribution of Google Guava in WEB-INF/lib when the platform is JBossAS 7.1. Please see also https://issues.jboss.org/browse/AS7-1809. > Be aware that there is no blank after the comma between net.sourceforge.cssparser and com.google.guava. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 24 18:49:18 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Tue, 24 Jan 2012 18:49:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11918) Create a showcase profile for JBoss AS 7.1 Message-ID: <718645631.20368.1327448958455.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Brian Leathem created RF-11918: ---------------------------------- Summary: Create a showcase profile for JBoss AS 7.1 Key: RF-11918 URL: https://issues.jboss.org/browse/RF-11918 Project: RichFaces Issue Type: Task Security Level: Public (Everyone can see) Components: showcase Reporter: Brian Leathem Fix For: 4.2.0.CR1 With RF-11657, the deployment bundle for JBoss AS 7.1 should have the google guava library excluded. Create a new debployment bundle for the showcase, excluding the google guava library. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 25 00:30:18 2012 From: jira-events at lists.jboss.org (Friedhelm Kuehn (JIRA)) Date: Wed, 25 Jan 2012 00:30:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11814) a4j:commandLink in tabPanel disabled if switchtype = ajax In-Reply-To: <796306910.9115.1323859989475.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <334210394.20721.1327469418493.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12661634#comment-12661634 ] Friedhelm Kuehn commented on RF-11814: -------------------------------------- OK for me. Thanks. > a4j:commandLink in tabPanel disabled if switchtype = ajax > --------------------------------------------------------- > > Key: RF-11814 > URL: https://issues.jboss.org/browse/RF-11814 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core, component-panels-layout-themes > Affects Versions: 4.1.0.CR2 > Environment: Win 7 64 Bit, Tomcat 7.0.23, Mojarra 2.1.3 > Reporter: Friedhelm Kuehn > Assignee: Brian Leathem > > In the following constellation (=extract from real page) the a4j:commandlink action method > is correctly triggered on clicking when tabPanels switchType = "client" but not when switchType = "ajax" > {code} > > > > > ..... > > > > > > > Logging out, please wait ! > > > {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 Jan 25 00:40:18 2012 From: jira-events at lists.jboss.org (Friedhelm Kuehn (JIRA)) Date: Wed, 25 Jan 2012 00:40:18 -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: <148935831.20748.1327470018404.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 updated RF-11884: --------------------------------- Attachment: Richfaces_4.1_Problems_Konfiguration.pdf Richfaces_4.1_Problems.pdf > 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 > Labels: waiting_on_user > Attachments: Richfaces_4.1_Problems.pdf, Richfaces_4.1_Problems_Konfiguration.pdf > > > 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 Jan 25 00:40:18 2012 From: jira-events at lists.jboss.org (Friedhelm Kuehn (JIRA)) Date: Wed, 25 Jan 2012 00:40:18 -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: <808717311.20751.1327470018639.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=12661640#comment-12661640 ] Friedhelm Kuehn commented on RF-11884: -------------------------------------- Yes I have tried compatibility mode - but since this problems are also present in IE8, I was not surprised that this did not change anything - ? I attach two PDF-documents with - (For first two problems) detailed documentation - Detailed documentation of my software configuration and Problem Analysis with hardcopies of everything I think could be helpful. Since - even with my browsers - the Richfaces Showcase from your server does work, I think there might be something wrong in the Tomcat-Area. I checked this multiple times and did not find anything. So I inserted hardcopy of the Tomcat configuration for you also. I would like to check the exact configuration of your ShowCase-Server to see if it makes a difference. - Can you please give it to me ? Thanks for your help. > 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 > Labels: waiting_on_user > Attachments: Richfaces_4.1_Problems.pdf, Richfaces_4.1_Problems_Konfiguration.pdf > > > 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 Jan 25 04:21:20 2012 From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA)) Date: Wed, 25 Jan 2012 04:21:20 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11875) rich:extendedDataTable in ajax loading mode, crashes when dataset length changes between requests In-Reply-To: <1944546618.3014.1326375801528.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <388823878.21155.1327483280301.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavol Pitonak reassigned RF-11875: ---------------------------------- Assignee: Jan Papousek (was: Pavol Pitonak) > rich:extendedDataTable in ajax loading mode, crashes when dataset length changes between requests > ------------------------------------------------------------------------------------------------- > > Key: RF-11875 > URL: https://issues.jboss.org/browse/RF-11875 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-ScrollableDataTable > Affects Versions: 4.1.0.Final > Environment: JSF-RI 2.0, Tomcat 6.0.29 > Reporter: Dmitry Volkov > Assignee: Jan Papousek > > rich:extendedDataTable in ajax loading mode(clientRows=".."), crashes when dataset length changes between requests. > It makes ajax loading mode unusable for database paging. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 25 04:25:19 2012 From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA)) Date: Wed, 25 Jan 2012 04:25:19 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11874) rich:extendedDataTable keyboard navigation fails in IE8 In-Reply-To: <1410319121.2645.1326369141473.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1056494046.21172.1327483519880.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavol Pitonak reassigned RF-11874: ---------------------------------- Assignee: J?n Jamrich (was: Pavol Pitonak) > rich:extendedDataTable keyboard navigation fails in IE8 > ------------------------------------------------------- > > Key: RF-11874 > URL: https://issues.jboss.org/browse/RF-11874 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-ScrollableDataTable > Affects Versions: 4.1.0.Final > Environment: JSF-RI 2 > Internet Explorer version 8.0.7601.17514 > Reporter: Dmitry Volkov > Assignee: J?n Jamrich > > Continous keyboard navigation fails in IE8 when ajax loading(clientRows="..") used. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 25 04:25:20 2012 From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA)) Date: Wed, 25 Jan 2012 04:25:20 -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: <1814239631.21176.1327483520524.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 ] Pavol Pitonak reassigned RF-11801: ---------------------------------- Assignee: Jan Papousek (was: Pavol Pitonak) > 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 Jan 25 05:20:18 2012 From: jira-events at lists.jboss.org (Juraj Huska (JIRA)) Date: Wed, 25 Jan 2012 05:20:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11919) showcase - names of some samples do not follow camel case naming convention Message-ID: <1840945137.21442.1327486818320.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Juraj Huska created RF-11919: -------------------------------- Summary: showcase - names of some samples do not follow camel case naming convention Key: RF-11919 URL: https://issues.jboss.org/browse/RF-11919 Project: RichFaces Issue Type: Enhancement Security Level: Public (Everyone can see) Reporter: Juraj Huska There are some samples in showcase which do not follow camel case naming convention. First of all it is inconsistent with other sample names and secondly it makes some problems with showcase tests, since I am using method for loading the appropriate page according to the test class name, which should be obviously named using camel case. Can you please rename following samples ? component demo - sample ######################## a4j:status - viewusage, referencedusage a4j:outputPanel - Auto update for h:messages 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 Jan 25 05:40:18 2012 From: jira-events at lists.jboss.org (SBS JIRA Integration (JIRA)) Date: Wed, 25 Jan 2012 05:40:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11916) extendedDataTable partial update => extend the functionality with INSERT and DELETE row where scroll position does not go up. In-Reply-To: <1922325197.20094.1327442658256.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1817772789.21471.1327488018350.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] SBS JIRA Integration updated RF-11916: -------------------------------------- Forum Reference: https://community.jboss.org/message/516078#516078 > extendedDataTable partial update => extend the functionality with INSERT and DELETE row where scroll position does not go up. > ----------------------------------------------------------------------------------------------------------------------------- > > Key: RF-11916 > URL: https://issues.jboss.org/browse/RF-11916 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Tom Giberius > > Situation: > 1) extendDataTable with a verticall ScrollBar > 2) Insert or delete record by insert/delete in myBean and by a re-render of the table. > 3) The re-render causes a full rebuild of the table in the DOM and the effect is that the scrollbar goes up to the beginning.In fact this makes a scrollable extendedDataTable not useful for inserting/deleting records. > Partial Table Render for extendedDataTable is available in RF 4.1 with a construction like: > render="myTable at rows(myBean.listOfUpdateRows):myColumn" > This works fine for already available rows and indeed it is an UPDATE. > Also @body, @header and @footer are available for partial table update. > I would like to have a kind of partitial table INSERT and UPDATE where not the whole table is "re-draw", only the record(s) are INSERTED or DELETED and where the scroll position for the user visually stays the same. Maintaining the scroll position is the reason for this request, a user should be able to insert/delete rows any where in a scrollalbe table larger then the table height. > It could look like: > render="myTable at insert(myBean.Row) > render="myTable at delete(myBean.RowKey) > Also take care of the "selected" row: > * For deletes the RowKey is passed, so no problem > * For inserts one could consider: > - Pass RowKey as parameter and insert before/after the given RowKey > - Use the current "selected record" > E.g.current selected record: > * No record - then insert in first position > * A record selected - insert after selected records > The inserted record is anyway the new "selected row" > Also with a delete you should consider what the "selected record" should be if a selected record is deleted. > I use the selected record (single selection mode) in insert/delete. For that I made some changes to the JavaScript of the extendenDataTable. > If you have questions I will gladly elaborate on 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 Jan 25 07:13:50 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 25 Jan 2012 07:13:50 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11891) Simple bug in org.richfaces.resource.Xcss2EcssConverter In-Reply-To: <815303006.6467.1326841279163.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <134488457.175.1327493630344.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12661825#comment-12661825 ] Luk?? Fry? commented on RF-11891: --------------------------------- Xcss2EcssConverter is not used across project, it's obvious the accidental change was used for debugging purposes. The first command line argument ({{args[1]}}) will be taken as the filename. > Simple bug in org.richfaces.resource.Xcss2EcssConverter > ------------------------------------------------------- > > Key: RF-11891 > URL: https://issues.jboss.org/browse/RF-11891 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 4.1.0.Final > Environment: Any > Reporter: Dmytro Batishchev > Assignee: Luk?? Fry? > Priority: Trivial > Fix For: 4.2.0.CR1 > > > Simple bug in org.richfaces.resource.Xcss2EcssConverter classfile in main class, please, comment out or delete next line: > {quote} > _String string = "E:/projs/richafces4/framework/trunk/impl/src/test/java/org/ajax4jsf/cache/extended.xcss"_ > {quote} > PS: Sorry for my English. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 25 07:17:50 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 25 Jan 2012 07:17:50 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11891) Simple bug in org.richfaces.resource.Xcss2EcssConverter In-Reply-To: <815303006.6467.1326841279163.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1043488941.196.1327493870566.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12661825#comment-12661825 ] Luk?? Fry? edited comment on RF-11891 at 1/25/12 7:16 AM: ---------------------------------------------------------- Xcss2EcssConverter is not used across project, it's obvious the accidental change was used for debugging purposes. The first command line argument ({{args[0]}}) will be taken as the filename. was (Author: lfryc): Xcss2EcssConverter is not used across project, it's obvious the accidental change was used for debugging purposes. The first command line argument ({{args[1]}}) will be taken as the filename. > Simple bug in org.richfaces.resource.Xcss2EcssConverter > ------------------------------------------------------- > > Key: RF-11891 > URL: https://issues.jboss.org/browse/RF-11891 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 4.1.0.Final > Environment: Any > Reporter: Dmytro Batishchev > Assignee: Luk?? Fry? > Priority: Trivial > Fix For: 4.2.0.CR1 > > > Simple bug in org.richfaces.resource.Xcss2EcssConverter classfile in main class, please, comment out or delete next line: > {quote} > _String string = "E:/projs/richafces4/framework/trunk/impl/src/test/java/org/ajax4jsf/cache/extended.xcss"_ > {quote} > PS: Sorry for my English. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 25 07:20:48 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 25 Jan 2012 07:20:48 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11891) Simple bug in org.richfaces.resource.Xcss2EcssConverter In-Reply-To: <815303006.6467.1326841279163.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <798317651.200.1327494048407.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved RF-11891. ----------------------------- Resolution: Done > Simple bug in org.richfaces.resource.Xcss2EcssConverter > ------------------------------------------------------- > > Key: RF-11891 > URL: https://issues.jboss.org/browse/RF-11891 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 4.1.0.Final > Environment: Any > Reporter: Dmytro Batishchev > Assignee: Luk?? Fry? > Priority: Trivial > Fix For: 4.2.0.CR1 > > > Simple bug in org.richfaces.resource.Xcss2EcssConverter classfile in main class, please, comment out or delete next line: > {quote} > _String string = "E:/projs/richafces4/framework/trunk/impl/src/test/java/org/ajax4jsf/cache/extended.xcss"_ > {quote} > PS: Sorry for my English. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 25 07:59:48 2012 From: jira-events at lists.jboss.org (Jan Papousek (JIRA)) Date: Wed, 25 Jan 2012 07:59:48 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11875) rich:extendedDataTable in ajax loading mode, crashes when dataset length changes between requests In-Reply-To: <1944546618.3014.1326375801528.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <181702573.420.1327496388479.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Papousek updated RF-11875: ------------------------------ Attachment: richfaces-showcase-jbas7.war > rich:extendedDataTable in ajax loading mode, crashes when dataset length changes between requests > ------------------------------------------------------------------------------------------------- > > Key: RF-11875 > URL: https://issues.jboss.org/browse/RF-11875 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-ScrollableDataTable > Affects Versions: 4.1.0.Final > Environment: JSF-RI 2.0, Tomcat 6.0.29 > Reporter: Dmitry Volkov > Assignee: Jan Papousek > Attachments: richfaces-showcase-jbas7.war > > > rich:extendedDataTable in ajax loading mode(clientRows=".."), crashes when dataset length changes between requests. > It makes ajax loading mode unusable for database paging. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 25 08:05:48 2012 From: jira-events at lists.jboss.org (Jan Papousek (JIRA)) Date: Wed, 25 Jan 2012 08:05:48 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11875) rich:extendedDataTable in ajax loading mode, crashes when dataset length changes between requests In-Reply-To: <1944546618.3014.1326375801528.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1580432456.455.1327496748599.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Papousek updated RF-11875: ------------------------------ Steps to Reproduce: I have used "/richfaces/component-sample.jsf?demo=extendedDataTable" page in RF Showcase to reproduce the problem. 1. Add the following code in "simpleTable-sample.xhtml" in h:form tag: {code:xml} {code} 2.Open this page "/richfaces/component-sample.jsf?demo=extendedDataTable" in browser. 3.Check "Turn ajax loading on/off" checkbox. 4.Click "removeFirst" button. 5.Scroll table content to the end. 6.Scroll table content to begin. Table is not refreshed and following exception is logged: {noformat} java.lang.IndexOutOfBoundsException: Index: 0, Size: 0 at java.util.LinkedList.entry(LinkedList.java:365) at java.util.LinkedList.remove(LinkedList.java:357) at org.richfaces.renderkit.ExtendedDataTableRenderer$2.process(ExtendedDataTableRenderer.java:520) at org.ajax4jsf.model.SequenceDataModel.walk(SequenceDataModel.java:65) at org.richfaces.component.UIDataTableBase.walk(UIDataTableBase.java:261) at org.richfaces.renderkit.ExtendedDataTableRenderer.encodeMetaComponent(ExtendedDataTableRenderer.java:512) at org.richfaces.component.UIDataTableBase.encodeMetaComponent(UIDataTableBase.java:295) at org.richfaces.component.AbstractExtendedDataTable.encodeMetaComponent(AbstractExtendedDataTable.java:109) at org.richfaces.context.ExtendedPartialViewContextImpl$RenderVisitCallback.visit(ExtendedPartialViewContextImpl.java:493) at org.richfaces.context.BaseExtendedVisitContext.invokeVisitCallback(BaseExtendedVisitContext.java:321) at org.richfaces.context.ExtendedVisitContext.invokeMetaComponentVisitCallback(ExtendedVisitContext.java:68) at org.richfaces.component.AbstractExtendedDataTable.visitDataChildren(AbstractExtendedDataTable.java:122) at org.richfaces.component.UIDataAdaptor.visitTree(UIDataAdaptor.java:1357) at javax.faces.component.UIForm.visitTree(UIForm.java:266) at javax.faces.component.UIComponent.visitTree(UIComponent.java:797) at javax.faces.component.UIComponentBase.visitTree(UIComponentBase.java:992) at javax.faces.component.UIComponent.visitTree(UIComponent.java:797) at javax.faces.component.UIComponentBase.visitTree(UIComponentBase.java:992) at org.richfaces.context.ExtendedPartialViewContextImpl.processPartialRenderPhase(ExtendedPartialViewContextImpl.java:272) at org.richfaces.context.ExtendedPartialViewContextImpl.processPartial(ExtendedPartialViewContextImpl.java:194) at javax.faces.context.PartialViewContextWrapper.processPartial(PartialViewContextWrapper.java:88) at javax.faces.component.UIViewRoot.encodeChildren(UIViewRoot.java:389) at javax.faces.component.UIComponent.encodeAll(UIComponent.java:617) ... {noformat} ---- *You can download and deploy already updated richfaces-showcase-jbas7.war from attachments on JBoss AS 7 (source codes are available on GitHub:* https://github.com/papousek/showcase/tree/RF-11875 *) instead of updating showcase on your own*. was: I have used "/richfaces/component-sample.jsf?demo=extendedDataTable" page in RF Showcase to reproduce the problem. 1. Add the following code in "simpleTable-sample.xhtml" in h:form tag: {code:xml} {code} 2.Open this page "/richfaces/component-sample.jsf?demo=extendedDataTable" in browser. 3.Check "Turn ajax loading on/off" checkbox. 4.Click "removeFirst" button. 5.Scroll table content to the end. 6.Scroll table content to begin. Table is not refreshed and following exception is logged: {noformat} java.lang.IndexOutOfBoundsException: Index: 0, Size: 0 at java.util.LinkedList.entry(LinkedList.java:365) at java.util.LinkedList.remove(LinkedList.java:357) at org.richfaces.renderkit.ExtendedDataTableRenderer$2.process(ExtendedDataTableRenderer.java:520) at org.ajax4jsf.model.SequenceDataModel.walk(SequenceDataModel.java:65) at org.richfaces.component.UIDataTableBase.walk(UIDataTableBase.java:261) at org.richfaces.renderkit.ExtendedDataTableRenderer.encodeMetaComponent(ExtendedDataTableRenderer.java:512) at org.richfaces.component.UIDataTableBase.encodeMetaComponent(UIDataTableBase.java:295) at org.richfaces.component.AbstractExtendedDataTable.encodeMetaComponent(AbstractExtendedDataTable.java:109) at org.richfaces.context.ExtendedPartialViewContextImpl$RenderVisitCallback.visit(ExtendedPartialViewContextImpl.java:493) at org.richfaces.context.BaseExtendedVisitContext.invokeVisitCallback(BaseExtendedVisitContext.java:321) at org.richfaces.context.ExtendedVisitContext.invokeMetaComponentVisitCallback(ExtendedVisitContext.java:68) at org.richfaces.component.AbstractExtendedDataTable.visitDataChildren(AbstractExtendedDataTable.java:122) at org.richfaces.component.UIDataAdaptor.visitTree(UIDataAdaptor.java:1357) at javax.faces.component.UIForm.visitTree(UIForm.java:266) at javax.faces.component.UIComponent.visitTree(UIComponent.java:797) at javax.faces.component.UIComponentBase.visitTree(UIComponentBase.java:992) at javax.faces.component.UIComponent.visitTree(UIComponent.java:797) at javax.faces.component.UIComponentBase.visitTree(UIComponentBase.java:992) at org.richfaces.context.ExtendedPartialViewContextImpl.processPartialRenderPhase(ExtendedPartialViewContextImpl.java:272) at org.richfaces.context.ExtendedPartialViewContextImpl.processPartial(ExtendedPartialViewContextImpl.java:194) at javax.faces.context.PartialViewContextWrapper.processPartial(PartialViewContextWrapper.java:88) at javax.faces.component.UIViewRoot.encodeChildren(UIViewRoot.java:389) at javax.faces.component.UIComponent.encodeAll(UIComponent.java:617) ... {noformat} > rich:extendedDataTable in ajax loading mode, crashes when dataset length changes between requests > ------------------------------------------------------------------------------------------------- > > Key: RF-11875 > URL: https://issues.jboss.org/browse/RF-11875 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-ScrollableDataTable > Affects Versions: 4.1.0.Final > Environment: JSF-RI 2.0, Tomcat 6.0.29 > Reporter: Dmitry Volkov > Assignee: Jan Papousek > Attachments: richfaces-showcase-jbas7.war > > > rich:extendedDataTable in ajax loading mode(clientRows=".."), crashes when dataset length changes between requests. > It makes ajax loading mode unusable for database paging. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 25 08:15:49 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 25 Jan 2012 08:15:49 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11920) for_each_module.sh: allow to execute paralelly Message-ID: <1798100927.539.1327497349613.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Luk?? Fry? created RF-11920: ------------------------------- Summary: for_each_module.sh: allow to execute paralelly Key: RF-11920 URL: https://issues.jboss.org/browse/RF-11920 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Components: build/distribution Affects Versions: 4.1.0.Final Reporter: Luk?? Fry? It would increase work turnaround when {{for_each_module.sh}} script could execute in parallel, preferably giving results in fix order of modules. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 25 08:17:52 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 25 Jan 2012 08:17:52 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11920) for_each_module.sh: allow to execute paralelly In-Reply-To: <1798100927.539.1327497349613.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1612763539.594.1327497472464.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated RF-11920: ---------------------------- Description: Currently, {{for_each_module.sh}} runs commands in sequence, which makes significant delays in work when triggering commands which takes time to proceed (like fetch from the server). It would increase work turnaround when {{for_each_module.sh}} script could execute in parallel, preferably giving results in fix order of modules. was: It would increase work turnaround when {{for_each_module.sh}} script could execute in parallel, preferably giving results in fix order of modules. > for_each_module.sh: allow to execute paralelly > ---------------------------------------------- > > Key: RF-11920 > URL: https://issues.jboss.org/browse/RF-11920 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: build > Affects Versions: 4.1.0.Final > Reporter: Luk?? Fry? > > Currently, {{for_each_module.sh}} runs commands in sequence, > which makes significant delays in work when triggering commands which takes time to proceed (like fetch from the server). > It would increase work turnaround when {{for_each_module.sh}} script could execute in parallel, > preferably giving results in fix order of modules. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 25 08:38:49 2012 From: jira-events at lists.jboss.org (Jan Papousek (JIRA)) Date: Wed, 25 Jan 2012 08:38:49 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11875) rich:extendedDataTable in ajax loading mode, crashes when dataset length changes between requests In-Reply-To: <1944546618.3014.1326375801528.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <12942332.658.1327498729123.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Papousek reassigned RF-11875: --------------------------------- Assignee: Brian Leathem (was: Jan Papousek) Confirmed. I've attached WAR file and updated description. > rich:extendedDataTable in ajax loading mode, crashes when dataset length changes between requests > ------------------------------------------------------------------------------------------------- > > Key: RF-11875 > URL: https://issues.jboss.org/browse/RF-11875 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-ScrollableDataTable > Affects Versions: 4.1.0.Final > Environment: JSF-RI 2.0, Tomcat 6.0.29 > Reporter: Dmitry Volkov > Assignee: Brian Leathem > Attachments: richfaces-showcase-jbas7.war > > > rich:extendedDataTable in ajax loading mode(clientRows=".."), crashes when dataset length changes between requests. > It makes ajax loading mode unusable for database paging. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 25 08:38:49 2012 From: jira-events at lists.jboss.org (Jan Papousek (JIRA)) Date: Wed, 25 Jan 2012 08:38:49 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11875) rich:extendedDataTable in ajax loading mode, crashes when dataset length changes between requests In-Reply-To: <1944546618.3014.1326375801528.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <849914154.663.1327498729470.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Papousek updated RF-11875: ------------------------------ Environment: JSF-RI 2.0, Tomcat 6.0.29 / JBoss AS 7.0.2.Final (was: JSF-RI 2.0, Tomcat 6.0.29) > rich:extendedDataTable in ajax loading mode, crashes when dataset length changes between requests > ------------------------------------------------------------------------------------------------- > > Key: RF-11875 > URL: https://issues.jboss.org/browse/RF-11875 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-ScrollableDataTable > Affects Versions: 4.1.0.Final > Environment: JSF-RI 2.0, Tomcat 6.0.29 / JBoss AS 7.0.2.Final > Reporter: Dmitry Volkov > Assignee: Brian Leathem > Attachments: richfaces-showcase-jbas7.war > > > rich:extendedDataTable in ajax loading mode(clientRows=".."), crashes when dataset length changes between requests. > It makes ajax loading mode unusable for database paging. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 25 08:40:48 2012 From: jira-events at lists.jboss.org (Juraj Huska (JIRA)) Date: Wed, 25 Jan 2012 08:40:48 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11919) showcase - names of some samples do not follow camel case naming convention In-Reply-To: <1840945137.21442.1327486818320.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1627191777.667.1327498848458.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj Huska updated RF-11919: ----------------------------- Environment: showcase app Priority: Trivial (was: Major) Component/s: qe showcase > showcase - names of some samples do not follow camel case naming convention > --------------------------------------------------------------------------- > > Key: RF-11919 > URL: https://issues.jboss.org/browse/RF-11919 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: qe, showcase > Environment: showcase app > Reporter: Juraj Huska > Priority: Trivial > > There are some samples in showcase which do not follow camel case naming convention. First of all it is inconsistent with other sample names and secondly it makes some problems with showcase tests, since I am using method for loading the appropriate page according to the test class name, which should be obviously named using camel case. Can you please rename following samples ? > component demo - sample > ######################## > a4j:status - viewusage, referencedusage > a4j:outputPanel - Auto update for h:messages 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 Jan 25 09:10:48 2012 From: jira-events at lists.jboss.org (Jan Papousek (JIRA)) Date: Wed, 25 Jan 2012 09:10:48 -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: <1035892220.732.1327500648683.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12661869#comment-12661869 ] Jan Papousek commented on RF-11801: ----------------------------------- Giovanni, could you provide simplified maven project which can be used for reproducing this bug? > 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 Jan 25 12:27:48 2012 From: jira-events at lists.jboss.org (Jean ANDRE (JIRA)) Date: Wed, 25 Jan 2012 12:27:48 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11855) error@malformedXML on inputText files - Ajax Validation on event change - RichFaces 4.1 Final In-Reply-To: <26805713.30230.1324582930232.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1683182724.1505.1327512468591.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean ANDRE reopened RF-11855: ----------------------------- Come on guys, do not miss the opportunity to solve a such bug - The fact is when we use f:ajax tag, it is working but when we use richfaces tag is not - What does it mean...? - The bug can be easily reproduced, just edit the createClient xhtml and replace the f:ajax tab by yours. RichFaces is your product and the ideal conditions does not really exist...as "complexity" is probably part of the problem. Sincerely. > error at malformedXML on inputText files - Ajax Validation on event change - RichFaces 4.1 Final > ---------------------------------------------------------------------------------------------- > > Key: RF-11855 > URL: https://issues.jboss.org/browse/RF-11855 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.1.0.Final > Environment: Websphere 8.0.0.1 - RAD 8.0.0.4 - JSF Mojorra 2.1.4 - Spring 3.0.6 Final - Hibernate Validator 4.2. - Java 6 > Reporter: Jean ANDRE > Assignee: Brian Leathem > Labels: INPUT, MALFORMED, UI, XML > Attachments: createClient1.xhtml, CreateClientController1.java, error at malformedXML-ScreenShot-1.jpg, error at malformedXML.debug.txt, error at malformedXML.viewSource.html, index.xhtml > > > We got a error at malformedXML message when we want to apply an ajax validation on imput text. > The field is include inside a tab in mode "server" - What ever the mode, we getting the error. Tab content is built by including some xhtml. See attachment. > {code} > > xmlns:h="http://java.sun.com/jsf/html" > xmlns:f="http://java.sun.com/jsf/core" > xmlns:rich="http://richfaces.org/rich" > xmlns:c="http://java.sun.com/jsp/jstl/core" > xmlns:a4j="http://richfaces.org/a4j"> > > > > > > > > > > > > > > > > {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 Jan 25 12:47:48 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 25 Jan 2012 12:47:48 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11921) Update the release-notes Message-ID: <432501842.1527.1327513668309.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Brian Leathem created RF-11921: ---------------------------------- Summary: Update the release-notes Key: RF-11921 URL: https://issues.jboss.org/browse/RF-11921 Project: RichFaces Issue Type: Task Security Level: Public (Everyone can see) Components: build/distribution Reporter: Brian Leathem Assignee: Brian Leathem Priority: Blocker Fix For: 4.2.0.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 Jan 25 12:57:48 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 25 Jan 2012 12:57:48 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11908) rich:datascroller not scrolling rich:dataGrid In-Reply-To: <938472980.13390.1327071498619.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <991052350.1571.1327514268904.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-11908: ------------------------------- Comment: was deleted (was: QE, please confirm) > rich:datascroller not scrolling rich:dataGrid > --------------------------------------------- > > Key: RF-11908 > URL: https://issues.jboss.org/browse/RF-11908 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component > Affects Versions: 3.3.3.Final > Environment: Windows OS in JBoss 5.1 > Reporter: Todd Gould > Assignee: Pavol Pitonak > > The rich:dataScroller does not work with the rich:dataGrid component. The datascroller represents the proper number of pages for the data in the dataGrid. However, when I select any of the datascroller controlls, the ajax request processes (as witnessed via the associated status), but the dataGrid remains on the first page. Nothing seems to be able to make it progress to another page. No ajax or other errors are generated and all appears to function well except that the datGrid does not scroll. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 25 12:57:48 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 25 Jan 2012 12:57:48 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11908) rich:datascroller not scrolling rich:dataGrid In-Reply-To: <938472980.13390.1327071498619.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <635314472.1573.1327514268964.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem reassigned RF-11908: ---------------------------------- Assignee: (was: Pavol Pitonak) > rich:datascroller not scrolling rich:dataGrid > --------------------------------------------- > > Key: RF-11908 > URL: https://issues.jboss.org/browse/RF-11908 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component > Affects Versions: 3.3.3.Final > Environment: Windows OS in JBoss 5.1 > Reporter: Todd Gould > > The rich:dataScroller does not work with the rich:dataGrid component. The datascroller represents the proper number of pages for the data in the dataGrid. However, when I select any of the datascroller controlls, the ajax request processes (as witnessed via the associated status), but the dataGrid remains on the first page. Nothing seems to be able to make it progress to another page. No ajax or other errors are generated and all appears to function well except that the datGrid does not scroll. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 25 12:59:48 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 25 Jan 2012 12:59:48 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11908) rich:datascroller not scrolling rich:dataGrid In-Reply-To: <938472980.13390.1327071498619.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1955656038.1580.1327514388523.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-11908: ------------------------------- Fix Version/s: 3.Future Forum Reference: https://community.jboss.org/message/647269#647269 (was: https://community.jboss.org/message/647269#647269) > rich:datascroller not scrolling rich:dataGrid > --------------------------------------------- > > Key: RF-11908 > URL: https://issues.jboss.org/browse/RF-11908 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component > Affects Versions: 3.3.3.Final > Environment: Windows OS in JBoss 5.1 > Reporter: Todd Gould > Fix For: 3.Future > > > The rich:dataScroller does not work with the rich:dataGrid component. The datascroller represents the proper number of pages for the data in the dataGrid. However, when I select any of the datascroller controlls, the ajax request processes (as witnessed via the associated status), but the dataGrid remains on the first page. Nothing seems to be able to make it progress to another page. No ajax or other errors are generated and all appears to function well except that the datGrid does not scroll. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 25 13:03:49 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 25 Jan 2012 13:03:49 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11915) MenuGroup with all items disabled or no items causes JS error In-Reply-To: <2107920490.18850.1327404678300.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <926560686.1586.1327514629047.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-11915: ------------------------------- Description: Submenu (r:menuGroup) containing only disabled items or no items, causes a JavaScript error when it is supposed to get hidden (moving cursor to the next item in the parent menu). In Firefox 9: {quote} parentMenu is undefined menu-base.js, line 126 {quote} In MSIE 7: {quote} 'nodeType' is null or not an object richfaces.js, line 43 {quote} It's the same error only reported from the different level of the call stack. was: Submenu (r:menuGroup) containing only disabled items or no items, causes a JavaScript error when it is supposed to get hidden (moving cursor to the next item in the parent menu). In Firefox 9: parentMenu is undefined menu-base.js, line 126 In MSIE 7: 'nodeType' is null or not an object richfaces.js, line 43 It's the same error only reported from the different level of the call stack. Steps to Reproduce: Test case {also works with "Disabled item" removed): {code} {code} # open the menu "Menu test case" # move the cursor down by the items # after leaving "Submenu with disabled items" and moving to "Last item", the error appears. was: Test case {also works with "Disabled item" removed): - open the menu "Menu test case" - move the cursor down by the items - after leaving "Submenu with disabled items" and moving to "Last item", the error appears. > MenuGroup with all items disabled or no items causes JS error > ------------------------------------------------------------- > > Key: RF-11915 > URL: https://issues.jboss.org/browse/RF-11915 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-menu > Affects Versions: 4.1.0.Final > Environment: Tomcat 6.0.26, MyFaces 2.1.13, RichFaces > Reporter: J?n Hala?a > > Submenu (r:menuGroup) containing only disabled items or no items, causes a JavaScript error when it is supposed to get hidden (moving cursor to the next item in the parent menu). > In Firefox 9: > {quote} > parentMenu is undefined > menu-base.js, line 126 > {quote} > In MSIE 7: > {quote} > 'nodeType' is null or not an object > richfaces.js, line 43 > {quote} > It's the same error only reported from the different level of the call stack. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 25 14:29:48 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 25 Jan 2012 14:29:48 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11915) MenuGroup with all items disabled or no items causes JS error In-Reply-To: <2107920490.18850.1327404678300.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1043479941.1818.1327519788839.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem reassigned RF-11915: ---------------------------------- Assignee: Pavol Pitonak QE, please verify. > MenuGroup with all items disabled or no items causes JS error > ------------------------------------------------------------- > > Key: RF-11915 > URL: https://issues.jboss.org/browse/RF-11915 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-menu > Affects Versions: 4.1.0.Final > Environment: Tomcat 6.0.26, MyFaces 2.1.13, RichFaces > Reporter: J?n Hala?a > Assignee: Pavol Pitonak > > Submenu (r:menuGroup) containing only disabled items or no items, causes a JavaScript error when it is supposed to get hidden (moving cursor to the next item in the parent menu). > In Firefox 9: > {quote} > parentMenu is undefined > menu-base.js, line 126 > {quote} > In MSIE 7: > {quote} > 'nodeType' is null or not an object > richfaces.js, line 43 > {quote} > It's the same error only reported from the different level of the call stack. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 25 14:31:48 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 25 Jan 2012 14:31:48 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11916) extendedDataTable partial update => extend the functionality with INSERT and DELETE row where scroll position does not go up. In-Reply-To: <1922325197.20094.1327442658256.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1619555150.1848.1327519908574.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-11916: ------------------------------- Fix Version/s: 4.Future Component/s: component-tables Forum Reference: https://community.jboss.org/message/516078#516078 (was: https://community.jboss.org/message/516078#516078) Thanks for taking the time to file a feature request. We'll evaluate this in the near future when we assess all the EDT feature requests. > extendedDataTable partial update => extend the functionality with INSERT and DELETE row where scroll position does not go up. > ----------------------------------------------------------------------------------------------------------------------------- > > Key: RF-11916 > URL: https://issues.jboss.org/browse/RF-11916 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-tables > Reporter: Tom Giberius > Fix For: 4.Future > > > Situation: > 1) extendDataTable with a verticall ScrollBar > 2) Insert or delete record by insert/delete in myBean and by a re-render of the table. > 3) The re-render causes a full rebuild of the table in the DOM and the effect is that the scrollbar goes up to the beginning.In fact this makes a scrollable extendedDataTable not useful for inserting/deleting records. > Partial Table Render for extendedDataTable is available in RF 4.1 with a construction like: > render="myTable at rows(myBean.listOfUpdateRows):myColumn" > This works fine for already available rows and indeed it is an UPDATE. > Also @body, @header and @footer are available for partial table update. > I would like to have a kind of partitial table INSERT and UPDATE where not the whole table is "re-draw", only the record(s) are INSERTED or DELETED and where the scroll position for the user visually stays the same. Maintaining the scroll position is the reason for this request, a user should be able to insert/delete rows any where in a scrollalbe table larger then the table height. > It could look like: > render="myTable at insert(myBean.Row) > render="myTable at delete(myBean.RowKey) > Also take care of the "selected" row: > * For deletes the RowKey is passed, so no problem > * For inserts one could consider: > - Pass RowKey as parameter and insert before/after the given RowKey > - Use the current "selected record" > E.g.current selected record: > * No record - then insert in first position > * A record selected - insert after selected records > The inserted record is anyway the new "selected row" > Also with a delete you should consider what the "selected record" should be if a selected record is deleted. > I use the selected record (single selection mode) in insert/delete. For that I made some changes to the JavaScript of the extendenDataTable. > If you have questions I will gladly elaborate on 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 Jan 25 14:33:48 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 25 Jan 2012 14:33:48 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11919) showcase - names of some samples do not follow camel case naming convention In-Reply-To: <1840945137.21442.1327486818320.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <850246606.1851.1327520028535.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-11919: ------------------------------- Assignee: Brian Leathem Fix Version/s: 4.2.0.CR1 > showcase - names of some samples do not follow camel case naming convention > --------------------------------------------------------------------------- > > Key: RF-11919 > URL: https://issues.jboss.org/browse/RF-11919 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: qe, showcase > Environment: showcase app > Reporter: Juraj Huska > Assignee: Brian Leathem > Priority: Trivial > Fix For: 4.2.0.CR1 > > > There are some samples in showcase which do not follow camel case naming convention. First of all it is inconsistent with other sample names and secondly it makes some problems with showcase tests, since I am using method for loading the appropriate page according to the test class name, which should be obviously named using camel case. Can you please rename following samples ? > component demo - sample > ######################## > a4j:status - viewusage, referencedusage > a4j:outputPanel - Auto update for h:messages 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 Jan 25 14:35:48 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 25 Jan 2012 14:35:48 -0500 (EST) 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: <615088529.1856.1327520148357.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 ] Brian Leathem reassigned RF-11905: ---------------------------------- Assignee: Juraj Huska Good job finding the upstream issue! It indicates the problem has been fixed in JBoss AS 7.1, would you please verify that this has been fixed for the showcase? > 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: Juraj Huska > Priority: Minor > > 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 Jan 25 16:46:48 2012 From: jira-events at lists.jboss.org (Jesper Vrelits (JIRA)) Date: Wed, 25 Jan 2012 16:46:48 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11656) Nested collapsibleSubTable always expanded In-Reply-To: <481335575.67197.1320749685382.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <983334762.1975.1327528008664.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12662025#comment-12662025 ] Jesper Vrelits commented on RF-11656: ------------------------------------- Any hope this will get fixed. It is a QE verified Major bug. I have a hard time understanding there is not more focus on fixing bugs, in this case a verified bug. > Nested collapsibleSubTable always expanded > ------------------------------------------ > > Key: RF-11656 > URL: https://issues.jboss.org/browse/RF-11656 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component > Affects Versions: 4.1.0.Milestone3 > Reporter: Jesper Vrelits > Assignee: Brian Leathem > Fix For: 4.3-Tracking > > > When I use nested collapsibleSubTable the nested collapsibleSubTable is always expanded. > Even if I put expended="#{false}" it is also expanded. > My facelet looks like this: > {code} > id="envtoggle" expandMode="ajax" expanded="#{environment.expanded}"> > > > > > > > > > > > > > > var="logicalinstance" id="logicaltoggle" expandMode="ajax" > expanded="#{group.expanded}"> > > > > > > > > > {code} > Group.expanded seems to be updated correctly, so it seems the Renderer does not use this. A guess is that it uses the parent collapsibleSubTable expanded value, because they seem synchronized. My guess it the Renderer code does not work with nested collapsible sub tables. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 25 16:48:48 2012 From: jira-events at lists.jboss.org (Jesper Vrelits (JIRA)) Date: Wed, 25 Jan 2012 16:48:48 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-10925) ELResolver #{bean.property[value]} and graphValidator causes exception In-Reply-To: <744570596.28727.1302796653333.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <857955669.1980.1327528128684.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-10925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesper Vrelits closed RF-10925. ------------------------------- Fix Version/s: (was: 4.Future) Resolution: Out of Date > ELResolver #{bean.property[value]} and graphValidator causes exception > ---------------------------------------------------------------------- > > Key: RF-10925 > URL: https://issues.jboss.org/browse/RF-10925 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-validators, regression > Affects Versions: 4.0.0.Final > Environment: Mojarra 2.0.4 + Tomcat 7 and Weblogic 10.3.4 > Reporter: Jesper Vrelits > > Not able to resolve property in bean when as #{bean.property[value]} when wrapped in graphValidator. > Veryified on Tomcat 7 and Weblogic 10.3.4. > If graphValidator is removed it works. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 25 17:22:48 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 25 Jan 2012 17:22:48 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11879) Add examle of usage of a4j:actionListener into RF showcase In-Reply-To: <43091471.3804.1326385042424.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <2053365943.2035.1327530168383.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem reassigned RF-11879: ---------------------------------- Assignee: Brian Leathem > Add examle of usage of a4j:actionListener into RF showcase > ---------------------------------------------------------- > > Key: RF-11879 > URL: https://issues.jboss.org/browse/RF-11879 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: showcase > Affects Versions: 4.1.0.Final > Reporter: Marek Novotny > Assignee: Brian Leathem > Priority: Minor > Fix For: 4.2.0.CR1 > > > a4j:actionListener is not presented in showcase example -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 25 19:29:49 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 25 Jan 2012 19:29:49 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11922) Nesting an a4j:actionListener in a composite component results in a java.io.NotSerializableException Message-ID: <340783677.2125.1327537789610.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Brian Leathem created RF-11922: ---------------------------------- Summary: Nesting an a4j:actionListener in a composite component results in a java.io.NotSerializableException Key: RF-11922 URL: https://issues.jboss.org/browse/RF-11922 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-a4j-core Affects Versions: 4.1.0.Final Reporter: Brian Leathem Fix For: 4.Future In the code samples below, an a4j:actionListener is nested in a composite component. This results in a java.io.NotSerializableException (stack trace below). {code:title=actionComposite.xhtml} {code} {code:title=actionListener.xhtml} {code} {code:title=Stacktrace} Caused by: java.io.NotSerializableException: org.richfaces.view.facelets.html.ActionListenerHandler at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1164) [:1.6.0_26] at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:330) [:1.6.0_26] at java.util.ArrayList.writeObject(ArrayList.java:570) [:1.6.0_26] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_26] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_26] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_26] at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_26] at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:945) [:1.6.0_26] at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1469) [:1.6.0_26] at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1400) [:1.6.0_26] at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1158) [:1.6.0_26] at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1518) [:1.6.0_26] at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1483) [:1.6.0_26] at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1400) [:1.6.0_26] at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1158) [:1.6.0_26] at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:330) [:1.6.0_26] at java.util.ArrayList.writeObject(ArrayList.java:570) [:1.6.0_26] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_26] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_26] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_26] at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_26] at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:945) [:1.6.0_26] at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1469) [:1.6.0_26] at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1400) [:1.6.0_26] at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1158) [:1.6.0_26] at java.io.ObjectOutputStream.writeArray(ObjectOutputStream.java:1346) [:1.6.0_26] at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1154) [:1.6.0_26] at java.io.ObjectOutputStream.writeArray(ObjectOutputStream.java:1346) [:1.6.0_26] at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1154) [:1.6.0_26] at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:330) [:1.6.0_26] at java.util.HashMap.writeObject(HashMap.java:1001) [:1.6.0_26] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_26] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_26] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_26] at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_26] at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:945) [:1.6.0_26] at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1469) [:1.6.0_26] at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1400) [:1.6.0_26] at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1158) [:1.6.0_26] at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:330) [:1.6.0_26] at com.sun.faces.renderkit.ClientSideStateHelper.doWriteState(ClientSideStateHelper.java:325) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] at com.sun.faces.renderkit.ClientSideStateHelper.writeState(ClientSideStateHelper.java:169) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] at com.sun.faces.renderkit.ResponseStateManagerImpl.getViewState(ResponseStateManagerImpl.java:135) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] ... 28 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 Jan 25 19:31:48 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 25 Jan 2012 19:31:48 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11922) Nesting an a4j:actionListener in a composite component results in a java.io.NotSerializableException In-Reply-To: <340783677.2125.1327537789610.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <600170514.2126.1327537908379.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12662047#comment-12662047 ] Brian Leathem commented on RF-11922: ------------------------------------ As an experiment, I added the Serializable interface to _org.richfaces.view.facelets.html.ActionListenerHandler_, this resulted in the stacktrace: {code} Caused by: java.io.NotSerializableException: com.sun.faces.facelets.tag.TagAttributeImpl at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1164) [:1.6.0_26] at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1518) [:1.6.0_26] at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1483) [:1.6.0_26] at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1400) [:1.6.0_26] at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1158) [:1.6.0_26] at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:330) [:1.6.0_26] at java.util.ArrayList.writeObject(ArrayList.java:570) [:1.6.0_26] at sun.reflect.GeneratedMethodAccessor47.invoke(Unknown Source) [:1.6.0_26] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_26] at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_26] at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:945) [:1.6.0_26] at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1469) [:1.6.0_26] at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1400) [:1.6.0_26] at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1158) [:1.6.0_26] at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1518) [:1.6.0_26] at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1483) [:1.6.0_26] at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1400) [:1.6.0_26] at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1158) [:1.6.0_26] at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:330) [:1.6.0_26] at java.util.ArrayList.writeObject(ArrayList.java:570) [:1.6.0_26] at sun.reflect.GeneratedMethodAccessor47.invoke(Unknown Source) [:1.6.0_26] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_26] at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_26] at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:945) [:1.6.0_26] at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1469) [:1.6.0_26] at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1400) [:1.6.0_26] at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1158) [:1.6.0_26] at java.io.ObjectOutputStream.writeArray(ObjectOutputStream.java:1346) [:1.6.0_26] at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1154) [:1.6.0_26] at java.io.ObjectOutputStream.writeArray(ObjectOutputStream.java:1346) [:1.6.0_26] at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1154) [:1.6.0_26] at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:330) [:1.6.0_26] at java.util.HashMap.writeObject(HashMap.java:1001) [:1.6.0_26] at sun.reflect.GeneratedMethodAccessor50.invoke(Unknown Source) [:1.6.0_26] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_26] at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_26] at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:945) [:1.6.0_26] at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1469) [:1.6.0_26] at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1400) [:1.6.0_26] at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1158) [:1.6.0_26] at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:330) [:1.6.0_26] at com.sun.faces.renderkit.ClientSideStateHelper.doWriteState(ClientSideStateHelper.java:325) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] at com.sun.faces.renderkit.ClientSideStateHelper.writeState(ClientSideStateHelper.java:169) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] at com.sun.faces.renderkit.ResponseStateManagerImpl.getViewState(ResponseStateManagerImpl.java:135) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] ... 28 more {code} > Nesting an a4j:actionListener in a composite component results in a java.io.NotSerializableException > ---------------------------------------------------------------------------------------------------- > > Key: RF-11922 > URL: https://issues.jboss.org/browse/RF-11922 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.1.0.Final > Reporter: Brian Leathem > Fix For: 4.Future > > > In the code samples below, an a4j:actionListener is nested in a composite component. This results in a java.io.NotSerializableException (stack trace below). > {code:title=actionComposite.xhtml} > > > > > > > > > > > > > > {code} > {code:title=actionListener.xhtml} > > > > > > > > > {code} > {code:title=Stacktrace} > Caused by: java.io.NotSerializableException: org.richfaces.view.facelets.html.ActionListenerHandler > at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1164) [:1.6.0_26] > at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:330) [:1.6.0_26] > at java.util.ArrayList.writeObject(ArrayList.java:570) [:1.6.0_26] > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_26] > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_26] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_26] > at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_26] > at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:945) [:1.6.0_26] > at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1469) [:1.6.0_26] > at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1400) [:1.6.0_26] > at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1158) [:1.6.0_26] > at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1518) [:1.6.0_26] > at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1483) [:1.6.0_26] > at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1400) [:1.6.0_26] > at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1158) [:1.6.0_26] > at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:330) [:1.6.0_26] > at java.util.ArrayList.writeObject(ArrayList.java:570) [:1.6.0_26] > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_26] > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_26] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_26] > at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_26] > at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:945) [:1.6.0_26] > at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1469) [:1.6.0_26] > at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1400) [:1.6.0_26] > at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1158) [:1.6.0_26] > at java.io.ObjectOutputStream.writeArray(ObjectOutputStream.java:1346) [:1.6.0_26] > at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1154) [:1.6.0_26] > at java.io.ObjectOutputStream.writeArray(ObjectOutputStream.java:1346) [:1.6.0_26] > at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1154) [:1.6.0_26] > at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:330) [:1.6.0_26] > at java.util.HashMap.writeObject(HashMap.java:1001) [:1.6.0_26] > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_26] > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_26] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_26] > at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_26] > at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:945) [:1.6.0_26] > at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1469) [:1.6.0_26] > at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1400) [:1.6.0_26] > at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1158) [:1.6.0_26] > at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:330) [:1.6.0_26] > at com.sun.faces.renderkit.ClientSideStateHelper.doWriteState(ClientSideStateHelper.java:325) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > at com.sun.faces.renderkit.ClientSideStateHelper.writeState(ClientSideStateHelper.java:169) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > at com.sun.faces.renderkit.ResponseStateManagerImpl.getViewState(ResponseStateManagerImpl.java:135) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > ... 28 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 Jan 26 06:12:49 2012 From: jira-events at lists.jboss.org (Justin Wyer (JIRA)) Date: Thu, 26 Jan 2012 06:12:49 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11088) rich:select modify manualInput behavior to avoid single item scoped item list popup when editing value In-Reply-To: <2012979835.24177.1309246043698.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1565251019.2770.1327576369470.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12662120#comment-12662120 ] Justin Wyer commented on RF-11088: ---------------------------------- An update to this issue, my changes no longer merged with upstream due to a large refactoring of the java script by Brian in august https://github.com/richfaces/components/commit/e28ee48a22b0aced146cb547f50f32d357f6912b > rich:select modify manualInput behavior to avoid single item scoped item list popup when editing value > ------------------------------------------------------------------------------------------------------ > > Key: RF-11088 > URL: https://issues.jboss.org/browse/RF-11088 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 4.0.0.Final, 4.0.1.Milestone1, 4.1.0.Milestone1 > Reporter: Justin Wyer > Assignee: Justin Wyer > Labels: rich:select > Fix For: 4.3-Tracking > > > rich:select has usability issues when using enableManualInput="true" this will address the issues discussed in the forum post. My current idea is to attempt to display the full item list and auto highlight the input's value. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 26 07:45:48 2012 From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA)) Date: Thu, 26 Jan 2012 07:45:48 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11915) MenuGroup with all items disabled or no items causes JS error In-Reply-To: <2107920490.18850.1327404678300.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <980613746.2977.1327581948647.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavol Pitonak reassigned RF-11915: ---------------------------------- Assignee: Brian Leathem (was: Pavol Pitonak) Reproduced in following environment: {quote} RichFaces 4.2.0-SNAPSHOT Metamer 4.2.0-SNAPSHOT Mojarra 2.1.5 JBoss AS 7.1.0.CR1 OpenJDK Runtime Environment 1.6.0_22-b22 @ Linux Firefox 9.0.1 @ Linux x86_64 {quote} > MenuGroup with all items disabled or no items causes JS error > ------------------------------------------------------------- > > Key: RF-11915 > URL: https://issues.jboss.org/browse/RF-11915 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-menu > Affects Versions: 4.1.0.Final > Environment: Tomcat 6.0.26, MyFaces 2.1.13, RichFaces > Reporter: J?n Hala?a > Assignee: Brian Leathem > > Submenu (r:menuGroup) containing only disabled items or no items, causes a JavaScript error when it is supposed to get hidden (moving cursor to the next item in the parent menu). > In Firefox 9: > {quote} > parentMenu is undefined > menu-base.js, line 126 > {quote} > In MSIE 7: > {quote} > 'nodeType' is null or not an object > richfaces.js, line 43 > {quote} > It's the same error only reported from the different level of the call stack. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 26 07:45:48 2012 From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA)) Date: Thu, 26 Jan 2012 07:45:48 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11915) MenuGroup with all items disabled or no items causes JS error In-Reply-To: <2107920490.18850.1327404678300.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <265923527.2980.1327581948783.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12662141#comment-12662141 ] Pavol Pitonak edited comment on RF-11915 at 1/26/12 7:45 AM: ------------------------------------------------------------- Reproduced in following environment: {quote} RichFaces 4.2.0-SNAPSHOT Metamer 4.2.0-SNAPSHOT Mojarra 2.1.5 JBoss AS 7.1.0.CR1 OpenJDK Runtime Environment 1.6.0_22-b22 @ Linux Firefox 9.0.1 @ Linux x86_64, Chrome 16.0.912.75 @ Linux x86_64 {quote} was (Author: ppitonak): Reproduced in following environment: {quote} RichFaces 4.2.0-SNAPSHOT Metamer 4.2.0-SNAPSHOT Mojarra 2.1.5 JBoss AS 7.1.0.CR1 OpenJDK Runtime Environment 1.6.0_22-b22 @ Linux Firefox 9.0.1 @ Linux x86_64 {quote} > MenuGroup with all items disabled or no items causes JS error > ------------------------------------------------------------- > > Key: RF-11915 > URL: https://issues.jboss.org/browse/RF-11915 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-menu > Affects Versions: 4.1.0.Final > Environment: Tomcat 6.0.26, MyFaces 2.1.13, RichFaces > Reporter: J?n Hala?a > Assignee: Brian Leathem > > Submenu (r:menuGroup) containing only disabled items or no items, causes a JavaScript error when it is supposed to get hidden (moving cursor to the next item in the parent menu). > In Firefox 9: > {quote} > parentMenu is undefined > menu-base.js, line 126 > {quote} > In MSIE 7: > {quote} > 'nodeType' is null or not an object > richfaces.js, line 43 > {quote} > It's the same error only reported from the different level of the call stack. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 26 09:44:48 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 26 Jan 2012 09:44:48 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11909) Custom resource mapping can't simply reuse pre-generated RichFaces resources In-Reply-To: <42430590.13417.1327071978848.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <117465284.3295.1327589088607.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12662182#comment-12662182 ] Luk?? Fry? commented on RF-11909: --------------------------------- Following **configuration names was renamed** (with backward compatible option to use old param names): {{org.richfaces.*resourceMapping*.enabled}} -> {{org.richfaces.*resourceLoading.optimization*.enabled}} {{org.richfaces.resourceMapping.compressedStages}} -> {{org.richfaces.resourceLoading.optimization.compression.stages}} {{org.richfaces.resourceMapping.packedStages}} -> {{org.richfaces.resourceLoading.optimization.packaging.stages}} Following *configuration params stay same*: {{org.richfaces.resourceMapping.mappingFile}} {{org.richfaces.resourceMapping.location}} However it is not necessary to set {{org.richfaces.resourceMapping.enabled}} in order to define custom mappings files. For defining *custom mapping files*, user needs just to either: * create {{META-INF/richfaces/static-resource-mappings.properties}} mapping file on classpath * create custom file on classpath and configure it's name to {{org.richfaces.resourceMapping.mappingFile}} Configurations from mapping files will be applied in *following order* (the last one will take precedence), it gives user chance to redefine mappings: * resource loading optimization ({{org.richfaces.resourceMapping.enabled}}) * {{META-INF/richfaces/static-resource-mappings.properties}} * custom files in {{org.richfaces.resourceMapping.mappingFile}} > Custom resource mapping can't simply reuse pre-generated RichFaces resources > ---------------------------------------------------------------------------- > > Key: RF-11909 > URL: https://issues.jboss.org/browse/RF-11909 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 4.1.0.Final > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 4.2.0.CR1 > > > Custom resource mapping can't simply reuse pre-generated RichFaces resources. > Use case: > * user wants to use resource mapping for several purposes > ** using RichFaces pre-generated resources in {{richfaces-components-ui.jar/META-INF/resources/org.richfaces.staticResources//...}} > ** using custom mappings like {{javax.faces:jsf.js=patched-jsf.js}} using e.g. {{my.war/resources/patched-jsf.js}} > ---- > With {{4.1.0.Final}}, configuration of {{org.richfaces.resourceMapping.location}} is by default referring to root of packed resources: > {code}#{facesContext.externalContext.requestContextPath}/org.richfaces.resources/javax.faces.resource/org.richfaces.staticResource/#{a4j.version.implementationVersion}/%Features%/#{resourceLocation} > {code} > and mapping file looks like: > {code} > jquery.js=jquery.js > {code} > When you want to reuse RichFaces mappings, you [need to copy mapping file from {{richfaces-component-ui.jar}}|http://docs.jboss.org/richfaces/latest_4_X/Developer_Guide/en-US/html/chap-Developer_Guide-Advanced_features.html#d0e1692] and extend it by custom properties. > and additionally you need to place custom resources to directory called specifically for RF, like: > {code} > my.war/resources/org.richfaces.staticResource/4.1.0.Final/PackedCompressed/patched-jsf.js > {code} > Other options: > * change all mappings in {{custom-mappings.properties}} at own > * copy all resources from {{richfaces-component-ui.jar}} to own location > ---- > For simplification, I suggest default resource mapping location root be > {code} > #{facesContext.externalContext.requestContextPath}/org.richfaces.resources/javax.faces.resource/#{resourceLocation} > {code} > so it would refer to JSF resources root ({{my.war/resources}} or {{some.jar/META-INF/resources}}) by default. > Then, we would force {{richfaces-components-ui.jar}} to define mappings which points from JSF resources root, e.g.: > {code} > jquery.js=org.richfaces.staticResource/4.1.0.Final/PackedCompressed/jquery.js > {code} > ---- > Additionally, Brian suggested support for multiple {{mapping.properties}} files, so their content will be merged. > It means user won't be forced to copy&paste RichFaces mapping configuration from {{richfaces-components-ui.jar}}. > ---- > Finally, the only thing user would need to define is: > {code:XML|title=web.xml} > > org.richfaces.resourceMapping.mappingFile > META-INF/custom-mapping.properties > > {code} > {code:title=META-INF/custom-mapping.properties} > javax.faces:jsf.js=patched-jsf.js > {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 Jan 26 09:44:48 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 26 Jan 2012 09:44:48 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11909) Custom resource mapping can't simply reuse pre-generated RichFaces resources In-Reply-To: <42430590.13417.1327071978848.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <108313886.3300.1327589088786.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12662182#comment-12662182 ] Luk?? Fry? edited comment on RF-11909 at 1/26/12 9:44 AM: ---------------------------------------------------------- Following **configuration names was renamed** (with backward compatible option to use old param names): {{org.richfaces.*resourceMapping*.enabled}} -> {{org.richfaces.*resourceLoading.optimization*.enabled}} {{org.richfaces.resourceMapping.compressedStages}} -> {{org.richfaces.resourceLoading.optimization.compression.stages}} {{org.richfaces.resourceMapping.packedStages}} -> {{org.richfaces.resourceLoading.optimization.packaging.stages}} Following *configuration params stay same*: {{org.richfaces.resourceMapping.mappingFile}} {{org.richfaces.resourceMapping.location}} However it is not necessary to set {{org.richfaces.resourceMapping.enabled}} in order to define custom mappings files. For defining *custom mapping files*, user needs just to either: * create {{META-INF/richfaces/static-resource-mappings.properties}} mapping file on classpath * create custom file on classpath and configure it's name in {{org.richfaces.resourceMapping.mappingFile}} (comma separated list of files) Configurations from mapping files will be applied in *following order* (the last one will take precedence), it gives user chance to redefine mappings: * resource loading optimization ({{org.richfaces.resourceMapping.enabled}}) * {{META-INF/richfaces/static-resource-mappings.properties}} * custom files in {{org.richfaces.resourceMapping.mappingFile}} was (Author: lfryc): Following **configuration names was renamed** (with backward compatible option to use old param names): {{org.richfaces.*resourceMapping*.enabled}} -> {{org.richfaces.*resourceLoading.optimization*.enabled}} {{org.richfaces.resourceMapping.compressedStages}} -> {{org.richfaces.resourceLoading.optimization.compression.stages}} {{org.richfaces.resourceMapping.packedStages}} -> {{org.richfaces.resourceLoading.optimization.packaging.stages}} Following *configuration params stay same*: {{org.richfaces.resourceMapping.mappingFile}} {{org.richfaces.resourceMapping.location}} However it is not necessary to set {{org.richfaces.resourceMapping.enabled}} in order to define custom mappings files. For defining *custom mapping files*, user needs just to either: * create {{META-INF/richfaces/static-resource-mappings.properties}} mapping file on classpath * create custom file on classpath and configure it's name to {{org.richfaces.resourceMapping.mappingFile}} Configurations from mapping files will be applied in *following order* (the last one will take precedence), it gives user chance to redefine mappings: * resource loading optimization ({{org.richfaces.resourceMapping.enabled}}) * {{META-INF/richfaces/static-resource-mappings.properties}} * custom files in {{org.richfaces.resourceMapping.mappingFile}} > Custom resource mapping can't simply reuse pre-generated RichFaces resources > ---------------------------------------------------------------------------- > > Key: RF-11909 > URL: https://issues.jboss.org/browse/RF-11909 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 4.1.0.Final > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 4.2.0.CR1 > > > Custom resource mapping can't simply reuse pre-generated RichFaces resources. > Use case: > * user wants to use resource mapping for several purposes > ** using RichFaces pre-generated resources in {{richfaces-components-ui.jar/META-INF/resources/org.richfaces.staticResources//...}} > ** using custom mappings like {{javax.faces:jsf.js=patched-jsf.js}} using e.g. {{my.war/resources/patched-jsf.js}} > ---- > With {{4.1.0.Final}}, configuration of {{org.richfaces.resourceMapping.location}} is by default referring to root of packed resources: > {code}#{facesContext.externalContext.requestContextPath}/org.richfaces.resources/javax.faces.resource/org.richfaces.staticResource/#{a4j.version.implementationVersion}/%Features%/#{resourceLocation} > {code} > and mapping file looks like: > {code} > jquery.js=jquery.js > {code} > When you want to reuse RichFaces mappings, you [need to copy mapping file from {{richfaces-component-ui.jar}}|http://docs.jboss.org/richfaces/latest_4_X/Developer_Guide/en-US/html/chap-Developer_Guide-Advanced_features.html#d0e1692] and extend it by custom properties. > and additionally you need to place custom resources to directory called specifically for RF, like: > {code} > my.war/resources/org.richfaces.staticResource/4.1.0.Final/PackedCompressed/patched-jsf.js > {code} > Other options: > * change all mappings in {{custom-mappings.properties}} at own > * copy all resources from {{richfaces-component-ui.jar}} to own location > ---- > For simplification, I suggest default resource mapping location root be > {code} > #{facesContext.externalContext.requestContextPath}/org.richfaces.resources/javax.faces.resource/#{resourceLocation} > {code} > so it would refer to JSF resources root ({{my.war/resources}} or {{some.jar/META-INF/resources}}) by default. > Then, we would force {{richfaces-components-ui.jar}} to define mappings which points from JSF resources root, e.g.: > {code} > jquery.js=org.richfaces.staticResource/4.1.0.Final/PackedCompressed/jquery.js > {code} > ---- > Additionally, Brian suggested support for multiple {{mapping.properties}} files, so their content will be merged. > It means user won't be forced to copy&paste RichFaces mapping configuration from {{richfaces-components-ui.jar}}. > ---- > Finally, the only thing user would need to define is: > {code:XML|title=web.xml} > > org.richfaces.resourceMapping.mappingFile > META-INF/custom-mapping.properties > > {code} > {code:title=META-INF/custom-mapping.properties} > javax.faces:jsf.js=patched-jsf.js > {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 Jan 26 10:59:49 2012 From: jira-events at lists.jboss.org (Juraj Huska (JIRA)) Date: Thu, 26 Jan 2012 10:59:49 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11923) rich:contextMenu - option to render context menu under mouse focus Message-ID: <1041095407.3568.1327593589409.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Juraj Huska created RF-11923: -------------------------------- Summary: rich:contextMenu - option to render context menu under mouse focus Key: RF-11923 URL: https://issues.jboss.org/browse/RF-11923 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Components: base functionality , component, component-menu, showcase Affects Versions: 4.1.0.Final Reporter: Juraj Huska Priority: Optional It would be nice IMHO to have an option to render context menu right under the mouse focus, like it is for example done in GNOME environment. So when user triggers context menu, then he will not need to move his mouse to select first option, but it will be enough just to click to have selected first option, since that option will be rendered under mouse focus. Nice use case for this is for example demo for rich:context menu from showcase, where only one menu item is in context menu, and takes some time to move the mouse on that option. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 26 11:15:48 2012 From: jira-events at lists.jboss.org (Juraj Huska (JIRA)) Date: Thu, 26 Jan 2012 11:15:48 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11924) showcase - rich:context - tree ContextMenu - header of popup should be bigger Message-ID: <259195289.3587.1327594548872.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Juraj Huska created RF-11924: -------------------------------- Summary: showcase - rich:context - tree ContextMenu - header of popup should be bigger Key: RF-11924 URL: https://issues.jboss.org/browse/RF-11924 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-menu, component-output, component-panels-layout-themes, showcase, skinning Affects Versions: 4.1.0.Final Environment: showcase app - 4.2.0-SNAPSHOT all browsers Reporter: Juraj Huska Priority: Trivial Attachments: contextMenuPopup.png The header of popup invoked from contextMenu in demos for rich:contextMenu, sample tree contextMenu is in some cases too small, and the cross for hiding the popup overlap with the header label. It is when the body of the popup is small in width. For example it is so when user select node USA, then the header of popup adapts the size of body, and the problem is there. Please see the screenshot for further reference. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 26 11:15:49 2012 From: jira-events at lists.jboss.org (Juraj Huska (JIRA)) Date: Thu, 26 Jan 2012 11:15:49 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11924) showcase - rich:context - tree ContextMenu - header of popup should be bigger In-Reply-To: <259195289.3587.1327594548872.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <286321125.3590.1327594549031.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj Huska updated RF-11924: ----------------------------- Attachment: contextMenuPopup.png > showcase - rich:context - tree ContextMenu - header of popup should be bigger > ----------------------------------------------------------------------------- > > Key: RF-11924 > URL: https://issues.jboss.org/browse/RF-11924 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-menu, component-output, component-panels-layout-themes, showcase, skinning > Affects Versions: 4.1.0.Final > Environment: showcase app - 4.2.0-SNAPSHOT > all browsers > Reporter: Juraj Huska > Priority: Trivial > Attachments: contextMenuPopup.png > > > The header of popup invoked from contextMenu in demos for rich:contextMenu, sample tree contextMenu is in some cases too small, and the cross for hiding the popup overlap with the header label. > It is when the body of the popup is small in width. For example it is so when user select node USA, then the header of popup adapts the size of body, and the problem is there. Please see the screenshot for further reference. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 26 11:17:48 2012 From: jira-events at lists.jboss.org (Juraj Huska (JIRA)) Date: Thu, 26 Jan 2012 11:17:48 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11924) showcase - rich:context - tree ContextMenu - header of popup should be bigger In-Reply-To: <259195289.3587.1327594548872.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <13500651.3593.1327594668467.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj Huska updated RF-11924: ----------------------------- Description: *The header of the popup* invoked from contextMenu *in demos for rich:contextMenu*, sample tree contextMenu *is* in some cases *too small*, and then the cross for hiding the popup overlap with the header label. It is when the body of the popup is small in width. For example it is so when user select node USA, then the *header of popup adapts the size of body*, and the problem is there. Please see the screenshot for further reference. was: The header of popup invoked from contextMenu in demos for rich:contextMenu, sample tree contextMenu is in some cases too small, and the cross for hiding the popup overlap with the header label. It is when the body of the popup is small in width. For example it is so when user select node USA, then the header of popup adapts the size of body, and the problem is there. Please see the screenshot for further reference. > showcase - rich:context - tree ContextMenu - header of popup should be bigger > ----------------------------------------------------------------------------- > > Key: RF-11924 > URL: https://issues.jboss.org/browse/RF-11924 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-menu, component-output, component-panels-layout-themes, showcase, skinning > Affects Versions: 4.1.0.Final > Environment: showcase app - 4.2.0-SNAPSHOT > all browsers > Reporter: Juraj Huska > Priority: Trivial > Attachments: contextMenuPopup.png > > > *The header of the popup* invoked from contextMenu *in demos for rich:contextMenu*, sample tree contextMenu *is* in some cases *too small*, and then the cross for hiding the popup overlap with the header label. > It is when the body of the popup is small in width. For example it is so when user select node USA, then the *header of popup adapts the size of body*, and the problem is there. Please see the screenshot for further reference. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 26 11:17:48 2012 From: jira-events at lists.jboss.org (Juraj Huska (JIRA)) Date: Thu, 26 Jan 2012 11:17:48 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11924) showcase - rich:context - tree ContextMenu - header of popup should be bigger In-Reply-To: <259195289.3587.1327594548872.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1060483094.3595.1327594668788.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj Huska updated RF-11924: ----------------------------- Description: *The header of the popup* invoked from contextMenu *in demos for rich:contextMenu*, sample tree contextMenu *is* in some cases *too small*, and then the cross for hiding the popup overlap with the header label. It is when the body of the popup is small in width. For example it is so when user select node USA, then the *header of popup adapts the size of body*, and the problem is there. Please see the *screenshot* for further reference. So the header should have set fixed width. was: *The header of the popup* invoked from contextMenu *in demos for rich:contextMenu*, sample tree contextMenu *is* in some cases *too small*, and then the cross for hiding the popup overlap with the header label. It is when the body of the popup is small in width. For example it is so when user select node USA, then the *header of popup adapts the size of body*, and the problem is there. Please see the screenshot for further reference. > showcase - rich:context - tree ContextMenu - header of popup should be bigger > ----------------------------------------------------------------------------- > > Key: RF-11924 > URL: https://issues.jboss.org/browse/RF-11924 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-menu, component-output, component-panels-layout-themes, showcase, skinning > Affects Versions: 4.1.0.Final > Environment: showcase app - 4.2.0-SNAPSHOT > all browsers > Reporter: Juraj Huska > Priority: Trivial > Attachments: contextMenuPopup.png > > > *The header of the popup* invoked from contextMenu *in demos for rich:contextMenu*, sample tree contextMenu *is* in some cases *too small*, and then the cross for hiding the popup overlap with the header label. > It is when the body of the popup is small in width. For example it is so when user select node USA, then the *header of popup adapts the size of body*, and the problem is there. Please see the *screenshot* for further reference. > So the header should have set fixed width. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 26 12:50:48 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Thu, 26 Jan 2012 12:50:48 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11922) Nesting an a4j:actionListener in a composite component results in a java.io.NotSerializableException In-Reply-To: <340783677.2125.1327537789610.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <2035205747.3841.1327600248396.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-11922: ------------------------------- Environment: JBoss AS 7.0.2, mojarra 2.1 > Nesting an a4j:actionListener in a composite component results in a java.io.NotSerializableException > ---------------------------------------------------------------------------------------------------- > > Key: RF-11922 > URL: https://issues.jboss.org/browse/RF-11922 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.1.0.Final > Environment: JBoss AS 7.0.2, mojarra 2.1 > Reporter: Brian Leathem > Fix For: 4.Future > > > In the code samples below, an a4j:actionListener is nested in a composite component. This results in a java.io.NotSerializableException (stack trace below). > {code:title=actionComposite.xhtml} > > > > > > > > > > > > > > {code} > {code:title=actionListener.xhtml} > > > > > > > > > {code} > {code:title=Stacktrace} > Caused by: java.io.NotSerializableException: org.richfaces.view.facelets.html.ActionListenerHandler > at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1164) [:1.6.0_26] > at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:330) [:1.6.0_26] > at java.util.ArrayList.writeObject(ArrayList.java:570) [:1.6.0_26] > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_26] > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_26] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_26] > at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_26] > at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:945) [:1.6.0_26] > at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1469) [:1.6.0_26] > at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1400) [:1.6.0_26] > at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1158) [:1.6.0_26] > at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1518) [:1.6.0_26] > at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1483) [:1.6.0_26] > at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1400) [:1.6.0_26] > at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1158) [:1.6.0_26] > at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:330) [:1.6.0_26] > at java.util.ArrayList.writeObject(ArrayList.java:570) [:1.6.0_26] > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_26] > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_26] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_26] > at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_26] > at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:945) [:1.6.0_26] > at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1469) [:1.6.0_26] > at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1400) [:1.6.0_26] > at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1158) [:1.6.0_26] > at java.io.ObjectOutputStream.writeArray(ObjectOutputStream.java:1346) [:1.6.0_26] > at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1154) [:1.6.0_26] > at java.io.ObjectOutputStream.writeArray(ObjectOutputStream.java:1346) [:1.6.0_26] > at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1154) [:1.6.0_26] > at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:330) [:1.6.0_26] > at java.util.HashMap.writeObject(HashMap.java:1001) [:1.6.0_26] > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_26] > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_26] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_26] > at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_26] > at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:945) [:1.6.0_26] > at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1469) [:1.6.0_26] > at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1400) [:1.6.0_26] > at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1158) [:1.6.0_26] > at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:330) [:1.6.0_26] > at com.sun.faces.renderkit.ClientSideStateHelper.doWriteState(ClientSideStateHelper.java:325) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > at com.sun.faces.renderkit.ClientSideStateHelper.writeState(ClientSideStateHelper.java:169) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > at com.sun.faces.renderkit.ResponseStateManagerImpl.getViewState(ResponseStateManagerImpl.java:135) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] > ... 28 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 Jan 26 12:59:48 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Thu, 26 Jan 2012 12:59:48 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11883) Support dynamic attachment of the contextMenu In-Reply-To: <80244479.55517.1326480261257.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1432233508.3858.1327600788465.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-11883. -------------------------------- Fix Version/s: 4.2.0.CR1 (was: 4.2-Tracking) Resolution: Done > Support dynamic attachment of the contextMenu > --------------------------------------------- > > Key: RF-11883 > URL: https://issues.jboss.org/browse/RF-11883 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-menu > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 4.2.0.CR1 > > > Support creating a single instance of the contextMenu that can be attached to any component without creating a new contextMenu 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 Jan 26 13:09:48 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 26 Jan 2012 13:09:48 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11909) Custom resource mapping can't simply reuse pre-generated RichFaces resources In-Reply-To: <42430590.13417.1327071978848.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1645343929.3868.1327601388664.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12662182#comment-12662182 ] Luk?? Fry? edited comment on RF-11909 at 1/26/12 1:09 PM: ---------------------------------------------------------- Following *configuration names was renamed* (with backward compatible option to use old param names): {{org.richfaces.*resourceMapping*.enabled}} -> {{org.richfaces.*resourceOptimization*.enabled}} {{org.richfaces.resourceMapping.compressedStages}} -> {{org.richfaces.resourceOptimization.compressionStages}} {{org.richfaces.resourceMapping.packedStages}} -> {{org.richfaces.resourceOptimization.packagingStages}} Following *configuration params stay same*: {{org.richfaces.resourceMapping.mappingFile}} {{org.richfaces.resourceMapping.location}} However it is not necessary to set {{org.richfaces.resourceMapping.enabled}} in order to define custom mappings files. For defining *custom mapping files*, user needs just to either: * create {{META-INF/richfaces/static-resource-mappings.properties}} mapping file on classpath * create custom file on classpath and configure it's name in {{org.richfaces.resourceMapping.mappingFile}} (comma separated list of files) Configurations from mapping files will be applied in *following order* (the last one will take precedence), it gives user chance to redefine mappings: * resource loading optimization ({{org.richfaces.resourceMapping.enabled}}) * {{META-INF/richfaces/static-resource-mappings.properties}} * custom files in {{org.richfaces.resourceMapping.mappingFile}} was (Author: lfryc): Following **configuration names was renamed** (with backward compatible option to use old param names): {{org.richfaces.*resourceMapping*.enabled}} -> {{org.richfaces.*resourceLoading.optimization*.enabled}} {{org.richfaces.resourceMapping.compressedStages}} -> {{org.richfaces.resourceLoading.optimization.compression.stages}} {{org.richfaces.resourceMapping.packedStages}} -> {{org.richfaces.resourceLoading.optimization.packaging.stages}} Following *configuration params stay same*: {{org.richfaces.resourceMapping.mappingFile}} {{org.richfaces.resourceMapping.location}} However it is not necessary to set {{org.richfaces.resourceMapping.enabled}} in order to define custom mappings files. For defining *custom mapping files*, user needs just to either: * create {{META-INF/richfaces/static-resource-mappings.properties}} mapping file on classpath * create custom file on classpath and configure it's name in {{org.richfaces.resourceMapping.mappingFile}} (comma separated list of files) Configurations from mapping files will be applied in *following order* (the last one will take precedence), it gives user chance to redefine mappings: * resource loading optimization ({{org.richfaces.resourceMapping.enabled}}) * {{META-INF/richfaces/static-resource-mappings.properties}} * custom files in {{org.richfaces.resourceMapping.mappingFile}} > Custom resource mapping can't simply reuse pre-generated RichFaces resources > ---------------------------------------------------------------------------- > > Key: RF-11909 > URL: https://issues.jboss.org/browse/RF-11909 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 4.1.0.Final > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 4.2.0.CR1 > > > Custom resource mapping can't simply reuse pre-generated RichFaces resources. > Use case: > * user wants to use resource mapping for several purposes > ** using RichFaces pre-generated resources in {{richfaces-components-ui.jar/META-INF/resources/org.richfaces.staticResources//...}} > ** using custom mappings like {{javax.faces:jsf.js=patched-jsf.js}} using e.g. {{my.war/resources/patched-jsf.js}} > ---- > With {{4.1.0.Final}}, configuration of {{org.richfaces.resourceMapping.location}} is by default referring to root of packed resources: > {code}#{facesContext.externalContext.requestContextPath}/org.richfaces.resources/javax.faces.resource/org.richfaces.staticResource/#{a4j.version.implementationVersion}/%Features%/#{resourceLocation} > {code} > and mapping file looks like: > {code} > jquery.js=jquery.js > {code} > When you want to reuse RichFaces mappings, you [need to copy mapping file from {{richfaces-component-ui.jar}}|http://docs.jboss.org/richfaces/latest_4_X/Developer_Guide/en-US/html/chap-Developer_Guide-Advanced_features.html#d0e1692] and extend it by custom properties. > and additionally you need to place custom resources to directory called specifically for RF, like: > {code} > my.war/resources/org.richfaces.staticResource/4.1.0.Final/PackedCompressed/patched-jsf.js > {code} > Other options: > * change all mappings in {{custom-mappings.properties}} at own > * copy all resources from {{richfaces-component-ui.jar}} to own location > ---- > For simplification, I suggest default resource mapping location root be > {code} > #{facesContext.externalContext.requestContextPath}/org.richfaces.resources/javax.faces.resource/#{resourceLocation} > {code} > so it would refer to JSF resources root ({{my.war/resources}} or {{some.jar/META-INF/resources}}) by default. > Then, we would force {{richfaces-components-ui.jar}} to define mappings which points from JSF resources root, e.g.: > {code} > jquery.js=org.richfaces.staticResource/4.1.0.Final/PackedCompressed/jquery.js > {code} > ---- > Additionally, Brian suggested support for multiple {{mapping.properties}} files, so their content will be merged. > It means user won't be forced to copy&paste RichFaces mapping configuration from {{richfaces-components-ui.jar}}. > ---- > Finally, the only thing user would need to define is: > {code:XML|title=web.xml} > > org.richfaces.resourceMapping.mappingFile > META-INF/custom-mapping.properties > > {code} > {code:title=META-INF/custom-mapping.properties} > javax.faces:jsf.js=patched-jsf.js > {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 Jan 26 13:09:49 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 26 Jan 2012 13:09:49 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11909) Custom resource mapping can't simply reuse pre-generated RichFaces resources In-Reply-To: <42430590.13417.1327071978848.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <549414178.3873.1327601389886.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved RF-11909. ----------------------------- Resolution: Done > Custom resource mapping can't simply reuse pre-generated RichFaces resources > ---------------------------------------------------------------------------- > > Key: RF-11909 > URL: https://issues.jboss.org/browse/RF-11909 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 4.1.0.Final > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 4.2.0.CR1 > > > Custom resource mapping can't simply reuse pre-generated RichFaces resources. > Use case: > * user wants to use resource mapping for several purposes > ** using RichFaces pre-generated resources in {{richfaces-components-ui.jar/META-INF/resources/org.richfaces.staticResources//...}} > ** using custom mappings like {{javax.faces:jsf.js=patched-jsf.js}} using e.g. {{my.war/resources/patched-jsf.js}} > ---- > With {{4.1.0.Final}}, configuration of {{org.richfaces.resourceMapping.location}} is by default referring to root of packed resources: > {code}#{facesContext.externalContext.requestContextPath}/org.richfaces.resources/javax.faces.resource/org.richfaces.staticResource/#{a4j.version.implementationVersion}/%Features%/#{resourceLocation} > {code} > and mapping file looks like: > {code} > jquery.js=jquery.js > {code} > When you want to reuse RichFaces mappings, you [need to copy mapping file from {{richfaces-component-ui.jar}}|http://docs.jboss.org/richfaces/latest_4_X/Developer_Guide/en-US/html/chap-Developer_Guide-Advanced_features.html#d0e1692] and extend it by custom properties. > and additionally you need to place custom resources to directory called specifically for RF, like: > {code} > my.war/resources/org.richfaces.staticResource/4.1.0.Final/PackedCompressed/patched-jsf.js > {code} > Other options: > * change all mappings in {{custom-mappings.properties}} at own > * copy all resources from {{richfaces-component-ui.jar}} to own location > ---- > For simplification, I suggest default resource mapping location root be > {code} > #{facesContext.externalContext.requestContextPath}/org.richfaces.resources/javax.faces.resource/#{resourceLocation} > {code} > so it would refer to JSF resources root ({{my.war/resources}} or {{some.jar/META-INF/resources}}) by default. > Then, we would force {{richfaces-components-ui.jar}} to define mappings which points from JSF resources root, e.g.: > {code} > jquery.js=org.richfaces.staticResource/4.1.0.Final/PackedCompressed/jquery.js > {code} > ---- > Additionally, Brian suggested support for multiple {{mapping.properties}} files, so their content will be merged. > It means user won't be forced to copy&paste RichFaces mapping configuration from {{richfaces-components-ui.jar}}. > ---- > Finally, the only thing user would need to define is: > {code:XML|title=web.xml} > > org.richfaces.resourceMapping.mappingFile > META-INF/custom-mapping.properties > > {code} > {code:title=META-INF/custom-mapping.properties} > javax.faces:jsf.js=patched-jsf.js > {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 Jan 26 15:09:48 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 26 Jan 2012 15:09:48 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11890) ResourceServlet does not set HTTP headers for caching In-Reply-To: <896407184.2481.1326733518446.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <384273869.4169.1327608588548.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12662285#comment-12662285 ] Luk?? Fry? commented on RF-11890: --------------------------------- Even though headers are not set for resources server by ResourceServlet, caching works on browser side out of the box, verified on RichFaces Showcase hosting http://showcase.richfaces.org/ > ResourceServlet does not set HTTP headers for caching > ----------------------------------------------------- > > Key: RF-11890 > URL: https://issues.jboss.org/browse/RF-11890 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 4.2.0.CR1 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > > {quote} > All RichFaces resources served by Faces Servlet have headers set appropriately for caching. > (You can check it by removing your Filter and turning resourceMapping=false). > > I assume you have problems with ResourceServlet where resources does not go through RichFaces ResourceHandler, so headers are set as for any other JSF resource - which means (AFAIK) no caching at all. > {quote} > This assumption needs to be verified before implementing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 26 15:09:48 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 26 Jan 2012 15:09:48 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11890) ResourceServlet does not set HTTP headers for caching In-Reply-To: <896407184.2481.1326733518446.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1794069512.4170.1327608588582.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? reassigned RF-11890: ------------------------------- Assignee: (was: Luk?? Fry?) > ResourceServlet does not set HTTP headers for caching > ----------------------------------------------------- > > Key: RF-11890 > URL: https://issues.jboss.org/browse/RF-11890 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 4.2.0.CR1 > Reporter: Luk?? Fry? > > {quote} > All RichFaces resources served by Faces Servlet have headers set appropriately for caching. > (You can check it by removing your Filter and turning resourceMapping=false). > > I assume you have problems with ResourceServlet where resources does not go through RichFaces ResourceHandler, so headers are set as for any other JSF resource - which means (AFAIK) no caching at all. > {quote} > This assumption needs to be verified before implementing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 26 15:09:48 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 26 Jan 2012 15:09:48 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11890) ResourceServlet does not set HTTP headers for caching In-Reply-To: <896407184.2481.1326733518446.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1541710495.4173.1327608588693.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated RF-11890: ---------------------------- Comment: was deleted (was: Check also that regular RichFaces resources have headers setup properly when resource mapping is off.) > ResourceServlet does not set HTTP headers for caching > ----------------------------------------------------- > > Key: RF-11890 > URL: https://issues.jboss.org/browse/RF-11890 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 4.2.0.CR1 > Reporter: Luk?? Fry? > > {quote} > All RichFaces resources served by Faces Servlet have headers set appropriately for caching. > (You can check it by removing your Filter and turning resourceMapping=false). > > I assume you have problems with ResourceServlet where resources does not go through RichFaces ResourceHandler, so headers are set as for any other JSF resource - which means (AFAIK) no caching at all. > {quote} > This assumption needs to be verified before implementing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 26 16:56:48 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Thu, 26 Jan 2012 16:56:48 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11875) rich:extendedDataTable in ajax loading mode, crashes when dataset length changes between requests In-Reply-To: <1944546618.3014.1326375801528.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1251116912.4337.1327615008389.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-11875: ------------------------------- Fix Version/s: 4.3-Tracking Assignee: (was: Brian Leathem) > rich:extendedDataTable in ajax loading mode, crashes when dataset length changes between requests > ------------------------------------------------------------------------------------------------- > > Key: RF-11875 > URL: https://issues.jboss.org/browse/RF-11875 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-ScrollableDataTable > Affects Versions: 4.1.0.Final > Environment: JSF-RI 2.0, Tomcat 6.0.29 / JBoss AS 7.0.2.Final > Reporter: Dmitry Volkov > Fix For: 4.3-Tracking > > Attachments: richfaces-showcase-jbas7.war > > > rich:extendedDataTable in ajax loading mode(clientRows=".."), crashes when dataset length changes between requests. > It makes ajax loading mode unusable for database paging. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 26 18:47:48 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Thu, 26 Jan 2012 18:47:48 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11879) Add examle of usage of a4j:actionListener into RF showcase In-Reply-To: <43091471.3804.1326385042424.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1774317855.4448.1327621668445.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-11879. -------------------------------- Resolution: Done Added an actionListener example to the showcase > Add examle of usage of a4j:actionListener into RF showcase > ---------------------------------------------------------- > > Key: RF-11879 > URL: https://issues.jboss.org/browse/RF-11879 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: showcase > Affects Versions: 4.1.0.Final > Reporter: Marek Novotny > Assignee: Brian Leathem > Priority: Minor > Fix For: 4.2.0.CR1 > > > a4j:actionListener is not presented in showcase example -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 26 19:12:48 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Thu, 26 Jan 2012 19:12:48 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11588) HeaderClass is ignored on ExtendedDataTable column In-Reply-To: <1427004328.27237.1319584545776.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <965077799.4475.1327623168591.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-11588. -------------------------------- Resolution: Done Funny how somethings are more clear when you look at them the next day. I've resolved this issue by moving the headerClass cssClass down one level in the rendered html, allowing it to fully override the pre-packaged classes. > HeaderClass is ignored on ExtendedDataTable column > -------------------------------------------------- > > Key: RF-11588 > URL: https://issues.jboss.org/browse/RF-11588 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.1.0.Milestone3 > Reporter: Cody Lerum > Assignee: Brian Leathem > Priority: Trivial > Fix For: 4.2.0.CR1 > > > When a header class is defined on a rich:column inside an rich:extendedDataTable it is ignored > Assume > {code} > > Foo > > > {code} > What is rendered is > {code} > > {code} > My style left is applied but the header is one level lower and has rf-edt-hdr-c-cnt style which will always make it center -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 26 19:19:48 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Thu, 26 Jan 2012 19:19:48 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11919) showcase - names of some samples do not follow camel case naming convention In-Reply-To: <1840945137.21442.1327486818320.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1751951958.4482.1327623588404.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-11919. -------------------------------- Resolution: Done > showcase - names of some samples do not follow camel case naming convention > --------------------------------------------------------------------------- > > Key: RF-11919 > URL: https://issues.jboss.org/browse/RF-11919 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: qe, showcase > Environment: showcase app > Reporter: Juraj Huska > Assignee: Brian Leathem > Priority: Trivial > Fix For: 4.2.0.CR1 > > > There are some samples in showcase which do not follow camel case naming convention. First of all it is inconsistent with other sample names and secondly it makes some problems with showcase tests, since I am using method for loading the appropriate page according to the test class name, which should be obviously named using camel case. Can you please rename following samples ? > component demo - sample > ######################## > a4j:status - viewusage, referencedusage > a4j:outputPanel - Auto update for h:messages 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 Fri Jan 27 06:53:50 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 27 Jan 2012 06:53:50 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11533) Notify and IE 8: can't close a message In-Reply-To: <1754239113.29618.1318507637333.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <229955176.5131.1327665230222.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12662397#comment-12662397 ] Luk?? Fry? commented on RF-11533: --------------------------------- Difference between Showcase and validator-demo was {{default-grid-reset.css}} which contained definition {code} div { margin: 0 }; {code} by trying to minimize the effect, I have configured: {code} div.rf-ntf-sum { margin: 0 }; {code} and it now works great in IE8. > Notify and IE 8: can't close a message > -------------------------------------- > > Key: RF-11533 > URL: https://issues.jboss.org/browse/RF-11533 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.1.0.Milestone3 > Environment: ?RichFaces 4.1.0.20111011-M3 r.68406156c3d647eee75816d4bd6a29a66b0b5a2f > ?Metamer 4.1.0.20111011-M3 r.22776 > ?Mojarra 2.1.3-SNAPSHOT > ?Apache Tomcat 7.0.22 > ?Java(TM) SE Runtime Environment 1.6.0_27-b07 @ Windows Server 2008 > ?Internet Explorer 8.0 @ Win32 > Reporter: Jan Papousek > Assignee: Luk?? Fry? > Fix For: 4.2.0.CR1 > > > Notify messages can't be closed in IE 8. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 27 06:55:48 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 27 Jan 2012 06:55:48 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11533) Notify and IE 8: can't close a message In-Reply-To: <1754239113.29618.1318507637333.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1672512078.5135.1327665348725.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved RF-11533. ----------------------------- Resolution: Done > Notify and IE 8: can't close a message > -------------------------------------- > > Key: RF-11533 > URL: https://issues.jboss.org/browse/RF-11533 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.1.0.Milestone3 > Environment: ?RichFaces 4.1.0.20111011-M3 r.68406156c3d647eee75816d4bd6a29a66b0b5a2f > ?Metamer 4.1.0.20111011-M3 r.22776 > ?Mojarra 2.1.3-SNAPSHOT > ?Apache Tomcat 7.0.22 > ?Java(TM) SE Runtime Environment 1.6.0_27-b07 @ Windows Server 2008 > ?Internet Explorer 8.0 @ Win32 > Reporter: Jan Papousek > Assignee: Luk?? Fry? > Fix For: 4.2.0.CR1 > > > Notify messages can't be closed in IE 8. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 27 06:57:48 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 27 Jan 2012 06:57:48 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11533) Notify and IE 8: can't close a message In-Reply-To: <1754239113.29618.1318507637333.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <36662549.5143.1327665468644.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12662397#comment-12662397 ] Luk?? Fry? edited comment on RF-11533 at 1/27/12 6:56 AM: ---------------------------------------------------------- I tried to find difference between Showcase and {{validator-demo}}. It was {{default-grid-reset.css}} from {{validator-demo}} which contained definition {code} div { margin: 0 }; {code} by trying to minimize the effect, I have configured: {code} div.rf-ntf-sum { margin: 0 }; {code} and it now works great in IE8. was (Author: lfryc): Difference between Showcase and validator-demo was {{default-grid-reset.css}} which contained definition {code} div { margin: 0 }; {code} by trying to minimize the effect, I have configured: {code} div.rf-ntf-sum { margin: 0 }; {code} and it now works great in IE8. > Notify and IE 8: can't close a message > -------------------------------------- > > Key: RF-11533 > URL: https://issues.jboss.org/browse/RF-11533 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.1.0.Milestone3 > Environment: ?RichFaces 4.1.0.20111011-M3 r.68406156c3d647eee75816d4bd6a29a66b0b5a2f > ?Metamer 4.1.0.20111011-M3 r.22776 > ?Mojarra 2.1.3-SNAPSHOT > ?Apache Tomcat 7.0.22 > ?Java(TM) SE Runtime Environment 1.6.0_27-b07 @ Windows Server 2008 > ?Internet Explorer 8.0 @ Win32 > Reporter: Jan Papousek > Assignee: Luk?? Fry? > Fix For: 4.2.0.CR1 > > > Notify messages can't be closed in IE 8. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 27 07:05:49 2012 From: jira-events at lists.jboss.org (Juraj Huska (JIRA)) Date: Fri, 27 Jan 2012 07:05:49 -0500 (EST) 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: <1904423781.5165.1327665949237.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=12662401#comment-12662401 ] Juraj Huska commented on RF-11905: ---------------------------------- I have successfully tried what was described in the AS7-2045 as workaround, with positive effects. So the problem can be solved in these ways: *1.* use proposed workaround, which means alter default datasource configuration of JBoss AS 7, which means to add to documentation, that this error is thrown if it is not set.... *2.* do not use datasource for connecting to database but use proper setting of connection, and then the workaround can be applied to showcase configuration instead of container one *3.* change hibernate.hbm2ddl.auto from create-drop to only create, which takes care of that exception, since it will not try to drop database schema after shutting down of AS, but instead will create new schema in each deploy Personally, I like the most the option 3. > 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: Juraj Huska > Priority: Minor > > 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 Jan 27 07:07:48 2012 From: jira-events at lists.jboss.org (Juraj Huska (JIRA)) Date: Fri, 27 Jan 2012 07:07:48 -0500 (EST) 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: <143449697.5170.1327666068672.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 updated RF-11905: ----------------------------- Assignee: (was: Juraj Huska) > 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 > Priority: Minor > > 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 Jan 27 07:09:49 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 27 Jan 2012 07:09:49 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11888) Resource Servlet can't handle query string appended to resource url In-Reply-To: <787852126.1337.1326719298230.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <849767741.5179.1327666189353.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12662404#comment-12662404 ] Luk?? Fry? commented on RF-11888: --------------------------------- You certainly don't need to append version suffix for RichFaces pre-generated resources, but for other resources served by ResourceServlet, you might want to. We are limiting what query parameters can be appended to ResourceServlet managed requests since there are security implications when user could append whatever query param (like {{ln=*}}). However I'm open to discuss addition of some safe attributes like {{v=*}} which would enable us to use versions with custom resources served by ResourceServlet (refered to as "resource mapping" feature). > Resource Servlet can't handle query string appended to resource url > ------------------------------------------------------------------- > > Key: RF-11888 > URL: https://issues.jboss.org/browse/RF-11888 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: resource handling > Affects Versions: 4.1.0.Final > Environment: Glassfish 3.1.1 (NO Tomcat)/Mojarra 2.1.3 Chrome browser - > Reporter: Brendan Healey > Assignee: Luk?? Fry? > Priority: Critical > > A custom resource handler (http://blogs.oracle.com/rlubke/entry/jsf_2_0_new_feature) > can be used to append a version string (i.e. ?v=23) to a resource url to force a > browser to refresh a resource rather than use any cached version. > At present any appending of a version string causes a 404 response status, for example: > Request URL: > https://localhost:8181/MyApp/org.richfaces.resources/javax.faces.resource/org.richfaces.staticResource/4.1.0.Final/PackedCompressed/blueSky/packed/packed.css?v=23 > Removing the url parameter makes it work ok. As you can see I have resourceMapping > enabled. > This is essential to cause a browser to issue a request to the server if a static > resource is held in a browser cache and is not expired, but you've upgraded the > richfaces version. You have to have a way to invalidate the cache, and I'm not > seeing how this can be done in a sensible way. You can set the Cache-Control > no-cache header, but I'd need to do this in a way that says "I've just upgraded > richfaces, so don't use the cache, issue a request to the server for the resource, > but cache the result and use this until the next time". -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 27 07:09:49 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 27 Jan 2012 07:09:49 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11888) Resource Servlet can't handle query string appended to resource url In-Reply-To: <787852126.1337.1326719298230.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <324160234.5182.1327666189496.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? reassigned RF-11888: ------------------------------- Assignee: (was: Luk?? Fry?) > Resource Servlet can't handle query string appended to resource url > ------------------------------------------------------------------- > > Key: RF-11888 > URL: https://issues.jboss.org/browse/RF-11888 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: resource handling > Affects Versions: 4.1.0.Final > Environment: Glassfish 3.1.1 (NO Tomcat)/Mojarra 2.1.3 Chrome browser - > Reporter: Brendan Healey > Priority: Critical > > A custom resource handler (http://blogs.oracle.com/rlubke/entry/jsf_2_0_new_feature) > can be used to append a version string (i.e. ?v=23) to a resource url to force a > browser to refresh a resource rather than use any cached version. > At present any appending of a version string causes a 404 response status, for example: > Request URL: > https://localhost:8181/MyApp/org.richfaces.resources/javax.faces.resource/org.richfaces.staticResource/4.1.0.Final/PackedCompressed/blueSky/packed/packed.css?v=23 > Removing the url parameter makes it work ok. As you can see I have resourceMapping > enabled. > This is essential to cause a browser to issue a request to the server if a static > resource is held in a browser cache and is not expired, but you've upgraded the > richfaces version. You have to have a way to invalidate the cache, and I'm not > seeing how this can be done in a sensible way. You can set the Cache-Control > no-cache header, but I'd need to do this in a way that says "I've just upgraded > richfaces, so don't use the cache, issue a request to the server for the resource, > but cache the result and use this until the next time". -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 27 07:31:48 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 27 Jan 2012 07:31:48 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11867) showcase - rich:hotKey - pressing of home or end key causes moving of whole page instead of just selected/removing all cities on FF 3.6.x In-Reply-To: <1258943306.48046.1326104829526.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1824809347.5217.1327667508804.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? reassigned RF-11867: ------------------------------- Assignee: Juraj Huska (was: Luk?? Fry?) Juraj, I have tried with FF {{3.6.21}} on {{Ubuntu}} and it works fine. Could you please check that you have tried that with latest Showcase {{4.2.0-SNAPSHOT}}? > showcase - rich:hotKey - pressing of home or end key causes moving of whole page instead of just selected/removing all cities on FF 3.6.x > ----------------------------------------------------------------------------------------------------------------------------------------- > > Key: RF-11867 > URL: https://issues.jboss.org/browse/RF-11867 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-misc, showcase > Affects Versions: 4.2.0.CR1 > Environment: container: Tomcat 7.0.20, JBoss AS 6.0.0.Final > browser: Firefox 3.6.24 > Reporter: Juraj Huska > Assignee: Juraj Huska > Priority: Minor > > The current binding for selecting/removing all cities in the demo for rich:hotKey are 'home' and 'end' buttons respectively. > It works as expected on Chrome and Firefox 8, however it is not working as expected on *Firefox 3.6.x*. > *Pressing of 'home' of 'end' button (city is selected, so the pickList has user focus) causes moving of the whole page, like the pickList has no focus. The cities are added/removed too, but with the side effect of the page moving, which indeed looks a little ugly.* > The workaround can be to use other keys. > What I would really appreciate is to bind some key to the switching between the two panels. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 27 07:33:49 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 27 Jan 2012 07:33:49 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11868) showcase - rich:hotKey - using bound hotKeys generates JS warning on FF 3.6.x In-Reply-To: <992167140.48074.1326105790453.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <2042214785.5221.1327667629840.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12662409#comment-12662409 ] Luk?? Fry? commented on RF-11868: --------------------------------- Since this warning is outside of our code and the warnings are shown only in Error Console or in developer tools, I suggest to do not fix it. > showcase - rich:hotKey - using bound hotKeys generates JS warning on FF 3.6.x > ----------------------------------------------------------------------------- > > Key: RF-11868 > URL: https://issues.jboss.org/browse/RF-11868 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-misc, showcase > Affects Versions: 4.2.0.CR1 > Environment: container: all > browser: Firefox 3.6.x > Reporter: Juraj Huska > Assignee: Luk?? Fry? > Priority: Minor > > Using of bound hot keys in the demo for rich:hotKey generates on Firefox 3.6.x a warning: > {code} > The 'charCode' property of a keydown event should not be used. The value is meaningless. > {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 Jan 27 07:33:50 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 27 Jan 2012 07:33:50 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11868) showcase - rich:hotKey - using bound hotKeys generates JS warning on FF 3.6.x In-Reply-To: <992167140.48074.1326105790453.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <880480107.5224.1327667630018.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved RF-11868. ----------------------------- Resolution: Won't Fix Please reopen if required. > showcase - rich:hotKey - using bound hotKeys generates JS warning on FF 3.6.x > ----------------------------------------------------------------------------- > > Key: RF-11868 > URL: https://issues.jboss.org/browse/RF-11868 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-misc, showcase > Affects Versions: 4.2.0.CR1 > Environment: container: all > browser: Firefox 3.6.x > Reporter: Juraj Huska > Assignee: Luk?? Fry? > Priority: Minor > > Using of bound hot keys in the demo for rich:hotKey generates on Firefox 3.6.x a warning: > {code} > The 'charCode' property of a keydown event should not be used. The value is meaningless. > {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 Jan 27 07:33:52 2012 From: jira-events at lists.jboss.org (Martin Dames (JIRA)) Date: Fri, 27 Jan 2012 07:33:52 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-3566) Can't use messages with fileUpload In-Reply-To: <14991295.1211962969325.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <120844144.5248.1327667632723.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-3566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12662411#comment-12662411 ] Martin Dames commented on RF-3566: ---------------------------------- My workaround for the negative case is to throw an exception in upload listener. Negative case could be the violation of total upload size if file is too big. This will force an "upload.transferError" and messages will be displayed. But I have no workaround for the positive case. > Can't use messages with fileUpload > ---------------------------------- > > Key: RF-3566 > URL: https://issues.jboss.org/browse/RF-3566 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 3.2.1 > Reporter: Ilya Shaikovsky > Assignee: Konstantin Mishin > Fix For: 4.0.0.Milestone5 > > > http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4153840#4153840 > Using his code in demosite listener I'm getting next behaviour. > "Transfer error occuried" error in file upload status. > But rich:messages which added to the page doesn't show anything. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 27 07:35:50 2012 From: jira-events at lists.jboss.org (Martin Dames (JIRA)) Date: Fri, 27 Jan 2012 07:35:50 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-3566) Can't use messages with fileUpload In-Reply-To: <14991295.1211962969325.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <1936149605.5276.1327667750619.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-3566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12662411#comment-12662411 ] Martin Dames edited comment on RF-3566 at 1/27/12 7:33 AM: ----------------------------------------------------------- My workaround for the negative case is to throw an exception in upload listener. Negative case could be the violation of total upload size if file is too big. This will force an "upload.transferError" and messages will be displayed. But I have no workaround for the positive case. (Richfaces 3.3.3) was (Author: specialagent): My workaround for the negative case is to throw an exception in upload listener. Negative case could be the violation of total upload size if file is too big. This will force an "upload.transferError" and messages will be displayed. But I have no workaround for the positive case. > Can't use messages with fileUpload > ---------------------------------- > > Key: RF-3566 > URL: https://issues.jboss.org/browse/RF-3566 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 3.2.1 > Reporter: Ilya Shaikovsky > Assignee: Konstantin Mishin > Fix For: 4.0.0.Milestone5 > > > http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4153840#4153840 > Using his code in demosite listener I'm getting next behaviour. > "Transfer error occuried" error in file upload status. > But rich:messages which added to the page doesn't show anything. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 27 07:49:48 2012 From: jira-events at lists.jboss.org (Juraj Huska (JIRA)) Date: Fri, 27 Jan 2012 07:49:48 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11867) showcase - rich:hotKey - pressing of home or end key causes moving of whole page instead of just selected/removing all cities on FF 3.6.x In-Reply-To: <1258943306.48046.1326104829526.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1696594036.5289.1327668588527.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12662413#comment-12662413 ] Juraj Huska commented on RF-11867: ---------------------------------- I have tried it again, with current snapshots on {{Firefox 3.6.25}} and I can not reproduce it again. > showcase - rich:hotKey - pressing of home or end key causes moving of whole page instead of just selected/removing all cities on FF 3.6.x > ----------------------------------------------------------------------------------------------------------------------------------------- > > Key: RF-11867 > URL: https://issues.jboss.org/browse/RF-11867 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-misc, showcase > Affects Versions: 4.2.0.CR1 > Environment: container: Tomcat 7.0.20, JBoss AS 6.0.0.Final > browser: Firefox 3.6.24 > Reporter: Juraj Huska > Assignee: Juraj Huska > Priority: Minor > > The current binding for selecting/removing all cities in the demo for rich:hotKey are 'home' and 'end' buttons respectively. > It works as expected on Chrome and Firefox 8, however it is not working as expected on *Firefox 3.6.x*. > *Pressing of 'home' of 'end' button (city is selected, so the pickList has user focus) causes moving of the whole page, like the pickList has no focus. The cities are added/removed too, but with the side effect of the page moving, which indeed looks a little ugly.* > The workaround can be to use other keys. > What I would really appreciate is to bind some key to the switching between the two panels. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 27 07:53:48 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 27 Jan 2012 07:53:48 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11867) showcase - rich:hotKey - pressing of home or end key causes moving of whole page instead of just selected/removing all cities on FF 3.6.x In-Reply-To: <1258943306.48046.1326104829526.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1795793877.5298.1327668828428.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved RF-11867. ----------------------------- Assignee: Luk?? Fry? (was: Juraj Huska) Resolution: Cannot Reproduce Bug > showcase - rich:hotKey - pressing of home or end key causes moving of whole page instead of just selected/removing all cities on FF 3.6.x > ----------------------------------------------------------------------------------------------------------------------------------------- > > Key: RF-11867 > URL: https://issues.jboss.org/browse/RF-11867 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-misc, showcase > Affects Versions: 4.2.0.CR1 > Environment: container: Tomcat 7.0.20, JBoss AS 6.0.0.Final > browser: Firefox 3.6.24 > Reporter: Juraj Huska > Assignee: Luk?? Fry? > Priority: Minor > > The current binding for selecting/removing all cities in the demo for rich:hotKey are 'home' and 'end' buttons respectively. > It works as expected on Chrome and Firefox 8, however it is not working as expected on *Firefox 3.6.x*. > *Pressing of 'home' of 'end' button (city is selected, so the pickList has user focus) causes moving of the whole page, like the pickList has no focus. The cities are added/removed too, but with the side effect of the page moving, which indeed looks a little ugly.* > The workaround can be to use other keys. > What I would really appreciate is to bind some key to the switching between the two panels. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 27 07:53:48 2012 From: jira-events at lists.jboss.org (Juraj Huska (JIRA)) Date: Fri, 27 Jan 2012 07:53:48 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11867) showcase - rich:hotKey - pressing of home or end key causes moving of whole page instead of just selected/removing all cities on FF 3.6.x In-Reply-To: <1258943306.48046.1326104829526.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <115289764.5300.1327668828493.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj Huska closed RF-11867. ---------------------------- > showcase - rich:hotKey - pressing of home or end key causes moving of whole page instead of just selected/removing all cities on FF 3.6.x > ----------------------------------------------------------------------------------------------------------------------------------------- > > Key: RF-11867 > URL: https://issues.jboss.org/browse/RF-11867 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-misc, showcase > Affects Versions: 4.2.0.CR1 > Environment: container: Tomcat 7.0.20, JBoss AS 6.0.0.Final > browser: Firefox 3.6.24 > Reporter: Juraj Huska > Assignee: Luk?? Fry? > Priority: Minor > > The current binding for selecting/removing all cities in the demo for rich:hotKey are 'home' and 'end' buttons respectively. > It works as expected on Chrome and Firefox 8, however it is not working as expected on *Firefox 3.6.x*. > *Pressing of 'home' of 'end' button (city is selected, so the pickList has user focus) causes moving of the whole page, like the pickList has no focus. The cities are added/removed too, but with the side effect of the page moving, which indeed looks a little ugly.* > The workaround can be to use other keys. > What I would really appreciate is to bind some key to the switching between the two panels. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 27 10:33:49 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 27 Jan 2012 10:33:49 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11925) PushHandlerFilter - release SessionManager reference at destroy Message-ID: <755697460.5872.1327678429352.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Luk?? Fry? created RF-11925: ------------------------------- Summary: PushHandlerFilter - release SessionManager reference at destroy Key: RF-11925 URL: https://issues.jboss.org/browse/RF-11925 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: core Affects Versions: 4.2.0.CR1 Reporter: Luk?? Fry? Fix For: 4.2.0.CR1 >From review: https://source.jboss.org/cru/REV-RF-12#c186 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 27 10:33:49 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 27 Jan 2012 10:33:49 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11925) PushHandlerFilter - release SessionManager reference at destroy In-Reply-To: <755697460.5872.1327678429352.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <2106614221.5874.1327678429867.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? reassigned RF-11925: ------------------------------- Assignee: Luk?? Fry? > PushHandlerFilter - release SessionManager reference at destroy > --------------------------------------------------------------- > > Key: RF-11925 > URL: https://issues.jboss.org/browse/RF-11925 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 4.2.0.CR1 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 4.2.0.CR1 > > > From review: > https://source.jboss.org/cru/REV-RF-12#c186 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 27 11:02:48 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 27 Jan 2012 11:02:48 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11925) PushHandlerFilter - release SessionManager reference at destroy In-Reply-To: <755697460.5872.1327678429352.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <475897319.5899.1327680168538.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved RF-11925. ----------------------------- Resolution: Done > PushHandlerFilter - release SessionManager reference at destroy > --------------------------------------------------------------- > > Key: RF-11925 > URL: https://issues.jboss.org/browse/RF-11925 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 4.2.0.CR1 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 4.2.0.CR1 > > > From review: > https://source.jboss.org/cru/REV-RF-12#c186 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 27 12:17:49 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Fri, 27 Jan 2012 12:17:49 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11838) Warning in Chrome console for pages with ajax In-Reply-To: <836209596.24520.1324389969366.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <982875866.6040.1327684669210.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12662465#comment-12662465 ] Brian Leathem commented on RF-11838: ------------------------------------ In richfaces-queue.js, we copy the event (otherwise IE fails) on [Line 129|https://github.com/richfaces/core/blob/develop/impl/src/main/resources/META-INF/resources/richfaces-queue.js#L129]: {code:title=richfaces-queue.js|Line 129} this.event = $.extend({}, event); {code} Since layerX and layerY are still properties of the Webkit event (they have not *yet* been removed), we are copying them in our event copy. The access to the event properties triggers the error. On solution is to remove the properties from the event prior to copying the event, as investigated quite thoroughly by the jsperf team: http://jsperf.com/removing-event-props/2 > Warning in Chrome console for pages with ajax > --------------------------------------------- > > Key: RF-11838 > URL: https://issues.jboss.org/browse/RF-11838 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: compatibility > Affects Versions: 4.1.0.Final > Environment: Google Chrome 16.0.912.63 > Reporter: Pavol Pitonak > Fix For: 4.2.0.CR1 > > > # open Showcase in Chrome http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=ajax&skin=blueSky > # open browser console > # type "xxx" into input > result: > The following warning is displayed in browser console 6 times (twice for each Ajax request). Seems to be Chrome-specific and seems not to influence functionality of any component. > {quote} > event.layerX and event.layerY are broken and deprecated in WebKit. They will be removed from the engine in the near future. > {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 Jan 27 12:26:48 2012 From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA)) Date: Fri, 27 Jan 2012 12:26:48 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11926) Unit tests failures in core module Message-ID: <1481588008.6051.1327685208437.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Pavol Pitonak created RF-11926: ---------------------------------- Summary: Unit tests failures in core module Key: RF-11926 URL: https://issues.jboss.org/browse/RF-11926 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: tests - unit Environment: RichFaces 4.2.0-SNAPSHOT Reporter: Pavol Pitonak Jenkins build for core module finished with 26 failures in unit tests. http://hudson.qa.jboss.com/hudson/view/RF-4.0/job/richfaces-4.2-core/227/ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 27 12:28:48 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Fri, 27 Jan 2012 12:28:48 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11926) Unit tests failures in core module In-Reply-To: <1481588008.6051.1327685208437.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1595535102.6062.1327685328934.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-11926: ------------------------------- Fix Version/s: 4.2.0.CR1 Priority: Blocker (was: Major) Assignee: Luk?? Fry? >From the hudson log, I see: {quote} [ERROR] 'dependencies.dependency.version' for org.jboss.test-jsf:jsf-mockito:jar is missing. @ line 133, column 21 [ERROR] 'dependencies.dependency.version' for org.mockito:mockito-all:jar is missing. @ line 138, column 21 {quote} Looks like this is just a simple matter of defining the mockito dependency versions. > Unit tests failures in core module > ---------------------------------- > > Key: RF-11926 > URL: https://issues.jboss.org/browse/RF-11926 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: tests - unit > Environment: RichFaces 4.2.0-SNAPSHOT > Reporter: Pavol Pitonak > Assignee: Luk?? Fry? > Priority: Blocker > Fix For: 4.2.0.CR1 > > > Jenkins build for core module finished with 26 failures in unit tests. > http://hudson.qa.jboss.com/hudson/view/RF-4.0/job/richfaces-4.2-core/227/ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 27 15:44:48 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Fri, 27 Jan 2012 15:44:48 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11838) Warning in Chrome console for pages with ajax In-Reply-To: <836209596.24520.1324389969366.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1782385950.6393.1327697088442.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-11838. -------------------------------- Assignee: Brian Leathem Resolution: Done Removed the layerX and layerY events > Warning in Chrome console for pages with ajax > --------------------------------------------- > > Key: RF-11838 > URL: https://issues.jboss.org/browse/RF-11838 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: compatibility > Affects Versions: 4.1.0.Final > Environment: Google Chrome 16.0.912.63 > Reporter: Pavol Pitonak > Assignee: Brian Leathem > Fix For: 4.2.0.CR1 > > > # open Showcase in Chrome http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=ajax&skin=blueSky > # open browser console > # type "xxx" into input > result: > The following warning is displayed in browser console 6 times (twice for each Ajax request). Seems to be Chrome-specific and seems not to influence functionality of any component. > {quote} > event.layerX and event.layerY are broken and deprecated in WebKit. They will be removed from the engine in the near future. > {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 Jan 27 17:25:48 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Fri, 27 Jan 2012 17:25:48 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11918) Create a showcase profile for JBoss AS 7.1 In-Reply-To: <718645631.20368.1327448958455.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1016142827.6511.1327703148956.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-11918. -------------------------------- Assignee: Brian Leathem Resolution: Done > Create a showcase profile for JBoss AS 7.1 > ------------------------------------------ > > Key: RF-11918 > URL: https://issues.jboss.org/browse/RF-11918 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: showcase > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 4.2.0.CR1 > > > With RF-11657, the deployment bundle for JBoss AS 7.1 should have the google guava library excluded. > Create a new debployment bundle for the showcase, excluding the google guava library. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 27 17:36:48 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Fri, 27 Jan 2012 17:36:48 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11927) RichFaces polling is broken Message-ID: <4359831.6528.1327703808393.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Brian Leathem created RF-11927: ---------------------------------- Summary: RichFaces polling is broken Key: RF-11927 URL: https://issues.jboss.org/browse/RF-11927 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-push/poll Reporter: Brian Leathem Priority: Blocker Fix For: 4.2.0.CR1 I noticed today that RichFaces polling in the showcase is broken. The page: http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=poll does not update. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 27 17:38:48 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Fri, 27 Jan 2012 17:38:48 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11927) RichFaces polling is broken In-Reply-To: <4359831.6528.1327703808393.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <608683520.6533.1327703928453.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12662524#comment-12662524 ] Brian Leathem commented on RF-11927: ------------------------------------ I downloaded a SNAPSHOT from nexus (richfaces-showcase-4.2.0-20120127.171745-21-jbas7.war), and polling works. So the breakage was introduced sometime since: 2012-01-27 17:17:45 (CET?) > RichFaces polling is broken > --------------------------- > > Key: RF-11927 > URL: https://issues.jboss.org/browse/RF-11927 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Reporter: Brian Leathem > Priority: Blocker > Fix For: 4.2.0.CR1 > > > I noticed today that RichFaces polling in the showcase is broken. The page: > http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=poll > does not update. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 27 17:53:49 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Fri, 27 Jan 2012 17:53:49 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11773) Mobile Showcase and rich:orderingList/rich:pickList - control buttons can't be enabled In-Reply-To: <677171215.62017.1322758002710.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <663140018.6558.1327704829462.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem reopened RF-11773: -------------------------------- Re-opening to remove fixVersion > Mobile Showcase and rich:orderingList/rich:pickList - control buttons can't be enabled > -------------------------------------------------------------------------------------- > > Key: RF-11773 > URL: https://issues.jboss.org/browse/RF-11773 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: mobile, showcase > Affects Versions: 4.1.0.CR2 > Environment: JBoss AS 7.1.0.Beta1 > mobile devices: Nexus - Android 2.3.6, iPad > Reporter: Jan Papousek > Assignee: Wesley Hales > > It works correctly on iPhone, Motorola Xoom(Andorid), Android emulator (2.3.3). > It does not work for Nexus mobile device and iPad. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 27 17:53:49 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Fri, 27 Jan 2012 17:53:49 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11773) Mobile Showcase and rich:orderingList/rich:pickList - control buttons can't be enabled In-Reply-To: <677171215.62017.1322758002710.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <795311074.6562.1327704829649.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-11773. -------------------------------- Fix Version/s: (was: 4.2.0.CR1) Resolution: Cannot Reproduce Bug > Mobile Showcase and rich:orderingList/rich:pickList - control buttons can't be enabled > -------------------------------------------------------------------------------------- > > Key: RF-11773 > URL: https://issues.jboss.org/browse/RF-11773 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: mobile, showcase > Affects Versions: 4.1.0.CR2 > Environment: JBoss AS 7.1.0.Beta1 > mobile devices: Nexus - Android 2.3.6, iPad > Reporter: Jan Papousek > Assignee: Wesley Hales > > It works correctly on iPhone, Motorola Xoom(Andorid), Android emulator (2.3.3). > It does not work for Nexus mobile device and iPad. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 27 17:53:49 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Fri, 27 Jan 2012 17:53:49 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11773) Mobile Showcase and rich:orderingList/rich:pickList - control buttons can't be enabled In-Reply-To: <677171215.62017.1322758002710.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <959283915.6564.1327704829782.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem closed RF-11773. ------------------------------ > Mobile Showcase and rich:orderingList/rich:pickList - control buttons can't be enabled > -------------------------------------------------------------------------------------- > > Key: RF-11773 > URL: https://issues.jboss.org/browse/RF-11773 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: mobile, showcase > Affects Versions: 4.1.0.CR2 > Environment: JBoss AS 7.1.0.Beta1 > mobile devices: Nexus - Android 2.3.6, iPad > Reporter: Jan Papousek > Assignee: Wesley Hales > > It works correctly on iPhone, Motorola Xoom(Andorid), Android emulator (2.3.3). > It does not work for Nexus mobile device and iPad. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 27 17:53:50 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Fri, 27 Jan 2012 17:53:50 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11774) mobile showcase - rich:tree - touch event on particular part of tree causes selecting of whole tree component In-Reply-To: <468905842.65339.1322827900636.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1309587764.6569.1327704830309.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-11774: ------------------------------- Fix Version/s: (was: 4.2.0.CR1) > mobile showcase - rich:tree - touch event on particular part of tree causes selecting of whole tree component > ------------------------------------------------------------------------------------------------------------- > > Key: RF-11774 > URL: https://issues.jboss.org/browse/RF-11774 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-tree, mobile, showcase > Affects Versions: 4.1.0.CR2 > Environment: app: mobile richfaces-showcase > container: JBoss AS 7.1.0.Beta1 > device: Motorola Xoom > Reporter: Juraj Huska > Assignee: Wesley Hales > Priority: Minor > > When I *touch particular part of the tree component*, e.g. sign for expanding the node, then *the whole tree component is selected* till the node is not expanded. > It *looks* quite *disturbing*, such a blinking. > This behavior is also noticeable on iPad1, however it is not so disruptive as in Android device, since the color of selecting the whole tree is different. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 27 17:53:50 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Fri, 27 Jan 2012 17:53:50 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11772) showcase - a4j:attachQueue - ajax request from mobile device generates WARNING on the server log In-Reply-To: <942002739.61843.1322757520977.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <164215332.6571.1327704830433.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-11772: ------------------------------- Fix Version/s: (was: 4.2.0.CR1) > showcase - a4j:attachQueue - ajax request from mobile device generates WARNING on the server log > ------------------------------------------------------------------------------------------------ > > Key: RF-11772 > URL: https://issues.jboss.org/browse/RF-11772 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core, mobile, showcase > Affects Versions: 4.1.0.CR2 > Environment: richfaces showcase 4.1.CR2 > container: JBoss AS 7.1.0.Beta1, JBoss AS 6.0.0.Final > mobile device: iPad1, Motorola Xoom, iPhone4 > Reporter: Juraj Huska > Assignee: Wesley Hales > Priority: Minor > > In demo for a4j:attachQueue, when typing to input, the *generated ajax requests cause warning logged on the container console*: > {code} > 17:29:40,118 WARNING [org.richfaces.log.Components] (http--0.0.0.0-8080-5) Queue with name 'j_idt9' has already been registered > {code} > The *functionality remains fine*, and this is noticeable *only on mobile devices*. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 27 18:02:48 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Fri, 27 Jan 2012 18:02:48 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11921) Update the release-notes In-Reply-To: <432501842.1527.1327513668309.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1242244530.6589.1327705368349.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-11921. -------------------------------- Resolution: Done > Update the release-notes > ------------------------ > > Key: RF-11921 > URL: https://issues.jboss.org/browse/RF-11921 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: build/distribution > Reporter: Brian Leathem > Assignee: Brian Leathem > Priority: Blocker > Fix For: 4.2.0.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 Jan 27 18:18:48 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Fri, 27 Jan 2012 18:18:48 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11927) RichFaces polling is broken In-Reply-To: <4359831.6528.1327703808393.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <337490997.6599.1327706328335.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12662536#comment-12662536 ] Brian Leathem commented on RF-11927: ------------------------------------ Rolling back cdk, components, core and showcase to the commit before RF-11909, and polling works. I'll step through successive commits (grouped by issue number) to see if I can isolate when this breaks. > RichFaces polling is broken > --------------------------- > > Key: RF-11927 > URL: https://issues.jboss.org/browse/RF-11927 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Reporter: Brian Leathem > Priority: Blocker > Fix For: 4.2.0.CR1 > > > I noticed today that RichFaces polling in the showcase is broken. The page: > http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=poll > does not update. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 27 18:25:48 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Fri, 27 Jan 2012 18:25:48 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11927) RichFaces polling is broken In-Reply-To: <4359831.6528.1327703808393.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <446930564.6608.1327706748613.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12662537#comment-12662537 ] Brian Leathem commented on RF-11927: ------------------------------------ This still works after rolling all the modules to the last commit of RF-11909. I'll continue stepping through commits to isolate when this broke. > RichFaces polling is broken > --------------------------- > > Key: RF-11927 > URL: https://issues.jboss.org/browse/RF-11927 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Reporter: Brian Leathem > Priority: Blocker > Fix For: 4.2.0.CR1 > > > I noticed today that RichFaces polling in the showcase is broken. The page: > http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=poll > does not update. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 27 18:53:48 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Fri, 27 Jan 2012 18:53:48 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11927) RichFaces polling is broken In-Reply-To: <4359831.6528.1327703808393.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <57152018.6611.1327708428332.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12662538#comment-12662538 ] Brian Leathem commented on RF-11927: ------------------------------------ This appears to have broken with commit 4b8c00721a0a46398eca10de1e49cc27e3874f50, the fix for RF-11838 > RichFaces polling is broken > --------------------------- > > Key: RF-11927 > URL: https://issues.jboss.org/browse/RF-11927 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Reporter: Brian Leathem > Priority: Blocker > Fix For: 4.2.0.CR1 > > > I noticed today that RichFaces polling in the showcase is broken. The page: > http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=poll > does not update. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 27 18:53:48 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Fri, 27 Jan 2012 18:53:48 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11927) RichFaces polling is broken In-Reply-To: <4359831.6528.1327703808393.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1896579101.6612.1327708428387.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem reassigned RF-11927: ---------------------------------- Assignee: Brian Leathem > RichFaces polling is broken > --------------------------- > > Key: RF-11927 > URL: https://issues.jboss.org/browse/RF-11927 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Reporter: Brian Leathem > Assignee: Brian Leathem > Priority: Blocker > Fix For: 4.2.0.CR1 > > > I noticed today that RichFaces polling in the showcase is broken. The page: > http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=poll > does not update. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 27 22:05:48 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Fri, 27 Jan 2012 22:05:48 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11927) RichFaces polling is broken In-Reply-To: <4359831.6528.1327703808393.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <44085453.6708.1327719948325.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-11927. -------------------------------- Resolution: Done Added an undefined check for event in the fix for RF-11838 > RichFaces polling is broken > --------------------------- > > Key: RF-11927 > URL: https://issues.jboss.org/browse/RF-11927 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Reporter: Brian Leathem > Assignee: Brian Leathem > Priority: Blocker > Fix For: 4.2.0.CR1 > > > I noticed today that RichFaces polling in the showcase is broken. The page: > http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=poll > does not update. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 29 16:44:48 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Sun, 29 Jan 2012 16:44:48 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11926) Unit tests failures in core module In-Reply-To: <1481588008.6051.1327685208437.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <655348379.7249.1327873488400.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved RF-11926. ----------------------------- Fix Version/s: (was: 4.2.0.CR1) Resolution: Rejected The issue of CI builds. Once I have tied to released versions of {{jsf-test}}, build passed fine. > Unit tests failures in core module > ---------------------------------- > > Key: RF-11926 > URL: https://issues.jboss.org/browse/RF-11926 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: tests - unit > Environment: RichFaces 4.2.0-SNAPSHOT > Reporter: Pavol Pitonak > Assignee: Luk?? Fry? > Priority: Blocker > > Jenkins build for core module finished with 26 failures in unit tests. > http://hudson.qa.jboss.com/hudson/view/RF-4.0/job/richfaces-4.2-core/227/ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 30 11:35:48 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?J=C3=A1n_Jamrich_=28JIRA=29?=) Date: Mon, 30 Jan 2012 11:35:48 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11904) rich:contextMenu @mode doesn't affect request type In-Reply-To: <1470389961.10951.1326984078257.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <797102823.8825.1327941348735.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] J?n Jamrich resolved RF-11904. ------------------------------ Resolution: Cannot Reproduce Bug Seems it is fixed. Ftest updated accordingly. > rich:contextMenu @mode doesn't affect request type > -------------------------------------------------- > > Key: RF-11904 > URL: https://issues.jboss.org/browse/RF-11904 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-misc > Environment: RichFaces 4.2.0-SNAPSHOT > Metamer 4.1.1-SNAPSHOT r.${buildNumber} > Mojarra 2.1.3-SNAPSHOT > JBoss AS 7.0.2.Final > Java(TM) SE Runtime Environment 1.6.0_26-b03 @ Linux > Firefox 10.0 @ Linux i686 > ----- > Richfaces component module built after merge to develop branch > Reporter: J?n Jamrich > Assignee: J?n Jamrich > > Since contextMenu should be similar to dropDownMenu, I'm missing behavior controlled by @mode in contextMenu like dropDownMenu. > In dropDownMenu @mode=ajax causes just one request performed when click menu item. No request for @mode=client and only for @mode=server multiple requests (first POST request for page where dropDownMenu triggered request and then multiple GET requests for all associated (referenced) resources such as CSS, JS... > But not for contextMenu. @mode set to client neither ajax doesn't change request type, always is full page refresh performed when click on contextMenu item. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 30 13:32:48 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 30 Jan 2012 13:32:48 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11926) Unit tests failures in core module In-Reply-To: <1481588008.6051.1327685208437.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <137607204.9115.1327948368356.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12662839#comment-12662839 ] Brian Leathem commented on RF-11926: ------------------------------------ Curious - why was this issue marked as "Rejected", rather than done? > Unit tests failures in core module > ---------------------------------- > > Key: RF-11926 > URL: https://issues.jboss.org/browse/RF-11926 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: tests - unit > Environment: RichFaces 4.2.0-SNAPSHOT > Reporter: Pavol Pitonak > Assignee: Luk?? Fry? > Priority: Blocker > > Jenkins build for core module finished with 26 failures in unit tests. > http://hudson.qa.jboss.com/hudson/view/RF-4.0/job/richfaces-4.2-core/227/ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 30 19:05:48 2012 From: jira-events at lists.jboss.org (Friedhelm Kuehn (JIRA)) Date: Mon, 30 Jan 2012 19:05:48 -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: <668982599.9574.1327968348686.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=12662908#comment-12662908 ] Friedhelm Kuehn commented on RF-11884: -------------------------------------- Hi Brian, I don't see anything moving here - what does 'waiting_on_user' mean ? Did you notice that I added documents with additional Information ? We are getting into troubles here, having to deliver our software soon - working with IE8 also. Regards, Friedhelm > 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 > Labels: waiting_on_user > Attachments: Richfaces_4.1_Problems.pdf, Richfaces_4.1_Problems_Konfiguration.pdf > > > 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 Jan 31 03:26:51 2012 From: jira-events at lists.jboss.org (kevin 2 (JIRA)) Date: Tue, 31 Jan 2012 03:26:51 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11017) rich:extendedDataTable: Problems with resizing and ordering of columns with Firefox 4 In-Reply-To: <2053110360.33219.1306595820932.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1535590303.10044.1327998411360.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12662953#comment-12662953 ] kevin 2 commented on RF-11017: ------------------------------ Hi, I still have this issue on Firefox 3.6, and IE 7,8 with RF4.1 Final! Is it really resolved ? > rich:extendedDataTable: Problems with resizing and ordering of columns with Firefox 4 > ------------------------------------------------------------------------------------- > > Key: RF-11017 > URL: https://issues.jboss.org/browse/RF-11017 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: compatibility, component-tables > Affects Versions: 4.1.0.Milestone1 > Environment: Tomcat6 and 7, Java 6, MyFaces 2.1.0-SNAPSHOT (28.05.2011), RichFaces 4.1.0-SNAPSHOT (28.05.2011) > Reporter: Rene O > Assignee: Luk?? Fry? > Attachments: jsf2testcase.war > > > To reproduce the two issues, i have append a testcase: > Issue 1 (ordering): > 1. call http://localhost:8080/jsf2testcase/tableTest.jsf > 2. try to change the order of the columns (e.g. A,B,C -> B,A,C) > 3. after that, the scrollbar of the table disappears > Note, that this issue appears with Firefox 4.0.1, but not with IE8 > Issue 2 (resizing): > 1. call http://localhost:8080/jsf2testcase/tableTestB.jsf > 2. click button to show table B > 3. try to resize the column width of table B > 4. resizing doesn't work in table B, but if you try to resize the column width of table A, it will work. So it must be a bug. > Note, that this issue appears with Firefox 4.0.1, but not with 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 Tue Jan 31 04:10:51 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 31 Jan 2012 04:10:51 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11926) Unit tests failures in core module In-Reply-To: <1481588008.6051.1327685208437.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <285994008.10114.1328001051591.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12662961#comment-12662961 ] Luk?? Fry? commented on RF-11926: --------------------------------- I haven't did anything special for resolving this issue. It was solved by RFPL-1989 process. > Unit tests failures in core module > ---------------------------------- > > Key: RF-11926 > URL: https://issues.jboss.org/browse/RF-11926 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: tests - unit > Environment: RichFaces 4.2.0-SNAPSHOT > Reporter: Pavol Pitonak > Assignee: Luk?? Fry? > Priority: Blocker > > Jenkins build for core module finished with 26 failures in unit tests. > http://hudson.qa.jboss.com/hudson/view/RF-4.0/job/richfaces-4.2-core/227/ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 31 04:12:48 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 31 Jan 2012 04:12:48 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11926) Unit tests failures in core module In-Reply-To: <1481588008.6051.1327685208437.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <803887831.10117.1328001168969.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12662961#comment-12662961 ] Luk?? Fry? edited comment on RF-11926 at 1/31/12 4:12 AM: ---------------------------------------------------------- I haven't did anything special for resolving this issue. It was solved by RFPL-1989 process. Actually, tests weren't failing and no changes were done in code to allow them pass, the cause was wrong timing/ordering of SNAPSHOT builds. was (Author: lfryc): I haven't did anything special for resolving this issue. It was solved by RFPL-1989 process. > Unit tests failures in core module > ---------------------------------- > > Key: RF-11926 > URL: https://issues.jboss.org/browse/RF-11926 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: tests - unit > Environment: RichFaces 4.2.0-SNAPSHOT > Reporter: Pavol Pitonak > Assignee: Luk?? Fry? > Priority: Blocker > > Jenkins build for core module finished with 26 failures in unit tests. > http://hudson.qa.jboss.com/hudson/view/RF-4.0/job/richfaces-4.2-core/227/ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 31 04:19:49 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 31 Jan 2012 04:19:49 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11017) rich:extendedDataTable: Problems with resizing and ordering of columns with Firefox 4 In-Reply-To: <2053110360.33219.1306595820932.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1654878903.10124.1328001589888.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? reopened RF-11017: ----------------------------- Assignee: Pavol Pitonak (was: Luk?? Fry?) Hi Kevin, I have reopened this issue to check issues. Pavol, could you please try EDT on listed browsers? > rich:extendedDataTable: Problems with resizing and ordering of columns with Firefox 4 > ------------------------------------------------------------------------------------- > > Key: RF-11017 > URL: https://issues.jboss.org/browse/RF-11017 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: compatibility, component-tables > Affects Versions: 4.1.0.Milestone1 > Environment: Tomcat6 and 7, Java 6, MyFaces 2.1.0-SNAPSHOT (28.05.2011), RichFaces 4.1.0-SNAPSHOT (28.05.2011) > Reporter: Rene O > Assignee: Pavol Pitonak > Attachments: jsf2testcase.war > > > To reproduce the two issues, i have append a testcase: > Issue 1 (ordering): > 1. call http://localhost:8080/jsf2testcase/tableTest.jsf > 2. try to change the order of the columns (e.g. A,B,C -> B,A,C) > 3. after that, the scrollbar of the table disappears > Note, that this issue appears with Firefox 4.0.1, but not with IE8 > Issue 2 (resizing): > 1. call http://localhost:8080/jsf2testcase/tableTestB.jsf > 2. click button to show table B > 3. try to resize the column width of table B > 4. resizing doesn't work in table B, but if you try to resize the column width of table A, it will work. So it must be a bug. > Note, that this issue appears with Firefox 4.0.1, but not with 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 Tue Jan 31 05:27:48 2012 From: jira-events at lists.jboss.org (kevin 2 (JIRA)) Date: Tue, 31 Jan 2012 05:27:48 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11017) rich:extendedDataTable: Problems with resizing and ordering of columns with Firefox 4 In-Reply-To: <2053110360.33219.1306595820932.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <291550033.10208.1328005668727.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12662972#comment-12662972 ] kevin 2 commented on RF-11017: ------------------------------ For information, I use Packed and Compressed ressources in my application. > rich:extendedDataTable: Problems with resizing and ordering of columns with Firefox 4 > ------------------------------------------------------------------------------------- > > Key: RF-11017 > URL: https://issues.jboss.org/browse/RF-11017 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: compatibility, component-tables > Affects Versions: 4.1.0.Milestone1 > Environment: Tomcat6 and 7, Java 6, MyFaces 2.1.0-SNAPSHOT (28.05.2011), RichFaces 4.1.0-SNAPSHOT (28.05.2011) > Reporter: Rene O > Assignee: Pavol Pitonak > Attachments: jsf2testcase.war > > > To reproduce the two issues, i have append a testcase: > Issue 1 (ordering): > 1. call http://localhost:8080/jsf2testcase/tableTest.jsf > 2. try to change the order of the columns (e.g. A,B,C -> B,A,C) > 3. after that, the scrollbar of the table disappears > Note, that this issue appears with Firefox 4.0.1, but not with IE8 > Issue 2 (resizing): > 1. call http://localhost:8080/jsf2testcase/tableTestB.jsf > 2. click button to show table B > 3. try to resize the column width of table B > 4. resizing doesn't work in table B, but if you try to resize the column width of table A, it will work. So it must be a bug. > Note, that this issue appears with Firefox 4.0.1, but not with 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 Tue Jan 31 11:15:50 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Tue, 31 Jan 2012 11:15:50 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11915) MenuGroup with all items disabled or no items causes JS error In-Reply-To: <2107920490.18850.1327404678300.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <2070853.11534.1328026550995.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-11915: ------------------------------- Fix Version/s: 4.3-Tracking > MenuGroup with all items disabled or no items causes JS error > ------------------------------------------------------------- > > Key: RF-11915 > URL: https://issues.jboss.org/browse/RF-11915 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-menu > Affects Versions: 4.1.0.Final > Environment: Tomcat 6.0.26, MyFaces 2.1.13, RichFaces > Reporter: J?n Hala?a > Assignee: Brian Leathem > Fix For: 4.3-Tracking > > > Submenu (r:menuGroup) containing only disabled items or no items, causes a JavaScript error when it is supposed to get hidden (moving cursor to the next item in the parent menu). > In Firefox 9: > {quote} > parentMenu is undefined > menu-base.js, line 126 > {quote} > In MSIE 7: > {quote} > 'nodeType' is null or not an object > richfaces.js, line 43 > {quote} > It's the same error only reported from the different level of the call stack. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 31 11:35:48 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Tue, 31 Jan 2012 11:35:48 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11888) Resource Servlet can't handle query string appended to resource url In-Reply-To: <787852126.1337.1326719298230.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1979463481.11674.1328027748595.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12663108#comment-12663108 ] Brian Leathem commented on RF-11888: ------------------------------------ Brendan, there are two paths forward: # close this ticket as the RichFaces version in thi URL is sufficient for your use case # add a version (v) attribute to the list of attributes pared by the ResourceServlet Since you opened this ticket, can you indicate which direction you would prefer it to proceed? > Resource Servlet can't handle query string appended to resource url > ------------------------------------------------------------------- > > Key: RF-11888 > URL: https://issues.jboss.org/browse/RF-11888 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: resource handling > Affects Versions: 4.1.0.Final > Environment: Glassfish 3.1.1 (NO Tomcat)/Mojarra 2.1.3 Chrome browser - > Reporter: Brendan Healey > Priority: Critical > Labels: waiting_on_user > > A custom resource handler (http://blogs.oracle.com/rlubke/entry/jsf_2_0_new_feature) > can be used to append a version string (i.e. ?v=23) to a resource url to force a > browser to refresh a resource rather than use any cached version. > At present any appending of a version string causes a 404 response status, for example: > Request URL: > https://localhost:8181/MyApp/org.richfaces.resources/javax.faces.resource/org.richfaces.staticResource/4.1.0.Final/PackedCompressed/blueSky/packed/packed.css?v=23 > Removing the url parameter makes it work ok. As you can see I have resourceMapping > enabled. > This is essential to cause a browser to issue a request to the server if a static > resource is held in a browser cache and is not expired, but you've upgraded the > richfaces version. You have to have a way to invalidate the cache, and I'm not > seeing how this can be done in a sensible way. You can set the Cache-Control > no-cache header, but I'd need to do this in a way that says "I've just upgraded > richfaces, so don't use the cache, issue a request to the server for the resource, > but cache the result and use this until the next time". -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 31 11:37:48 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Tue, 31 Jan 2012 11:37:48 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11890) ResourceServlet does not set HTTP headers for caching In-Reply-To: <896407184.2481.1326733518446.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1106050137.11678.1328027868457.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-11890: ------------------------------- Assignee: Luk?? Fry? Forum Reference: https://community.jboss.org/message/646969#646969 (was: https://community.jboss.org/message/646969#646969) Lukas, I thought we discussed this issue, and found it to be the result of a local setting in your browser? > ResourceServlet does not set HTTP headers for caching > ----------------------------------------------------- > > Key: RF-11890 > URL: https://issues.jboss.org/browse/RF-11890 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 4.2.0.CR1 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > > {quote} > All RichFaces resources served by Faces Servlet have headers set appropriately for caching. > (You can check it by removing your Filter and turning resourceMapping=false). > > I assume you have problems with ResourceServlet where resources does not go through RichFaces ResourceHandler, so headers are set as for any other JSF resource - which means (AFAIK) no caching at all. > {quote} > This assumption needs to be verified before implementing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 31 11:37:48 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Tue, 31 Jan 2012 11:37:48 -0500 (EST) 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: <1937720914.11687.1328027868738.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 ] Brian Leathem reassigned RF-11905: ---------------------------------- Assignee: Juraj Huska Juraj, so are you saying this is still a problem with JBoss AS 7.1? I thought from the linked AS7 issue that it had been resolved with AS 7.1. > 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: Juraj Huska > Priority: Minor > > 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 Tue Jan 31 11:47:48 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Tue, 31 Jan 2012 11:47:48 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11923) rich:contextMenu - option to render context menu under mouse focus In-Reply-To: <1041095407.3568.1327593589409.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <381491693.11734.1328028468834.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-11923: ------------------------------- Fix Version/s: 4.3-Tracking Component/s: (was: component) (was: base functionality ) (was: showcase) Rather than make this the default bahaviour (which I think will annoy those expecting the traditional windows behaviour for contextMenus), we could add an offsetX and offsetY attribute to the contextMenu, to control the initial menu placement. > rich:contextMenu - option to render context menu under mouse focus > ------------------------------------------------------------------ > > Key: RF-11923 > URL: https://issues.jboss.org/browse/RF-11923 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-menu > Affects Versions: 4.1.0.Final > Reporter: Juraj Huska > Priority: Optional > Fix For: 4.3-Tracking > > > It would be nice IMHO to have an option to render context menu right under the mouse focus, like it is for example done in GNOME environment. So when user triggers context menu, then he will not need to move his mouse to select first option, but it will be enough just to click to have selected first option, since that option will be rendered under mouse focus. > Nice use case for this is for example demo for rich:context menu from showcase, where only one menu item is in context menu, and takes some time to move the mouse on that option. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 31 11:47:48 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Tue, 31 Jan 2012 11:47:48 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11924) showcase - rich:context - tree ContextMenu - header of popup should be bigger In-Reply-To: <259195289.3587.1327594548872.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <28966757.11736.1328028468936.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-11924: ------------------------------- Fix Version/s: 4.3-Tracking Assignee: Brian Leathem Component/s: (was: component-output) (was: component-panels-layout-themes) (was: skinning) > showcase - rich:context - tree ContextMenu - header of popup should be bigger > ----------------------------------------------------------------------------- > > Key: RF-11924 > URL: https://issues.jboss.org/browse/RF-11924 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-menu, showcase > Affects Versions: 4.1.0.Final > Environment: showcase app - 4.2.0-SNAPSHOT > all browsers > Reporter: Juraj Huska > Assignee: Brian Leathem > Priority: Trivial > Fix For: 4.3-Tracking > > Attachments: contextMenuPopup.png > > > *The header of the popup* invoked from contextMenu *in demos for rich:contextMenu*, sample tree contextMenu *is* in some cases *too small*, and then the cross for hiding the popup overlap with the header label. > It is when the body of the popup is small in width. For example it is so when user select node USA, then the *header of popup adapts the size of body*, and the problem is there. Please see the *screenshot* for further reference. > So the header should have set fixed width. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 31 12:00:49 2012 From: jira-events at lists.jboss.org (Juraj Huska (JIRA)) Date: Tue, 31 Jan 2012 12:00:49 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11928) showcase - client side validation demos - not rendered due to incompatible guava library Message-ID: <481007270.11771.1328029249101.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Juraj Huska created RF-11928: -------------------------------- Summary: showcase - client side validation demos - not rendered due to incompatible guava library Key: RF-11928 URL: https://issues.jboss.org/browse/RF-11928 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: compatibility, component-validators, core, showcase Affects Versions: 4.2.0.CR1 Environment: container: JBoss AS 7.0.2.Final browsers: all Reporter: Juraj Huska Accessing demos for client side validation in showcase, causes throwing an error and not rendering the components at all. *Error:* {code} 16:13:19,788 INFO [javax.enterprise.resource.webcontainer.jsf.context] (http-localhost.localdomain-127.0.0.1-8080-1) Exception when handling error trying to reset the response.: java.lang.NoSuchMethodError: com.google.common.collect.ImmutableSet.copyOf(Ljava/util/Collection;)Lcom/google/common/collect/ImmutableSet; at org.richfaces.renderkit.html.ClientOnlyScript.(ClientOnlyScript.java:35) [richfaces-components-ui-4.2.0.CR1.jar:] at org.richfaces.renderkit.html.ClientValidatorRenderer.createValidatorScript(ClientValidatorRenderer.java:184) [richfaces-components-ui-4.2.0.CR1.jar:] at org.richfaces.renderkit.html.ClientValidatorRenderer.createValidatorScript(ClientValidatorRenderer.java:154) [richfaces-components-ui-4.2.0.CR1.jar:] at org.richfaces.renderkit.html.ClientValidatorRenderer.buildAndStoreValidatorScript(ClientValidatorRenderer.java:125) [richfaces-components-ui-4.2.0.CR1.jar:] at org.richfaces.renderkit.html.ClientValidatorRenderer.getScript(ClientValidatorRenderer.java:60) [richfaces-components-ui-4.2.0.CR1.jar:] at javax.faces.component.behavior.ClientBehaviorBase.getScript(ClientBehaviorBase.java:103) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] at org.richfaces.component.behavior.ClientValidatorImpl.getScript(ClientValidatorImpl.java:91) [richfaces-components-ui-4.2.0.CR1.jar:] at com.sun.faces.renderkit.RenderKitUtils.getSingleBehaviorHandler(RenderKitUtils.java:1607) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] at com.sun.faces.renderkit.RenderKitUtils.renderHandler(RenderKitUtils.java:1700) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] at com.sun.faces.renderkit.RenderKitUtils.renderOnchange(RenderKitUtils.java:388) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] at com.sun.faces.renderkit.html_basic.TextRenderer.getEndTextToRender(TextRenderer.java:134) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeEnd(HtmlBasicRenderer.java:170) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] at javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:875) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:312) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] at com.sun.faces.renderkit.html_basic.GridRenderer.renderRow(GridRenderer.java:185) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] at com.sun.faces.renderkit.html_basic.GridRenderer.encodeChildren(GridRenderer.java:129) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:845) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1756) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] at org.richfaces.renderkit.RendererBase.renderChildren(RendererBase.java:276) [richfaces-components-ui-4.2.0.CR1.jar:] at org.richfaces.renderkit.html.PanelRenderer.encodeEnd(PanelRenderer.java:181) [richfaces-components-ui-4.2.0.CR1.jar:] at javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:875) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1763) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] at javax.faces.render.Renderer.encodeChildren(Renderer.java:168) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:845) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1756) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1759) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1759) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] at com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:401) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] at com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:131) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:288) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:288) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:121) [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.render(LifecycleImpl.java:139) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] at org.richfaces.demo.arrangeablemodel.PersistenceLifecycle.render(PersistenceLifecycle.java:66) [classes:] at javax.faces.webapp.FacesServlet.service(FacesServlet.java:594) [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] {code} The demos works fine on JBoss AS 7.1.0.CR1b. The thing is that the showcase deployment on *JBoss AS 7.0.2.Final* uses *guava-r6* shipped with container, and deployment on *JBoss AS 7.1.0.CR1b uses shipped guava-10.0.1.* So it should be set in jboss-deployment-structure.xml that application is bringing it own guava. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 31 12:16:48 2012 From: jira-events at lists.jboss.org (Juraj Huska (JIRA)) Date: Tue, 31 Jan 2012 12:16:48 -0500 (EST) 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: <1693882071.11789.1328030208600.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=12663119#comment-12663119 ] Juraj Huska commented on RF-11905: ---------------------------------- Sorry for not including this essential info but it does not work without workaround event on JBoss AS 7.1.0.CR1b. I am trying to ask Jozef Hartinger, how he solved this issue. > 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: Juraj Huska > Priority: Minor > > 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 Tue Jan 31 13:35:48 2012 From: jira-events at lists.jboss.org (Juraj Huska (JIRA)) Date: Tue, 31 Jan 2012 13:35:48 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11929) showcase - a4j:actionListener - move commandButtons from panelGrid to make it look better Message-ID: <1893744032.11917.1328034948546.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Juraj Huska created RF-11929: -------------------------------- Summary: showcase - a4j:actionListener - move commandButtons from panelGrid to make it look better Key: RF-11929 URL: https://issues.jboss.org/browse/RF-11929 Project: RichFaces Issue Type: Enhancement Security Level: Public (Everyone can see) Components: component-a4j-core, showcase Affects Versions: 4.2.0.CR1 Environment: all containers all browsers Reporter: Juraj Huska Priority: Trivial In demo for a4j:actionListener there are commandButtons included in the panelGrid together with panel which they generate. Invoking listener by type(middle command button) causes that the rendered panel is enlarged, and since the buttons are in the same panelGrid they are moved too, which looks weird. IMHO their should be moved from that panelGrid to be independent on the width of generated message. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 31 13:40:48 2012 From: jira-events at lists.jboss.org (Juraj Huska (JIRA)) Date: Tue, 31 Jan 2012 13:40:48 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11930) showcase - a4j:actionListener - typo in demo description Message-ID: <1104931443.11919.1328035248356.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Juraj Huska created RF-11930: -------------------------------- Summary: showcase - a4j:actionListener - typo in demo description Key: RF-11930 URL: https://issues.jboss.org/browse/RF-11930 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-a4j-core, showcase Affects Versions: 4.2.0.CR1 Environment: all containers all browsers Reporter: Juraj Huska Priority: Minor In the demo for a4j:actionListener there is a typo in demo description. It is in the description to second way of attaching of actionListener. ??2. By listerner class, using the type 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 Tue Jan 31 16:31:48 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Tue, 31 Jan 2012 16:31:48 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11931) The generated VDL doc should include a column displaying the default value of an attribute Message-ID: <155690999.12218.1328045508320.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Brian Leathem created RF-11931: ---------------------------------- Summary: The generated VDL doc should include a column displaying the default value of an attribute Key: RF-11931 URL: https://issues.jboss.org/browse/RF-11931 Project: RichFaces Issue Type: Enhancement Security Level: Public (Everyone can see) Components: cdk, doc Reporter: 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 Tue Jan 31 16:33:48 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Tue, 31 Jan 2012 16:33:48 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11931) The generated VDL doc should include a column displaying the default value of an attribute In-Reply-To: <155690999.12218.1328045508320.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <129091588.12220.1328045628383.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-11931: ------------------------------- Assignee: Luk?? Fry? Fix Version/s: 4.2.0.Final Lukas, assigning to you for your feedback on the idea. > The generated VDL doc should include a column displaying the default value of an attribute > ------------------------------------------------------------------------------------------ > > Key: RF-11931 > URL: https://issues.jboss.org/browse/RF-11931 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: cdk, doc > Reporter: Brian Leathem > Assignee: Luk?? Fry? > Fix For: 4.2.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 Jan 31 19:09:48 2012 From: jira-events at lists.jboss.org (Brendan Healey (JIRA)) Date: Tue, 31 Jan 2012 19:09:48 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11888) Resource Servlet can't handle query string appended to resource url In-Reply-To: <787852126.1337.1326719298230.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1886150699.12430.1328054988507.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12663205#comment-12663205 ] Brendan Healey commented on RF-11888: ------------------------------------- Hello Brian, apologies for not responding earlier and thanks for the follow up. Here's my perspective. My initial bug report was clearly erroneous in that I'd fixated on the appending of a version string and failed to take into account the fact that the URL contains the richfaces release version. As such my concerns that stale richfaces resources with a long max-age (set by my application) could be served from browser cache following a richfaces upgrade were invalid. On this basis I'd be happy for the ticket to be closed. However... I think you need to consider the fact that unless you are able to handle the appending of a version string you'll be fielding a slow but steady stream of enquiries from now to eternity. As part of the very simple implementation of the ResourceHandler interface you have to extend the ResourceHandlerWrapper class and override the createResource() method. In this method you will deal with any exclusions, any URLs to which you do not wish to append a version string. Here is the implementation I use: @Override public Resource createResource(String resourceName, String libraryName) { Resource resource = super.createResource(resourceName, libraryName); if(resourceName.equals("jquery.js") || (libraryName != null && (libraryName.equals("org.richfaces") || libraryName.equals(SQCC_LIBRARY)))) { return resource; } else { return new CustomResource(resource); } } The thing that is that when you use you are using jquery bundled with the richfaces libraries, as we all know. When you're using resource mapping it's this tag which triggers the loading of packed.js, not the first richfaces component on the page. I'm already seeing people on the forum hitting this problem where they get the 'jsf is undefined' error, which can be alleviated by using . Although entirely logical, especially with the benefit of hindsight, it's not immediately obvious that using the richfaces jquery is going to load the packed/compressed richfaces resources. As relevant to the resource handler, as you can see from my implementation of the createResource() method above that it's presently necessary to exclude the resource name (not the library name) "jquery.js" from having a version string appended, or it won't work. I'd say this took me half a day to fully debug and put a workaround into place, so the question is whether you wish to proliferate this scenario for other developers, or just handle the version string. I recommend the latter option. Thanks for your help. Brendan. > Resource Servlet can't handle query string appended to resource url > ------------------------------------------------------------------- > > Key: RF-11888 > URL: https://issues.jboss.org/browse/RF-11888 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: resource handling > Affects Versions: 4.1.0.Final > Environment: Glassfish 3.1.1 (NO Tomcat)/Mojarra 2.1.3 Chrome browser - > Reporter: Brendan Healey > Priority: Critical > Labels: waiting_on_user > > A custom resource handler (http://blogs.oracle.com/rlubke/entry/jsf_2_0_new_feature) > can be used to append a version string (i.e. ?v=23) to a resource url to force a > browser to refresh a resource rather than use any cached version. > At present any appending of a version string causes a 404 response status, for example: > Request URL: > https://localhost:8181/MyApp/org.richfaces.resources/javax.faces.resource/org.richfaces.staticResource/4.1.0.Final/PackedCompressed/blueSky/packed/packed.css?v=23 > Removing the url parameter makes it work ok. As you can see I have resourceMapping > enabled. > This is essential to cause a browser to issue a request to the server if a static > resource is held in a browser cache and is not expired, but you've upgraded the > richfaces version. You have to have a way to invalidate the cache, and I'm not > seeing how this can be done in a sensible way. You can set the Cache-Control > no-cache header, but I'd need to do this in a way that says "I've just upgraded > richfaces, so don't use the cache, issue a request to the server for the resource, > but cache the result and use this until the next time". -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 31 19:32:48 2012 From: jira-events at lists.jboss.org (Mauro Castaldo (JIRA)) Date: Tue, 31 Jan 2012 19:32:48 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11932) extendedDataTable: cannot unselect selected row with CTRL+Click when using single selection mode Message-ID: <1739551615.12449.1328056368365.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Mauro Castaldo created RF-11932: ----------------------------------- Summary: extendedDataTable: cannot unselect selected row with CTRL+Click when using single selection mode Key: RF-11932 URL: https://issues.jboss.org/browse/RF-11932 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-tables Affects Versions: 4.1.0.Final Environment: Internet Explorer 9 / Google Chrome 18.0.1017.2 Reporter: Mauro Castaldo Priority: Minor extendedDataTable: cannot unselect selected row with CTRL+Click when using single selection mode. In RichFaces 3.3 you can unselect selected row using CTRL+Click. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
State Footer Capital Footer
Footer
> State Footer > > Capital Footer >
> Footer >
> index.jsf (ligne 77) > RichFaces.ui is undefined > [Stopper sur une erreur] RichFaces.ui.Menu(...":"MenuForm:mainToolBar"} ); > index.jsf (ligne 77) > RichFaces.ui is undefined > [Stopper sur une erreur]
> index.jsf (ligne 85) > RichFaces.ui is undefined > [Stopper sur une erreur]
> index.jsf (ligne 88) > RichFaces.ui is undefined > [Stopper sur une erreur] > index.jsf (ligne 88) > RichFaces.ui is undefined > [Stopper sur une erreur] > index.jsf (ligne 88) > {code} > more over there is many CSS errors/warning > {code} > L'utilisation de getAttributeNodeNS() est obsol?te. Utilisez getAttributeNS() ? la place. > Une fin de valeur ?tait attendue, mais ? "#E5973E " ? a ?t? trouv?. Erreur d'analyse de la valeur pour ? border ?. D?claration abandonn?e. > *.rf-insl-tt{position:absolute;display..."#E5973E ";background-color:#FAE6B0;} > packed.css (ligne 108) > Erreur d'analyse de la valeur pour ? filter ?. D?claration abandonn?e. > *.rf-fu-inp{filter:alpha(opacity=0);fo...y:0;position:absolute;right:0;top:0;} > packed.css (ligne 158) > Propri?t? ? text-color ? inconnue. D?claration abandonn?e. > *.rf-fu-itm-st{display:none;margin-top...000;background-color:#fff;padding:0;} > packed.css (ligne 164) > Erreur d'analyse de la valeur pour ? filter ?. D?claration abandonn?e. > *.rf-tab-cnt{border:1px solid #C4C0B9;...opacity:.1;filter:alpha(opacity=10);} > packed.css (ligne 184) > Erreur d'analyse de la valeur pour ? filter ?. D?claration abandonn?e. > *.rf-pp-shade{position:fixed;width:100...opacity:.5;filter:alpha(opacity=50);} > packed.css (ligne 185) > Erreur d'analyse de la valeur pour ? filter ?. D?claration abandonn?e. > *.rf-pp-shdw{background-color:#000;opa...6px;left:6px;bottom:-6px;z-index:-1;} > packed.css (ligne 186) > Propri?t? ? repeat-x ? inconnue. D?claration abandonn?e. > *.rf-pp-hdr{background:url(../org.rich...g-left:10px;cursor:move;padding:2px;} > packed.css (ligne 188) > Erreur d'analyse de la valeur pour ? font-size ?. D?claration abandonn?e. > *.rf-cal-sp-inp{border:0;padding:0 0 0...Arial,Verdana,sans-serif;width:18px;} > packed.css (ligne 354) > Erreur d'analyse de la valeur pour ? filter ?. D?claration abandonn?e. > *.rf-cal-edtr-shdw{background:#FFF;opacity:.5;filter:alpha(opacity=50);} > packed.css (ligne 369) > Erreur d'analyse de la valeur pour ? filter ?. D?claration abandonn?e. > *.rf-cal-edtr-layout-shdw{background-c...opacity:.3;filter:alpha(opacity=30);} > {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 Jan 5 23:00:09 2012 From: jira-events at lists.jboss.org (Brian Leathem (Updated) (JIRA)) Date: Thu, 5 Jan 2012 23:00:09 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11805) a4j:queue onerror doesn't seem to work In-Reply-To: <1117998666.86597.1323452020759.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <452026625.44481.1325822409466.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-11805: ------------------------------- Labels: waiting_on_user (was: ) Assignee: (was: Brian Leathem) Forum Reference: http://community.jboss.org/message/634654#634654 (was: http://community.jboss.org/message/634654#634654) Brendan, can you try clicking on the button a second time, to see if the expected behavior is then achieved? This would confirm that it is indeed related to RF-9118. > a4j:queue onerror doesn't seem to work > -------------------------------------- > > Key: RF-11805 > URL: https://issues.jboss.org/browse/RF-11805 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.1.0.CR2 > Reporter: Brendan Healey > Labels: waiting_on_user > > I was just testing some 'global' ajax error handling code. I put an > outside a form, then forced an ajax error like this: > > > > > > public void forceAjaxError(AjaxBehaviorEvent event) { > getResponse().setStatus(501); > } > > public HttpServletResponse getResponse() { > return (HttpServletResponse) FacesContext.getCurrentInstance().getExternalContext().getResponse(); > } > > so I click into and out of the input, the ajax POST request completes with a 501 status but no alert is shown. > I just tried it with a4j:status and this does pick up 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 Thu Jan 5 23:02:09 2012 From: jira-events at lists.jboss.org (Brian Leathem (Updated) (JIRA)) Date: Thu, 5 Jan 2012 23:02:09 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11828) showcase - rich:inplaceInput - entering value does not work In-Reply-To: <727507047.21455.1324316289442.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1405179926.44483.1325822529368.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-11828: ------------------------------- Fix Version/s: 4.1.1.Final Assignee: (was: Brian Leathem) Possibly related to other component breakages in the showcase when the hotkey was introduced. > showcase - rich:inplaceInput - entering value does not work > ----------------------------------------------------------- > > Key: RF-11828 > URL: https://issues.jboss.org/browse/RF-11828 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input, showcase > Affects Versions: 4.1.0.Final > Environment: richfaces-showcase 4.1.1-SNAPSHOT > all containers > all browsers > Reporter: Juraj Huska > Priority: Minor > Fix For: 4.1.1.Final > > > *Submitting* the value of rich:inplaceInput does not work *by pressing the enter key* as it should. > When I *click outside* of the component then the value of *input is edited correctly*. > This issue is occurring from 4.1.1-SNAPSHOT showcase version. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 6 05:40:09 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28Resolved=29_=28JIRA=29?=) Date: Fri, 6 Jan 2012 05:40:09 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11851) rich:hotKey - add support for onkeypress, onkeydown and onkeyup In-Reply-To: <2116883574.29436.1324557550117.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1300250042.44849.1325846409481.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved RF-11851. ----------------------------- Resolution: Done > rich:hotKey - add support for onkeypress, onkeydown and onkeyup > --------------------------------------------------------------- > > Key: RF-11851 > URL: https://issues.jboss.org/browse/RF-11851 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: component-misc > Affects Versions: 4.1.1.Final > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Priority: Critical > Labels: needs-qe > Fix For: 4.1.1.Final > > > The binding will be done only for such types which have defined some handler. > This will mean removing {{@type}} 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 Fri Jan 6 06:02:09 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28Updated=29_=28JIRA=29?=) Date: Fri, 6 Jan 2012 06:02:09 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11837) Hot key: onkeypress attribute doesn't work with special keys In-Reply-To: <1275549371.24421.1324389250026.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1691511377.44870.1325847729489.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated RF-11837: ---------------------------- Summary: Hot key: onkeypress attribute doesn't work with special keys (was: Hot key: type attribute doesn't work when set to keypress) > Hot key: onkeypress attribute doesn't work with special keys > ------------------------------------------------------------ > > Key: RF-11837 > URL: https://issues.jboss.org/browse/RF-11837 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-misc > Affects Versions: 4.1.0.Final > Environment: RichFaces 4.1.1-SNAPSHOT > Metamer 4.1.1-SNAPSHOT > Mojarra 2.1.3 > JBoss AS 7.1.0.Beta1 > OpenJDK Runtime Environment 1.6.0_22-b22 @ Linux > Chrome 16.0.912.63 @ Linux i686 > Reporter: Pavol Pitonak > Assignee: Luk?? Fry? > Fix For: 4.1.1.Final > > > # deploy Metamer and open http://localhost:8080/metamer/faces/components/richHotKey/simple.xhtml > # press Ctrl+X > # set attribute type=keypress > # press Ctrl+X > result: > * first action is executed, second 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 Fri Jan 6 06:08:09 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28Commented=29_=28JIRA=29?=) Date: Fri, 6 Jan 2012 06:08:09 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11837) Hot key: onkeypress attribute doesn't work with special keys In-Reply-To: <1275549371.24421.1324389250026.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <739790552.44874.1325848089559.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12654248#comment-12654248 ] Luk?? Fry? commented on RF-11837: --------------------------------- Problem is with {{jquery.hotkeys.js}} plugin which does not observe {{keypress}} event when special key is hold ([there is issue managed outside of upstream|https://github.com/tzuryby/jquery.hotkeys/issues/7]). I'm not suggesting to go more deeply, since plugin itself is not addressing this issue. We should either * *document that special keys can't be used* with {{keypress}} * or rather *remove this attribute at all* ** it can be replaced with {{keyup}} > Hot key: onkeypress attribute doesn't work with special keys > ------------------------------------------------------------ > > Key: RF-11837 > URL: https://issues.jboss.org/browse/RF-11837 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-misc > Affects Versions: 4.1.0.Final > Environment: RichFaces 4.1.1-SNAPSHOT > Metamer 4.1.1-SNAPSHOT > Mojarra 2.1.3 > JBoss AS 7.1.0.Beta1 > OpenJDK Runtime Environment 1.6.0_22-b22 @ Linux > Chrome 16.0.912.63 @ Linux i686 > Reporter: Pavol Pitonak > Assignee: Luk?? Fry? > Fix For: 4.1.1.Final > > > # deploy Metamer and open http://localhost:8080/metamer/faces/components/richHotKey/simple.xhtml > # press Ctrl+X > # set attribute type=keypress > # press Ctrl+X > result: > * first action is executed, second 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 Fri Jan 6 06:19:10 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28Commented=29_=28JIRA=29?=) Date: Fri, 6 Jan 2012 06:19:10 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11839) Hot key doesn't work when focus in on editor In-Reply-To: <334225743.24536.1324390329689.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <199455277.44894.1325848750021.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12654251#comment-12654251 ] Luk?? Fry? commented on RF-11839: --------------------------------- We would need to go step deeper and when {{hotKey}} is bound to editor, it would be necessary to register this event in {{iframe}} used by editor. This is not as easy as it seems because {{selector}} can generically point to the browser that we are not able to detect at server-side and furthermore, jQuery would be necessary to load into that {{iframe}}. {{Editor}} itself has support for hotkeys (using keystroke plugin), then integration could be managed using [{{Editor}}'s API|http://docs.cksource.com/ckeditor_api/symbols/src/plugins_keystrokes_plugin.js.html]. > Hot key doesn't work when focus in on editor > -------------------------------------------- > > Key: RF-11839 > URL: https://issues.jboss.org/browse/RF-11839 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input, component-misc > Affects Versions: 4.1.0.Final > Environment: RichFaces 4.1.1-SNAPSHOT > Metamer 4.1.1-SNAPSHOT > Mojarra 2.1.3 > JBoss AS 7.1.0.Beta1 > OpenJDK Runtime Environment 1.6.0_22-b22 @ Linux > Chrome 16.0.912.63 @ Linux x86_64, Firefox 8.0 @ Linux x86_64 > Reporter: Pavol Pitonak > Assignee: Luk?? Fry? > Fix For: 4.1.1.Final > > > # deploy Metamer and open http://localhost:8080/metamer/faces/components/richHotKey/editor.xhtml > # press Ctrl+X (to focus on editor) > # press Alt+X (to blur from editor) > result: > * when Ctrl+X is pressed, focus is in editor > * when Alt+X is pressed, nothing happens (editor should no longer be focused) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 6 06:21:09 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28Updated=29_=28JIRA=29?=) Date: Fri, 6 Jan 2012 06:21:09 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11839) Hot key doesn't work when focus in on editor In-Reply-To: <334225743.24536.1324390329689.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1739280549.44900.1325848869622.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated RF-11839: ---------------------------- Workaround Description: Use CKEditor's [keyStroke handler|http://docs.cksource.com/ckeditor_api/symbols/CKEDITOR.keystrokeHandler.html] to handle key events when editor focus. Workaround: Workaround Exists > Hot key doesn't work when focus in on editor > -------------------------------------------- > > Key: RF-11839 > URL: https://issues.jboss.org/browse/RF-11839 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input, component-misc > Affects Versions: 4.1.0.Final > Environment: RichFaces 4.1.1-SNAPSHOT > Metamer 4.1.1-SNAPSHOT > Mojarra 2.1.3 > JBoss AS 7.1.0.Beta1 > OpenJDK Runtime Environment 1.6.0_22-b22 @ Linux > Chrome 16.0.912.63 @ Linux x86_64, Firefox 8.0 @ Linux x86_64 > Reporter: Pavol Pitonak > Assignee: Luk?? Fry? > Fix For: 4.1.1.Final > > > # deploy Metamer and open http://localhost:8080/metamer/faces/components/richHotKey/editor.xhtml > # press Ctrl+X (to focus on editor) > # press Alt+X (to blur from editor) > result: > * when Ctrl+X is pressed, focus is in editor > * when Alt+X is pressed, nothing happens (editor should no longer be focused) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 6 06:23:10 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28Resolved=29_=28JIRA=29?=) Date: Fri, 6 Jan 2012 06:23:10 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11839) Hot key doesn't work when focus in on editor In-Reply-To: <334225743.24536.1324390329689.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <2009166673.44917.1325848990733.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved RF-11839. ----------------------------- Fix Version/s: (was: 4.1.1.Final) Resolution: Rejected I'm rejecting this issue since proposed solutions are too complex and single-purpose, and furthermore workaround for the issue exists. Limitation will be documented in scope of RFPL-1955. > Hot key doesn't work when focus in on editor > -------------------------------------------- > > Key: RF-11839 > URL: https://issues.jboss.org/browse/RF-11839 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input, component-misc > Affects Versions: 4.1.0.Final > Environment: RichFaces 4.1.1-SNAPSHOT > Metamer 4.1.1-SNAPSHOT > Mojarra 2.1.3 > JBoss AS 7.1.0.Beta1 > OpenJDK Runtime Environment 1.6.0_22-b22 @ Linux > Chrome 16.0.912.63 @ Linux x86_64, Firefox 8.0 @ Linux x86_64 > Reporter: Pavol Pitonak > Assignee: Luk?? Fry? > > # deploy Metamer and open http://localhost:8080/metamer/faces/components/richHotKey/editor.xhtml > # press Ctrl+X (to focus on editor) > # press Alt+X (to blur from editor) > result: > * when Ctrl+X is pressed, focus is in editor > * when Alt+X is pressed, nothing happens (editor should no longer be focused) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 6 07:55:10 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28Resolved=29_=28JIRA=29?=) Date: Fri, 6 Jan 2012 07:55:10 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11824) rich:hotKey - add option to prevent default event handling In-Reply-To: <2043524135.17961.1324056189409.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1957515992.45397.1325854510475.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved RF-11824. ----------------------------- Resolution: Done Added {{preventDefault}} option, {{true}} by default. > rich:hotKey - add option to prevent default event handling > ---------------------------------------------------------- > > Key: RF-11824 > URL: https://issues.jboss.org/browse/RF-11824 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-misc > Affects Versions: 4.1.1.Final > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Priority: Critical > Fix For: 4.1.1.Final > > > Some hot-keys are triggering default event handling ({{ctrl+a}}, {{page-up}}, etc.), > we may try to prevent this behavior, however it is not as simple as {{event.preventDefault()}} or {{return false;}}. > *_Please vote on issue if you would like to having this issue 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 Jan 6 07:57:09 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28Updated=29_=28JIRA=29?=) Date: Fri, 6 Jan 2012 07:57:09 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11837) Hot key: remove onkeypress attribute since it doesn't work with special keys and breaks compatibility with other onkeyup/onkeydown In-Reply-To: <1275549371.24421.1324389250026.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <767209437.45402.1325854629786.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated RF-11837: ---------------------------- Summary: Hot key: remove onkeypress attribute since it doesn't work with special keys and breaks compatibility with other onkeyup/onkeydown (was: Hot key: onkeypress attribute doesn't work with special keys) > Hot key: remove onkeypress attribute since it doesn't work with special keys and breaks compatibility with other onkeyup/onkeydown > ---------------------------------------------------------------------------------------------------------------------------------- > > Key: RF-11837 > URL: https://issues.jboss.org/browse/RF-11837 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-misc > Affects Versions: 4.1.0.Final > Environment: RichFaces 4.1.1-SNAPSHOT > Metamer 4.1.1-SNAPSHOT > Mojarra 2.1.3 > JBoss AS 7.1.0.Beta1 > OpenJDK Runtime Environment 1.6.0_22-b22 @ Linux > Chrome 16.0.912.63 @ Linux i686 > Reporter: Pavol Pitonak > Assignee: Luk?? Fry? > Fix For: 4.1.1.Final > > > # deploy Metamer and open http://localhost:8080/metamer/faces/components/richHotKey/simple.xhtml > # press Ctrl+X > # set attribute type=keypress > # press Ctrl+X > result: > * first action is executed, second 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 Fri Jan 6 07:59:09 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28Resolved=29_=28JIRA=29?=) Date: Fri, 6 Jan 2012 07:59:09 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11837) Hot key: remove onkeypress attribute since it doesn't work with special keys and breaks compatibility with other onkeyup/onkeydown In-Reply-To: <1275549371.24421.1324389250026.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <783490908.45425.1325854749400.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved RF-11837. ----------------------------- Resolution: Done > Hot key: remove onkeypress attribute since it doesn't work with special keys and breaks compatibility with other onkeyup/onkeydown > ---------------------------------------------------------------------------------------------------------------------------------- > > Key: RF-11837 > URL: https://issues.jboss.org/browse/RF-11837 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-misc > Affects Versions: 4.1.0.Final > Environment: RichFaces 4.1.1-SNAPSHOT > Metamer 4.1.1-SNAPSHOT > Mojarra 2.1.3 > JBoss AS 7.1.0.Beta1 > OpenJDK Runtime Environment 1.6.0_22-b22 @ Linux > Chrome 16.0.912.63 @ Linux i686 > Reporter: Pavol Pitonak > Assignee: Luk?? Fry? > Fix For: 4.1.1.Final > > > # deploy Metamer and open http://localhost:8080/metamer/faces/components/richHotKey/simple.xhtml > # press Ctrl+X > # set attribute type=keypress > # press Ctrl+X > result: > * first action is executed, second 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 Fri Jan 6 08:40:10 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28Updated=29_=28JIRA=29?=) Date: Fri, 6 Jan 2012 08:40:10 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11840) jquery.hotkeys.js prevents pickList to observe key events In-Reply-To: <1746550578.24557.1324390689563.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1851651379.45604.1325857210435.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated RF-11840: ---------------------------- Summary: jquery.hotkeys.js prevents pickList to observe key events (was: Hot key: arrow keys do not work in pick/ordering list when hot key is on page) > jquery.hotkeys.js prevents pickList to observe key events > --------------------------------------------------------- > > Key: RF-11840 > URL: https://issues.jboss.org/browse/RF-11840 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-misc, component-selects > Affects Versions: 4.1.0.Final > Environment: RichFaces 4.1.1-SNAPSHOT > Metamer 4.1.1-SNAPSHOT > Mojarra 2.1.3-b02 > JBoss AS 7.1.0.Beta1 > OpenJDK Runtime Environment 1.6.0_22-b22 @ Linux > Chrome 16.0.912.63 @ Linux i686 > Reporter: Pavol Pitonak > Assignee: Luk?? Fry? > Fix For: 4.1.1.Final > > > # deploy Metamer and open http://localhost:8080/metamer/faces/components/richHotKey/pickList.xhtml > # click into pick list to select third item (Phoenix, Arizona) > # press arrow down > result: > * the following item in pick list should be selected (Little Rock, Arkansas) but browser scrolls the page instead > * when rich:hotKey is removed from page, arrows down/up start working again > * there is the same problem with *ordering 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 Fri Jan 6 08:42:09 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28Commented=29_=28JIRA=29?=) Date: Fri, 6 Jan 2012 08:42:09 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11840) jquery.hotkeys.js prevents pickList to observe key events In-Reply-To: <1746550578.24557.1324390689563.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <100013576.45621.1325857329556.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12654297#comment-12654297 ] Luk?? Fry? commented on RF-11840: --------------------------------- {{rich:hotKey}} does not have to be on page to reproduce issue, it's enough to include {{jquery.hotkeys.js}} script in the page: {code:XML} {code} > jquery.hotkeys.js prevents pickList to observe key events > --------------------------------------------------------- > > Key: RF-11840 > URL: https://issues.jboss.org/browse/RF-11840 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-misc, component-selects > Affects Versions: 4.1.0.Final > Environment: RichFaces 4.1.1-SNAPSHOT > Metamer 4.1.1-SNAPSHOT > Mojarra 2.1.3-b02 > JBoss AS 7.1.0.Beta1 > OpenJDK Runtime Environment 1.6.0_22-b22 @ Linux > Chrome 16.0.912.63 @ Linux i686 > Reporter: Pavol Pitonak > Assignee: Luk?? Fry? > Fix For: 4.1.1.Final > > > # deploy Metamer and open http://localhost:8080/metamer/faces/components/richHotKey/pickList.xhtml > # click into pick list to select third item (Phoenix, Arizona) > # press arrow down > result: > * the following item in pick list should be selected (Little Rock, Arkansas) but browser scrolls the page instead > * when rich:hotKey is removed from page, arrows down/up start working again > * there is the same problem with *ordering 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 Fri Jan 6 09:26:10 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28Resolved=29_=28JIRA=29?=) Date: Fri, 6 Jan 2012 09:26:10 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11863) showcase - rich:hotKey - mistake in demo description In-Reply-To: <1960056587.38881.1325672830689.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <261336216.45940.1325859970899.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved RF-11863. ----------------------------- Resolution: Done Used *Home* and *End* instead of arrows. > showcase - rich:hotKey - mistake in demo description > ---------------------------------------------------- > > Key: RF-11863 > URL: https://issues.jboss.org/browse/RF-11863 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-misc, examples, showcase > Affects Versions: 4.1.1.Final > Environment: showcase 4.1.1-SNAPSHOT > Reporter: Juraj Huska > Assignee: Luk?? Fry? > Priority: Trivial > Fix For: 4.1.1.Final > > > In the demo description is said: ??Press Home or End buttons in order to move all items between lists.?? > However, for this action (moving all items), the 'ctrl+right' and 'ctrl+left' shortcuts are bound. > The demo description should be updated according to current bindings. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 6 09:28:09 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28Resolved=29_=28JIRA=29?=) Date: Fri, 6 Jan 2012 09:28:09 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11840) jquery.hotkeys.js prevents pickList to observe key events In-Reply-To: <1746550578.24557.1324390689563.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <959600165.45944.1325860089551.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved RF-11840. ----------------------------- Resolution: Done Sanitized {{jquery.hotkeys.js}} to do not wrap handler when no {{options.key}} provided in {{jQuery.bind('key', options);}} > jquery.hotkeys.js prevents pickList to observe key events > --------------------------------------------------------- > > Key: RF-11840 > URL: https://issues.jboss.org/browse/RF-11840 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-misc, component-selects > Affects Versions: 4.1.0.Final > Environment: RichFaces 4.1.1-SNAPSHOT > Metamer 4.1.1-SNAPSHOT > Mojarra 2.1.3-b02 > JBoss AS 7.1.0.Beta1 > OpenJDK Runtime Environment 1.6.0_22-b22 @ Linux > Chrome 16.0.912.63 @ Linux i686 > Reporter: Pavol Pitonak > Assignee: Luk?? Fry? > Fix For: 4.1.1.Final > > > # deploy Metamer and open http://localhost:8080/metamer/faces/components/richHotKey/pickList.xhtml > # click into pick list to select third item (Phoenix, Arizona) > # press arrow down > result: > * the following item in pick list should be selected (Little Rock, Arkansas) but browser scrolls the page instead > * when rich:hotKey is removed from page, arrows down/up start working again > * there is the same problem with *ordering 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 Fri Jan 6 09:32:10 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28Updated=29_=28JIRA=29?=) Date: Fri, 6 Jan 2012 09:32:10 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11816) Notify stack: names of CSS classes do not follow naming conventions In-Reply-To: <1667763817.10485.1323880569406.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <223497612.45978.1325860330421.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated RF-11816: ---------------------------- Priority: Major (was: Minor) Affects: Compatibility/Configuration > Notify stack: names of CSS classes do not follow naming conventions > ------------------------------------------------------------------- > > Key: RF-11816 > URL: https://issues.jboss.org/browse/RF-11816 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-validators > Affects Versions: 4.1.0.Final > Reporter: Pavol Pitonak > Assignee: Luk?? Fry? > Fix For: 4.1.1.Final > > > Notify stack has 4 CSS classes that do not follow naming conventions: > * rf-ntf-pos-topLeft > * rf-ntf-pos-topRight > * rf-ntf-pos-bottomLeft > * rf-ntf-pos-bottomRight > Compare with similar classes of popup panel: > * rf-pp-hndlr-tl > * rf-pp-hndlr-tr > * rf-pp-hndlr-bl > * rf-pp-hndlr-br -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 6 09:36:10 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28Commented=29_=28JIRA=29?=) Date: Fri, 6 Jan 2012 09:36:10 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11615) Upgrade to JBoss Parent version 8 In-Reply-To: <1714858172.39799.1320059745985.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1375395871.46012.1325860570554.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12654326#comment-12654326 ] Luk?? Fry? commented on RF-11615: --------------------------------- {code} Tests in error: testMarshal(org.richfaces.cdk.xmlconfig.testmodel.BehaviorBeanTest): JAXB Marshaller error testMarshal(org.richfaces.cdk.xmlconfig.testmodel.ValidatorBeanTest): JAXB Marshaller error testMarshal(org.richfaces.cdk.xmlconfig.testmodel.ConverterBeanTest): JAXB Marshaller error generationTest(org.richfaces.cdk.xmlconfig.TaglibGeneratorVisitorTest): org.dom4j.DocumentFactory cannot be cast to org.dom4j.DocumentFactory [INFO] RichFaces CDK Generator ........................... FAILURE {code} > Upgrade to JBoss Parent version 8 > --------------------------------- > > Key: RF-11615 > URL: https://issues.jboss.org/browse/RF-11615 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 4.1.0.Milestone4 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Priority: Minor > Fix For: 4.1.1.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 Fri Jan 6 09:54:09 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28Issue_Comment_Edited=29_=28JIRA=29?=) Date: Fri, 6 Jan 2012 09:54:09 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11615) Upgrade to JBoss Parent version 8 In-Reply-To: <1714858172.39799.1320059745985.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <225717931.46059.1325861649718.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12654326#comment-12654326 ] Luk?? Fry? edited comment on RF-11615 at 1/6/12 9:52 AM: --------------------------------------------------------- Following issue is brought by upgrade to of {{maven-surefire-plugin}} ({{2.5}} -> {{2.10}}), bug has been identified with plugin version {{2.9}}. Problem is solved with latest version of plugin: {{2.11}}. {code} Tests in error: testMarshal(org.richfaces.cdk.xmlconfig.testmodel.BehaviorBeanTest): JAXB Marshaller error testMarshal(org.richfaces.cdk.xmlconfig.testmodel.ValidatorBeanTest): JAXB Marshaller error testMarshal(org.richfaces.cdk.xmlconfig.testmodel.ConverterBeanTest): JAXB Marshaller error generationTest(org.richfaces.cdk.xmlconfig.TaglibGeneratorVisitorTest): org.dom4j.DocumentFactory cannot be cast to org.dom4j.DocumentFactory [INFO] RichFaces CDK Generator ........................... FAILURE {code} was (Author: lfryc): {code} Tests in error: testMarshal(org.richfaces.cdk.xmlconfig.testmodel.BehaviorBeanTest): JAXB Marshaller error testMarshal(org.richfaces.cdk.xmlconfig.testmodel.ValidatorBeanTest): JAXB Marshaller error testMarshal(org.richfaces.cdk.xmlconfig.testmodel.ConverterBeanTest): JAXB Marshaller error generationTest(org.richfaces.cdk.xmlconfig.TaglibGeneratorVisitorTest): org.dom4j.DocumentFactory cannot be cast to org.dom4j.DocumentFactory [INFO] RichFaces CDK Generator ........................... FAILURE {code} > Upgrade to JBoss Parent version 8 > --------------------------------- > > Key: RF-11615 > URL: https://issues.jboss.org/browse/RF-11615 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 4.1.0.Milestone4 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Priority: Minor > Fix For: 4.1.1.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 Fri Jan 6 10:02:09 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28Issue_Comment_Edited=29_=28JIRA=29?=) Date: Fri, 6 Jan 2012 10:02:09 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11615) Upgrade to JBoss Parent version 8 In-Reply-To: <1714858172.39799.1320059745985.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <347066272.46103.1325862129650.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12654326#comment-12654326 ] Luk?? Fry? edited comment on RF-11615 at 1/6/12 10:00 AM: ---------------------------------------------------------- Following issue is brought by upgrade to of {{maven-surefire-plugin}} ({{2.5}} -> {{2.10}}), bug has been identified with plugin version {{2.9}}. Problem is solved with latest version of plugin: {{2.11}}. {code} Tests in error: testMarshal(org.richfaces.cdk.xmlconfig.testmodel.BehaviorBeanTest): JAXB Marshaller error testMarshal(org.richfaces.cdk.xmlconfig.testmodel.ValidatorBeanTest): JAXB Marshaller error testMarshal(org.richfaces.cdk.xmlconfig.testmodel.ConverterBeanTest): JAXB Marshaller error generationTest(org.richfaces.cdk.xmlconfig.TaglibGeneratorVisitorTest): org.dom4j.DocumentFactory cannot be cast to org.dom4j.DocumentFactory [INFO] RichFaces CDK Generator ........................... FAILURE {code} Problem is probably related to: http://jira.codehaus.org/browse/SUREFIRE-801 was (Author: lfryc): Following issue is brought by upgrade to of {{maven-surefire-plugin}} ({{2.5}} -> {{2.10}}), bug has been identified with plugin version {{2.9}}. Problem is solved with latest version of plugin: {{2.11}}. {code} Tests in error: testMarshal(org.richfaces.cdk.xmlconfig.testmodel.BehaviorBeanTest): JAXB Marshaller error testMarshal(org.richfaces.cdk.xmlconfig.testmodel.ValidatorBeanTest): JAXB Marshaller error testMarshal(org.richfaces.cdk.xmlconfig.testmodel.ConverterBeanTest): JAXB Marshaller error generationTest(org.richfaces.cdk.xmlconfig.TaglibGeneratorVisitorTest): org.dom4j.DocumentFactory cannot be cast to org.dom4j.DocumentFactory [INFO] RichFaces CDK Generator ........................... FAILURE {code} > Upgrade to JBoss Parent version 8 > --------------------------------- > > Key: RF-11615 > URL: https://issues.jboss.org/browse/RF-11615 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 4.1.0.Milestone4 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Priority: Minor > Fix For: 4.1.1.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 Fri Jan 6 10:44:09 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28Commented=29_=28JIRA=29?=) Date: Fri, 6 Jan 2012 10:44:09 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11808) Archetypes : remove the generation of *-source jars plumbing In-Reply-To: <1095649657.3045.1323708909608.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1639551280.46248.1325864649532.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12654346#comment-12654346 ] Luk?? Fry? commented on RF-11808: --------------------------------- These sources are assembled during release in order to package them in RichFaces distribution ({{build/dist/pom.xml}}). I don't think we should remove them from distribution since user's might use them. > Archetypes : remove the generation of *-source jars plumbing > ------------------------------------------------------------ > > Key: RF-11808 > URL: https://issues.jboss.org/browse/RF-11808 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: archetype > Affects Versions: 4.1.0.CR2 > Reporter: Fred Bricon > Assignee: Luk?? Fry? > Priority: Minor > Fix For: 4.1.1.Final > > > The RF archetypes have some configuration to create *-source jars. Since the sources are already packaged in the actual archetype, this seems unnecessary, clutters the pom.xml and adds extra overhead to maintain the maven-assembly-plugin configuration. > Unless there's a good reason to keep that boilerplate, my suggestion is to stop generating the *-source packages and clean up the pom.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 Jan 6 10:44:09 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28Issue_Comment_Edited=29_=28JIRA=29?=) Date: Fri, 6 Jan 2012 10:44:09 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11808) Archetypes : remove the generation of *-source jars plumbing In-Reply-To: <1095649657.3045.1323708909608.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <997677781.46251.1325864649627.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12654346#comment-12654346 ] Luk?? Fry? edited comment on RF-11808 at 1/6/12 10:43 AM: ---------------------------------------------------------- These sources are assembled during release in order to package them in RichFaces distribution ({{build/dist/pom.xml}}). I don't think we should remove them from distribution since user's might use them to install to local repository. was (Author: lfryc): These sources are assembled during release in order to package them in RichFaces distribution ({{build/dist/pom.xml}}). I don't think we should remove them from distribution since user's might use them. > Archetypes : remove the generation of *-source jars plumbing > ------------------------------------------------------------ > > Key: RF-11808 > URL: https://issues.jboss.org/browse/RF-11808 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: archetype > Affects Versions: 4.1.0.CR2 > Reporter: Fred Bricon > Assignee: Luk?? Fry? > Priority: Minor > Fix For: 4.1.1.Final > > > The RF archetypes have some configuration to create *-source jars. Since the sources are already packaged in the actual archetype, this seems unnecessary, clutters the pom.xml and adds extra overhead to maintain the maven-assembly-plugin configuration. > Unless there's a good reason to keep that boilerplate, my suggestion is to stop generating the *-source packages and clean up the pom.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 Jan 6 11:09:09 2012 From: jira-events at lists.jboss.org (SBS JIRA Integration (Updated) (JIRA)) Date: Fri, 6 Jan 2012 11:09:09 -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: <1201845717.46313.1325866149658.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 ] SBS JIRA Integration updated RF-11739: -------------------------------------- Forum Reference: http://community.jboss.org/message/642770#642770, http://community.jboss.org/message/638045#638045 (was: 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? > Priority: Critical > Fix For: 4.1.1.Final, 4.2-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 Jan 6 11:19:10 2012 From: jira-events at lists.jboss.org (Brian Leathem (Issue Comment Edited) (JIRA)) Date: Fri, 6 Jan 2012 11:19:10 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11749) columnGroup does not work in extendedDataTable header facet In-Reply-To: <1511398401.50702.1322577640646.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <276942840.46354.1325866750535.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12649057#comment-12649057 ] Brian Leathem edited comment on RF-11749 at 1/6/12 11:18 AM: ------------------------------------------------------------- I used the same header in rich:extendedDataTable of before Richfaces 3.3.3, it worked well. It seems the complex header is no problem in rich:dataTable. {code} {code} was (Author: hantsy): I used the same header in rich:extendedDataTable of before Richfaces 3.3.3, it worked well. It seems the complex header is no problem in rich:dataTable. > columnGroup does not work in extendedDataTable header facet > ----------------------------------------------------------- > > Key: RF-11749 > URL: https://issues.jboss.org/browse/RF-11749 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Environment: Richfaces 4.1CR1 > Reporter: hantsy bai > Labels: waiting_on_user > Attachments: extenedDataTable.png > > > columnGroup does not work in extendedDataTable header facet,Please refer the forum post. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 6 11:25:09 2012 From: jira-events at lists.jboss.org (Brian Leathem (Updated) (JIRA)) Date: Fri, 6 Jan 2012 11:25:09 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11749) columnGroup does not work in extendedDataTable header facet In-Reply-To: <1511398401.50702.1322577640646.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <458975261.46405.1325867109529.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-11749: ------------------------------- Fix Version/s: 4.2-Tracking Labels: (was: waiting_on_user) Component/s: component-tables Forum Reference: http://community.jboss.org/thread/175491?tstart=0 (was: http://community.jboss.org/thread/175491?tstart=0) > columnGroup does not work in extendedDataTable header facet > ----------------------------------------------------------- > > Key: RF-11749 > URL: https://issues.jboss.org/browse/RF-11749 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Environment: Richfaces 4.1CR1 > Reporter: hantsy bai > Fix For: 4.2-Tracking > > Attachments: extenedDataTable.png > > > columnGroup does not work in extendedDataTable header facet,Please refer the forum post. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 6 11:25:10 2012 From: jira-events at lists.jboss.org (Brian Leathem (Resolved) (JIRA)) Date: Fri, 6 Jan 2012 11:25:10 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11753) faulty rendering of rich:dataTable and rich:collapsibleSubTable In-Reply-To: <1052538550.53617.1322646160994.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <586105443.46414.1325867110100.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-11753. -------------------------------- Labels: (was: waiting_on_user) Assignee: Brian Leathem Resolution: Out of Date Already fixed. > faulty rendering of rich:dataTable and rich:collapsibleSubTable > --------------------------------------------------------------- > > Key: RF-11753 > URL: https://issues.jboss.org/browse/RF-11753 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables, regression > Affects Versions: 4.1.0.CR1 > Environment: Apache Tomcat 6.0 > Java 1.6.0_24 > Mojarra 2.1.2 > Reporter: Pavel Hofr?k > Assignee: Brian Leathem > > a4j:commandLink launches action listener and render a4j:outputPanel. In this listener I change data that are displayed in a4j:outputPanel (There are some h:outputTexts and rich:dataTable) > Problem is that data are succesfully changed in managed bean, all outputTexts are rendered with changes, but not dataTable. When I render this outputPanel again (with no changes in mb), table is succesfully rendered with proper values. > There would be problem that dataTable holds reference to List in its value, but I create new one, so referende is invalid. > Same problem goes to collapsibleSubTable > RF 4.1M3 and M4 were ok > code example is in http://community.jboss.org/message/638563 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 6 11:27:12 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28Resolved=29_=28JIRA=29?=) Date: Fri, 6 Jan 2012 11:27:12 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11615) Upgrade to JBoss Parent version 8 In-Reply-To: <1714858172.39799.1320059745985.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1484633542.46429.1325867233004.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved RF-11615. ----------------------------- Resolution: Done All issues incorporated by upgrade were solved. > Upgrade to JBoss Parent version 8 > --------------------------------- > > Key: RF-11615 > URL: https://issues.jboss.org/browse/RF-11615 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 4.1.0.Milestone4 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Priority: Minor > Fix For: 4.1.1.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 Fri Jan 6 11:43:09 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28Commented=29_=28JIRA=29?=) Date: Fri, 6 Jan 2012 11:43:09 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11808) Archetypes : remove the generation of *-source jars plumbing In-Reply-To: <1095649657.3045.1323708909608.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1572929972.46501.1325868189492.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12654372#comment-12654372 ] Luk?? Fry? commented on RF-11808: --------------------------------- Ok, I have decided to package {{richfaces-archetype-simpleapp.jar}} as part of the ZIP distribution of RichFaces. > Archetypes : remove the generation of *-source jars plumbing > ------------------------------------------------------------ > > Key: RF-11808 > URL: https://issues.jboss.org/browse/RF-11808 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: archetype > Affects Versions: 4.1.0.CR2 > Reporter: Fred Bricon > Assignee: Luk?? Fry? > Priority: Minor > Fix For: 4.1.1.Final > > > The RF archetypes have some configuration to create *-source jars. Since the sources are already packaged in the actual archetype, this seems unnecessary, clutters the pom.xml and adds extra overhead to maintain the maven-assembly-plugin configuration. > Unless there's a good reason to keep that boilerplate, my suggestion is to stop generating the *-source packages and clean up the pom.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 Jan 6 11:43:09 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28Resolved=29_=28JIRA=29?=) Date: Fri, 6 Jan 2012 11:43:09 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11808) Archetypes : remove the generation of *-source jars plumbing In-Reply-To: <1095649657.3045.1323708909608.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <804465527.46503.1325868189596.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved RF-11808. ----------------------------- Resolution: Done > Archetypes : remove the generation of *-source jars plumbing > ------------------------------------------------------------ > > Key: RF-11808 > URL: https://issues.jboss.org/browse/RF-11808 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: archetype > Affects Versions: 4.1.0.CR2 > Reporter: Fred Bricon > Assignee: Luk?? Fry? > Priority: Minor > Fix For: 4.1.1.Final > > > The RF archetypes have some configuration to create *-source jars. Since the sources are already packaged in the actual archetype, this seems unnecessary, clutters the pom.xml and adds extra overhead to maintain the maven-assembly-plugin configuration. > Unless there's a good reason to keep that boilerplate, my suggestion is to stop generating the *-source packages and clean up the pom.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 Jan 6 13:33:09 2012 From: jira-events at lists.jboss.org (SBS JIRA Integration (Updated) (JIRA)) Date: Fri, 6 Jan 2012 13:33:09 -0500 (EST) 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: <1008352534.46620.1325874789443.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] SBS JIRA Integration updated RF-11842: -------------------------------------- Forum Reference: http://community.jboss.org/message/645104#645104 > 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.1.1.Final > Reporter: Brian Leathem > Fix For: 4.2-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 Fri Jan 6 20:39:09 2012 From: jira-events at lists.jboss.org (Andrew Wheeler (Created) (JIRA)) Date: Fri, 6 Jan 2012 20:39:09 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11864) selectOneMenu with converter inside collapsiblePanel does not show correct value when switchType is ajax Message-ID: <1856188393.47025.1325900349394.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> selectOneMenu with converter inside collapsiblePanel does not show correct value when switchType is ajax -------------------------------------------------------------------------------------------------------- Key: RF-11864 URL: https://issues.jboss.org/browse/RF-11864 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.1.0.Final Environment: Linux, 7.0.2.Final, Seam 3.1.Final (faces, solder and persistence) Reporter: Andrew Wheeler If the panel contents contain a selectOneMenu with a custom converter and the switchType is "ajax" then the correct option is not shown. If the switchType is changed to "client" then the correct option is displayed. In both instances the converter function getAsString returns the correct value but it appears this is not used to mark the option as selected. {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 Jan 6 20:49:09 2012 From: jira-events at lists.jboss.org (Andrew Wheeler (Created) (JIRA)) Date: Fri, 6 Jan 2012 20:49:09 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11865) Partial build of component tree for lazy loaded components Message-ID: <624327655.47030.1325900949445.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Partial build of component tree for lazy loaded components ---------------------------------------------------------- Key: RF-11865 URL: https://issues.jboss.org/browse/RF-11865 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 4.1.0.Final Environment: Any Reporter: Andrew Wheeler Priority: Minor I often use collapsible panel with switchType="ajax". This prevents the rendering of the content until it is requested by the user. This however does not prevent the component tree from being constructed. In one use-case the panel hides expensive to construct output from a JCR query. It would be nice if RichFaces could place a marker in the component tree and only construct the child elements on the first request. This would improve page rendering and memory usage considerably. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 6 23:54:09 2012 From: jira-events at lists.jboss.org (Andrew Wheeler (Commented) (JIRA)) Date: Fri, 6 Jan 2012 23:54:09 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11864) selectOneMenu with converter inside collapsiblePanel does not show correct value when switchType is ajax In-Reply-To: <1856188393.47025.1325900349394.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1812068164.47063.1325912049457.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12654461#comment-12654461 ] Andrew Wheeler commented on RF-11864: ------------------------------------- Sorry, but this appears to be my problem. I had a mis-match between the scope of the backing bean and the data used to produce the option lists. This caused the the two values to "not equal" even though they naturally are. > selectOneMenu with converter inside collapsiblePanel does not show correct value when switchType is ajax > -------------------------------------------------------------------------------------------------------- > > Key: RF-11864 > URL: https://issues.jboss.org/browse/RF-11864 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.1.0.Final > Environment: Linux, 7.0.2.Final, Seam 3.1.Final (faces, solder and persistence) > Reporter: Andrew Wheeler > Labels: ajax, lazy-loaded > > If the panel contents contain a selectOneMenu with a custom converter and the switchType is "ajax" then the correct option is not shown. If the switchType is changed to "client" then the correct option is displayed. In both instances the converter function getAsString returns the correct value but it appears this is not used to mark the option as selected. > {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 Jan 6 23:54:09 2012 From: jira-events at lists.jboss.org (Andrew Wheeler (Closed) (JIRA)) Date: Fri, 6 Jan 2012 23:54:09 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11864) selectOneMenu with converter inside collapsiblePanel does not show correct value when switchType is ajax In-Reply-To: <1856188393.47025.1325900349394.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1201163298.47065.1325912049528.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Wheeler closed RF-11864. ------------------------------- Resolution: Done > selectOneMenu with converter inside collapsiblePanel does not show correct value when switchType is ajax > -------------------------------------------------------------------------------------------------------- > > Key: RF-11864 > URL: https://issues.jboss.org/browse/RF-11864 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.1.0.Final > Environment: Linux, 7.0.2.Final, Seam 3.1.Final (faces, solder and persistence) > Reporter: Andrew Wheeler > Labels: ajax, lazy-loaded > > If the panel contents contain a selectOneMenu with a custom converter and the switchType is "ajax" then the correct option is not shown. If the switchType is changed to "client" then the correct option is displayed. In both instances the converter function getAsString returns the correct value but it appears this is not used to mark the option as selected. > {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 Jan 9 04:46:15 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28Created=29_=28JIRA=29?=) Date: Mon, 9 Jan 2012 04:46:15 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11866) Push: Provide more useful message when subtopic does not meet criteria Message-ID: <1682962725.47910.1326102375475.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Push: Provide more useful message when subtopic does not meet criteria ---------------------------------------------------------------------- Key: RF-11866 URL: https://issues.jboss.org/browse/RF-11866 Project: RichFaces Issue Type: Enhancement Security Level: Public (Everyone can see) Components: core Affects Versions: 4.1.0.Final Reporter: Luk?? Fry? Assignee: Luk?? Fry? Priority: Minor Fix For: 4.1.1.Final See forums. https://github.com/richfaces/core/blob/develop/api/src/main/java/org/richfaces/application/push/TopicKey.java#L76 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 9 05:09:11 2012 From: jira-events at lists.jboss.org (Juraj Huska (Closed) (JIRA)) Date: Mon, 9 Jan 2012 05:09:11 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11863) showcase - rich:hotKey - mistake in demo description In-Reply-To: <1960056587.38881.1325672830689.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <917802285.48011.1326103751729.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj Huska closed RF-11863. ---------------------------- Verified that text description is right now. > showcase - rich:hotKey - mistake in demo description > ---------------------------------------------------- > > Key: RF-11863 > URL: https://issues.jboss.org/browse/RF-11863 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-misc, examples, showcase > Affects Versions: 4.1.1.Final > Environment: showcase 4.1.1-SNAPSHOT > Reporter: Juraj Huska > Assignee: Luk?? Fry? > Priority: Trivial > Fix For: 4.1.1.Final > > > In the demo description is said: ??Press Home or End buttons in order to move all items between lists.?? > However, for this action (moving all items), the 'ctrl+right' and 'ctrl+left' shortcuts are bound. > The demo description should be updated according to current bindings. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 9 05:27:09 2012 From: jira-events at lists.jboss.org (Juraj Huska (Created) (JIRA)) Date: Mon, 9 Jan 2012 05:27:09 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11867) showcase - rich:hotKey - pressing of home or end key causes moving of whole page instead of just selected/removing all cities on FF 3.6.x Message-ID: <1258943306.48046.1326104829526.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> showcase - rich:hotKey - pressing of home or end key causes moving of whole page instead of just selected/removing all cities on FF 3.6.x ----------------------------------------------------------------------------------------------------------------------------------------- Key: RF-11867 URL: https://issues.jboss.org/browse/RF-11867 Project: RichFaces Issue Type: Enhancement Security Level: Public (Everyone can see) Components: component-misc, showcase Affects Versions: 4.1.1.Final Environment: container: Tomcat 7.0.20, JBoss AS 6.0.0.Final browser: Firefox 3.6.24 Reporter: Juraj Huska Priority: Minor The current binding for selecting/removing all cities in the demo for rich:hotKey are 'home' and 'end' buttons respectively. It works as expected on Chrome and Firefox 8, however it is not working as expected on *Firefox 3.6.x*. Pressing of 'home' of 'end' button (city is selected, so the pickList has user focus) causes moving of the whole page, like the pickList has no focus. The cities are added/removed too, but with the side effect of the page moving, which indeed looks a little ugly. The workaround can be to use other keys. What I would really appreciate is to bind some key to the switching between the two panels. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 9 05:27:10 2012 From: jira-events at lists.jboss.org (Juraj Huska (Updated) (JIRA)) Date: Mon, 9 Jan 2012 05:27:10 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11867) showcase - rich:hotKey - pressing of home or end key causes moving of whole page instead of just selected/removing all cities on FF 3.6.x In-Reply-To: <1258943306.48046.1326104829526.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1792275095.48050.1326104830051.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj Huska updated RF-11867: ----------------------------- Description: The current binding for selecting/removing all cities in the demo for rich:hotKey are 'home' and 'end' buttons respectively. It works as expected on Chrome and Firefox 8, however it is not working as expected on *Firefox 3.6.x*. *Pressing of 'home' of 'end' button (city is selected, so the pickList has user focus) causes moving of the whole page, like the pickList has no focus. The cities are added/removed too, but with the side effect of the page moving, which indeed looks a little ugly.* The workaround can be to use other keys. What I would really appreciate is to bind some key to the switching between the two panels. was: The current binding for selecting/removing all cities in the demo for rich:hotKey are 'home' and 'end' buttons respectively. It works as expected on Chrome and Firefox 8, however it is not working as expected on *Firefox 3.6.x*. Pressing of 'home' of 'end' button (city is selected, so the pickList has user focus) causes moving of the whole page, like the pickList has no focus. The cities are added/removed too, but with the side effect of the page moving, which indeed looks a little ugly. The workaround can be to use other keys. What I would really appreciate is to bind some key to the switching between the two panels. > showcase - rich:hotKey - pressing of home or end key causes moving of whole page instead of just selected/removing all cities on FF 3.6.x > ----------------------------------------------------------------------------------------------------------------------------------------- > > Key: RF-11867 > URL: https://issues.jboss.org/browse/RF-11867 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-misc, showcase > Affects Versions: 4.1.1.Final > Environment: container: Tomcat 7.0.20, JBoss AS 6.0.0.Final > browser: Firefox 3.6.24 > Reporter: Juraj Huska > Priority: Minor > > The current binding for selecting/removing all cities in the demo for rich:hotKey are 'home' and 'end' buttons respectively. > It works as expected on Chrome and Firefox 8, however it is not working as expected on *Firefox 3.6.x*. > *Pressing of 'home' of 'end' button (city is selected, so the pickList has user focus) causes moving of the whole page, like the pickList has no focus. The cities are added/removed too, but with the side effect of the page moving, which indeed looks a little ugly.* > The workaround can be to use other keys. > What I would really appreciate is to bind some key to the switching between the two panels. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 9 05:43:10 2012 From: jira-events at lists.jboss.org (Juraj Huska (Created) (JIRA)) Date: Mon, 9 Jan 2012 05:43:10 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11868) showcase - rich:hotKey - using bound hotKeys generates JS warning on FF 3.6.x Message-ID: <992167140.48074.1326105790453.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> showcase - rich:hotKey - using bound hotKeys generates JS warning on FF 3.6.x ----------------------------------------------------------------------------- Key: RF-11868 URL: https://issues.jboss.org/browse/RF-11868 Project: RichFaces Issue Type: Enhancement Security Level: Public (Everyone can see) Components: component-misc, showcase Affects Versions: 4.1.1.Final Environment: container: all browser: Firefox 3.6.x Reporter: Juraj Huska Priority: Minor Using of bound hot keys in the demo for rich:hotKey generates on Firefox 3.6.x a warning: {code} The 'charCode' property of a keydown event should not be used. The value is meaningless. {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 Jan 9 05:47:09 2012 From: jira-events at lists.jboss.org (Juraj Huska (Commented) (JIRA)) Date: Mon, 9 Jan 2012 05:47:09 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11868) showcase - rich:hotKey - using bound hotKeys generates JS warning on FF 3.6.x In-Reply-To: <992167140.48074.1326105790453.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1642909258.48085.1326106029478.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12654548#comment-12654548 ] Juraj Huska commented on RF-11868: ---------------------------------- It is generated due to JS, generated for rich:hotKey components. > showcase - rich:hotKey - using bound hotKeys generates JS warning on FF 3.6.x > ----------------------------------------------------------------------------- > > Key: RF-11868 > URL: https://issues.jboss.org/browse/RF-11868 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-misc, showcase > Affects Versions: 4.1.1.Final > Environment: container: all > browser: Firefox 3.6.x > Reporter: Juraj Huska > Priority: Minor > > Using of bound hot keys in the demo for rich:hotKey generates on Firefox 3.6.x a warning: > {code} > The 'charCode' property of a keydown event should not be used. The value is meaningless. > {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 Jan 9 05:51:09 2012 From: jira-events at lists.jboss.org (Juraj Huska (Commented) (JIRA)) Date: Mon, 9 Jan 2012 05:51:09 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11867) showcase - rich:hotKey - pressing of home or end key causes moving of whole page instead of just selected/removing all cities on FF 3.6.x In-Reply-To: <1258943306.48046.1326104829526.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1286122620.48092.1326106269425.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12654550#comment-12654550 ] Juraj Huska commented on RF-11867: ---------------------------------- Just note that *it works fine with last stable FF. (9.0.1).* > showcase - rich:hotKey - pressing of home or end key causes moving of whole page instead of just selected/removing all cities on FF 3.6.x > ----------------------------------------------------------------------------------------------------------------------------------------- > > Key: RF-11867 > URL: https://issues.jboss.org/browse/RF-11867 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-misc, showcase > Affects Versions: 4.1.1.Final > Environment: container: Tomcat 7.0.20, JBoss AS 6.0.0.Final > browser: Firefox 3.6.24 > Reporter: Juraj Huska > Priority: Minor > > The current binding for selecting/removing all cities in the demo for rich:hotKey are 'home' and 'end' buttons respectively. > It works as expected on Chrome and Firefox 8, however it is not working as expected on *Firefox 3.6.x*. > *Pressing of 'home' of 'end' button (city is selected, so the pickList has user focus) causes moving of the whole page, like the pickList has no focus. The cities are added/removed too, but with the side effect of the page moving, which indeed looks a little ugly.* > The workaround can be to use other keys. > What I would really appreciate is to bind some key to the switching between the two panels. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 9 05:55:09 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28Updated=29_=28JIRA=29?=) Date: Mon, 9 Jan 2012 05:55:09 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11827) showcase - all rich:autocomplete demos do not work on 4.1.1-SNAPSHOT In-Reply-To: <945549203.21383.1324314009775.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1402739973.48098.1326106509789.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated RF-11827: ---------------------------- Priority: Critical (was: Major) > showcase - all rich:autocomplete demos do not work on 4.1.1-SNAPSHOT > -------------------------------------------------------------------- > > Key: RF-11827 > URL: https://issues.jboss.org/browse/RF-11827 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input, showcase > Environment: richfaces showcase 4.1.1-SNAPSHOT > all containers > all brosers > Reporter: Juraj Huska > Assignee: Luk?? Fry? > Priority: Critical > Fix For: 4.1.1.Final > > > Demos for rich:autocomplete do not work, *whole functionality of autocomplete is broken somehow*. > It is noticeable on *all containers* and on *all browsers*. > It works fine on 4.1.0-SNAPSHOT showcase wars. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 9 06:01:10 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28Assigned=29_=28JIRA=29?=) Date: Mon, 9 Jan 2012 06:01:10 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11827) showcase - all rich:autocomplete demos do not work on 4.1.1-SNAPSHOT In-Reply-To: <945549203.21383.1324314009775.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <709061735.48116.1326106870969.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? reassigned RF-11827: ------------------------------- Assignee: Juraj Huska (was: Luk?? Fry?) Jura, It seems problems you have experienced was solved in RF-11840. Could you please verify that? > showcase - all rich:autocomplete demos do not work on 4.1.1-SNAPSHOT > -------------------------------------------------------------------- > > Key: RF-11827 > URL: https://issues.jboss.org/browse/RF-11827 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input, showcase > Environment: richfaces showcase 4.1.1-SNAPSHOT > all containers > all brosers > Reporter: Juraj Huska > Assignee: Juraj Huska > Priority: Critical > Fix For: 4.1.1.Final > > > Demos for rich:autocomplete do not work, *whole functionality of autocomplete is broken somehow*. > It is noticeable on *all containers* and on *all browsers*. > It works fine on 4.1.0-SNAPSHOT showcase wars. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 9 06:15:10 2012 From: jira-events at lists.jboss.org (Juraj Huska (Created) (JIRA)) Date: Mon, 9 Jan 2012 06:15:10 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11869) showcase - JS warning - Use of getAttributeNodeNS() is deprecated. Use getAttributeNS() instead. Message-ID: <905845731.48184.1326107710988.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> showcase - JS warning - Use of getAttributeNodeNS() is deprecated. Use getAttributeNS() instead. ------------------------------------------------------------------------------------------------ Key: RF-11869 URL: https://issues.jboss.org/browse/RF-11869 Project: RichFaces Issue Type: Enhancement Security Level: Public (Everyone can see) Components: showcase Environment: Firefox 8,9 Reporter: Juraj Huska When the welcome file of showcase is loaded the JS warning is generated: {code} Use of getAttributeNodeNS() is deprecated. Use getAttributeNS() instead. {code} I was not able to find where the function getAttributeNodeNS() is called. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 9 06:17:10 2012 From: jira-events at lists.jboss.org (Juraj Huska (Updated) (JIRA)) Date: Mon, 9 Jan 2012 06:17:10 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11869) showcase - JS warning - Use of getAttributeNodeNS() is deprecated. Use getAttributeNS() instead. In-Reply-To: <905845731.48184.1326107710988.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <2031517068.48196.1326107830532.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj Huska updated RF-11869: ----------------------------- Priority: Minor (was: Major) Description: When the welcome file of showcase is loaded the JS warning is generated: {code} Use of getAttributeNodeNS() is deprecated. Use getAttributeNS() instead. {code} I was not able to find where the function getAttributeNodeNS() is called. And I have not found any issues which are possibly affected by this. was: When the welcome file of showcase is loaded the JS warning is generated: {code} Use of getAttributeNodeNS() is deprecated. Use getAttributeNS() instead. {code} I was not able to find where the function getAttributeNodeNS() is called. > showcase - JS warning - Use of getAttributeNodeNS() is deprecated. Use getAttributeNS() instead. > ------------------------------------------------------------------------------------------------ > > Key: RF-11869 > URL: https://issues.jboss.org/browse/RF-11869 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: showcase > Environment: Firefox 8,9 > Reporter: Juraj Huska > Priority: Minor > > When the welcome file of showcase is loaded the JS warning is generated: > {code} > Use of getAttributeNodeNS() is deprecated. Use getAttributeNS() instead. > {code} > I was not able to find where the function getAttributeNodeNS() is called. And I have not found any issues which are possibly affected by 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 Jan 9 06:47:09 2012 From: jira-events at lists.jboss.org (Juraj Huska (Commented) (JIRA)) Date: Mon, 9 Jan 2012 06:47:09 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11827) showcase - all rich:autocomplete demos do not work on 4.1.1-SNAPSHOT In-Reply-To: <945549203.21383.1324314009775.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1748778399.48280.1326109629456.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12654559#comment-12654559 ] Juraj Huska commented on RF-11827: ---------------------------------- I have verified that the autocomplete demos work now for both maven repo wars and for manually built wars. > showcase - all rich:autocomplete demos do not work on 4.1.1-SNAPSHOT > -------------------------------------------------------------------- > > Key: RF-11827 > URL: https://issues.jboss.org/browse/RF-11827 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input, showcase > Environment: richfaces showcase 4.1.1-SNAPSHOT > all containers > all brosers > Reporter: Juraj Huska > Assignee: Juraj Huska > Priority: Critical > Fix For: 4.1.1.Final > > > Demos for rich:autocomplete do not work, *whole functionality of autocomplete is broken somehow*. > It is noticeable on *all containers* and on *all browsers*. > It works fine on 4.1.0-SNAPSHOT showcase wars. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 9 12:50:10 2012 From: jira-events at lists.jboss.org (Hendy Irawan (Commented) (JIRA)) Date: Mon, 9 Jan 2012 12:50:10 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11103) org.richfaces.skin = plain causes java.lang.IllegalArgumentException: Width (2000) and height (0) cannot be <= 0 In-Reply-To: <358213818.37054.1309943543675.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <934955942.49502.1326131410426.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12654661#comment-12654661 ] Hendy Irawan commented on RF-11103: ----------------------------------- Still affects RichFaces 4.1.0.Final on JBoss AS 7.1.CR1. Please fix this... Thank you. > org.richfaces.skin = plain causes java.lang.IllegalArgumentException: Width (2000) and height (0) cannot be <= 0 > ---------------------------------------------------------------------------------------------------------------- > > Key: RF-11103 > URL: https://issues.jboss.org/browse/RF-11103 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: skinning > Reporter: u j > Priority: Minor > Fix For: 4.Future > > > I tried > {code} > > org.richfaces.skin > plain > > {code} > > and the skinning seems to be disabled, but I get > {code} > 14:44:21,584 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/myapp].[Faces Servlet]] Servlet.service() para servlet Faces Servlet lanz? excepci?n: java.lang.IllegalArgumentException: Width (2000) and height (0) cannot be <= 0 > at java.awt.image.DirectColorModel.createCompatibleWritableRaster(DirectColorModel.java:999) [:1.6.0_24] > at java.awt.image.BufferedImage.(BufferedImage.java:321) [:1.6.0_24] > at org.richfaces.resource.ImageType.createARGBImage(ImageType.java:103) [:4.0.0-SNAPSHOT] > at org.richfaces.resource.ImageType.access$200(ImageType.java:34) [:4.0.0-SNAPSHOT] > at org.richfaces.resource.ImageType$2.createImage(ImageType.java:44) [:4.0.0-SNAPSHOT] > at org.richfaces.resource.ImageType.createImage(ImageType.java:118) [:4.0.0-SNAPSHOT] > at org.richfaces.resource.Java2DUserResourceWrapperImpl.paintAndWrite(Java2DUserResourceWrapperImpl.java:155) [:4.0.0-SNAPSHOT] > at org.richfaces.resource.Java2DUserResourceWrapperImpl.getInputStream(Java2DUserResourceWrapperImpl.java:65) [:4.0.0-SNAPSHOT] > at org.richfaces.resource.CachedResourceImpl.initialize(CachedResourceImpl.java:178) [:4.0.0-SNAPSHOT] > at org.richfaces.resource.ResourceHandlerImpl.handleResourceRequest(ResourceHandlerImpl.java:171) [:4.0.0-SNAPSHOT] > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:407) [:2.1.1-FCS] > 14:45:38,493 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/myapp].[Faces Servlet]] Servlet.service() para servlet Faces Servlet lanz? excepci?n: java.lang.IllegalArgumentException: Width (1) and height (0) cannot be <= 0 > at java.awt.image.DirectColorModel.createCompatibleWritableRaster(DirectColorModel.java:999) [:1.6.0_24] > at java.awt.image.BufferedImage.(BufferedImage.java:321) [:1.6.0_24] > at org.richfaces.resource.ImageType.createARGBImage(ImageType.java:103) [:4.0.0-SNAPSHOT] > at org.richfaces.resource.ImageType.access$200(ImageType.java:34) [:4.0.0-SNAPSHOT] > at org.richfaces.resource.ImageType$2.createImage(ImageType.java:44) [:4.0.0-SNAPSHOT] > at org.richfaces.resource.ImageType.createImage(ImageType.java:118) [:4.0.0-SNAPSHOT] > at org.richfaces.resource.Java2DUserResourceWrapperImpl.paintAndWrite(Java2DUserResourceWrapperImpl.java:155) [:4.0.0-SNAPSHOT] > at org.richfaces.resource.Java2DUserResourceWrapperImpl.getInputStream(Java2DUserResourceWrapperImpl.java:65) [:4.0.0-SNAPSHOT] > at org.richfaces.resource.CachedResourceImpl.initialize(CachedResourceImpl.java:178) [:4.0.0-SNAPSHOT] > at org.richfaces.resource.ResourceHandlerImpl.handleResourceRequest(ResourceHandlerImpl.java:171) [:4.0.0-SNAPSHOT] > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:407) [:2.1.1-FCS] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:324) [:6.0.0.Final] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242) [:6.0.0.Final] > at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:67) [:6.0.0.Final] > {code} > I found a note > http://echelog.matzon.dk/logs/browse/richfaces/1306706400 > 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 Mon Jan 9 16:02:09 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28Created=29_=28JIRA=29?=) Date: Mon, 9 Jan 2012 16:02:09 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11870) SNAPSHOT artifacts in non-default profiles Message-ID: <1079472273.50047.1326142929821.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> SNAPSHOT artifacts in non-default profiles ------------------------------------------ Key: RF-11870 URL: https://issues.jboss.org/browse/RF-11870 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: build/distribution Affects Versions: 4.0.0.Final Reporter: Luk?? Fry? Fix For: 4.1.1.Final Look for -SNAPSHOT occurences across framework, docs and all build deps. Replace with release versions and verify build locally with given profiles. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 9 16:04:09 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28Updated=29_=28JIRA=29?=) Date: Mon, 9 Jan 2012 16:04:09 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11870) Eliminate SNAPSHOT artifacts in non-default profiles In-Reply-To: <1079472273.50047.1326142929821.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <112727381.50050.1326143049369.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated RF-11870: ---------------------------- Summary: Eliminate SNAPSHOT artifacts in non-default profiles (was: SNAPSHOT artifacts in non-default profiles) Description: Look for -SNAPSHOT occurences across framework, docs and all build deps. Replace with release versions and verify build locally with given profiles. This is required by Maven Central. was: Look for -SNAPSHOT occurences across framework, docs and all build deps. Replace with release versions and verify build locally with given profiles. > Eliminate SNAPSHOT artifacts in non-default profiles > ---------------------------------------------------- > > Key: RF-11870 > URL: https://issues.jboss.org/browse/RF-11870 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 4.0.0.Final > Reporter: Luk?? Fry? > Fix For: 4.1.1.Final > > > Look for -SNAPSHOT occurences across framework, docs and all build deps. > Replace with release versions and verify build locally with given profiles. > This is required by Maven Central. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 9 16:19:11 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28Assigned=29_=28JIRA=29?=) Date: Mon, 9 Jan 2012 16:19:11 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11855) error@malformedXML on inputText files - Ajax Validation on event change - RichFaces 4.1 Final In-Reply-To: <26805713.30230.1324582930232.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1670457044.50104.1326143951398.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? reassigned RF-11855: ------------------------------- Assignee: Luk?? Fry? > error at malformedXML on inputText files - Ajax Validation on event change - RichFaces 4.1 Final > ---------------------------------------------------------------------------------------------- > > Key: RF-11855 > URL: https://issues.jboss.org/browse/RF-11855 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.1.0.Final > Environment: Websphere 8.0.0.1 - RAD 8.0.0.4 - JSF Mojorra 2.1.4 - Spring 3.0.6 Final - Hibernate Validator 4.2. - Java 6 > Reporter: Jean ANDRE > Assignee: Luk?? Fry? > Labels: INPUT, MALFORMED, UI, XML > Attachments: createClient1.xhtml, CreateClientController1.java, error at malformedXML-ScreenShot-1.jpg, error at malformedXML.debug.txt, error at malformedXML.viewSource.html, index.xhtml > > > We got a error at malformedXML message when we want to apply an ajax validation on imput text. > The field is include inside a tab in mode "server" - What ever the mode, we getting the error. Tab content is built by including some xhtml. See attachment. > {code} > > xmlns:h="http://java.sun.com/jsf/html" > xmlns:f="http://java.sun.com/jsf/core" > xmlns:rich="http://richfaces.org/rich" > xmlns:c="http://java.sun.com/jsp/jstl/core" > xmlns:a4j="http://richfaces.org/a4j"> > > > > > > > > > > > > > > > > {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 Jan 9 16:19:11 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28Assigned=29_=28JIRA=29?=) Date: Mon, 9 Jan 2012 16:19:11 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11855) error@malformedXML on inputText files - Ajax Validation on event change - RichFaces 4.1 Final In-Reply-To: <26805713.30230.1324582930232.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1530642476.50107.1326143951581.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? reassigned RF-11855: ------------------------------- Assignee: (was: Luk?? Fry?) > error at malformedXML on inputText files - Ajax Validation on event change - RichFaces 4.1 Final > ---------------------------------------------------------------------------------------------- > > Key: RF-11855 > URL: https://issues.jboss.org/browse/RF-11855 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.1.0.Final > Environment: Websphere 8.0.0.1 - RAD 8.0.0.4 - JSF Mojorra 2.1.4 - Spring 3.0.6 Final - Hibernate Validator 4.2. - Java 6 > Reporter: Jean ANDRE > Labels: INPUT, MALFORMED, UI, XML > Attachments: createClient1.xhtml, CreateClientController1.java, error at malformedXML-ScreenShot-1.jpg, error at malformedXML.debug.txt, error at malformedXML.viewSource.html, index.xhtml > > > We got a error at malformedXML message when we want to apply an ajax validation on imput text. > The field is include inside a tab in mode "server" - What ever the mode, we getting the error. Tab content is built by including some xhtml. See attachment. > {code} > > xmlns:h="http://java.sun.com/jsf/html" > xmlns:f="http://java.sun.com/jsf/core" > xmlns:rich="http://richfaces.org/rich" > xmlns:c="http://java.sun.com/jsp/jstl/core" > xmlns:a4j="http://richfaces.org/a4j"> > > > > > > > > > > > > > > > > {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 Jan 9 17:56:09 2012 From: jira-events at lists.jboss.org (Brian Leathem (Updated) (JIRA)) Date: Mon, 9 Jan 2012 17:56:09 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11471) Upgrade to latest version of Atmosphere In-Reply-To: <1090154337.14335.1318029736037.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1976814370.50576.1326149769922.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-11471: ------------------------------- Fix Version/s: 4.1.1.Final (was: 4.2-Tracking) Component/s: component-push/poll third-party (was: core) 0.8.2 is the latest version as of the date of this comment: http://groups.google.com/group/atmosphere-framework/browse_thread/thread/8a4bdc4a2c9f151c?pli=1 > Upgrade to latest version of Atmosphere > --------------------------------------- > > Key: RF-11471 > URL: https://issues.jboss.org/browse/RF-11471 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: component-push/poll, third-party > Affects Versions: 4.1.0.Milestone3 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Priority: Critical > Fix For: 4.1.1.Final > > > Atmosphere 0.8.0-RC2 is planned to be released [1] on right on 4.1.0.M3 code-freeze, we will wait before start of QE cycle to grab this release. > [1] http://groups.google.com/group/atmosphere-framework/browse_thread/thread/caffae0c616c250a -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 10 08:08:09 2012 From: jira-events at lists.jboss.org (Jan Papousek (Created) (JIRA)) Date: Tue, 10 Jan 2012 08:08:09 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11871) Mobile Showcase and a4j:poll demo: stop button doesn't respond on the first click Message-ID: <1495571967.52108.1326200889891.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Mobile Showcase and a4j:poll demo: stop button doesn't respond on the first click --------------------------------------------------------------------------------- Key: RF-11871 URL: https://issues.jboss.org/browse/RF-11871 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: mobile, showcase Affects Versions: 4.1.1.Final Environment: richfaces-showcase-4.1.1-20120106.230242-18 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 Tue Jan 10 08:10:09 2012 From: jira-events at lists.jboss.org (Jan Papousek (Updated) (JIRA)) Date: Tue, 10 Jan 2012 08:10:09 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11871) Mobile Showcase and a4j:poll demo: stop button doesn't respond on the first click In-Reply-To: <1495571967.52108.1326200889891.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1536856517.52112.1326201009508.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Papousek updated RF-11871: ------------------------------ Workaround Description: # deploy showcase and open http://localhost:8080/showcase/phoneHome.jsf#poll:poll (or open http://showcase-jpapouse.rhcloud.com/phoneHome.jsf#poll:poll without deploying) # click on the "Stop" button -> nothing happens (wrong) # click on the "Stop" button again -> polling is stopped (correct) was: # open http://localhost:8080/showcase/phoneHome.jsf#poll:poll # click on the "Stop" button -> nothing happens (wrong) # click on the "Stop" button again -> polling is stopped (correct) > Mobile Showcase and a4j:poll demo: stop button doesn't respond on the first click > --------------------------------------------------------------------------------- > > Key: RF-11871 > URL: https://issues.jboss.org/browse/RF-11871 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: mobile, showcase > Affects Versions: 4.1.1.Final > Environment: richfaces-showcase-4.1.1-20120106.230242-18 > 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 Tue Jan 10 08:17:09 2012 From: jira-events at lists.jboss.org (Jan Papousek (Created) (JIRA)) Date: Tue, 10 Jan 2012 08:17:09 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11872) Mobile Showcase and a4j:region demo: submit button doesn't respond on the first click Message-ID: <1714655772.52122.1326201429582.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> 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.1.1.Final Environment: richfaces-showcase-4.1.1-20120106.230242-18 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 Tue Jan 10 18:48:09 2012 From: jira-events at lists.jboss.org (Wesley Hales (Created) (JIRA)) Date: Tue, 10 Jan 2012 18:48:09 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11873) Enhancements to slidfast.js library Message-ID: <1754905174.53324.1326239289395.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Enhancements to slidfast.js library ----------------------------------- Key: RF-11873 URL: https://issues.jboss.org/browse/RF-11873 Project: RichFaces Issue Type: Enhancement Security Level: Public (Everyone can see) Reporter: Wesley Hales Assignee: Wesley Hales Fix For: 4.1.1.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 Jan 10 18:53:09 2012 From: jira-events at lists.jboss.org (Wesley Hales (Resolved) (JIRA)) Date: Tue, 10 Jan 2012 18:53:09 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11873) Enhancements to slidfast.js library In-Reply-To: <1754905174.53324.1326239289395.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1621045086.53328.1326239589862.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wesley Hales resolved RF-11873. ------------------------------- Resolution: Done > Enhancements to slidfast.js library > ----------------------------------- > > Key: RF-11873 > URL: https://issues.jboss.org/browse/RF-11873 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Wesley Hales > Assignee: Wesley Hales > Fix For: 4.1.1.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 Jan 11 08:45:13 2012 From: jira-events at lists.jboss.org (Pavol Pitonak (Updated) (JIRA)) Date: Wed, 11 Jan 2012 08:45:13 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11547) Panel menu group doesn't keep state after request In-Reply-To: <598634309.33788.1318600157354.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <558985320.54541.1326289513066.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavol Pitonak updated RF-11547: ------------------------------- Component/s: compatibility > Panel menu group doesn't keep state after request > ------------------------------------------------- > > Key: RF-11547 > URL: https://issues.jboss.org/browse/RF-11547 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: compatibility, component-menu > Affects Versions: 4.1.0.Milestone3 > Environment: RichFaces 4.1.0-SNAPSHOT > Metamer 4.1.0-SNAPSHOT r.22800 > Mojarra 2.1.3-SNAPSHOT > JBoss Web 7.0.1.Final > OpenJDK Runtime Environment 1.6.0_22-b22 @ Linux > Chrome 14.0.835.202 @ Linux i686 > Reporter: Pavol Pitonak > Labels: ci_issue > Fix For: 4.Future > > > # deploy Metamer > # open panel menu group inside iteration component, e.g. http://localhost:8080/metamer/faces/components/richPanelMenuGroup/simple.xhtml?templates=richList > # click on "Group 2" > # set some attribute, e.g. bypassUpdates=null > result: > group 2 is expanded again, this happens inside rich:collapsibleSubTable, rich:dataTable, rich:dataGrid, rich:extendedDataTable, rich:list, and a4j:repeat -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 12 06:52:21 2012 From: jira-events at lists.jboss.org (Dmitry Volkov (JIRA)) Date: Thu, 12 Jan 2012 06:52:21 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11874) rich:extendedDataTable keyboard navigation fails in IE8 Message-ID: <1410319121.2645.1326369141473.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Dmitry Volkov created RF-11874: ---------------------------------- Summary: rich:extendedDataTable keyboard navigation fails in IE8 Key: RF-11874 URL: https://issues.jboss.org/browse/RF-11874 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-ScrollableDataTable Affects Versions: 4.1.0.Final Environment: JSF-RI 2 Internet Explorer version 8.0.7601.17514 Reporter: Dmitry Volkov Continous keyboard navigation fails in IE8 when ajax loading(clientRows="..") used. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 12 08:43:21 2012 From: jira-events at lists.jboss.org (Dmitry Volkov (JIRA)) Date: Thu, 12 Jan 2012 08:43:21 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11875) rich:extendedDataTable in ajax loading mode, crashes when dataset length changes between requests Message-ID: <1944546618.3014.1326375801528.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Dmitry Volkov created RF-11875: ---------------------------------- Summary: rich:extendedDataTable in ajax loading mode, crashes when dataset length changes between requests Key: RF-11875 URL: https://issues.jboss.org/browse/RF-11875 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Dmitry Volkov rich:extendedDataTable in ajax loading mode(clientRows=".."), crashes when dataset length changes between requests. It makes ajax loading mode unusable for database paging. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 12 08:45:21 2012 From: jira-events at lists.jboss.org (Dmitry Volkov (JIRA)) Date: Thu, 12 Jan 2012 08:45:21 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11875) rich:extendedDataTable in ajax loading mode, crashes when dataset length changes between requests In-Reply-To: <1944546618.3014.1326375801528.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <586860284.3018.1326375921966.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Volkov updated RF-11875: ------------------------------- Affects Version/s: 4.1.0.Final Environment: JSF-RI 2.0, Tomcat 6.0.29 Component/s: component-ScrollableDataTable > rich:extendedDataTable in ajax loading mode, crashes when dataset length changes between requests > ------------------------------------------------------------------------------------------------- > > Key: RF-11875 > URL: https://issues.jboss.org/browse/RF-11875 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-ScrollableDataTable > Affects Versions: 4.1.0.Final > Environment: JSF-RI 2.0, Tomcat 6.0.29 > Reporter: Dmitry Volkov > > rich:extendedDataTable in ajax loading mode(clientRows=".."), crashes when dataset length changes between requests. > It makes ajax loading mode unusable for database paging. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 12 10:26:21 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 12 Jan 2012 10:26:21 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11876) Add jsf.js resource dependency to all components to work around RF-11739 Message-ID: <850827564.3537.1326381981377.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Luk?? Fry? created RF-11876: ------------------------------- Summary: Add jsf.js resource dependency to all components to work around RF-11739 Key: RF-11876 URL: https://issues.jboss.org/browse/RF-11876 Project: RichFaces Issue Type: Task Security Level: Public (Everyone can see) Components: component Affects Versions: 4.0.0.Final Reporter: Luk?? Fry? Assignee: Luk?? Fry? Priority: Critical Fix For: 4.1.1.Final By adding {{jsf.js}} dependency properly to each component, components will be forced to load {{jsf.js}} just before any RF component requests {{packed.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 Thu Jan 12 10:26:21 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 12 Jan 2012 10:26:21 -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: <433059302.3540.1326381981746.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 ] Luk?? Fry? updated RF-11739: ---------------------------- Fix Version/s: (was: 4.1.1.Final) Priority: Major (was: Critical) Complexity: High 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) There is available workaround on the framework level: RF-11876, scheduling this fix to {{4.2-Tracking}}. > 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.2-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 Thu Jan 12 10:30:22 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 12 Jan 2012 10:30:22 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11877) Upgrade Servlets API to 3.0 in BOM Message-ID: <904396798.3551.1326382222093.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Luk?? Fry? created RF-11877: ------------------------------- Summary: Upgrade Servlets API to 3.0 in BOM Key: RF-11877 URL: https://issues.jboss.org/browse/RF-11877 Project: RichFaces Issue Type: Component Upgrade Security Level: Public (Everyone can see) Components: core Affects Versions: 4.0.0.Final Reporter: Luk?? Fry? Assignee: Luk?? Fry? Priority: Critical Fix For: 4.1.1.Final This issue could break backward compatibility with Servlets 2.5 environments, we should make sure there are no extensive changes in version 3.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 Thu Jan 12 11:11:21 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 12 Jan 2012 11:11:21 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11870) Eliminate SNAPSHOT artifacts in non-default profiles In-Reply-To: <1079472273.50047.1326142929821.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1527243673.3772.1326384681328.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? reassigned RF-11870: ------------------------------- Assignee: Luk?? Fry? > Eliminate SNAPSHOT artifacts in non-default profiles > ---------------------------------------------------- > > Key: RF-11870 > URL: https://issues.jboss.org/browse/RF-11870 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 4.0.0.Final > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 4.1.1.Final > > > Look for -SNAPSHOT occurences across framework, docs and all build deps. > Replace with release versions and verify build locally with given profiles. > This is required by Maven Central. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 12 11:13:23 2012 From: jira-events at lists.jboss.org (Marek Novotny (JIRA)) Date: Thu, 12 Jan 2012 11:13:23 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11878) Add ajax UI tag actionListener to Migration guide Message-ID: <121148811.3790.1326384803339.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Marek Novotny created RF-11878: ---------------------------------- Summary: Add ajax UI tag actionListener to Migration guide Key: RF-11878 URL: https://issues.jboss.org/browse/RF-11878 Project: RichFaces Issue Type: Task Security Level: Public (Everyone can see) Components: doc Affects Versions: 4.1.0.Final Reporter: Marek Novotny Add a4j:actionListener to Migration guide for easy migration path from a4j:support -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 12 11:17:22 2012 From: jira-events at lists.jboss.org (Marek Novotny (JIRA)) Date: Thu, 12 Jan 2012 11:17:22 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11879) Add examle of usage of a4j:actionListener into RF showcase Message-ID: <43091471.3804.1326385042424.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Marek Novotny created RF-11879: ---------------------------------- Summary: Add examle of usage of a4j:actionListener into RF showcase Key: RF-11879 URL: https://issues.jboss.org/browse/RF-11879 Project: RichFaces Issue Type: Task Security Level: Public (Everyone can see) Components: showcase Affects Versions: 4.1.0.Final Reporter: Marek Novotny Priority: Minor a4j:actionListener is not presented in showcase example -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 12 13:15:23 2012 From: jira-events at lists.jboss.org (Dirk Dollar (JIRA)) Date: Thu, 12 Jan 2012 13:15:23 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11880) a4j:jsFunction needs to call event.data instead of data Message-ID: <1048556209.4142.1326392123634.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Dirk Dollar created RF-11880: -------------------------------- Summary: a4j:jsFunction needs to call event.data instead of data Key: RF-11880 URL: https://issues.jboss.org/browse/RF-11880 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.1.0.Final Reporter: Dirk Dollar a4j:jsFunction needs to call event.data instead of data in order to work First I doubted my skills, then I thought it's a bug, now I see there exists a workaround (thanks stackoverflow) http://stackoverflow.com/questions/1365491/how-to-correctly-access-the-data-field-in-an-a4jjsfunction-result please please include in your migration guide, I spent ridiculous amount of time on it for what it is - and i'm certainly not the first 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 Jan 12 16:17:21 2012 From: jira-events at lists.jboss.org (Nicola Nick (JIRA)) Date: Thu, 12 Jan 2012 16:17:21 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11881) Rich Faces 4 can't change jQuery selector Message-ID: <1628113380.4505.1326403041921.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Nicola Nick created RF-11881: -------------------------------- Summary: Rich Faces 4 can't change jQuery selector Key: RF-11881 URL: https://issues.jboss.org/browse/RF-11881 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Nicola Nick I used Rich Faces 4 in my project. Morover i have to use prototype functionality. In the last version of rich faces is used only jQuery. The my problem is that i have to reserve $ selector to prototype but i can't do it because i don't know how to change the selector inside richfaces library. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 12 16:19:22 2012 From: jira-events at lists.jboss.org (Nicola Nick (JIRA)) Date: Thu, 12 Jan 2012 16:19:22 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11881) Rich Faces 4 can't change jQuery selector In-Reply-To: <1628113380.4505.1326403041921.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1916861611.4521.1326403162561.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicola Nick updated RF-11881: ----------------------------- Issue Type: Feature Request (was: Bug) > Rich Faces 4 can't change jQuery selector > ------------------------------------------ > > Key: RF-11881 > URL: https://issues.jboss.org/browse/RF-11881 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Nicola Nick > > I used Rich Faces 4 in my project. Morover i have to use prototype functionality. > In the last version of rich faces is used only jQuery. The my problem is that i have to reserve $ selector to prototype but i can't do it because i don't know how to change the selector inside richfaces library. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 12 20:13:21 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?J=C3=A1n_Jamrich_=28JIRA=29?=) Date: Thu, 12 Jan 2012 20:13:21 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11846) rich:validator ignores @NotEmpty In-Reply-To: <651588956.26878.1324469409370.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1311189443.52523.1326417201500.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12659111#comment-12659111 ] J?n Jamrich commented on RF-11846: ---------------------------------- I was not able to simulate this on latest Metamer. I made another page with inputs (there already was example for rich:validator enclosing many inputs with binding to bean validated by bean validator (JSR-303)) containing simple rich:validator per input. RichFaces 4.1.1-SNAPSHOT Metamer 4.1.1-SNAPSHOT r.${buildNumber} Mojarra 2.1.3-SNAPSHOT JBoss AS 7.0.2.Final Java(TM) SE Runtime Environment 1.6.0_26-b03 @ Linux Chrome 15.0.874.106 @ Linux i686 https://source.jboss.org/browse/RichFaces/modules/tests/metamer/trunk/application/src/main/webapp/components/richValidator/csvOnJsr303.xhtml?r=23141 > rich:validator ignores @NotEmpty > -------------------------------- > > Key: RF-11846 > URL: https://issues.jboss.org/browse/RF-11846 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-validators > Affects Versions: 4.1.0.Final > Environment: Maven 3, Tomcat 6.0.x, Ubuntu 11.10 x64, Glassfish jsf 2.x implementation, Hibernate validator 4.1.0.Final > Reporter: Mercer Traieste > Assignee: J?n Jamrich > > I want to have [client-side validation|http://richfaces-showcase.appspot.com/richfaces/component-sample.jsf?demo=clientValidation&sample=jsr303&skin=blueSky] using rich:validator in Richfaces 4.1, but @NotEmpty is ignored. > {code:xml} > > > > > > {code} > {code:java} > import org.hibernate.validator.constraints.NotEmpty; > import javax.faces.bean.ManagedBean; > import javax.faces.bean.SessionScoped; > import java.io.Serializable; > @ManagedBean > @SessionScoped > public class RichBean implements Serializable { > private static final long serialVersionUID = -2403138958014741653L; > @NotEmpty > private String firstName; > public String getFirstName() { > return firstName; > } > public void setFirstName(String firstName) { > this.firstName = firstName; > } > } > {code} > @Email, another specific Hibernate validator 4.1 annotation works 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 Thu Jan 12 20:13:21 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?J=C3=A1n_Jamrich_=28JIRA=29?=) Date: Thu, 12 Jan 2012 20:13:21 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11846) rich:validator ignores @NotEmpty In-Reply-To: <651588956.26878.1324469409370.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <790844569.52527.1326417201605.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] J?n Jamrich resolved RF-11846. ------------------------------ Resolution: Cannot Reproduce Bug I was not able to simulate this issue. It works for me on latest richfaces snapshots in Metamer > rich:validator ignores @NotEmpty > -------------------------------- > > Key: RF-11846 > URL: https://issues.jboss.org/browse/RF-11846 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-validators > Affects Versions: 4.1.0.Final > Environment: Maven 3, Tomcat 6.0.x, Ubuntu 11.10 x64, Glassfish jsf 2.x implementation, Hibernate validator 4.1.0.Final > Reporter: Mercer Traieste > Assignee: J?n Jamrich > > I want to have [client-side validation|http://richfaces-showcase.appspot.com/richfaces/component-sample.jsf?demo=clientValidation&sample=jsr303&skin=blueSky] using rich:validator in Richfaces 4.1, but @NotEmpty is ignored. > {code:xml} > > > > > > {code} > {code:java} > import org.hibernate.validator.constraints.NotEmpty; > import javax.faces.bean.ManagedBean; > import javax.faces.bean.SessionScoped; > import java.io.Serializable; > @ManagedBean > @SessionScoped > public class RichBean implements Serializable { > private static final long serialVersionUID = -2403138958014741653L; > @NotEmpty > private String firstName; > public String getFirstName() { > return firstName; > } > public void setFirstName(String firstName) { > this.firstName = firstName; > } > } > {code} > @Email, another specific Hibernate validator 4.1 annotation works 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 Jan 13 06:29:22 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 13 Jan 2012 06:29:22 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11816) Notify stack: names of CSS classes do not follow naming conventions In-Reply-To: <1667763817.10485.1323880569406.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1207060103.53350.1326454162361.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved RF-11816. ----------------------------- Resolution: Done > Notify stack: names of CSS classes do not follow naming conventions > ------------------------------------------------------------------- > > Key: RF-11816 > URL: https://issues.jboss.org/browse/RF-11816 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-validators > Affects Versions: 4.1.0.Final > Reporter: Pavol Pitonak > Assignee: Luk?? Fry? > Fix For: 4.2.0.CR1 > > > Notify stack has 4 CSS classes that do not follow naming conventions: > * rf-ntf-pos-topLeft > * rf-ntf-pos-topRight > * rf-ntf-pos-bottomLeft > * rf-ntf-pos-bottomRight > Compare with similar classes of popup panel: > * rf-pp-hndlr-tl > * rf-pp-hndlr-tr > * rf-pp-hndlr-bl > * rf-pp-hndlr-br -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 13 07:13:22 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 13 Jan 2012 07:13:22 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11810) Fix the richfaces-components-ui build to do not overwrite assemblied JAR In-Reply-To: <1133407192.4657.1323764289624.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <138852206.53413.1326456802852.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved RF-11810. ----------------------------- Resolution: Done > Fix the richfaces-components-ui build to do not overwrite assemblied JAR > ------------------------------------------------------------------------ > > Key: RF-11810 > URL: https://issues.jboss.org/browse/RF-11810 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 4.1.0.Final > Reporter: Marek Novotny > Assignee: Luk?? Fry? > Fix For: 4.2.0.CR1 > > > (Issue reported by Lukas Fryc) > Marek Novotny (manaRH) has recently reported that sometimes RF build fails for him since {{richfaces-components-ui}} module is generating JAR using {{maven-assembly-plugin}} which has the same name as the standard {{maven-jar-plugin}} artifact would be called. > This may lead into potential clash for bad timings, especially when these plugins are ran on the same lifecycle phase. > The symptoms are failing applications (and functional tests) which are not able to use any UI implementation classes. > We should either: > # change lifecycle mapping of plugins > # modify {{maven-jar-plugin}} settings > {code:title=Log from Hudson console http://hudson.qa.jboss.com/hudson/job/richfaces-4.1-all-jboss/62/console} > [INFO] ------------------------------------------------------------------------ > [INFO] Building RichFaces Examples Aggregator 4.1.0-SNAPSHOT > [INFO] ------------------------------------------------------------------------ > [INFO] > [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ examples-aggregator --- > [INFO] > [INFO] --- maven-enforcer-plugin:1.0:enforce (enforce-java-version) @ examples-aggregator --- > [INFO] > [INFO] --- maven-enforcer-plugin:1.0:enforce (enforce-maven-version) @ examples-aggregator --- > [INFO] > [INFO] --- maven-source-plugin:2.1.2:jar-no-fork (attach-sources) @ examples-aggregator --- > projectSucceeded org.richfaces.examples:examples-aggregator:4.1.0-SNAPSHOT > [JENKINS] Archiving /mnt/hudson_workspace/workspace/richfaces-4.1-all-jboss/dev-examples/pom.xml to /qa/hudson_master/hudson_home/hudson_workspace/jobs/richfaces-4.1-all-jboss/modules/org.richfaces.examples$examples-aggregator/builds/2011-12-09_06-01-08/archive/org.richfaces.examples/examples-aggregator/4.1.0-SNAPSHOT/examples-aggregator-4.1.0-SNAPSHOT.pom > [INFO] > [INFO] ------------------------------------------------------------------------ > [INFO] Building RichFaces Showcase 4.1.0-SNAPSHOT > [INFO] ------------------------------------------------------------------------ > [INFO] > [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ richfaces-showcase --- > [INFO] Deleting /mnt/hudson_workspace/workspace/richfaces-4.1-all-jboss/showcase/target > [INFO] > [INFO] --- maven-enforcer-plugin:1.0:enforce (enforce-java-version) @ richfaces-showcase --- > [INFO] > [INFO] --- maven-enforcer-plugin:1.0:enforce (enforce-maven-version) @ richfaces-showcase --- > [INFO] > [INFO] --- maven-checkstyle-plugin:2.5:check (richfaces-checkstyle-report) @ richfaces-showcase --- > [INFO] > [INFO] [debug] execute contextualize > [INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ richfaces-showcase --- > [INFO] Using 'UTF-8' encoding to copy filtered resources. > [INFO] Copying 9 resources > [INFO] Copying 0 resource > [INFO] > [INFO] --- maven-compiler-plugin:2.3.1:compile (default-compile) @ richfaces-showcase --- > [INFO] Compiling 97 source files to /mnt/hudson_workspace/workspace/richfaces-4.1-all-jboss/showcase/target/classes > [INFO] ------------------------------------------------------------- > [ERROR] COMPILATION ERROR : > [INFO] ------------------------------------------------------------- > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.1-all-jboss/showcase/src/main/java/org/richfaces/demo/calendar/model/CalendarModelItem.java:[3,26] cannot find symbol > symbol : class CalendarDataModelItem > location: package org.richfaces.model > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.1-all-jboss/showcase/src/main/java/org/richfaces/demo/calendar/model/CalendarModelItem.java:[5,42] cannot find symbol > symbol: class CalendarDataModelItem > public class CalendarModelItem implements CalendarDataModelItem { > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.1-all-jboss/showcase/src/main/java/org/richfaces/demo/tree/TreeBean.java:[36,30] cannot find symbol > symbol : class UITree > location: package org.richfaces.component > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.1-all-jboss/showcase/src/main/java/org/richfaces/demo/tables/ExtTableSelectionBean.java:[13,30] cannot find symbol > symbol : class UIExtendedDataTable > location: package org.richfaces.component > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.1-all-jboss/showcase/src/main/java/org/richfaces/demo/calendar/model/CalendarModel.java:[10,26] cannot find symbol > symbol : class CalendarDataModel > location: package org.richfaces.model > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.1-all-jboss/showcase/src/main/java/org/richfaces/demo/calendar/model/CalendarModel.java:[11,26] cannot find symbol > symbol : class CalendarDataModelItem > location: package org.richfaces.model > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.1-all-jboss/showcase/src/main/java/org/richfaces/demo/calendar/model/CalendarModel.java:[15,38] cannot find symbol > symbol: class CalendarDataModel > public class CalendarModel implements CalendarDataModel { > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.1-all-jboss/showcase/src/main/java/org/richfaces/demo/calendar/model/CalendarModel.java:[28,11] cannot find symbol > symbol : class CalendarDataModelItem > location: class org.richfaces.demo.calendar.model.CalendarModel > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.1-all-jboss/showcase/src/main/java/org/richfaces/demo/tree/TreeBean.java:[72,8] cannot find symbol > symbol : class UITree > location: class org.richfaces.demo.tree.TreeBean > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.1-all-jboss/showcase/src/main/java/org/richfaces/demo/tree/TreeBean.java:[72,23] cannot find symbol > symbol : class UITree > location: class org.richfaces.demo.tree.TreeBean > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.1-all-jboss/showcase/src/main/java/org/richfaces/demo/tables/ExtTableSelectionBean.java:[26,8] cannot find symbol > symbol : class UIExtendedDataTable > location: class org.richfaces.demo.tables.ExtTableSelectionBean > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.1-all-jboss/showcase/src/main/java/org/richfaces/demo/tables/ExtTableSelectionBean.java:[26,41] cannot find symbol > symbol : class UIExtendedDataTable > location: class org.richfaces.demo.tables.ExtTableSelectionBean > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.1-all-jboss/showcase/src/main/java/org/richfaces/demo/calendar/model/CalendarModel.java:[29,8] cannot find symbol > symbol : class CalendarDataModelItem > location: class org.richfaces.demo.calendar.model.CalendarModel > [INFO] 13 errors > [INFO] ------------------------------------------------------------- > mojoFailed org.apache.maven.plugins:maven-compiler-plugin:2.3.1(default-compile) > projectFailed org.richfaces.examples:richfaces-showcase:4.1.0-SNAPSHOT > [JENKINS] Archiving /mnt/hudson_workspace/workspace/richfaces-4.1-all-jboss/showcase/pom.xml to /qa/hudson_master/hudson_home/hudson_workspace/jobs/richfaces-4.1-all-jboss/modules/org.richfaces.examples$richfaces-showcase/builds/2011-12-09_06-01-09/archive/org.richfaces.examples/richfaces-showcase/4.1.0-SNAPSHOT/richfaces-showcase-4.1.0-SNAPSHOT.pom > sessionEnded > [INFO] ------------------------------------------------------------------------ > [INFO] Reactor Summary: > [INFO] > [INFO] RichFaces BOM ..................................... SUCCESS [5.347s] > [INFO] RichFaces Root Parent ............................. SUCCESS [3.868s] > [INFO] RichFaces Core Parent ............................. SUCCESS [0.434s] > [INFO] RichFaces Core API ................................ SUCCESS [55.658s] > [INFO] RichFaces Core Implementation ..................... SUCCESS [5:34.292s] > [INFO] RichFaces Core Aggregator ......................... SUCCESS [0.269s] > [INFO] RichFaces CDK Parent .............................. SUCCESS [0.423s] > [INFO] RichFaces CDK Commons ............................. SUCCESS [14.724s] > [INFO] RichFaces CDK Annotations ......................... SUCCESS [13.308s] > [INFO] RichFaces CDK Attributes .......................... SUCCESS [16.929s] > [INFO] RichFaces CDK XInclude Transformer ................ SUCCESS [24.699s] > [INFO] RichFaces CDK Generator ........................... SUCCESS [2:09.707s] > [INFO] RichFaces CDK Generator Maven Plugin .............. SUCCESS [26.485s] > [INFO] RichFaces CDK Resources Maven Plugin .............. SUCCESS [32.530s] > [INFO] RichFaces CDK Distribution ........................ SUCCESS [29.946s] > [INFO] RichFaces CDK Aggregator .......................... SUCCESS [0.244s] > [INFO] RichFaces UI Components Parent .................... SUCCESS [1.515s] > [INFO] RichFaces UI Components: Common API ............... SUCCESS [20.304s] > [INFO] RichFaces UI Components: Common UI ................ SUCCESS [1:07.241s] > [INFO] RichFaces UI Components: Common Aggregator ........ SUCCESS [0.417s] > [INFO] RichFaces UI Components: Core API ................. SUCCESS [10.942s] > [INFO] RichFaces UI Components: Core UI .................. SUCCESS [2:25.334s] > [INFO] RichFaces UI Components: Core Aggregator .......... SUCCESS [0.368s] > [INFO] RichFaces UI Components: Iteration API ............ SUCCESS [18.222s] > [INFO] RichFaces UI Components: Iteration UI ............. SUCCESS [3:02.748s] > [INFO] RichFaces UI Components: Iteration Aggregator ..... SUCCESS [0.401s] > [INFO] RichFaces UI Components: Miscellanous UI .......... SUCCESS [33.776s] > [INFO] RichFaces UI Components: Miscellanous Aggregator .. SUCCESS [0.366s] > [INFO] RichFaces UI Components: Output API ............... SUCCESS [14.140s] > [INFO] RichFaces UI Components: Output UI ................ SUCCESS [3:05.517s] > [INFO] RichFaces UI Components: Output Aggregator ........ SUCCESS [0.390s] > [INFO] RichFaces UI Components: Input API ................ SUCCESS [13.374s] > [INFO] RichFaces UI Components: Input UI ................. SUCCESS [4:40.374s] > [INFO] RichFaces UI Components: Input Aggregator ......... SUCCESS [0.371s] > [INFO] RichFaces UI Components: Drag-n-Drop API .......... SUCCESS [12.126s] > [INFO] RichFaces UI Components: Drag-n-Drop UI ........... SUCCESS [30.145s] > [INFO] RichFaces UI Components: Drag-n-Drop Aggregator ... SUCCESS [0.406s] > [INFO] RichFaces UI Components: Validator api ............ SUCCESS [15.710s] > [INFO] RichFaces UI Components: Validator ui ............. SUCCESS [2:46.216s] > [INFO] RichFaces UI Components: validator-aggregator ..... SUCCESS [0.372s] > [INFO] Richfaces UI Components API ....................... SUCCESS [23.604s] > [INFO] RichFaces UI Components Static Resources .......... SUCCESS [1:47.298s] > [INFO] RichFaces UI Components UI ........................ SUCCESS [2:01.812s] > [INFO] RichFaces UI Distribution ......................... SUCCESS [0.369s] > [INFO] RichFaces UI Components Aggregator ................ SUCCESS [0.269s] > [INFO] RichFaces Archetypes Simple Application ........... SUCCESS [7.277s] > [INFO] RichFaces Archetypes Component .................... SUCCESS [3.212s] > [INFO] RichFaces Archetypes Component Short .............. SUCCESS [1.981s] > [INFO] RichFaces Archetypes Components Aggregator ........ SUCCESS [2.562s] > [INFO] RichFaces Archetypes GAE Application .............. SUCCESS [2.730s] > [INFO] RichFaces Archetypes Aggregator ................... SUCCESS [0.264s] > [INFO] RichFaces Examples Parent ......................... SUCCESS [0.411s] > [INFO] RichFaces Examples Template ....................... SUCCESS [15.603s] > [INFO] RichFaces Examples Core ........................... SUCCESS [16.374s] > [INFO] RichFaces Examples Miscellanous ................... SUCCESS [12.221s] > [INFO] RichFaces Examples Outputs ........................ SUCCESS [14.603s] > [INFO] RichFaces Examples Inputs ......................... SUCCESS [19.791s] > [INFO] RichFaces Examples Repeater ....................... SUCCESS [26.964s] > [INFO] RichFaces Examples Iteration ...................... SUCCESS [30.285s] > [INFO] RichFaces Examples Push ........................... SUCCESS [18.215s] > [INFO] RichFaces Examples Validators ..................... SUCCESS [19.452s] > [INFO] RichFaces Examples DND ............................ SUCCESS [13.337s] > [INFO] RichFaces Examples Richfaces IRC Client Application SUCCESS [14.630s] > [INFO] RichFaces Examples Aggregator ..................... SUCCESS [0.241s] > [INFO] RichFaces Showcase ................................ FAILURE [12.109s] > [INFO] RichFaces Distribution Assembler .................. SKIPPED > [INFO] RichFaces Aggregator .............................. SKIPPED > [INFO] ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 41:12.509s > [INFO] Finished at: Fri Dec 09 06:42:33 EST 2011 > [INFO] Final Memory: 312M/708M > [INFO] ------------------------------------------------------------------------ > maven builder waiting > mavenExecutionResult exceptions not empty > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.3.1:compile (default-compile) on project richfaces-showcase: Compilation failure > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) > at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) > at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) > at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) > at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) > at org.jvnet.hudson.maven3.launcher.Maven3Launcher.main(Maven3Launcher.java:79) > 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.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:329) > at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:239) > at org.jvnet.hudson.maven3.agent.Maven3Main.launch(Maven3Main.java:146) > at hudson.maven.Maven3Builder.call(Maven3Builder.java:127) > at hudson.maven.Maven3Builder.call(Maven3Builder.java:74) > at hudson.remoting.UserRequest.perform(UserRequest.java:114) > at hudson.remoting.UserRequest.perform(UserRequest.java:48) > at hudson.remoting.Request$2.run(Request.java:270) > 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:660) > Caused by: org.apache.maven.plugin.CompilationFailureException: Compilation failure > at org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:656) > at org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:128) > at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) > ... 27 more > channel stopped > Email was triggered for: Failure > Sending email for trigger: Failure > ERROR: Ignore Problem expanding maven opts macros org.jenkinsci.plugins.tokenmacro.TokenMacro > Sending email to: richfaces-builds at lists.jboss.org > Finished: FAILURE > {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 Jan 13 07:27:21 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 13 Jan 2012 07:27:21 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11866) Push: Provide more useful message when subtopic does not meet criteria In-Reply-To: <1682962725.47910.1326102375475.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <2123712788.53439.1326457641404.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved RF-11866. ----------------------------- Resolution: Done > Push: Provide more useful message when subtopic does not meet criteria > ---------------------------------------------------------------------- > > Key: RF-11866 > URL: https://issues.jboss.org/browse/RF-11866 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 4.1.0.Final > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Priority: Minor > Fix For: 4.2.0.CR1 > > > See forums. > https://github.com/richfaces/core/blob/develop/api/src/main/java/org/richfaces/application/push/TopicKey.java#L76 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 13 07:44:21 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 13 Jan 2012 07:44:21 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11870) Eliminate SNAPSHOT artifacts in non-default profiles In-Reply-To: <1079472273.50047.1326142929821.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <988869388.53552.1326458661457.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12659190#comment-12659190 ] Luk?? Fry? commented on RF-11870: --------------------------------- There were SNAPSHOT dependencies in integration tests ({{src/it}}) and project which are not part of the framework build ({{core/legacy-tests}}). > Eliminate SNAPSHOT artifacts in non-default profiles > ---------------------------------------------------- > > Key: RF-11870 > URL: https://issues.jboss.org/browse/RF-11870 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 4.0.0.Final > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 4.2.0.CR1 > > > Look for -SNAPSHOT occurences across framework, docs and all build deps. > Replace with release versions and verify build locally with given profiles. > This is required by Maven Central. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 13 07:44:21 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 13 Jan 2012 07:44:21 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11870) Eliminate SNAPSHOT artifacts in non-default profiles In-Reply-To: <1079472273.50047.1326142929821.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1075942401.53553.1326458661515.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved RF-11870. ----------------------------- Resolution: Done > Eliminate SNAPSHOT artifacts in non-default profiles > ---------------------------------------------------- > > Key: RF-11870 > URL: https://issues.jboss.org/browse/RF-11870 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 4.0.0.Final > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 4.2.0.CR1 > > > Look for -SNAPSHOT occurences across framework, docs and all build deps. > Replace with release versions and verify build locally with given profiles. > This is required by Maven Central. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 13 07:50:21 2012 From: jira-events at lists.jboss.org (Dirk Dollar (JIRA)) Date: Fri, 13 Jan 2012 07:50:21 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11882) a4j jsFunction cannot transform java class to json in the getData method call Message-ID: <1733561605.53594.1326459021528.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Dirk Dollar created RF-11882: -------------------------------- Summary: 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 I get a 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" Which wasn't there in richfaces 3.3.3 The code snippet: 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;} } } results in the mentioned 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 Fri Jan 13 07:54:22 2012 From: jira-events at lists.jboss.org (Dirk Dollar (JIRA)) Date: Fri, 13 Jan 2012 07:54:22 -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: <1754363298.53664.1326459262912.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 ] Dirk Dollar updated RF-11882: ----------------------------- Description: I get a FATAL: ...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" Which wasn't there in richfaces 3.3.3 The code snippet: 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;} } } results in the mentioned error was: I get a 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" Which wasn't there in richfaces 3.3.3 The code snippet: 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;} } } results in the mentioned error > 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 > > I get a > FATAL: > ...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" > Which wasn't there in richfaces 3.3.3 > The code snippet: > 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;} > } > } > results in the mentioned 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 Fri Jan 13 09:37:23 2012 From: jira-events at lists.jboss.org (Dirk Dollar (JIRA)) Date: Fri, 13 Jan 2012 09:37:23 -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: <688538701.54505.1326465443557.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 ] Dirk Dollar updated RF-11882: ----------------------------- Priority: Minor (was: Major) Description: I get a FATAL: ...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" Which wasn't there in richfaces 3.3.3 The code snippet: 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;} } } 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 was: I get a FATAL: ...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" Which wasn't there in richfaces 3.3.3 The code snippet: 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;} } } results in the mentioned error > 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 > Priority: Minor > > I get a > FATAL: > ...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" > Which wasn't there in richfaces 3.3.3 > The code snippet: > 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;} > } > } > 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 Jan 13 10:46:22 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 13 Jan 2012 10:46:22 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11876) Add jsf.js resource dependency to all components to work around RF-11739 In-Reply-To: <850827564.3537.1326381981377.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <361486724.54945.1326469582218.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved RF-11876. ----------------------------- Labels: needs-qe (was: ) Resolution: Done Only some of components had wrongly defined dependencies. {{jsf.js}} dependency was added mainly to {{base-component.reslib}} which resolves issues for most of the components. > Add jsf.js resource dependency to all components to work around RF-11739 > ------------------------------------------------------------------------ > > Key: RF-11876 > URL: https://issues.jboss.org/browse/RF-11876 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: component > Affects Versions: 4.0.0.Final > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Priority: Critical > Labels: needs-qe > Fix For: 4.2.0.CR1 > > > By adding {{jsf.js}} dependency properly to each component, > components will be forced to load {{jsf.js}} just before any RF component requests {{packed.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 Jan 13 10:48:21 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 13 Jan 2012 10:48:21 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11877) Upgrade Servlets API to 3.0 in BOM In-Reply-To: <904396798.3551.1326382222093.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <345472111.54962.1326469701421.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12659279#comment-12659279 ] Luk?? Fry? commented on RF-11877: --------------------------------- Servlets 3.0 API has following additions: Pluggability Easy of Development Async Servlet support Security The backward compatibility is solved but * not using Async servlet or detect its support, note that RichFaces does not use it directly, but uses Atmosphere which handle interoperability * automatic registration of servlets does not work, user needs to register them in {{web.xml}} > Upgrade Servlets API to 3.0 in BOM > ---------------------------------- > > Key: RF-11877 > URL: https://issues.jboss.org/browse/RF-11877 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 4.0.0.Final > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Priority: Critical > Fix For: 4.2.0.CR1 > > > This issue could break backward compatibility with Servlets 2.5 environments, > we should make sure there are no extensive changes in version 3.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 Fri Jan 13 11:03:22 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 13 Jan 2012 11:03:22 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11828) showcase - rich:inplaceInput - entering value does not work In-Reply-To: <727507047.21455.1324316289442.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <478759361.55017.1326470602478.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? reassigned RF-11828: ------------------------------- Assignee: Luk?? Fry? > showcase - rich:inplaceInput - entering value does not work > ----------------------------------------------------------- > > Key: RF-11828 > URL: https://issues.jboss.org/browse/RF-11828 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input, showcase > Affects Versions: 4.1.0.Final > Environment: richfaces-showcase 4.1.1-SNAPSHOT > all containers > all browsers > Reporter: Juraj Huska > Assignee: Luk?? Fry? > Priority: Minor > Fix For: 4.2.0.CR1 > > > *Submitting* the value of rich:inplaceInput does not work *by pressing the enter key* as it should. > When I *click outside* of the component then the value of *input is edited correctly*. > This issue is occurring from 4.1.1-SNAPSHOT showcase version. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 13 11:03:22 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 13 Jan 2012 11:03:22 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11745) OutOfMemoryError: PermGen space when building on Jenkins In-Reply-To: <272433447.49466.1322559760800.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <446629592.55020.1326470602897.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? reassigned RF-11745: ------------------------------- Assignee: Luk?? Fry? > OutOfMemoryError: PermGen space when building on Jenkins > -------------------------------------------------------- > > Key: RF-11745 > URL: https://issues.jboss.org/browse/RF-11745 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 4.1.0.CR1 > Reporter: Pavol Pitonak > Assignee: Luk?? Fry? > Fix For: 4.2.0.CR1 > > > When RichFaces are built from Jenkins without any extra settings for heap and perm gen. However, it works fine if following options are set *-Xmx512m -XX:MaxPermSize=128m*. Isn't it possible to set those values directly in build (pom.xml)? > {code} > mvn -f build/pom.xml -Pbuild,release clean deploy > {code} > {quote} > [INFO] RichFaces UI Components: Drag-n-Drop Aggregator ... SUCCESS [0.129s] > [INFO] RichFaces UI Components: Validator api ............ SUCCESS [15.729s] > [INFO] RichFaces UI Components: Validator ui ............. SUCCESS [4:17.709s] > [INFO] RichFaces UI Components: validator-aggregator ..... SUCCESS [0.186s] > [INFO] Richfaces UI Components API ....................... SUCCESS [1:22.666s] > [INFO] RichFaces UI Components Static Resources .......... SUCCESS [2:08.555s] > [INFO] RichFaces UI Components UI ........................ SUCCESS [2:56.547s] > [INFO] RichFaces UI Distribution ......................... SUCCESS [0.099s] > [INFO] RichFaces UI Components Aggregator ................ SUCCESS [0.099s] > [INFO] RichFaces Showcase ................................ FAILURE [1:57.991s] > [INFO] RichFaces Distribution Assembler .................. SKIPPED > [INFO] RichFaces Aggregator .............................. SKIPPED > [INFO] ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 57:50.540s > [INFO] Finished at: Mon Nov 28 05:38:15 EST 2011 > [INFO] Final Memory: 123M/577M > [INFO] ------------------------------------------------------------------------ > --------------------------------------------------- > constituent[0]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-embedder-3.0.3.jar > constituent[1]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-settings-3.0.3.jar > constituent[2]: file:/qa/tools/opt/apache-maven-3.0.3/lib/plexus-utils-2.0.6.jar > constituent[3]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-core-3.0.3.jar > constituent[4]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-model-3.0.3.jar > constituent[5]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-settings-builder-3.0.3.jar > constituent[6]: file:/qa/tools/opt/apache-maven-3.0.3/lib/plexus-interpolation-1.14.jar > constituent[7]: file:/qa/tools/opt/apache-maven-3.0.3/lib/plexus-component-annotations-1.5.5.jar > constituent[8]: file:/qa/tools/opt/apache-maven-3.0.3/lib/plexus-sec-dispatcher-1.3.jar > constituent[9]: file:/qa/tools/opt/apache-maven-3.0.3/lib/plexus-cipher-1.4.jar > constituent[10]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-repository-metadata-3.0.3.jar > constituent[11]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-artifact-3.0.3.jar > constituent[12]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-plugin-api-3.0.3.jar > constituent[13]: file:/qa/tools/opt/apache-maven-3.0.3/lib/sisu-inject-plexus-2.1.1.jar > constituent[14]: file:/qa/tools/opt/apache-maven-3.0.3/lib/sisu-inject-bean-2.1.1.jar > constituent[15]: file:/qa/tools/opt/apache-maven-3.0.3/lib/sisu-guice-2.9.4-no_aop.jar > constituent[16]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-model-builder-3.0.3.jar > constituent[17]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-aether-provider-3.0.3.jar > constituent[18]: file:/qa/tools/opt/apache-maven-3.0.3/lib/aether-api-1.11.jar > constituent[19]: file:/qa/tools/opt/apache-maven-3.0.3/lib/aether-spi-1.11.jar > constituent[20]: file:/qa/tools/opt/apache-maven-3.0.3/lib/aether-util-1.11.jar > constituent[21]: file:/qa/tools/opt/apache-maven-3.0.3/lib/aether-impl-1.11.jar > constituent[22]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-compat-3.0.3.jar > constituent[23]: file:/qa/tools/opt/apache-maven-3.0.3/lib/wagon-provider-api-1.0-beta-7.jar > constituent[24]: file:/qa/tools/opt/apache-maven-3.0.3/lib/commons-cli-1.2.jar > constituent[25]: file:/qa/tools/opt/apache-maven-3.0.3/lib/wagon-http-lightweight-1.0-beta-7.jar > constituent[26]: file:/qa/tools/opt/apache-maven-3.0.3/lib/wagon-http-shared-1.0-beta-7.jar > constituent[27]: file:/qa/tools/opt/apache-maven-3.0.3/lib/xercesMinimal-1.9.6.2.jar > constituent[28]: file:/qa/tools/opt/apache-maven-3.0.3/lib/nekohtml-1.9.6.2.jar > constituent[29]: file:/qa/tools/opt/apache-maven-3.0.3/lib/wagon-file-1.0-beta-7.jar > constituent[30]: file:/qa/tools/opt/apache-maven-3.0.3/lib/aether-connector-wagon-1.11.jar > --------------------------------------------------- > Exception in thread "main" java.lang.OutOfMemoryError: PermGen space > Exception in thread "Thread-1200" java.lang.OutOfMemoryError: PermGen space > Archiving artifacts > Finished: FAILURE > {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 Jan 13 11:13:22 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 13 Jan 2012 11:13:22 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11877) Upgrade Servlets API to 3.0 in BOM In-Reply-To: <904396798.3551.1326382222093.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <11870551.55095.1326471202207.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12659279#comment-12659279 ] Luk?? Fry? edited comment on RF-11877 at 1/13/12 11:13 AM: ----------------------------------------------------------- Servlets 3.0 API has following additions: Pluggability Easy of Development Async Servlet support Security The backward compatibility is solved by * not using Async servlet or detect its support, note that RichFaces does not use it directly, but uses Atmosphere which handle interoperability * automatic registration of servlets does not work, user needs to register them in {{web.xml}} was (Author: lfryc): Servlets 3.0 API has following additions: Pluggability Easy of Development Async Servlet support Security The backward compatibility is solved but * not using Async servlet or detect its support, note that RichFaces does not use it directly, but uses Atmosphere which handle interoperability * automatic registration of servlets does not work, user needs to register them in {{web.xml}} > Upgrade Servlets API to 3.0 in BOM > ---------------------------------- > > Key: RF-11877 > URL: https://issues.jboss.org/browse/RF-11877 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 4.0.0.Final > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Priority: Critical > Fix For: 4.2.0.CR1 > > > This issue could break backward compatibility with Servlets 2.5 environments, > we should make sure there are no extensive changes in version 3.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 Fri Jan 13 11:17:22 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 13 Jan 2012 11:17:22 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11877) Upgrade Servlets API to 3.0 in BOM In-Reply-To: <904396798.3551.1326382222093.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <491207927.55102.1326471442077.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12659289#comment-12659289 ] Luk?? Fry? commented on RF-11877: --------------------------------- We need to change GAV, not only version, from {{javax.servlet:servlet-api:2.5}} to {{javax.servlet:javax.servlet-api:3.0.1}} > Upgrade Servlets API to 3.0 in BOM > ---------------------------------- > > Key: RF-11877 > URL: https://issues.jboss.org/browse/RF-11877 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 4.0.0.Final > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Priority: Critical > Fix For: 4.2.0.CR1 > > > This issue could break backward compatibility with Servlets 2.5 environments, > we should make sure there are no extensive changes in version 3.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 Fri Jan 13 11:25:23 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 13 Jan 2012 11:25:23 -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: <2010590579.55160.1326471923673.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=12659294#comment-12659294 ] Luk?? Fry? commented on RF-11739: --------------------------------- Just note the workaround has been applied in {{4.2}} with RF-11876. > 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 Jan 13 11:29:24 2012 From: jira-events at lists.jboss.org (Juraj Huska (JIRA)) Date: Fri, 13 Jan 2012 11:29:24 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11828) showcase - rich:inplaceInput - entering value does not work In-Reply-To: <727507047.21455.1324316289442.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <927738109.55178.1326472164600.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj Huska closed RF-11828. ---------------------------- Fix Version/s: (was: 4.2.0.CR1) Resolution: Cannot Reproduce Bug > showcase - rich:inplaceInput - entering value does not work > ----------------------------------------------------------- > > Key: RF-11828 > URL: https://issues.jboss.org/browse/RF-11828 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input, showcase > Affects Versions: 4.1.0.Final > Environment: richfaces-showcase 4.1.1-SNAPSHOT > all containers > all browsers > Reporter: Juraj Huska > Assignee: Luk?? Fry? > Priority: Minor > > *Submitting* the value of rich:inplaceInput does not work *by pressing the enter key* as it should. > When I *click outside* of the component then the value of *input is edited correctly*. > This issue is occurring from 4.1.1-SNAPSHOT showcase version. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 13 13:34:21 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Fri, 13 Jan 2012 13:34:21 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11848) round corner support out of the box In-Reply-To: <1667668977.28991.1324544229472.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <23320839.55508.1326479661396.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem reassigned RF-11848: ---------------------------------- Assignee: Dupont Dupont > round corner support out of the box > ----------------------------------- > > Key: RF-11848 > URL: https://issues.jboss.org/browse/RF-11848 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: skinning > Reporter: Dupont Dupont > Assignee: Dupont Dupont > Fix For: 4.Future > > > Add round corner support to richfaces native styles. > > Something like jquery ui round-corner support (http://jqueryui.com/themeroller/) - using only css, no img. > Afterward, as a user just specify a kin property as roundCorner=4px and voila : all components have round corners. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 13 13:44:21 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Fri, 13 Jan 2012 13:44:21 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11883) Support dynamic attachment of the contextMenu Message-ID: <80244479.55517.1326480261257.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Brian Leathem created RF-11883: ---------------------------------- Summary: Support dynamic attachment of the contextMenu Key: RF-11883 URL: https://issues.jboss.org/browse/RF-11883 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Components: component-menu Reporter: Brian Leathem Assignee: Brian Leathem Fix For: 4.2-Tracking Support creating a single instance of the contextMenu that can be attached to any component without creating a new contextMenu 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 Sat Jan 14 03:45:22 2012 From: jira-events at lists.jboss.org (Friedhelm Kuehn (JIRA)) Date: Sat, 14 Jan 2012 03:45:22 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11884) Multiple Errors with IE8/9 Message-ID: <1562607854.56099.1326530722497.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Friedhelm Kuehn created RF-11884: ------------------------------------ Summary: 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 RF is removed) Reporter: Friedhelm Kuehn Priority: Critical 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 Sat Jan 14 03:49:22 2012 From: jira-events at lists.jboss.org (Friedhelm Kuehn (JIRA)) Date: Sat, 14 Jan 2012 03:49:22 -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: <514963290.56104.1326530962399.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 updated RF-11884: --------------------------------- 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) (was: 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 RF is removed)) > 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 > > 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 Sun Jan 15 09:17:18 2012 From: jira-events at lists.jboss.org (Ibrahim Abu Ghosh (JIRA)) Date: Sun, 15 Jan 2012 09:17:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11885) RF 4.1 final a4j:push CDI topic is configured Message-ID: <880165753.172.1326637038332.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Ibrahim Abu Ghosh created RF-11885: -------------------------------------- Summary: RF 4.1 final a4j:push CDI topic is configured Key: RF-11885 URL: https://issues.jboss.org/browse/RF-11885 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-push/poll Affects Versions: 4.1.0.Final Environment: JBoss 6.0 final JDK 1.6.0_24 Reporter: Ibrahim Abu Ghosh i tried to use a4j:push cdi as in showcase, but my consumer page shows a message (topic 'my topic name' is not configured). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 15 09:17:18 2012 From: jira-events at lists.jboss.org (Ibrahim Abu Ghosh (JIRA)) Date: Sun, 15 Jan 2012 09:17:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11885) RF 4.1 final a4j:push CDI topic is configured In-Reply-To: <880165753.172.1326637038332.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <2063436997.174.1326637038388.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ibrahim Abu Ghosh updated RF-11885: ----------------------------------- Labels: a4j:push cdi (was: ) Forum Reference: https://community.jboss.org/thread/176270 (was: https://community.jboss.org/thread/176270) > RF 4.1 final a4j:push CDI topic is configured > --------------------------------------------- > > Key: RF-11885 > URL: https://issues.jboss.org/browse/RF-11885 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Affects Versions: 4.1.0.Final > Environment: JBoss 6.0 final > JDK 1.6.0_24 > Reporter: Ibrahim Abu Ghosh > Labels: a4j:push, cdi > > i tried to use a4j:push cdi as in showcase, but my consumer page shows a message (topic 'my topic name' is not configured). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 15 09:17:18 2012 From: jira-events at lists.jboss.org (SBS JIRA Integration (JIRA)) Date: Sun, 15 Jan 2012 09:17:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11885) RF 4.1 final a4j:push CDI topic is configured In-Reply-To: <880165753.172.1326637038332.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <299555514.178.1326637038536.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] SBS JIRA Integration updated RF-11885: -------------------------------------- Forum Reference: https://community.jboss.org/message/642038#642038, https://community.jboss.org/thread/176270 (was: https://community.jboss.org/thread/176270) > RF 4.1 final a4j:push CDI topic is configured > --------------------------------------------- > > Key: RF-11885 > URL: https://issues.jboss.org/browse/RF-11885 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Affects Versions: 4.1.0.Final > Environment: JBoss 6.0 final > JDK 1.6.0_24 > Reporter: Ibrahim Abu Ghosh > Labels: a4j:push, cdi > > i tried to use a4j:push cdi as in showcase, but my consumer page shows a message (topic 'my topic name' is not configured). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 15 16:25:18 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?J=C3=A1n_Jamrich_=28JIRA=29?=) Date: Sun, 15 Jan 2012 16:25:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11846) rich:validator ignores @NotEmpty In-Reply-To: <651588956.26878.1324469409370.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <856933239.245.1326662718780.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] J?n Jamrich reopened RF-11846: ------------------------------ Assignee: (was: J?n Jamrich) But maybe I found it (correct me if I'm wrong): If form with input bound to some bean (JSR-303 validated) with wrong value (in this case empty input), client side validation doesn't raise message if just blur event fired on this input. When input preset by correct value (input is not empty), and then value is deleted by user and then blur event fired, validation message appears in msg box. But I'm not sure if there is workaround for this or it is expected behavior. There is page in Metamer with JSR-303 validation with CSV together: https://source.jboss.org/viewrep/RichFaces/modules/tests/metamer/trunk/application/src/main/webapp/components/richValidator/csvOnJsr303.xhtml#r23141 An legacy example for CSV on JSR-303 validated bean: https://source.jboss.org/viewrep/RichFaces/modules/tests/metamer/trunk/application/src/main/webapp/components/richValidator/csv.xhtml > rich:validator ignores @NotEmpty > -------------------------------- > > Key: RF-11846 > URL: https://issues.jboss.org/browse/RF-11846 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-validators > Affects Versions: 4.1.0.Final > Environment: Maven 3, Tomcat 6.0.x, Ubuntu 11.10 x64, Glassfish jsf 2.x implementation, Hibernate validator 4.1.0.Final > Reporter: Mercer Traieste > > I want to have [client-side validation|http://richfaces-showcase.appspot.com/richfaces/component-sample.jsf?demo=clientValidation&sample=jsr303&skin=blueSky] using rich:validator in Richfaces 4.1, but @NotEmpty is ignored. > {code:xml} > > > > > > {code} > {code:java} > import org.hibernate.validator.constraints.NotEmpty; > import javax.faces.bean.ManagedBean; > import javax.faces.bean.SessionScoped; > import java.io.Serializable; > @ManagedBean > @SessionScoped > public class RichBean implements Serializable { > private static final long serialVersionUID = -2403138958014741653L; > @NotEmpty > private String firstName; > public String getFirstName() { > return firstName; > } > public void setFirstName(String firstName) { > this.firstName = firstName; > } > } > {code} > @Email, another specific Hibernate validator 4.1 annotation works 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 Mon Jan 16 03:58:18 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 16 Jan 2012 03:58:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11877) Upgrade Servlets API to 3.0 in BOM In-Reply-To: <904396798.3551.1326382222093.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1826337932.607.1326704298644.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved RF-11877. ----------------------------- Resolution: Done > Upgrade Servlets API to 3.0 in BOM > ---------------------------------- > > Key: RF-11877 > URL: https://issues.jboss.org/browse/RF-11877 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 4.0.0.Final > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Priority: Critical > Fix For: 4.2.0.CR1 > > > This issue could break backward compatibility with Servlets 2.5 environments, > we should make sure there are no extensive changes in version 3.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 Mon Jan 16 04:17:18 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 16 Jan 2012 04:17:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11886) Style of the panelMenu changed from 4.1 Message-ID: <383594832.626.1326705438390.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Luk?? Fry? created RF-11886: ------------------------------- Summary: Style of the panelMenu changed from 4.1 Key: RF-11886 URL: https://issues.jboss.org/browse/RF-11886 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: showcase Affects Versions: 4.1.0.Final Environment: Showcase Reporter: Luk?? Fry? Fix For: 4.2.0.CR1 On the screenshots, there is visual change of panelMenu from 4.1 (http://showcase.richfaces.org/), the border around the panelMenu has been 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 Jan 16 04:21:21 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 16 Jan 2012 04:21:21 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11886) Style of the panelMenu changed from 4.1 In-Reply-To: <383594832.626.1326705438390.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <512513442.653.1326705681641.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated RF-11886: ---------------------------- Attachment: new.png old.png > Style of the panelMenu changed from 4.1 > --------------------------------------- > > Key: RF-11886 > URL: https://issues.jboss.org/browse/RF-11886 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: showcase > Affects Versions: 4.1.0.Final > Environment: Showcase > Reporter: Luk?? Fry? > Fix For: 4.2.0.CR1 > > Attachments: new.png, old.png > > > On the screenshots, there is visual change of panelMenu from 4.1 (http://showcase.richfaces.org/), > the border around the panelMenu has been 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 Jan 16 04:21:25 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 16 Jan 2012 04:21:25 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11886) Style of the panelMenu changed from 4.1 In-Reply-To: <383594832.626.1326705438390.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1408123768.672.1326705685102.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated RF-11886: ---------------------------- Priority: Minor (was: Major) > Style of the panelMenu changed from 4.1 > --------------------------------------- > > Key: RF-11886 > URL: https://issues.jboss.org/browse/RF-11886 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: showcase > Affects Versions: 4.1.0.Final > Environment: Showcase > Reporter: Luk?? Fry? > Priority: Minor > Fix For: 4.2.0.CR1 > > Attachments: new.png, old.png > > > On the screenshots, there is visual change of panelMenu from 4.1 (http://showcase.richfaces.org/), > the border around the panelMenu has been 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 Jan 16 05:53:18 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 16 Jan 2012 05:53:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11471) Upgrade to latest version of Atmosphere In-Reply-To: <1090154337.14335.1318029736037.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <614675641.916.1326711198677.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12659488#comment-12659488 ] Luk?? Fry? commented on RF-11471: --------------------------------- When upgraded to Atmosphere {{0.8.3}}, it throws: {code} 11:51:58,101 SEVERE [org.richfaces.log.Application] (http-localhost.localdomain-127.0.0.1-8080-6) null: java.lang.NullPointerException at org.atmosphere.cpr.AtmosphereResourceEventImpl.isResuming(AtmosphereResourceEventImpl.java:89) [atmosphere-runtime-0.8.3.jar:] at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:599) [atmosphere-runtime-0.8.3.jar:] at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:584) [atmosphere-runtime-0.8.3.jar:] at org.atmosphere.cpr.AsynchronousProcessor.timedout(AsynchronousProcessor.java:380) [atmosphere-runtime-0.8.3.jar:] at org.atmosphere.container.Servlet30CometSupport$CometListener.onTimeout(Servlet30CometSupport.java:186) [atmosphere-runtime-0.8.3.jar:] at org.apache.catalina.core.StandardWrapperValve.async(StandardWrapperValve.java:584) [jbossweb-7.0.1.Final.jar:7.0.2.Final] at org.apache.catalina.core.StandardWrapperValve.event(StandardWrapperValve.java:402) [jbossweb-7.0.1.Final.jar:7.0.2.Final] at org.apache.catalina.core.StandardContextValve.__event(StandardContextValve.java:183) [jbossweb-7.0.1.Final.jar:7.0.2.Final] at org.apache.catalina.core.StandardContextValve.event(StandardContextValve.java) [jbossweb-7.0.1.Final.jar:7.0.2.Final] at org.apache.catalina.valves.ValveBase.event(ValveBase.java:193) [jbossweb-7.0.1.Final.jar:7.0.2.Final] at org.apache.catalina.valves.ValveBase.event(ValveBase.java:193) [jbossweb-7.0.1.Final.jar:7.0.2.Final] at org.apache.catalina.valves.ValveBase.event(ValveBase.java:193) [jbossweb-7.0.1.Final.jar:7.0.2.Final] at org.apache.catalina.core.StandardHostValve.event(StandardHostValve.java:256) [jbossweb-7.0.1.Final.jar:7.0.2.Final] at org.apache.catalina.valves.ValveBase.event(ValveBase.java:193) [jbossweb-7.0.1.Final.jar:7.0.2.Final] at org.apache.catalina.core.StandardEngineValve.event(StandardEngineValve.java:128) [jbossweb-7.0.1.Final.jar:7.0.2.Final] at org.apache.catalina.connector.CoyoteAdapter.event(CoyoteAdapter.java:265) [jbossweb-7.0.1.Final.jar:7.0.2.Final] at org.apache.coyote.http11.Http11Processor.event(Http11Processor.java:757) [jbossweb-7.0.1.Final.jar:7.0.2.Final] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.event(Http11Protocol.java:615) [jbossweb-7.0.1.Final.jar:7.0.2.Final] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:939) [jbossweb-7.0.1.Final.jar:7.0.2.Final] at java.lang.Thread.run(Thread.java:662) [:1.6.0_26] {code} > Upgrade to latest version of Atmosphere > --------------------------------------- > > Key: RF-11471 > URL: https://issues.jboss.org/browse/RF-11471 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: component-push/poll, third-party > Affects Versions: 4.1.0.Milestone3 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Priority: Critical > Fix For: 4.2.0.CR1 > > > Atmosphere 0.8.0-RC2 is planned to be released [1] on right on 4.1.0.M3 code-freeze, we will wait before start of QE cycle to grab this release. > [1] http://groups.google.com/group/atmosphere-framework/browse_thread/thread/caffae0c616c250a -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 16 06:28:18 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 16 Jan 2012 06:28:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11887) Showcase: ajax transitions between demos/samples Message-ID: <410816163.1013.1326713298365.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Luk?? Fry? created RF-11887: ------------------------------- Summary: Showcase: ajax transitions between demos/samples Key: RF-11887 URL: https://issues.jboss.org/browse/RF-11887 Project: RichFaces Issue Type: Enhancement Security Level: Public (Everyone can see) Components: showcase Reporter: Luk?? Fry? When navigating between demos/samples, whole page updates are necessary currently. Navigation may be much more fluent when using Ajax transitions only. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 16 06:42:18 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 16 Jan 2012 06:42:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11471) Upgrade to latest version of Atmosphere In-Reply-To: <1090154337.14335.1318029736037.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <947940917.1064.1326714138887.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12659500#comment-12659500 ] Luk?? Fry? commented on RF-11471: --------------------------------- I cannot reproduce NPE above anymore, passing for verification to QE: RFPL-1978 > Upgrade to latest version of Atmosphere > --------------------------------------- > > Key: RF-11471 > URL: https://issues.jboss.org/browse/RF-11471 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: component-push/poll, third-party > Affects Versions: 4.1.0.Milestone3 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Priority: Critical > Fix For: 4.2.0.CR1 > > > Atmosphere 0.8.0-RC2 is planned to be released [1] on right on 4.1.0.M3 code-freeze, we will wait before start of QE cycle to grab this release. > [1] http://groups.google.com/group/atmosphere-framework/browse_thread/thread/caffae0c616c250a -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 16 06:44:18 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 16 Jan 2012 06:44:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11471) Upgrade to Atmosphere 0.8.3 In-Reply-To: <1090154337.14335.1318029736037.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1072972360.1078.1326714258833.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated RF-11471: ---------------------------- Summary: Upgrade to Atmosphere 0.8.3 (was: Upgrade to latest version of Atmosphere) > Upgrade to Atmosphere 0.8.3 > --------------------------- > > Key: RF-11471 > URL: https://issues.jboss.org/browse/RF-11471 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: component-push/poll, third-party > Affects Versions: 4.1.0.Milestone3 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Priority: Critical > Fix For: 4.2.0.CR1 > > > Atmosphere 0.8.0-RC2 is planned to be released [1] on right on 4.1.0.M3 code-freeze, we will wait before start of QE cycle to grab this release. > [1] http://groups.google.com/group/atmosphere-framework/browse_thread/thread/caffae0c616c250a -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 16 06:44:18 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 16 Jan 2012 06:44:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11471) Upgrade to Atmosphere 0.8.3 In-Reply-To: <1090154337.14335.1318029736037.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1241758793.1079.1326714258894.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved RF-11471. ----------------------------- Resolution: Done > Upgrade to Atmosphere 0.8.3 > --------------------------- > > Key: RF-11471 > URL: https://issues.jboss.org/browse/RF-11471 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: component-push/poll, third-party > Affects Versions: 4.1.0.Milestone3 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Priority: Critical > Fix For: 4.2.0.CR1 > > > Atmosphere 0.8.0-RC2 is planned to be released [1] on right on 4.1.0.M3 code-freeze, we will wait before start of QE cycle to grab this release. > [1] http://groups.google.com/group/atmosphere-framework/browse_thread/thread/caffae0c616c250a -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 16 08:08:18 2012 From: jira-events at lists.jboss.org (Brendan Healey (JIRA)) Date: Mon, 16 Jan 2012 08:08:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11888) Resource Servlet can't handle query string appended to resource url Message-ID: <787852126.1337.1326719298230.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Brendan Healey created RF-11888: ----------------------------------- Summary: Resource Servlet can't handle query string appended to resource url Key: RF-11888 URL: https://issues.jboss.org/browse/RF-11888 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: resource handling Affects Versions: 4.1.0.Final Environment: Glassfish 3.1.1 (NO Tomcat)/Mojarra 2.1.3 Chrome browser - Reporter: Brendan Healey A custom resource handler (http://blogs.oracle.com/rlubke/entry/jsf_2_0_new_feature) can be used to append a version string (i.e. ?v=23) to a resource url to force a browser to refresh a resource rather than use any cached version. This is useful as a last resort strategy, perhaps after a major redeployment, and also in the event that there are other problems setting useful ETag and Last-Modified http response headers. At present any appending of a version string causes a 404 response status, for example: Request URL: https://localhost:8181/MyApp/org.richfaces.resources/javax.faces.resource/org.richfaces.staticResource/4.1.0.Final/PackedCompressed/blueSky/packed/packed.css?v=23 Removing the url parameter makes it work ok. As you can see I have resourceMapping enabled. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 16 08:35:18 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 16 Jan 2012 08:35:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11745) OutOfMemoryError: PermGen space when building on Jenkins In-Reply-To: <272433447.49466.1322559760800.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1782133384.1435.1326720918604.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12659532#comment-12659532 ] Luk?? Fry? commented on RF-11745: --------------------------------- PermGen size is setup in build-JVM settings MAVEN_OPTS, so it cannot be influenced in {{pom.xml}}. > OutOfMemoryError: PermGen space when building on Jenkins > -------------------------------------------------------- > > Key: RF-11745 > URL: https://issues.jboss.org/browse/RF-11745 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 4.1.0.CR1 > Reporter: Pavol Pitonak > Assignee: Luk?? Fry? > Fix For: 4.2.0.CR1 > > > When RichFaces are built from Jenkins without any extra settings for heap and perm gen. However, it works fine if following options are set *-Xmx512m -XX:MaxPermSize=128m*. Isn't it possible to set those values directly in build (pom.xml)? > {code} > mvn -f build/pom.xml -Pbuild,release clean deploy > {code} > {quote} > [INFO] RichFaces UI Components: Drag-n-Drop Aggregator ... SUCCESS [0.129s] > [INFO] RichFaces UI Components: Validator api ............ SUCCESS [15.729s] > [INFO] RichFaces UI Components: Validator ui ............. SUCCESS [4:17.709s] > [INFO] RichFaces UI Components: validator-aggregator ..... SUCCESS [0.186s] > [INFO] Richfaces UI Components API ....................... SUCCESS [1:22.666s] > [INFO] RichFaces UI Components Static Resources .......... SUCCESS [2:08.555s] > [INFO] RichFaces UI Components UI ........................ SUCCESS [2:56.547s] > [INFO] RichFaces UI Distribution ......................... SUCCESS [0.099s] > [INFO] RichFaces UI Components Aggregator ................ SUCCESS [0.099s] > [INFO] RichFaces Showcase ................................ FAILURE [1:57.991s] > [INFO] RichFaces Distribution Assembler .................. SKIPPED > [INFO] RichFaces Aggregator .............................. SKIPPED > [INFO] ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 57:50.540s > [INFO] Finished at: Mon Nov 28 05:38:15 EST 2011 > [INFO] Final Memory: 123M/577M > [INFO] ------------------------------------------------------------------------ > --------------------------------------------------- > constituent[0]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-embedder-3.0.3.jar > constituent[1]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-settings-3.0.3.jar > constituent[2]: file:/qa/tools/opt/apache-maven-3.0.3/lib/plexus-utils-2.0.6.jar > constituent[3]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-core-3.0.3.jar > constituent[4]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-model-3.0.3.jar > constituent[5]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-settings-builder-3.0.3.jar > constituent[6]: file:/qa/tools/opt/apache-maven-3.0.3/lib/plexus-interpolation-1.14.jar > constituent[7]: file:/qa/tools/opt/apache-maven-3.0.3/lib/plexus-component-annotations-1.5.5.jar > constituent[8]: file:/qa/tools/opt/apache-maven-3.0.3/lib/plexus-sec-dispatcher-1.3.jar > constituent[9]: file:/qa/tools/opt/apache-maven-3.0.3/lib/plexus-cipher-1.4.jar > constituent[10]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-repository-metadata-3.0.3.jar > constituent[11]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-artifact-3.0.3.jar > constituent[12]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-plugin-api-3.0.3.jar > constituent[13]: file:/qa/tools/opt/apache-maven-3.0.3/lib/sisu-inject-plexus-2.1.1.jar > constituent[14]: file:/qa/tools/opt/apache-maven-3.0.3/lib/sisu-inject-bean-2.1.1.jar > constituent[15]: file:/qa/tools/opt/apache-maven-3.0.3/lib/sisu-guice-2.9.4-no_aop.jar > constituent[16]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-model-builder-3.0.3.jar > constituent[17]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-aether-provider-3.0.3.jar > constituent[18]: file:/qa/tools/opt/apache-maven-3.0.3/lib/aether-api-1.11.jar > constituent[19]: file:/qa/tools/opt/apache-maven-3.0.3/lib/aether-spi-1.11.jar > constituent[20]: file:/qa/tools/opt/apache-maven-3.0.3/lib/aether-util-1.11.jar > constituent[21]: file:/qa/tools/opt/apache-maven-3.0.3/lib/aether-impl-1.11.jar > constituent[22]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-compat-3.0.3.jar > constituent[23]: file:/qa/tools/opt/apache-maven-3.0.3/lib/wagon-provider-api-1.0-beta-7.jar > constituent[24]: file:/qa/tools/opt/apache-maven-3.0.3/lib/commons-cli-1.2.jar > constituent[25]: file:/qa/tools/opt/apache-maven-3.0.3/lib/wagon-http-lightweight-1.0-beta-7.jar > constituent[26]: file:/qa/tools/opt/apache-maven-3.0.3/lib/wagon-http-shared-1.0-beta-7.jar > constituent[27]: file:/qa/tools/opt/apache-maven-3.0.3/lib/xercesMinimal-1.9.6.2.jar > constituent[28]: file:/qa/tools/opt/apache-maven-3.0.3/lib/nekohtml-1.9.6.2.jar > constituent[29]: file:/qa/tools/opt/apache-maven-3.0.3/lib/wagon-file-1.0-beta-7.jar > constituent[30]: file:/qa/tools/opt/apache-maven-3.0.3/lib/aether-connector-wagon-1.11.jar > --------------------------------------------------- > Exception in thread "main" java.lang.OutOfMemoryError: PermGen space > Exception in thread "Thread-1200" java.lang.OutOfMemoryError: PermGen space > Archiving artifacts > Finished: FAILURE > {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 Mon Jan 16 08:39:18 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 16 Jan 2012 08:39:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11745) OutOfMemoryError: PermGen space when building on Jenkins In-Reply-To: <272433447.49466.1322559760800.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1187880609.1441.1326721158483.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated RF-11745: ---------------------------- Attachment: Screenshot-components-1.png > OutOfMemoryError: PermGen space when building on Jenkins > -------------------------------------------------------- > > Key: RF-11745 > URL: https://issues.jboss.org/browse/RF-11745 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 4.1.0.CR1 > Reporter: Pavol Pitonak > Assignee: Luk?? Fry? > Fix For: 4.2.0.CR1 > > Attachments: Screenshot-components-1.png > > > When RichFaces are built from Jenkins without any extra settings for heap and perm gen. However, it works fine if following options are set *-Xmx512m -XX:MaxPermSize=128m*. Isn't it possible to set those values directly in build (pom.xml)? > {code} > mvn -f build/pom.xml -Pbuild,release clean deploy > {code} > {quote} > [INFO] RichFaces UI Components: Drag-n-Drop Aggregator ... SUCCESS [0.129s] > [INFO] RichFaces UI Components: Validator api ............ SUCCESS [15.729s] > [INFO] RichFaces UI Components: Validator ui ............. SUCCESS [4:17.709s] > [INFO] RichFaces UI Components: validator-aggregator ..... SUCCESS [0.186s] > [INFO] Richfaces UI Components API ....................... SUCCESS [1:22.666s] > [INFO] RichFaces UI Components Static Resources .......... SUCCESS [2:08.555s] > [INFO] RichFaces UI Components UI ........................ SUCCESS [2:56.547s] > [INFO] RichFaces UI Distribution ......................... SUCCESS [0.099s] > [INFO] RichFaces UI Components Aggregator ................ SUCCESS [0.099s] > [INFO] RichFaces Showcase ................................ FAILURE [1:57.991s] > [INFO] RichFaces Distribution Assembler .................. SKIPPED > [INFO] RichFaces Aggregator .............................. SKIPPED > [INFO] ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 57:50.540s > [INFO] Finished at: Mon Nov 28 05:38:15 EST 2011 > [INFO] Final Memory: 123M/577M > [INFO] ------------------------------------------------------------------------ > --------------------------------------------------- > constituent[0]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-embedder-3.0.3.jar > constituent[1]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-settings-3.0.3.jar > constituent[2]: file:/qa/tools/opt/apache-maven-3.0.3/lib/plexus-utils-2.0.6.jar > constituent[3]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-core-3.0.3.jar > constituent[4]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-model-3.0.3.jar > constituent[5]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-settings-builder-3.0.3.jar > constituent[6]: file:/qa/tools/opt/apache-maven-3.0.3/lib/plexus-interpolation-1.14.jar > constituent[7]: file:/qa/tools/opt/apache-maven-3.0.3/lib/plexus-component-annotations-1.5.5.jar > constituent[8]: file:/qa/tools/opt/apache-maven-3.0.3/lib/plexus-sec-dispatcher-1.3.jar > constituent[9]: file:/qa/tools/opt/apache-maven-3.0.3/lib/plexus-cipher-1.4.jar > constituent[10]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-repository-metadata-3.0.3.jar > constituent[11]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-artifact-3.0.3.jar > constituent[12]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-plugin-api-3.0.3.jar > constituent[13]: file:/qa/tools/opt/apache-maven-3.0.3/lib/sisu-inject-plexus-2.1.1.jar > constituent[14]: file:/qa/tools/opt/apache-maven-3.0.3/lib/sisu-inject-bean-2.1.1.jar > constituent[15]: file:/qa/tools/opt/apache-maven-3.0.3/lib/sisu-guice-2.9.4-no_aop.jar > constituent[16]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-model-builder-3.0.3.jar > constituent[17]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-aether-provider-3.0.3.jar > constituent[18]: file:/qa/tools/opt/apache-maven-3.0.3/lib/aether-api-1.11.jar > constituent[19]: file:/qa/tools/opt/apache-maven-3.0.3/lib/aether-spi-1.11.jar > constituent[20]: file:/qa/tools/opt/apache-maven-3.0.3/lib/aether-util-1.11.jar > constituent[21]: file:/qa/tools/opt/apache-maven-3.0.3/lib/aether-impl-1.11.jar > constituent[22]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-compat-3.0.3.jar > constituent[23]: file:/qa/tools/opt/apache-maven-3.0.3/lib/wagon-provider-api-1.0-beta-7.jar > constituent[24]: file:/qa/tools/opt/apache-maven-3.0.3/lib/commons-cli-1.2.jar > constituent[25]: file:/qa/tools/opt/apache-maven-3.0.3/lib/wagon-http-lightweight-1.0-beta-7.jar > constituent[26]: file:/qa/tools/opt/apache-maven-3.0.3/lib/wagon-http-shared-1.0-beta-7.jar > constituent[27]: file:/qa/tools/opt/apache-maven-3.0.3/lib/xercesMinimal-1.9.6.2.jar > constituent[28]: file:/qa/tools/opt/apache-maven-3.0.3/lib/nekohtml-1.9.6.2.jar > constituent[29]: file:/qa/tools/opt/apache-maven-3.0.3/lib/wagon-file-1.0-beta-7.jar > constituent[30]: file:/qa/tools/opt/apache-maven-3.0.3/lib/aether-connector-wagon-1.11.jar > --------------------------------------------------- > Exception in thread "main" java.lang.OutOfMemoryError: PermGen space > Exception in thread "Thread-1200" java.lang.OutOfMemoryError: PermGen space > Archiving artifacts > Finished: FAILURE > {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 Mon Jan 16 08:43:19 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 16 Jan 2012 08:43:19 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11745) OutOfMemoryError: PermGen space when building on Jenkins In-Reply-To: <272433447.49466.1322559760800.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1225117408.1482.1326721399480.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12659535#comment-12659535 ] Luk?? Fry? commented on RF-11745: --------------------------------- I have verified that build of {{components}} isn't too memory consuming, see attached {{jconsole}} chart ({{static-resources}} part is highlighted by red color). For comparison, other increases of perm gen are introduced by compilation phase ({{maven-compiler-plugin}}), stable memory usage level is test-run time. > OutOfMemoryError: PermGen space when building on Jenkins > -------------------------------------------------------- > > Key: RF-11745 > URL: https://issues.jboss.org/browse/RF-11745 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 4.1.0.CR1 > Reporter: Pavol Pitonak > Assignee: Luk?? Fry? > Fix For: 4.2.0.CR1 > > Attachments: Screenshot-components-1.png > > > When RichFaces are built from Jenkins without any extra settings for heap and perm gen. However, it works fine if following options are set *-Xmx512m -XX:MaxPermSize=128m*. Isn't it possible to set those values directly in build (pom.xml)? > {code} > mvn -f build/pom.xml -Pbuild,release clean deploy > {code} > {quote} > [INFO] RichFaces UI Components: Drag-n-Drop Aggregator ... SUCCESS [0.129s] > [INFO] RichFaces UI Components: Validator api ............ SUCCESS [15.729s] > [INFO] RichFaces UI Components: Validator ui ............. SUCCESS [4:17.709s] > [INFO] RichFaces UI Components: validator-aggregator ..... SUCCESS [0.186s] > [INFO] Richfaces UI Components API ....................... SUCCESS [1:22.666s] > [INFO] RichFaces UI Components Static Resources .......... SUCCESS [2:08.555s] > [INFO] RichFaces UI Components UI ........................ SUCCESS [2:56.547s] > [INFO] RichFaces UI Distribution ......................... SUCCESS [0.099s] > [INFO] RichFaces UI Components Aggregator ................ SUCCESS [0.099s] > [INFO] RichFaces Showcase ................................ FAILURE [1:57.991s] > [INFO] RichFaces Distribution Assembler .................. SKIPPED > [INFO] RichFaces Aggregator .............................. SKIPPED > [INFO] ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 57:50.540s > [INFO] Finished at: Mon Nov 28 05:38:15 EST 2011 > [INFO] Final Memory: 123M/577M > [INFO] ------------------------------------------------------------------------ > --------------------------------------------------- > constituent[0]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-embedder-3.0.3.jar > constituent[1]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-settings-3.0.3.jar > constituent[2]: file:/qa/tools/opt/apache-maven-3.0.3/lib/plexus-utils-2.0.6.jar > constituent[3]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-core-3.0.3.jar > constituent[4]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-model-3.0.3.jar > constituent[5]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-settings-builder-3.0.3.jar > constituent[6]: file:/qa/tools/opt/apache-maven-3.0.3/lib/plexus-interpolation-1.14.jar > constituent[7]: file:/qa/tools/opt/apache-maven-3.0.3/lib/plexus-component-annotations-1.5.5.jar > constituent[8]: file:/qa/tools/opt/apache-maven-3.0.3/lib/plexus-sec-dispatcher-1.3.jar > constituent[9]: file:/qa/tools/opt/apache-maven-3.0.3/lib/plexus-cipher-1.4.jar > constituent[10]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-repository-metadata-3.0.3.jar > constituent[11]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-artifact-3.0.3.jar > constituent[12]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-plugin-api-3.0.3.jar > constituent[13]: file:/qa/tools/opt/apache-maven-3.0.3/lib/sisu-inject-plexus-2.1.1.jar > constituent[14]: file:/qa/tools/opt/apache-maven-3.0.3/lib/sisu-inject-bean-2.1.1.jar > constituent[15]: file:/qa/tools/opt/apache-maven-3.0.3/lib/sisu-guice-2.9.4-no_aop.jar > constituent[16]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-model-builder-3.0.3.jar > constituent[17]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-aether-provider-3.0.3.jar > constituent[18]: file:/qa/tools/opt/apache-maven-3.0.3/lib/aether-api-1.11.jar > constituent[19]: file:/qa/tools/opt/apache-maven-3.0.3/lib/aether-spi-1.11.jar > constituent[20]: file:/qa/tools/opt/apache-maven-3.0.3/lib/aether-util-1.11.jar > constituent[21]: file:/qa/tools/opt/apache-maven-3.0.3/lib/aether-impl-1.11.jar > constituent[22]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-compat-3.0.3.jar > constituent[23]: file:/qa/tools/opt/apache-maven-3.0.3/lib/wagon-provider-api-1.0-beta-7.jar > constituent[24]: file:/qa/tools/opt/apache-maven-3.0.3/lib/commons-cli-1.2.jar > constituent[25]: file:/qa/tools/opt/apache-maven-3.0.3/lib/wagon-http-lightweight-1.0-beta-7.jar > constituent[26]: file:/qa/tools/opt/apache-maven-3.0.3/lib/wagon-http-shared-1.0-beta-7.jar > constituent[27]: file:/qa/tools/opt/apache-maven-3.0.3/lib/xercesMinimal-1.9.6.2.jar > constituent[28]: file:/qa/tools/opt/apache-maven-3.0.3/lib/nekohtml-1.9.6.2.jar > constituent[29]: file:/qa/tools/opt/apache-maven-3.0.3/lib/wagon-file-1.0-beta-7.jar > constituent[30]: file:/qa/tools/opt/apache-maven-3.0.3/lib/aether-connector-wagon-1.11.jar > --------------------------------------------------- > Exception in thread "main" java.lang.OutOfMemoryError: PermGen space > Exception in thread "Thread-1200" java.lang.OutOfMemoryError: PermGen space > Archiving artifacts > Finished: FAILURE > {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 Mon Jan 16 08:45:18 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 16 Jan 2012 08:45:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11745) OutOfMemoryError: PermGen space when building on Jenkins In-Reply-To: <272433447.49466.1322559760800.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <142305833.1496.1326721518265.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12659537#comment-12659537 ] Luk?? Fry? commented on RF-11745: --------------------------------- As there is nothing we can do about lowering memory consumption, I suggest to: * setup {{MAVEN_OPTS}} appropriately * separate build of modules ({{core}}, {{components}}) > OutOfMemoryError: PermGen space when building on Jenkins > -------------------------------------------------------- > > Key: RF-11745 > URL: https://issues.jboss.org/browse/RF-11745 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 4.1.0.CR1 > Reporter: Pavol Pitonak > Assignee: Luk?? Fry? > Fix For: 4.2.0.CR1 > > Attachments: Screenshot-components-1.png > > > When RichFaces are built from Jenkins without any extra settings for heap and perm gen. However, it works fine if following options are set *-Xmx512m -XX:MaxPermSize=128m*. Isn't it possible to set those values directly in build (pom.xml)? > {code} > mvn -f build/pom.xml -Pbuild,release clean deploy > {code} > {quote} > [INFO] RichFaces UI Components: Drag-n-Drop Aggregator ... SUCCESS [0.129s] > [INFO] RichFaces UI Components: Validator api ............ SUCCESS [15.729s] > [INFO] RichFaces UI Components: Validator ui ............. SUCCESS [4:17.709s] > [INFO] RichFaces UI Components: validator-aggregator ..... SUCCESS [0.186s] > [INFO] Richfaces UI Components API ....................... SUCCESS [1:22.666s] > [INFO] RichFaces UI Components Static Resources .......... SUCCESS [2:08.555s] > [INFO] RichFaces UI Components UI ........................ SUCCESS [2:56.547s] > [INFO] RichFaces UI Distribution ......................... SUCCESS [0.099s] > [INFO] RichFaces UI Components Aggregator ................ SUCCESS [0.099s] > [INFO] RichFaces Showcase ................................ FAILURE [1:57.991s] > [INFO] RichFaces Distribution Assembler .................. SKIPPED > [INFO] RichFaces Aggregator .............................. SKIPPED > [INFO] ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 57:50.540s > [INFO] Finished at: Mon Nov 28 05:38:15 EST 2011 > [INFO] Final Memory: 123M/577M > [INFO] ------------------------------------------------------------------------ > --------------------------------------------------- > constituent[0]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-embedder-3.0.3.jar > constituent[1]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-settings-3.0.3.jar > constituent[2]: file:/qa/tools/opt/apache-maven-3.0.3/lib/plexus-utils-2.0.6.jar > constituent[3]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-core-3.0.3.jar > constituent[4]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-model-3.0.3.jar > constituent[5]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-settings-builder-3.0.3.jar > constituent[6]: file:/qa/tools/opt/apache-maven-3.0.3/lib/plexus-interpolation-1.14.jar > constituent[7]: file:/qa/tools/opt/apache-maven-3.0.3/lib/plexus-component-annotations-1.5.5.jar > constituent[8]: file:/qa/tools/opt/apache-maven-3.0.3/lib/plexus-sec-dispatcher-1.3.jar > constituent[9]: file:/qa/tools/opt/apache-maven-3.0.3/lib/plexus-cipher-1.4.jar > constituent[10]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-repository-metadata-3.0.3.jar > constituent[11]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-artifact-3.0.3.jar > constituent[12]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-plugin-api-3.0.3.jar > constituent[13]: file:/qa/tools/opt/apache-maven-3.0.3/lib/sisu-inject-plexus-2.1.1.jar > constituent[14]: file:/qa/tools/opt/apache-maven-3.0.3/lib/sisu-inject-bean-2.1.1.jar > constituent[15]: file:/qa/tools/opt/apache-maven-3.0.3/lib/sisu-guice-2.9.4-no_aop.jar > constituent[16]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-model-builder-3.0.3.jar > constituent[17]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-aether-provider-3.0.3.jar > constituent[18]: file:/qa/tools/opt/apache-maven-3.0.3/lib/aether-api-1.11.jar > constituent[19]: file:/qa/tools/opt/apache-maven-3.0.3/lib/aether-spi-1.11.jar > constituent[20]: file:/qa/tools/opt/apache-maven-3.0.3/lib/aether-util-1.11.jar > constituent[21]: file:/qa/tools/opt/apache-maven-3.0.3/lib/aether-impl-1.11.jar > constituent[22]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-compat-3.0.3.jar > constituent[23]: file:/qa/tools/opt/apache-maven-3.0.3/lib/wagon-provider-api-1.0-beta-7.jar > constituent[24]: file:/qa/tools/opt/apache-maven-3.0.3/lib/commons-cli-1.2.jar > constituent[25]: file:/qa/tools/opt/apache-maven-3.0.3/lib/wagon-http-lightweight-1.0-beta-7.jar > constituent[26]: file:/qa/tools/opt/apache-maven-3.0.3/lib/wagon-http-shared-1.0-beta-7.jar > constituent[27]: file:/qa/tools/opt/apache-maven-3.0.3/lib/xercesMinimal-1.9.6.2.jar > constituent[28]: file:/qa/tools/opt/apache-maven-3.0.3/lib/nekohtml-1.9.6.2.jar > constituent[29]: file:/qa/tools/opt/apache-maven-3.0.3/lib/wagon-file-1.0-beta-7.jar > constituent[30]: file:/qa/tools/opt/apache-maven-3.0.3/lib/aether-connector-wagon-1.11.jar > --------------------------------------------------- > Exception in thread "main" java.lang.OutOfMemoryError: PermGen space > Exception in thread "Thread-1200" java.lang.OutOfMemoryError: PermGen space > Archiving artifacts > Finished: FAILURE > {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 Mon Jan 16 08:47:19 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 16 Jan 2012 08:47:19 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11745) OutOfMemoryError: PermGen space when building on Jenkins In-Reply-To: <272433447.49466.1322559760800.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <207429766.1505.1326721639433.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12659537#comment-12659537 ] Luk?? Fry? edited comment on RF-11745 at 1/16/12 8:45 AM: ---------------------------------------------------------- As there is nothing we can do about lowering memory consumption, I suggest to: * setup {{MAVEN_OPTS}} appropriately * separate build of modules ({{core}}, {{components}}, ...) was (Author: lfryc): As there is nothing we can do about lowering memory consumption, I suggest to: * setup {{MAVEN_OPTS}} appropriately * separate build of modules ({{core}}, {{components}}) > OutOfMemoryError: PermGen space when building on Jenkins > -------------------------------------------------------- > > Key: RF-11745 > URL: https://issues.jboss.org/browse/RF-11745 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 4.1.0.CR1 > Reporter: Pavol Pitonak > Assignee: Luk?? Fry? > Attachments: Screenshot-components-1.png > > > When RichFaces are built from Jenkins without any extra settings for heap and perm gen. However, it works fine if following options are set *-Xmx512m -XX:MaxPermSize=128m*. Isn't it possible to set those values directly in build (pom.xml)? > {code} > mvn -f build/pom.xml -Pbuild,release clean deploy > {code} > {quote} > [INFO] RichFaces UI Components: Drag-n-Drop Aggregator ... SUCCESS [0.129s] > [INFO] RichFaces UI Components: Validator api ............ SUCCESS [15.729s] > [INFO] RichFaces UI Components: Validator ui ............. SUCCESS [4:17.709s] > [INFO] RichFaces UI Components: validator-aggregator ..... SUCCESS [0.186s] > [INFO] Richfaces UI Components API ....................... SUCCESS [1:22.666s] > [INFO] RichFaces UI Components Static Resources .......... SUCCESS [2:08.555s] > [INFO] RichFaces UI Components UI ........................ SUCCESS [2:56.547s] > [INFO] RichFaces UI Distribution ......................... SUCCESS [0.099s] > [INFO] RichFaces UI Components Aggregator ................ SUCCESS [0.099s] > [INFO] RichFaces Showcase ................................ FAILURE [1:57.991s] > [INFO] RichFaces Distribution Assembler .................. SKIPPED > [INFO] RichFaces Aggregator .............................. SKIPPED > [INFO] ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 57:50.540s > [INFO] Finished at: Mon Nov 28 05:38:15 EST 2011 > [INFO] Final Memory: 123M/577M > [INFO] ------------------------------------------------------------------------ > --------------------------------------------------- > constituent[0]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-embedder-3.0.3.jar > constituent[1]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-settings-3.0.3.jar > constituent[2]: file:/qa/tools/opt/apache-maven-3.0.3/lib/plexus-utils-2.0.6.jar > constituent[3]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-core-3.0.3.jar > constituent[4]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-model-3.0.3.jar > constituent[5]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-settings-builder-3.0.3.jar > constituent[6]: file:/qa/tools/opt/apache-maven-3.0.3/lib/plexus-interpolation-1.14.jar > constituent[7]: file:/qa/tools/opt/apache-maven-3.0.3/lib/plexus-component-annotations-1.5.5.jar > constituent[8]: file:/qa/tools/opt/apache-maven-3.0.3/lib/plexus-sec-dispatcher-1.3.jar > constituent[9]: file:/qa/tools/opt/apache-maven-3.0.3/lib/plexus-cipher-1.4.jar > constituent[10]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-repository-metadata-3.0.3.jar > constituent[11]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-artifact-3.0.3.jar > constituent[12]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-plugin-api-3.0.3.jar > constituent[13]: file:/qa/tools/opt/apache-maven-3.0.3/lib/sisu-inject-plexus-2.1.1.jar > constituent[14]: file:/qa/tools/opt/apache-maven-3.0.3/lib/sisu-inject-bean-2.1.1.jar > constituent[15]: file:/qa/tools/opt/apache-maven-3.0.3/lib/sisu-guice-2.9.4-no_aop.jar > constituent[16]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-model-builder-3.0.3.jar > constituent[17]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-aether-provider-3.0.3.jar > constituent[18]: file:/qa/tools/opt/apache-maven-3.0.3/lib/aether-api-1.11.jar > constituent[19]: file:/qa/tools/opt/apache-maven-3.0.3/lib/aether-spi-1.11.jar > constituent[20]: file:/qa/tools/opt/apache-maven-3.0.3/lib/aether-util-1.11.jar > constituent[21]: file:/qa/tools/opt/apache-maven-3.0.3/lib/aether-impl-1.11.jar > constituent[22]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-compat-3.0.3.jar > constituent[23]: file:/qa/tools/opt/apache-maven-3.0.3/lib/wagon-provider-api-1.0-beta-7.jar > constituent[24]: file:/qa/tools/opt/apache-maven-3.0.3/lib/commons-cli-1.2.jar > constituent[25]: file:/qa/tools/opt/apache-maven-3.0.3/lib/wagon-http-lightweight-1.0-beta-7.jar > constituent[26]: file:/qa/tools/opt/apache-maven-3.0.3/lib/wagon-http-shared-1.0-beta-7.jar > constituent[27]: file:/qa/tools/opt/apache-maven-3.0.3/lib/xercesMinimal-1.9.6.2.jar > constituent[28]: file:/qa/tools/opt/apache-maven-3.0.3/lib/nekohtml-1.9.6.2.jar > constituent[29]: file:/qa/tools/opt/apache-maven-3.0.3/lib/wagon-file-1.0-beta-7.jar > constituent[30]: file:/qa/tools/opt/apache-maven-3.0.3/lib/aether-connector-wagon-1.11.jar > --------------------------------------------------- > Exception in thread "main" java.lang.OutOfMemoryError: PermGen space > Exception in thread "Thread-1200" java.lang.OutOfMemoryError: PermGen space > Archiving artifacts > Finished: FAILURE > {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 Mon Jan 16 08:47:19 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 16 Jan 2012 08:47:19 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11745) OutOfMemoryError: PermGen space when building on Jenkins In-Reply-To: <272433447.49466.1322559760800.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <663806902.1513.1326721639907.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved RF-11745. ----------------------------- Fix Version/s: (was: 4.2.0.CR1) Resolution: Won't Fix > OutOfMemoryError: PermGen space when building on Jenkins > -------------------------------------------------------- > > Key: RF-11745 > URL: https://issues.jboss.org/browse/RF-11745 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 4.1.0.CR1 > Reporter: Pavol Pitonak > Assignee: Luk?? Fry? > Attachments: Screenshot-components-1.png > > > When RichFaces are built from Jenkins without any extra settings for heap and perm gen. However, it works fine if following options are set *-Xmx512m -XX:MaxPermSize=128m*. Isn't it possible to set those values directly in build (pom.xml)? > {code} > mvn -f build/pom.xml -Pbuild,release clean deploy > {code} > {quote} > [INFO] RichFaces UI Components: Drag-n-Drop Aggregator ... SUCCESS [0.129s] > [INFO] RichFaces UI Components: Validator api ............ SUCCESS [15.729s] > [INFO] RichFaces UI Components: Validator ui ............. SUCCESS [4:17.709s] > [INFO] RichFaces UI Components: validator-aggregator ..... SUCCESS [0.186s] > [INFO] Richfaces UI Components API ....................... SUCCESS [1:22.666s] > [INFO] RichFaces UI Components Static Resources .......... SUCCESS [2:08.555s] > [INFO] RichFaces UI Components UI ........................ SUCCESS [2:56.547s] > [INFO] RichFaces UI Distribution ......................... SUCCESS [0.099s] > [INFO] RichFaces UI Components Aggregator ................ SUCCESS [0.099s] > [INFO] RichFaces Showcase ................................ FAILURE [1:57.991s] > [INFO] RichFaces Distribution Assembler .................. SKIPPED > [INFO] RichFaces Aggregator .............................. SKIPPED > [INFO] ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 57:50.540s > [INFO] Finished at: Mon Nov 28 05:38:15 EST 2011 > [INFO] Final Memory: 123M/577M > [INFO] ------------------------------------------------------------------------ > --------------------------------------------------- > constituent[0]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-embedder-3.0.3.jar > constituent[1]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-settings-3.0.3.jar > constituent[2]: file:/qa/tools/opt/apache-maven-3.0.3/lib/plexus-utils-2.0.6.jar > constituent[3]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-core-3.0.3.jar > constituent[4]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-model-3.0.3.jar > constituent[5]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-settings-builder-3.0.3.jar > constituent[6]: file:/qa/tools/opt/apache-maven-3.0.3/lib/plexus-interpolation-1.14.jar > constituent[7]: file:/qa/tools/opt/apache-maven-3.0.3/lib/plexus-component-annotations-1.5.5.jar > constituent[8]: file:/qa/tools/opt/apache-maven-3.0.3/lib/plexus-sec-dispatcher-1.3.jar > constituent[9]: file:/qa/tools/opt/apache-maven-3.0.3/lib/plexus-cipher-1.4.jar > constituent[10]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-repository-metadata-3.0.3.jar > constituent[11]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-artifact-3.0.3.jar > constituent[12]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-plugin-api-3.0.3.jar > constituent[13]: file:/qa/tools/opt/apache-maven-3.0.3/lib/sisu-inject-plexus-2.1.1.jar > constituent[14]: file:/qa/tools/opt/apache-maven-3.0.3/lib/sisu-inject-bean-2.1.1.jar > constituent[15]: file:/qa/tools/opt/apache-maven-3.0.3/lib/sisu-guice-2.9.4-no_aop.jar > constituent[16]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-model-builder-3.0.3.jar > constituent[17]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-aether-provider-3.0.3.jar > constituent[18]: file:/qa/tools/opt/apache-maven-3.0.3/lib/aether-api-1.11.jar > constituent[19]: file:/qa/tools/opt/apache-maven-3.0.3/lib/aether-spi-1.11.jar > constituent[20]: file:/qa/tools/opt/apache-maven-3.0.3/lib/aether-util-1.11.jar > constituent[21]: file:/qa/tools/opt/apache-maven-3.0.3/lib/aether-impl-1.11.jar > constituent[22]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-compat-3.0.3.jar > constituent[23]: file:/qa/tools/opt/apache-maven-3.0.3/lib/wagon-provider-api-1.0-beta-7.jar > constituent[24]: file:/qa/tools/opt/apache-maven-3.0.3/lib/commons-cli-1.2.jar > constituent[25]: file:/qa/tools/opt/apache-maven-3.0.3/lib/wagon-http-lightweight-1.0-beta-7.jar > constituent[26]: file:/qa/tools/opt/apache-maven-3.0.3/lib/wagon-http-shared-1.0-beta-7.jar > constituent[27]: file:/qa/tools/opt/apache-maven-3.0.3/lib/xercesMinimal-1.9.6.2.jar > constituent[28]: file:/qa/tools/opt/apache-maven-3.0.3/lib/nekohtml-1.9.6.2.jar > constituent[29]: file:/qa/tools/opt/apache-maven-3.0.3/lib/wagon-file-1.0-beta-7.jar > constituent[30]: file:/qa/tools/opt/apache-maven-3.0.3/lib/aether-connector-wagon-1.11.jar > --------------------------------------------------- > Exception in thread "main" java.lang.OutOfMemoryError: PermGen space > Exception in thread "Thread-1200" java.lang.OutOfMemoryError: PermGen space > Archiving artifacts > Finished: FAILURE > {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 Mon Jan 16 08:52:18 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 16 Jan 2012 08:52:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11745) OutOfMemoryError: PermGen space when building on Jenkins In-Reply-To: <272433447.49466.1322559760800.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <650187538.1518.1326721938247.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12659539#comment-12659539 ] Luk?? Fry? commented on RF-11745: --------------------------------- Wiki about [How to build RichFaces 4.0|https://community.jboss.org/wiki/HowToBuildRichFaces40] was updated accordingly. > OutOfMemoryError: PermGen space when building on Jenkins > -------------------------------------------------------- > > Key: RF-11745 > URL: https://issues.jboss.org/browse/RF-11745 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 4.1.0.CR1 > Reporter: Pavol Pitonak > Assignee: Luk?? Fry? > Attachments: Screenshot-components-1.png > > > When RichFaces are built from Jenkins without any extra settings for heap and perm gen. However, it works fine if following options are set *-Xmx512m -XX:MaxPermSize=128m*. Isn't it possible to set those values directly in build (pom.xml)? > {code} > mvn -f build/pom.xml -Pbuild,release clean deploy > {code} > {quote} > [INFO] RichFaces UI Components: Drag-n-Drop Aggregator ... SUCCESS [0.129s] > [INFO] RichFaces UI Components: Validator api ............ SUCCESS [15.729s] > [INFO] RichFaces UI Components: Validator ui ............. SUCCESS [4:17.709s] > [INFO] RichFaces UI Components: validator-aggregator ..... SUCCESS [0.186s] > [INFO] Richfaces UI Components API ....................... SUCCESS [1:22.666s] > [INFO] RichFaces UI Components Static Resources .......... SUCCESS [2:08.555s] > [INFO] RichFaces UI Components UI ........................ SUCCESS [2:56.547s] > [INFO] RichFaces UI Distribution ......................... SUCCESS [0.099s] > [INFO] RichFaces UI Components Aggregator ................ SUCCESS [0.099s] > [INFO] RichFaces Showcase ................................ FAILURE [1:57.991s] > [INFO] RichFaces Distribution Assembler .................. SKIPPED > [INFO] RichFaces Aggregator .............................. SKIPPED > [INFO] ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 57:50.540s > [INFO] Finished at: Mon Nov 28 05:38:15 EST 2011 > [INFO] Final Memory: 123M/577M > [INFO] ------------------------------------------------------------------------ > --------------------------------------------------- > constituent[0]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-embedder-3.0.3.jar > constituent[1]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-settings-3.0.3.jar > constituent[2]: file:/qa/tools/opt/apache-maven-3.0.3/lib/plexus-utils-2.0.6.jar > constituent[3]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-core-3.0.3.jar > constituent[4]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-model-3.0.3.jar > constituent[5]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-settings-builder-3.0.3.jar > constituent[6]: file:/qa/tools/opt/apache-maven-3.0.3/lib/plexus-interpolation-1.14.jar > constituent[7]: file:/qa/tools/opt/apache-maven-3.0.3/lib/plexus-component-annotations-1.5.5.jar > constituent[8]: file:/qa/tools/opt/apache-maven-3.0.3/lib/plexus-sec-dispatcher-1.3.jar > constituent[9]: file:/qa/tools/opt/apache-maven-3.0.3/lib/plexus-cipher-1.4.jar > constituent[10]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-repository-metadata-3.0.3.jar > constituent[11]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-artifact-3.0.3.jar > constituent[12]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-plugin-api-3.0.3.jar > constituent[13]: file:/qa/tools/opt/apache-maven-3.0.3/lib/sisu-inject-plexus-2.1.1.jar > constituent[14]: file:/qa/tools/opt/apache-maven-3.0.3/lib/sisu-inject-bean-2.1.1.jar > constituent[15]: file:/qa/tools/opt/apache-maven-3.0.3/lib/sisu-guice-2.9.4-no_aop.jar > constituent[16]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-model-builder-3.0.3.jar > constituent[17]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-aether-provider-3.0.3.jar > constituent[18]: file:/qa/tools/opt/apache-maven-3.0.3/lib/aether-api-1.11.jar > constituent[19]: file:/qa/tools/opt/apache-maven-3.0.3/lib/aether-spi-1.11.jar > constituent[20]: file:/qa/tools/opt/apache-maven-3.0.3/lib/aether-util-1.11.jar > constituent[21]: file:/qa/tools/opt/apache-maven-3.0.3/lib/aether-impl-1.11.jar > constituent[22]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-compat-3.0.3.jar > constituent[23]: file:/qa/tools/opt/apache-maven-3.0.3/lib/wagon-provider-api-1.0-beta-7.jar > constituent[24]: file:/qa/tools/opt/apache-maven-3.0.3/lib/commons-cli-1.2.jar > constituent[25]: file:/qa/tools/opt/apache-maven-3.0.3/lib/wagon-http-lightweight-1.0-beta-7.jar > constituent[26]: file:/qa/tools/opt/apache-maven-3.0.3/lib/wagon-http-shared-1.0-beta-7.jar > constituent[27]: file:/qa/tools/opt/apache-maven-3.0.3/lib/xercesMinimal-1.9.6.2.jar > constituent[28]: file:/qa/tools/opt/apache-maven-3.0.3/lib/nekohtml-1.9.6.2.jar > constituent[29]: file:/qa/tools/opt/apache-maven-3.0.3/lib/wagon-file-1.0-beta-7.jar > constituent[30]: file:/qa/tools/opt/apache-maven-3.0.3/lib/aether-connector-wagon-1.11.jar > --------------------------------------------------- > Exception in thread "main" java.lang.OutOfMemoryError: PermGen space > Exception in thread "Thread-1200" java.lang.OutOfMemoryError: PermGen space > Archiving artifacts > Finished: FAILURE > {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 Mon Jan 16 08:56:18 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 16 Jan 2012 08:56:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11889) maven-resources-plugin: ResourceWriter: close streams appropriately Message-ID: <942338142.1532.1326722178330.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Luk?? Fry? created RF-11889: ------------------------------- Summary: maven-resources-plugin: ResourceWriter: close streams appropriately Key: RF-11889 URL: https://issues.jboss.org/browse/RF-11889 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: cdk Affects Versions: 4.1.0.Final Reporter: Luk?? Fry? Assignee: Luk?? Fry? Priority: Minor Fix For: 4.2.0.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 Jan 16 08:58:18 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 16 Jan 2012 08:58:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11889) maven-resources-plugin: ResourceWriter: close streams appropriately In-Reply-To: <942338142.1532.1326722178330.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1395424682.1538.1326722298464.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved RF-11889. ----------------------------- Resolution: Done > maven-resources-plugin: ResourceWriter: close streams appropriately > ------------------------------------------------------------------- > > Key: RF-11889 > URL: https://issues.jboss.org/browse/RF-11889 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: cdk > Affects Versions: 4.1.0.Final > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Priority: Minor > Fix For: 4.2.0.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 Jan 16 09:22:18 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?J=C3=A1n_Jamrich_=28JIRA=29?=) Date: Mon, 16 Jan 2012 09:22:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11850) RF 4.1.0.Final: Problem using columnResize with more than one extendedDataTable on the same page. In-Reply-To: <1719236551.29235.1324550769802.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1035455200.1658.1326723738822.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12659546#comment-12659546 ] J?n Jamrich commented on RF-11850: ---------------------------------- Issue confirmed. Created page with 2 EDT to simulate this problem. https://source.jboss.org/browse/RichFaces/modules/tests/metamer/trunk/application/src/main/webapp/components/richExtendedDataTable/rf-11850.xhtml?r=23151 > RF 4.1.0.Final: Problem using columnResize with more than one extendedDataTable on the same page. > ------------------------------------------------------------------------------------------------- > > Key: RF-11850 > URL: https://issues.jboss.org/browse/RF-11850 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.1.0.Final > Environment: Windows 7 x64 or arch linux x86 > JBoss 7.0.1 Final or Glassfish 3.1 > Reporter: Christian Peter > Assignee: J?n Jamrich > Priority: Minor > > Hello, > I've encountered some problems using richfaces extendedDataTables in RichFace 4.1.0.Final > Here is the facelet: > {code:title=facelet} > > > > Header7 > #{item.name} > > > > Header8 > #{item.uuid} > > > > Header9 > #{item.uuid} > > > > Header10 > #{item.uuid} > > > > > > > > > > Header7 > #{item.name} > > > > Header8 > #{item.uuid} > > > Header9 > #{item.uuid} > > > > Header10 > #{item.uuid} > > > > > > {code} > > Resizing the columns on the first table works perfectly, but if someone tries to resize the second tables' columns as well, I've got NullPointer exceptions like: > {code:title=stacktrace} > java.lang.NullPointerException > at org.richfaces.renderkit.SortingFilteringRowsRenderer.updateAttribute(SortingFilteringRowsRenderer.java:135) [richfaces-components-ui-4.1.0.Final.jar: > at org.richfaces.renderkit.ExtendedDataTableRenderer.updateWidthOfColumns(ExtendedDataTableRenderer.java:825) [richfaces-components-ui-4.1.0.Final.jar:] > at org.richfaces.renderkit.ExtendedDataTableRenderer.doDecode(ExtendedDataTableRenderer.java:808) [richfaces-components-ui-4.1.0.Final.jar:] > at org.richfaces.renderkit.RendererBase.decode(RendererBase.java:80) [richfaces-components-ui-4.1.0.Final.jar:] > at javax.faces.component.UIComponentBase.decode(UIComponentBase.java:787) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at org.richfaces.component.UIDataAdaptor.processDecodes(UIDataAdaptor.java:819) [richfaces-components-ui-4.1.0.Final.jar:] > at org.richfaces.context.PartialViewExecuteVisitCallback.visit(PartialViewExecuteVisitCallback.java:53) [richfaces-core-impl-4.1.0.Final.jar:] > at org.richfaces.context.BaseExtendedVisitContext.invokeVisitCallback(BaseExtendedVisitContext.java:321) [richfaces-core-impl-4.1.0.Final.jar:] > at org.richfaces.component.UIDataAdaptor.visitTree(UIDataAdaptor.java:1319) [richfaces-components-ui-4.1.0.Final.jar:] > at javax.faces.component.UIComponent.visitTree(UIComponent.java:1600) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at javax.faces.component.UIForm.visitTree(UIForm.java:344) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at javax.faces.component.UIComponent.visitTree(UIComponent.java:1600) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at javax.faces.component.UIComponent.visitTree(UIComponent.java:1600) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at org.richfaces.context.ExtendedPartialViewContextImpl.executeComponents(ExtendedPartialViewContextImpl.java:237) [richfaces-core-impl-4.1.0.Final.jar: > at org.richfaces.context.ExtendedPartialViewContextImpl.processPartialExecutePhase(ExtendedPartialViewContextImpl.java:217) [richfaces-core-impl-4.1.0.F > at org.richfaces.context.ExtendedPartialViewContextImpl.processPartial(ExtendedPartialViewContextImpl.java:196) [richfaces-core-impl-4.1.0.Final.jar:] > at javax.faces.component.UIViewRoot.processDecodes(UIViewRoot.java:931) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at com.sun.faces.lifecycle.ApplyRequestValuesPhase.execute(ApplyRequestValuesPhase.java:78) [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 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] > {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 Jan 16 09:22:18 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?J=C3=A1n_Jamrich_=28JIRA=29?=) Date: Mon, 16 Jan 2012 09:22:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11850) RF 4.1.0.Final: Problem using columnResize with more than one extendedDataTable on the same page. In-Reply-To: <1719236551.29235.1324550769802.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <2060229095.1662.1326723738992.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] J?n Jamrich reassigned RF-11850: -------------------------------- Assignee: (was: J?n Jamrich) > RF 4.1.0.Final: Problem using columnResize with more than one extendedDataTable on the same page. > ------------------------------------------------------------------------------------------------- > > Key: RF-11850 > URL: https://issues.jboss.org/browse/RF-11850 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.1.0.Final > Environment: Windows 7 x64 or arch linux x86 > JBoss 7.0.1 Final or Glassfish 3.1 > Reporter: Christian Peter > Priority: Minor > > Hello, > I've encountered some problems using richfaces extendedDataTables in RichFace 4.1.0.Final > Here is the facelet: > {code:title=facelet} > > > > Header7 > #{item.name} > > > > Header8 > #{item.uuid} > > > > Header9 > #{item.uuid} > > > > Header10 > #{item.uuid} > > > > > > > > > > Header7 > #{item.name} > > > > Header8 > #{item.uuid} > > > Header9 > #{item.uuid} > > > > Header10 > #{item.uuid} > > > > > > {code} > > Resizing the columns on the first table works perfectly, but if someone tries to resize the second tables' columns as well, I've got NullPointer exceptions like: > {code:title=stacktrace} > java.lang.NullPointerException > at org.richfaces.renderkit.SortingFilteringRowsRenderer.updateAttribute(SortingFilteringRowsRenderer.java:135) [richfaces-components-ui-4.1.0.Final.jar: > at org.richfaces.renderkit.ExtendedDataTableRenderer.updateWidthOfColumns(ExtendedDataTableRenderer.java:825) [richfaces-components-ui-4.1.0.Final.jar:] > at org.richfaces.renderkit.ExtendedDataTableRenderer.doDecode(ExtendedDataTableRenderer.java:808) [richfaces-components-ui-4.1.0.Final.jar:] > at org.richfaces.renderkit.RendererBase.decode(RendererBase.java:80) [richfaces-components-ui-4.1.0.Final.jar:] > at javax.faces.component.UIComponentBase.decode(UIComponentBase.java:787) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at org.richfaces.component.UIDataAdaptor.processDecodes(UIDataAdaptor.java:819) [richfaces-components-ui-4.1.0.Final.jar:] > at org.richfaces.context.PartialViewExecuteVisitCallback.visit(PartialViewExecuteVisitCallback.java:53) [richfaces-core-impl-4.1.0.Final.jar:] > at org.richfaces.context.BaseExtendedVisitContext.invokeVisitCallback(BaseExtendedVisitContext.java:321) [richfaces-core-impl-4.1.0.Final.jar:] > at org.richfaces.component.UIDataAdaptor.visitTree(UIDataAdaptor.java:1319) [richfaces-components-ui-4.1.0.Final.jar:] > at javax.faces.component.UIComponent.visitTree(UIComponent.java:1600) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at javax.faces.component.UIForm.visitTree(UIForm.java:344) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at javax.faces.component.UIComponent.visitTree(UIComponent.java:1600) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at javax.faces.component.UIComponent.visitTree(UIComponent.java:1600) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at org.richfaces.context.ExtendedPartialViewContextImpl.executeComponents(ExtendedPartialViewContextImpl.java:237) [richfaces-core-impl-4.1.0.Final.jar: > at org.richfaces.context.ExtendedPartialViewContextImpl.processPartialExecutePhase(ExtendedPartialViewContextImpl.java:217) [richfaces-core-impl-4.1.0.F > at org.richfaces.context.ExtendedPartialViewContextImpl.processPartial(ExtendedPartialViewContextImpl.java:196) [richfaces-core-impl-4.1.0.Final.jar:] > at javax.faces.component.UIViewRoot.processDecodes(UIViewRoot.java:931) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at com.sun.faces.lifecycle.ApplyRequestValuesPhase.execute(ApplyRequestValuesPhase.java:78) [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 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] > {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 Jan 16 09:28:18 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?J=C3=A1n_Jamrich_=28JIRA=29?=) Date: Mon, 16 Jan 2012 09:28:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11783) disabled a4j:commandButton with nested tooltip disappears when enabled with ajax render In-Reply-To: <1145377794.68082.1322915200637.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1011004618.1686.1326724098439.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12659551#comment-12659551 ] J?n Jamrich commented on RF-11783: ---------------------------------- Created example with tooltip within a4j:commandButton, but didn't get the same behavior. But tooltip is not working (not displayed even conditions for render met). (Since I wrongly commented commit, it is missing in "Source" tracking. There is related commit: https://source.jboss.org/changelog/RichFaces?cs=23150) Example page: https://source.jboss.org/browse/RichFaces/modules/tests/metamer/trunk/application/src/main/webapp/components/richTooltip/rf11783.xhtml?r=23150 > disabled a4j:commandButton with nested tooltip disappears when enabled with ajax render > --------------------------------------------------------------------------------------- > > Key: RF-11783 > URL: https://issues.jboss.org/browse/RF-11783 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.1.0.Milestone4 > Environment: Mojarra 2.1.3, Glassfish 3.1.1. > Reporter: Brendan Healey > Assignee: J?n Jamrich > > The following code resides in the footer of an extendedDataTable, although my > guess is that this is not relevant. The button is initially disabled, then > bean.property is set true and we do ajax render="myButton". The button > disappears from the screen. Removing the tooltip makes it work as expected. > id="myButton" > value=" test " > action="apage?faces-redirect=true" > disabled="#{empty bean.property}"> > > > > > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 16 09:28:18 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?J=C3=A1n_Jamrich_=28JIRA=29?=) Date: Mon, 16 Jan 2012 09:28:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11783) disabled a4j:commandButton with nested tooltip disappears when enabled with ajax render In-Reply-To: <1145377794.68082.1322915200637.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1654115733.1690.1326724098620.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] J?n Jamrich reassigned RF-11783: -------------------------------- Assignee: (was: J?n Jamrich) > disabled a4j:commandButton with nested tooltip disappears when enabled with ajax render > --------------------------------------------------------------------------------------- > > Key: RF-11783 > URL: https://issues.jboss.org/browse/RF-11783 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.1.0.Milestone4 > Environment: Mojarra 2.1.3, Glassfish 3.1.1. > Reporter: Brendan Healey > > The following code resides in the footer of an extendedDataTable, although my > guess is that this is not relevant. The button is initially disabled, then > bean.property is set true and we do ajax render="myButton". The button > disappears from the screen. Removing the tooltip makes it work as expected. > id="myButton" > value=" test " > action="apage?faces-redirect=true" > disabled="#{empty bean.property}"> > > > > > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 16 09:31:18 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?J=C3=A1n_Jamrich_=28JIRA=29?=) Date: Mon, 16 Jan 2012 09:31:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11814) a4j:commandLink in tabPanel disabled if switchtype = ajax In-Reply-To: <796306910.9115.1323859989475.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1710371138.1699.1326724278440.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12659552#comment-12659552 ] J?n Jamrich commented on RF-11814: ---------------------------------- Issue confirmed. Created page demonstration problem: https://source.jboss.org/browse/RichFaces/modules/tests/metamer/trunk/application/src/main/webapp/components/richTabPanel/rf-11814.xhtml?r=23149 > a4j:commandLink in tabPanel disabled if switchtype = ajax > --------------------------------------------------------- > > Key: RF-11814 > URL: https://issues.jboss.org/browse/RF-11814 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core, component-panels-layout-themes > Affects Versions: 4.1.0.CR2 > Environment: Win 7 64 Bit, Tomcat 7.0.23, Mojarra 2.1.3 > Reporter: Friedhelm Kuehn > Assignee: J?n Jamrich > > In the following constellation (=extract from real page) the a4j:commandlink action method > is correctly triggered on clicking when tabPanels switchType = "client" but not when switchType = "ajax" > {code} > > > > > ..... > > > > > > > Logging out, please wait ! > > > {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 Jan 16 09:31:18 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?J=C3=A1n_Jamrich_=28JIRA=29?=) Date: Mon, 16 Jan 2012 09:31:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11814) a4j:commandLink in tabPanel disabled if switchtype = ajax In-Reply-To: <796306910.9115.1323859989475.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1839739319.1712.1326724278905.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] J?n Jamrich reassigned RF-11814: -------------------------------- Assignee: (was: J?n Jamrich) > a4j:commandLink in tabPanel disabled if switchtype = ajax > --------------------------------------------------------- > > Key: RF-11814 > URL: https://issues.jboss.org/browse/RF-11814 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core, component-panels-layout-themes > Affects Versions: 4.1.0.CR2 > Environment: Win 7 64 Bit, Tomcat 7.0.23, Mojarra 2.1.3 > Reporter: Friedhelm Kuehn > > In the following constellation (=extract from real page) the a4j:commandlink action method > is correctly triggered on clicking when tabPanels switchType = "client" but not when switchType = "ajax" > {code} > > > > > ..... > > > > > > > Logging out, please wait ! > > > {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 Jan 16 11:14:20 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 16 Jan 2012 11:14:20 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11827) showcase - all rich:autocomplete demos do not work on 4.1.1-SNAPSHOT In-Reply-To: <945549203.21383.1324314009775.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1855153413.2120.1326730460147.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved RF-11827. ----------------------------- Assignee: Luk?? Fry? (was: Juraj Huska) Fix Version/s: (was: 4.2.0.CR1) Resolution: Cannot Reproduce Bug As Juraj said, this issue cannot be reproduced anymore. > showcase - all rich:autocomplete demos do not work on 4.1.1-SNAPSHOT > -------------------------------------------------------------------- > > Key: RF-11827 > URL: https://issues.jboss.org/browse/RF-11827 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input, showcase > Environment: richfaces showcase 4.1.1-SNAPSHOT > all containers > all brosers > Reporter: Juraj Huska > Assignee: Luk?? Fry? > Priority: Critical > > Demos for rich:autocomplete do not work, *whole functionality of autocomplete is broken somehow*. > It is noticeable on *all containers* and on *all browsers*. > It works fine on 4.1.0-SNAPSHOT showcase wars. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 16 12:05:18 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 16 Jan 2012 12:05:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11890) ResourceServlet does not set HTTP headers for caching Message-ID: <896407184.2481.1326733518446.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Luk?? Fry? created RF-11890: ------------------------------- Summary: ResourceServlet does not set HTTP headers for caching Key: RF-11890 URL: https://issues.jboss.org/browse/RF-11890 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: core Affects Versions: 4.2.0.CR1 Reporter: Luk?? Fry? Assignee: Luk?? Fry? {quote} All RichFaces resources served by Faces Servlet have headers set appropriately for caching. (You can check it by removing your Filter and turning resourceMapping=false). I assume you have problems with ResourceServlet where resources does not go through RichFaces ResourceHandler, so headers are set as for any other JSF resource - which means (AFAIK) no caching at all. {quote} This assumption needs to be verified before implementing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 17 00:57:18 2012 From: jira-events at lists.jboss.org (Daniel Dostal (JIRA)) Date: Tue, 17 Jan 2012 00:57:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-10267) Accordion creating from Java NPE if activeItem is not set In-Reply-To: <1587760478.27386.1295566550122.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <2127776043.3692.1326779838688.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-10267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12659740#comment-12659740 ] Daniel Dostal commented on RF-10267: ------------------------------------ The API clearly states that this field is not required. The description is also empty. I have just installed 4.1.0.Final and this bug is still current. I'm not even sure what this item should be. I'll set them to blank, but this is quite sad. > Accordion creating from Java NPE if activeItem is not set > --------------------------------------------------------- > > Key: RF-10267 > URL: https://issues.jboss.org/browse/RF-10267 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: base functionality > Affects Versions: 4.0.0.Milestone5 > Environment: Ununtu 10.10, Java 6 > Reporter: Konstantin Pupkov > Priority: Minor > Fix For: 4.Future > > > in Java... > FacesContext ctx=FacesContext.getCurrentInstance(); > pendingBar = (HtmlAccordion) ctx > .getApplication() > .createComponent(ctx, HtmlAccordion.COMPONENT_TYPE, "org.richfaces.AccordionRenderer"); > pendingBar.setId("pend"); > ...... > error on page: > ... > ava.lang.NullPointerException > org.richfaces.component.AbstractAccordion.getActiveItem(AbstractAccordion.java:50) > org.richfaces.renderkit.html.TogglePanelRenderer.doEncodeBegin(TogglePanelRenderer.java:116) > org.richfaces.renderkit.html.AccordionRenderer.doEncodeBegin(AccordionRenderer.java:55) > org.richfaces.renderkit.RendererBase.encodeBegin(RendererBase.java:116) > javax.faces.component.UIComponentBase.encodeBegin(UIComponentBase.java:824) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 17 03:33:18 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 17 Jan 2012 03:33:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11890) ResourceServlet does not set HTTP headers for caching In-Reply-To: <896407184.2481.1326733518446.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <18456987.4068.1326789198279.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12659759#comment-12659759 ] Luk?? Fry? commented on RF-11890: --------------------------------- Check also that regular RichFaces resources have headers setup properly when resource mapping is off. > ResourceServlet does not set HTTP headers for caching > ----------------------------------------------------- > > Key: RF-11890 > URL: https://issues.jboss.org/browse/RF-11890 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 4.2.0.CR1 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > > {quote} > All RichFaces resources served by Faces Servlet have headers set appropriately for caching. > (You can check it by removing your Filter and turning resourceMapping=false). > > I assume you have problems with ResourceServlet where resources does not go through RichFaces ResourceHandler, so headers are set as for any other JSF resource - which means (AFAIK) no caching at all. > {quote} > This assumption needs to be verified before implementing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 17 03:48:18 2012 From: jira-events at lists.jboss.org (shimon lifshitz (JIRA)) Date: Tue, 17 Jan 2012 03:48:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-10779) columnClasses not working on rich:dataGrid In-Reply-To: <2097570417.35324.1300457326600.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <735261082.4092.1326790098524.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-10779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12659760#comment-12659760 ] shimon lifshitz commented on RF-10779: -------------------------------------- Is there a workaround? I think it is a bug because it exist in older versions. > columnClasses not working on rich:dataGrid > ------------------------------------------ > > Key: RF-10779 > URL: https://issues.jboss.org/browse/RF-10779 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.0.0.CR1 > Environment: Windows Vista Build 6001 > apache-tomcat-7.0.11 > Sun jdk1.6.0_14 > RichFaces richfaces-4.0.0.20110227-CR1 > Mojarra JSF 2.0.3-FCS > Reporter: Karl Mueller > Fix For: 4.Future > > > The attribute columnClasses shows no effect when used on rich:dataGrid. > The assigned css classe(s) do not show up in the generated html table and the styles are not applied. > Only the "rf-dg-c" class gets assigned to the td tag. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 17 04:02:19 2012 From: jira-events at lists.jboss.org (shimon lifshitz (JIRA)) Date: Tue, 17 Jan 2012 04:02:19 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-10779) columnClasses not working on rich:dataGrid In-Reply-To: <2097570417.35324.1300457326600.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <2147373346.4152.1326790939347.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-10779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12659768#comment-12659768 ] shimon lifshitz commented on RF-10779: -------------------------------------- In the show case, there is a comment that dataGrid uses all panelGrid attributes, but columnClasses is attribute in panelGrid and doesnot exist in dataGrid. > columnClasses not working on rich:dataGrid > ------------------------------------------ > > Key: RF-10779 > URL: https://issues.jboss.org/browse/RF-10779 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.0.0.CR1 > Environment: Windows Vista Build 6001 > apache-tomcat-7.0.11 > Sun jdk1.6.0_14 > RichFaces richfaces-4.0.0.20110227-CR1 > Mojarra JSF 2.0.3-FCS > Reporter: Karl Mueller > Fix For: 4.Future > > > The attribute columnClasses shows no effect when used on rich:dataGrid. > The assigned css classe(s) do not show up in the generated html table and the styles are not applied. > Only the "rf-dg-c" class gets assigned to the td tag. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 17 04:28:18 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?J=C3=A1n_Jamrich_=28JIRA=29?=) Date: Tue, 17 Jan 2012 04:28:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11825) rich:fileUpload - File selected for upload is duplicated in IE 8 when placed in composite component In-Reply-To: <723368030.20345.1324296789427.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1411351186.4267.1326792498383.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] J?n Jamrich resolved RF-11825. ------------------------------ Assignee: (was: J?n Jamrich) Resolution: Cannot Reproduce Bug Created example in Metamer (see Source tab for details), but I was not able to reproduce it. > rich:fileUpload - File selected for upload is duplicated in IE 8 when placed in composite component > --------------------------------------------------------------------------------------------------- > > Key: RF-11825 > URL: https://issues.jboss.org/browse/RF-11825 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.1.0.Final > Environment: Apache Tomcat 6.0 > Java 1.6.0_24 > Mojarra 2.1.2 > Reporter: Pavel Hofr?k > Labels: composite_component, fileUpload, richfaces > > When rich:fileUpload is part of composite component, and this component is placed in page, than when file is selected from system dialog, it is added twice in list of files. > This fault occurs in IE 8. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 17 07:08:18 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 17 Jan 2012 07:08:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11483) Elegant way for Push topic creating In-Reply-To: <11494155.16954.1318245975997.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1467164002.4712.1326802098511.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12659820#comment-12659820 ] Luk?? Fry? commented on RF-11483: --------------------------------- This issue is much more critical, because the {{PushContext}} is not initialized properly in time when needs to be used in order to initialize {{PushServlet}} properly. {{PushContext}} is initialized in Showcase when {{TopicsContext#lookup()}} is called, which is called by {{TopicsInitializer}} at JSF application startup. So following {{NullPointerException}} is thrown because {{PushContextImpl#init(...)}} wasn't called yet. {code} 12:55:43,883 ERROR [stderr] (MSC service thread 1-3) java.lang.NullPointerException 12:55:43,883 ERROR [stderr] (MSC service thread 1-3) at org.richfaces.webapp.PushHandlerFilter.init(PushHandlerFilter.java:64) 12:55:43,883 ERROR [stderr] (MSC service thread 1-3) at org.atmosphere.util.AtmosphereFilterChain.init(AtmosphereFilterChain.java:105) 12:55:43,884 ERROR [stderr] (MSC service thread 1-3) at org.atmosphere.handler.ReflectorServletProcessor$FilterChainServletWrapper.init(ReflectorServletProcessor.java:273) 12:55:43,884 ERROR [stderr] (MSC service thread 1-3) at org.atmosphere.handler.ReflectorServletProcessor.init(ReflectorServletProcessor.java:164) 12:55:43,884 ERROR [stderr] (MSC service thread 1-3) at org.atmosphere.cpr.AtmosphereServlet.initAtmosphereHandler(AtmosphereServlet.java:813) 12:55:43,884 ERROR [stderr] (MSC service thread 1-3) at org.atmosphere.cpr.AtmosphereServlet.init(AtmosphereServlet.java:566) 12:55:43,884 ERROR [stderr] (MSC service thread 1-3) at org.richfaces.webapp.PushServlet.init(PushServlet.java:98) 12:55:43,884 ERROR [stderr] (MSC service thread 1-3) at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1202) 12:55:43,884 ERROR [stderr] (MSC service thread 1-3) at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1102) 12:55:43,884 ERROR [stderr] (MSC service thread 1-3) at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3631) 12:55:43,885 ERROR [stderr] (MSC service thread 1-3) at org.apache.catalina.core.StandardContext.start(StandardContext.java:3844) 12:55:43,885 ERROR [stderr] (MSC service thread 1-3) at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:70) 12:55:43,885 ERROR [stderr] (MSC service thread 1-3) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) 12:55:43,885 ERROR [stderr] (MSC service thread 1-3) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) 12:55:43,885 ERROR [stderr] (MSC service thread 1-3) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) 12:55:43,885 ERROR [stderr] (MSC service thread 1-3) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) 12:55:43,885 ERROR [stderr] (MSC service thread 1-3) at java.lang.Thread.run(Thread.java:662) {code} Exception above is hidden behind following meaningless exception: {code} 12:52:47,369 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/new_project]] (MSC service thread 1-3) Servlet /new_project threw load() exception: javax.servlet.ServletException at org.atmosphere.cpr.AtmosphereServlet.init(AtmosphereServlet.java:577) [atmosphere-runtime-0.8.0-RC1.jar:] at org.richfaces.webapp.PushServlet.init(PushServlet.java:98) [richfaces-core-impl-4.1.0.Final.jar:] at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1202) [jbossweb-7.0.1.Final.jar:7.0.2.Final] at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1102) [jbossweb-7.0.1.Final.jar:7.0.2.Final] at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3631) [jbossweb-7.0.1.Final.jar:7.0.2.Final] at org.apache.catalina.core.StandardContext.start(StandardContext.java:3844) [jbossweb-7.0.1.Final.jar:7.0.2.Final] at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:70) [jboss-as-web-7.0.2.Final.jar:7.0.2.Final] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_26] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_26] at java.lang.Thread.run(Thread.java:662) [:1.6.0_26] {code} > Elegant way for Push topic creating > ----------------------------------- > > Key: RF-11483 > URL: https://issues.jboss.org/browse/RF-11483 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-push/poll, core > Affects Versions: 4.1.0.Milestone1 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 4.2.0.CR1 > > > Currently, topics have to be initialized with similar class: > https://github.com/richfaces/showcase/blob/4.1.0.20110910-M2/src/main/java/org/richfaces/demo/push/TopicsInitializer.java > I suggest to create topic on demand (lazily), when it is accessed first. > It needs following changes: > * {{PushRendererBase}} - will create Topic for @address attribute > * {{JMSTopicsContextImpl}} - will create topic when JMS message received > * {{PushObserverMethod}} - will create topic when @Push event for given topic observed > * ... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 17 07:08:19 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 17 Jan 2012 07:08:19 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11483) Elegant way for Push topic creating In-Reply-To: <11494155.16954.1318245975997.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <540222923.4718.1326802099400.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated RF-11483: ---------------------------- Fix Version/s: 4.2.0.CR1 (was: 4.3-Tracking) Priority: Critical (was: Major) Forum Reference: http://community.jboss.org/message/630871#630871 (was: http://community.jboss.org/message/630871#630871) Scheduled to {{4.2.0.CR1}} and increased priority to {{critical}}. > Elegant way for Push topic creating > ----------------------------------- > > Key: RF-11483 > URL: https://issues.jboss.org/browse/RF-11483 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-push/poll, core > Affects Versions: 4.1.0.Milestone1 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Priority: Critical > Fix For: 4.2.0.CR1 > > > Currently, topics have to be initialized with similar class: > https://github.com/richfaces/showcase/blob/4.1.0.20110910-M2/src/main/java/org/richfaces/demo/push/TopicsInitializer.java > I suggest to create topic on demand (lazily), when it is accessed first. > It needs following changes: > * {{PushRendererBase}} - will create Topic for @address attribute > * {{JMSTopicsContextImpl}} - will create topic when JMS message received > * {{PushObserverMethod}} - will create topic when @Push event for given topic observed > * ... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 17 09:31:18 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Tue, 17 Jan 2012 09:31:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11834) [RF4.1.final] rich:picklist don't support @RequestScope In-Reply-To: <823611390.23103.1324374549401.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <2006891551.5089.1326810678403.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-11834: ------------------------------- Fix Version/s: 4.2.0.CR1 Assignee: Brian Leathem Forum Reference: http://community.jboss.org/thread/176257?tstart=0 (was: http://community.jboss.org/thread/176257?tstart=0) > [RF4.1.final] rich:picklist don't support @RequestScope > ------------------------------------------------------- > > Key: RF-11834 > URL: https://issues.jboss.org/browse/RF-11834 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 4.1.0.Final > Environment: JBoss 7 / RF4.1.final jdk 1.6_u27 > Reporter: Adrien Adrien > Assignee: Brian Leathem > Labels: picklist, scope > Fix For: 4.2.0.CR1 > > > picklist don't works if backbean is @requestScope. > (it worked in RF 3.3.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 Jan 17 09:33:18 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Tue, 17 Jan 2012 09:33:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11850) RF 4.1.0.Final: Problem using columnResize with more than one extendedDataTable on the same page. In-Reply-To: <1719236551.29235.1324550769802.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1488885565.5101.1326810798580.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-11850: ------------------------------- Fix Version/s: 4.2.0.CR1 Forum Reference: http://community.jboss.org/message/641921#641921 (was: http://community.jboss.org/message/641921#641921) > RF 4.1.0.Final: Problem using columnResize with more than one extendedDataTable on the same page. > ------------------------------------------------------------------------------------------------- > > Key: RF-11850 > URL: https://issues.jboss.org/browse/RF-11850 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.1.0.Final > Environment: Windows 7 x64 or arch linux x86 > JBoss 7.0.1 Final or Glassfish 3.1 > Reporter: Christian Peter > Priority: Minor > Fix For: 4.2.0.CR1 > > > Hello, > I've encountered some problems using richfaces extendedDataTables in RichFace 4.1.0.Final > Here is the facelet: > {code:title=facelet} > > > > Header7 > #{item.name} > > > > Header8 > #{item.uuid} > > > > Header9 > #{item.uuid} > > > > Header10 > #{item.uuid} > > > > > > > > > > Header7 > #{item.name} > > > > Header8 > #{item.uuid} > > > Header9 > #{item.uuid} > > > > Header10 > #{item.uuid} > > > > > > {code} > > Resizing the columns on the first table works perfectly, but if someone tries to resize the second tables' columns as well, I've got NullPointer exceptions like: > {code:title=stacktrace} > java.lang.NullPointerException > at org.richfaces.renderkit.SortingFilteringRowsRenderer.updateAttribute(SortingFilteringRowsRenderer.java:135) [richfaces-components-ui-4.1.0.Final.jar: > at org.richfaces.renderkit.ExtendedDataTableRenderer.updateWidthOfColumns(ExtendedDataTableRenderer.java:825) [richfaces-components-ui-4.1.0.Final.jar:] > at org.richfaces.renderkit.ExtendedDataTableRenderer.doDecode(ExtendedDataTableRenderer.java:808) [richfaces-components-ui-4.1.0.Final.jar:] > at org.richfaces.renderkit.RendererBase.decode(RendererBase.java:80) [richfaces-components-ui-4.1.0.Final.jar:] > at javax.faces.component.UIComponentBase.decode(UIComponentBase.java:787) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at org.richfaces.component.UIDataAdaptor.processDecodes(UIDataAdaptor.java:819) [richfaces-components-ui-4.1.0.Final.jar:] > at org.richfaces.context.PartialViewExecuteVisitCallback.visit(PartialViewExecuteVisitCallback.java:53) [richfaces-core-impl-4.1.0.Final.jar:] > at org.richfaces.context.BaseExtendedVisitContext.invokeVisitCallback(BaseExtendedVisitContext.java:321) [richfaces-core-impl-4.1.0.Final.jar:] > at org.richfaces.component.UIDataAdaptor.visitTree(UIDataAdaptor.java:1319) [richfaces-components-ui-4.1.0.Final.jar:] > at javax.faces.component.UIComponent.visitTree(UIComponent.java:1600) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at javax.faces.component.UIForm.visitTree(UIForm.java:344) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at javax.faces.component.UIComponent.visitTree(UIComponent.java:1600) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at javax.faces.component.UIComponent.visitTree(UIComponent.java:1600) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at org.richfaces.context.ExtendedPartialViewContextImpl.executeComponents(ExtendedPartialViewContextImpl.java:237) [richfaces-core-impl-4.1.0.Final.jar: > at org.richfaces.context.ExtendedPartialViewContextImpl.processPartialExecutePhase(ExtendedPartialViewContextImpl.java:217) [richfaces-core-impl-4.1.0.F > at org.richfaces.context.ExtendedPartialViewContextImpl.processPartial(ExtendedPartialViewContextImpl.java:196) [richfaces-core-impl-4.1.0.Final.jar:] > at javax.faces.component.UIViewRoot.processDecodes(UIViewRoot.java:931) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at com.sun.faces.lifecycle.ApplyRequestValuesPhase.execute(ApplyRequestValuesPhase.java:78) [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 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] > {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 Jan 17 15:43:19 2012 From: jira-events at lists.jboss.org (Wesley Hales (JIRA)) Date: Tue, 17 Jan 2012 15:43:19 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11772) showcase - a4j:attachQueue - ajax request from mobile device generates WARNING on the server log In-Reply-To: <942002739.61843.1322757520977.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <446907323.6181.1326832999587.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wesley Hales resolved RF-11772. ------------------------------- Resolution: Won't Fix This issue is ok for mobile showcase only. It does not appear in regular demo. > showcase - a4j:attachQueue - ajax request from mobile device generates WARNING on the server log > ------------------------------------------------------------------------------------------------ > > Key: RF-11772 > URL: https://issues.jboss.org/browse/RF-11772 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core, mobile, showcase > Affects Versions: 4.1.0.CR2 > Environment: richfaces showcase 4.1.CR2 > container: JBoss AS 7.1.0.Beta1, JBoss AS 6.0.0.Final > mobile device: iPad1, Motorola Xoom, iPhone4 > Reporter: Juraj Huska > Assignee: Wesley Hales > Priority: Minor > Fix For: 4.2.0.CR1 > > > In demo for a4j:attachQueue, when typing to input, the *generated ajax requests cause warning logged on the container console*: > {code} > 17:29:40,118 WARNING [org.richfaces.log.Components] (http--0.0.0.0-8080-5) Queue with name 'j_idt9' has already been registered > {code} > The *functionality remains fine*, and this is noticeable *only on mobile devices*. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 17 15:47:18 2012 From: jira-events at lists.jboss.org (Wesley Hales (JIRA)) Date: Tue, 17 Jan 2012 15:47:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11773) Mobile Showcase and rich:orderingList/rich:pickList - control buttons can't be enabled In-Reply-To: <677171215.62017.1322758002710.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1785709887.6188.1326833238842.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12659971#comment-12659971 ] Wesley Hales commented on RF-11773: ----------------------------------- Works for me on iPad/iOS 5.0.1 I don't have a Nexus Android 2.3.6 to test on. We will say Android 2.3.3 is good enough for our first level of support. Android has a lot of fragmentation with their support, so it will vary across devices. > Mobile Showcase and rich:orderingList/rich:pickList - control buttons can't be enabled > -------------------------------------------------------------------------------------- > > Key: RF-11773 > URL: https://issues.jboss.org/browse/RF-11773 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: mobile, showcase > Affects Versions: 4.1.0.CR2 > Environment: JBoss AS 7.1.0.Beta1 > mobile devices: Nexus - Android 2.3.6, iPad > Reporter: Jan Papousek > Assignee: Wesley Hales > Fix For: 4.2.0.CR1 > > > It works correctly on iPhone, Motorola Xoom(Andorid), Android emulator (2.3.3). > It does not work for Nexus mobile device and iPad. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 17 15:47:18 2012 From: jira-events at lists.jboss.org (Wesley Hales (JIRA)) Date: Tue, 17 Jan 2012 15:47:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11773) Mobile Showcase and rich:orderingList/rich:pickList - control buttons can't be enabled In-Reply-To: <677171215.62017.1322758002710.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <82930192.6192.1326833238945.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wesley Hales resolved RF-11773. ------------------------------- Resolution: Won't Fix > Mobile Showcase and rich:orderingList/rich:pickList - control buttons can't be enabled > -------------------------------------------------------------------------------------- > > Key: RF-11773 > URL: https://issues.jboss.org/browse/RF-11773 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: mobile, showcase > Affects Versions: 4.1.0.CR2 > Environment: JBoss AS 7.1.0.Beta1 > mobile devices: Nexus - Android 2.3.6, iPad > Reporter: Jan Papousek > Assignee: Wesley Hales > Fix For: 4.2.0.CR1 > > > It works correctly on iPhone, Motorola Xoom(Andorid), Android emulator (2.3.3). > It does not work for Nexus mobile device and iPad. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 17 15:49:19 2012 From: jira-events at lists.jboss.org (Wesley Hales (JIRA)) Date: Tue, 17 Jan 2012 15:49:19 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11774) mobile showcase - rich:tree - touch event on particular part of tree causes selecting of whole tree component In-Reply-To: <468905842.65339.1322827900636.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1364965805.6207.1326833359820.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12659974#comment-12659974 ] Wesley Hales commented on RF-11774: ----------------------------------- I can't reproduce either. Although, I'm sure the issue exists. The tree component was not written for touch envs, and I tried to use CSS to make it useable. > mobile showcase - rich:tree - touch event on particular part of tree causes selecting of whole tree component > ------------------------------------------------------------------------------------------------------------- > > Key: RF-11774 > URL: https://issues.jboss.org/browse/RF-11774 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-tree, mobile, showcase > Affects Versions: 4.1.0.CR2 > Environment: app: mobile richfaces-showcase > container: JBoss AS 7.1.0.Beta1 > device: Motorola Xoom > Reporter: Juraj Huska > Assignee: Wesley Hales > Priority: Minor > Fix For: 4.2.0.CR1 > > > When I *touch particular part of the tree component*, e.g. sign for expanding the node, then *the whole tree component is selected* till the node is not expanded. > It *looks* quite *disturbing*, such a blinking. > This behavior is also noticeable on iPad1, however it is not so disruptive as in Android device, since the color of selecting the whole tree is different. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 17 15:49:19 2012 From: jira-events at lists.jboss.org (Wesley Hales (JIRA)) Date: Tue, 17 Jan 2012 15:49:19 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11774) mobile showcase - rich:tree - touch event on particular part of tree causes selecting of whole tree component In-Reply-To: <468905842.65339.1322827900636.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1462406506.6210.1326833359958.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wesley Hales resolved RF-11774. ------------------------------- Resolution: Won't Fix > mobile showcase - rich:tree - touch event on particular part of tree causes selecting of whole tree component > ------------------------------------------------------------------------------------------------------------- > > Key: RF-11774 > URL: https://issues.jboss.org/browse/RF-11774 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-tree, mobile, showcase > Affects Versions: 4.1.0.CR2 > Environment: app: mobile richfaces-showcase > container: JBoss AS 7.1.0.Beta1 > device: Motorola Xoom > Reporter: Juraj Huska > Assignee: Wesley Hales > Priority: Minor > Fix For: 4.2.0.CR1 > > > When I *touch particular part of the tree component*, e.g. sign for expanding the node, then *the whole tree component is selected* till the node is not expanded. > It *looks* quite *disturbing*, such a blinking. > This behavior is also noticeable on iPad1, however it is not so disruptive as in Android device, since the color of selecting the whole tree is different. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 17 16:06:18 2012 From: jira-events at lists.jboss.org (Wesley Hales (JIRA)) Date: Tue, 17 Jan 2012 16:06:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11778) mobile showcase - rich:calendar - days of new month are smaller than others In-Reply-To: <621211492.65741.1322833540899.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1672039134.6238.1326834378359.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wesley Hales resolved RF-11778. ------------------------------- Resolution: Done > mobile showcase - rich:calendar - days of new month are smaller than others > --------------------------------------------------------------------------- > > Key: RF-11778 > URL: https://issues.jboss.org/browse/RF-11778 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input, mobile, showcase, skinning > Environment: richfaces showcase 4.1.CR1 > Reporter: Juraj Huska > Assignee: Wesley Hales > Priority: Minor > Fix For: 4.2.0.CR1 > > Attachments: calendarNewMonthDaysWrongSize.PNG > > > The size of the days which are from the new month are smaller than the other days in the displayed month. > 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 Jan 17 16:06:18 2012 From: jira-events at lists.jboss.org (Wesley Hales (JIRA)) Date: Tue, 17 Jan 2012 16:06:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11775) mobile showcase - rich:panelMenu - sub menus are not indented accordingly In-Reply-To: <989282194.65392.1322829281680.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1980920136.6242.1326834378591.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wesley Hales resolved RF-11775. ------------------------------- Resolution: Done > mobile showcase - rich:panelMenu - sub menus are not indented accordingly > ------------------------------------------------------------------------- > > Key: RF-11775 > URL: https://issues.jboss.org/browse/RF-11775 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-menu, mobile, showcase, skinning > Affects Versions: 4.1.0.CR2 > Environment: richfaces showcase 4.1.CR1 > devices: iPad1, Motorla Xoom > Reporter: Juraj Huska > Assignee: Wesley Hales > Priority: Minor > Fix For: 4.2.0.CR1 > > Attachments: correctIndentation.png, incorrectIndentation.PNG > > > The *items of sub menu* of richPanel are *not indented correctly*. They have the same indentation as all items in that menu item, although they are lower in the hierarchy. > Please see the attachment where is probably more clear what I mean. There you can find the correct indention from desktop showcase and the incorrect one from mobile 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 Tue Jan 17 18:01:19 2012 From: jira-events at lists.jboss.org (Dmytro Batishchev (JIRA)) Date: Tue, 17 Jan 2012 18:01:19 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11891) Simple bug in org.richfaces.resource.Xcss2EcssConverter Message-ID: <815303006.6467.1326841279163.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Dmytro Batishchev created RF-11891: -------------------------------------- Summary: Simple bug in org.richfaces.resource.Xcss2EcssConverter Key: RF-11891 URL: https://issues.jboss.org/browse/RF-11891 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: core Affects Versions: 4.1.0.Final Environment: Any Reporter: Dmytro Batishchev Simple bug in org.richfaces.resource.Xcss2EcssConverter class, please, comment out next line: {quote} _String string = "E:/projs/richafces4/framework/trunk/impl/src/test/java/org/ajax4jsf/cache/extended.xcss"_ {quote} PS: Sorry for my English. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 18 01:18:18 2012 From: jira-events at lists.jboss.org (Dmytro Batishchev (JIRA)) Date: Wed, 18 Jan 2012 01:18:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11891) Simple bug in org.richfaces.resource.Xcss2EcssConverter In-Reply-To: <815303006.6467.1326841279163.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <151173961.6786.1326867498432.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Batishchev updated RF-11891: ----------------------------------- Description: Simple bug in org.richfaces.resource.Xcss2EcssConverter classfile in main class, please, comment out or delete next line: {quote} _String string = "E:/projs/richafces4/framework/trunk/impl/src/test/java/org/ajax4jsf/cache/extended.xcss"_ {quote} PS: Sorry for my English. was: Simple bug in org.richfaces.resource.Xcss2EcssConverter class, please, comment out next line: {quote} _String string = "E:/projs/richafces4/framework/trunk/impl/src/test/java/org/ajax4jsf/cache/extended.xcss"_ {quote} PS: Sorry for my English. > Simple bug in org.richfaces.resource.Xcss2EcssConverter > ------------------------------------------------------- > > Key: RF-11891 > URL: https://issues.jboss.org/browse/RF-11891 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 4.1.0.Final > Environment: Any > Reporter: Dmytro Batishchev > > Simple bug in org.richfaces.resource.Xcss2EcssConverter classfile in main class, please, comment out or delete next line: > {quote} > _String string = "E:/projs/richafces4/framework/trunk/impl/src/test/java/org/ajax4jsf/cache/extended.xcss"_ > {quote} > PS: Sorry for my English. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 18 04:04:18 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 18 Jan 2012 04:04:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11892) Push: turn on JMS integration by default Message-ID: <985205215.6984.1326877458621.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Luk?? Fry? created RF-11892: ------------------------------- Summary: Push: turn on JMS integration by default Key: RF-11892 URL: https://issues.jboss.org/browse/RF-11892 Project: RichFaces Issue Type: Task Security Level: Public (Everyone can see) Components: component-push/poll Affects Versions: 4.1.0.Final, 4.0.0.Final Reporter: Luk?? Fry? Assignee: Luk?? Fry? Fix For: 4.2.0.CR1 On team meeting [1], we have discussed necessity to simplify configuration of Push in order to simplify starting with push for new users. I suggest to replace current configuration {{org.richfaces.push.jms.disable}} with {{org.richfaces.push.jms.enable}}, leaving previous one with no effect or providing warning. [1] https://community.jboss.org/wiki/RichFacesTeamMeetingAgenda2012-01-17 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 18 04:14:19 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 18 Jan 2012 04:14:19 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11893) Increment version number to 4.2.0-SNAPSHOT Message-ID: <1843504770.7002.1326878059466.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Luk?? Fry? created RF-11893: ------------------------------- Summary: Increment version number to 4.2.0-SNAPSHOT Key: RF-11893 URL: https://issues.jboss.org/browse/RF-11893 Project: RichFaces Issue Type: Task Security Level: Public (Everyone can see) Components: build/distribution, qe Affects Versions: 4.2.0.CR1 Reporter: Luk?? Fry? Assignee: Luk?? Fry? Fix For: 4.2.0.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 Jan 18 04:38:19 2012 From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA)) Date: Wed, 18 Jan 2012 04:38:19 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11838) Warning in Chrome console for pages with ajax In-Reply-To: <836209596.24520.1324389969366.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1666609354.7055.1326879499508.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavol Pitonak reopened RF-11838: -------------------------------- I see the warning in Chrome's console after jQuery upgrade (jQuery.fn.jquery returns 1.7.1). {quote} RichFaces 4.1.1-SNAPSHOT Metamer 4.1.1-SNAPSHOT Mojarra 2.1.5 JBoss AS 7.1.0.CR1 OpenJDK Runtime Environment 1.6.0_22-b22 @ Linux Chrome 16.0.912.75 @ Linux i686 {quote} > Warning in Chrome console for pages with ajax > --------------------------------------------- > > Key: RF-11838 > URL: https://issues.jboss.org/browse/RF-11838 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: compatibility > Affects Versions: 4.1.0.Final > Environment: Google Chrome 16.0.912.63 > Reporter: Pavol Pitonak > > # open Showcase in Chrome http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=ajax&skin=blueSky > # open browser console > # type "xxx" into input > result: > The following warning is displayed in browser console 6 times (twice for each Ajax request). Seems to be Chrome-specific and seems not to influence functionality of any component. > {quote} > event.layerX and event.layerY are broken and deprecated in WebKit. They will be removed from the engine in the near future. > {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 Jan 18 07:40:18 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 18 Jan 2012 07:40:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11894) PushHandlerFilter initialization fails when PushServlet registered manually Message-ID: <487983712.7487.1326890418351.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Luk?? Fry? created RF-11894: ------------------------------- Summary: PushHandlerFilter initialization fails when PushServlet registered manually Key: RF-11894 URL: https://issues.jboss.org/browse/RF-11894 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: core Affects Versions: 4.1.0.Final Reporter: Luk?? Fry? Assignee: Luk?? Fry? Fix For: 4.2.0.CR1 When {{PushContext}} is not touched before the {{PushHandlerImpl}} is initialized, {{SessionManager}} is not stored in the {{ServletContext}} attributes and initialization fails. {{NullPointerException}} is thrown in this case: {code} 12:55:43,883 ERROR [stderr] (MSC service thread 1-3) java.lang.NullPointerException 12:55:43,883 ERROR [stderr] (MSC service thread 1-3) at org.richfaces.webapp.PushHandlerFilter.init(PushHandlerFilter.java:64) 12:55:43,883 ERROR [stderr] (MSC service thread 1-3) at org.atmosphere.util.AtmosphereFilterChain.init(AtmosphereFilterChain.java:105) 12:55:43,884 ERROR [stderr] (MSC service thread 1-3) at org.atmosphere.handler.ReflectorServletProcessor$FilterChainServletWrapper.init(ReflectorServletProcessor.java:273) 12:55:43,884 ERROR [stderr] (MSC service thread 1-3) at org.atmosphere.handler.ReflectorServletProcessor.init(ReflectorServletProcessor.java:164) 12:55:43,884 ERROR [stderr] (MSC service thread 1-3) at org.atmosphere.cpr.AtmosphereServlet.initAtmosphereHandler(AtmosphereServlet.java:813) 12:55:43,884 ERROR [stderr] (MSC service thread 1-3) at org.atmosphere.cpr.AtmosphereServlet.init(AtmosphereServlet.java:566) 12:55:43,884 ERROR [stderr] (MSC service thread 1-3) at org.richfaces.webapp.PushServlet.init(PushServlet.java:98) 12:55:43,884 ERROR [stderr] (MSC service thread 1-3) at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1202) 12:55:43,884 ERROR [stderr] (MSC service thread 1-3) at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1102) 12:55:43,884 ERROR [stderr] (MSC service thread 1-3) at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3631) 12:55:43,885 ERROR [stderr] (MSC service thread 1-3) at org.apache.catalina.core.StandardContext.start(StandardContext.java:3844) 12:55:43,885 ERROR [stderr] (MSC service thread 1-3) at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:70) 12:55:43,885 ERROR [stderr] (MSC service thread 1-3) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) 12:55:43,885 ERROR [stderr] (MSC service thread 1-3) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) 12:55:43,885 ERROR [stderr] (MSC service thread 1-3) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) 12:55:43,885 ERROR [stderr] (MSC service thread 1-3) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) 12:55:43,885 ERROR [stderr] (MSC service thread 1-3) at java.lang.Thread.run(Thread.java:662) {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 Jan 18 07:40:18 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 18 Jan 2012 07:40:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11894) PushHandlerFilter initialization fails when PushServlet registered manually In-Reply-To: <487983712.7487.1326890418351.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1224134537.7488.1326890418408.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12660129#comment-12660129 ] Luk?? Fry? commented on RF-11894: --------------------------------- Solution is initialize {{SessionManager}} reference lazily. > PushHandlerFilter initialization fails when PushServlet registered manually > --------------------------------------------------------------------------- > > Key: RF-11894 > URL: https://issues.jboss.org/browse/RF-11894 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 4.1.0.Final > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 4.2.0.CR1 > > > When {{PushContext}} is not touched before the {{PushHandlerImpl}} is initialized, {{SessionManager}} is not stored in the {{ServletContext}} attributes and initialization fails. > {{NullPointerException}} is thrown in this case: > {code} > 12:55:43,883 ERROR [stderr] (MSC service thread 1-3) java.lang.NullPointerException > 12:55:43,883 ERROR [stderr] (MSC service thread 1-3) at org.richfaces.webapp.PushHandlerFilter.init(PushHandlerFilter.java:64) > 12:55:43,883 ERROR [stderr] (MSC service thread 1-3) at org.atmosphere.util.AtmosphereFilterChain.init(AtmosphereFilterChain.java:105) > 12:55:43,884 ERROR [stderr] (MSC service thread 1-3) at org.atmosphere.handler.ReflectorServletProcessor$FilterChainServletWrapper.init(ReflectorServletProcessor.java:273) > 12:55:43,884 ERROR [stderr] (MSC service thread 1-3) at org.atmosphere.handler.ReflectorServletProcessor.init(ReflectorServletProcessor.java:164) > 12:55:43,884 ERROR [stderr] (MSC service thread 1-3) at org.atmosphere.cpr.AtmosphereServlet.initAtmosphereHandler(AtmosphereServlet.java:813) > 12:55:43,884 ERROR [stderr] (MSC service thread 1-3) at org.atmosphere.cpr.AtmosphereServlet.init(AtmosphereServlet.java:566) > 12:55:43,884 ERROR [stderr] (MSC service thread 1-3) at org.richfaces.webapp.PushServlet.init(PushServlet.java:98) > 12:55:43,884 ERROR [stderr] (MSC service thread 1-3) at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1202) > 12:55:43,884 ERROR [stderr] (MSC service thread 1-3) at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1102) > 12:55:43,884 ERROR [stderr] (MSC service thread 1-3) at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3631) > 12:55:43,885 ERROR [stderr] (MSC service thread 1-3) at org.apache.catalina.core.StandardContext.start(StandardContext.java:3844) > 12:55:43,885 ERROR [stderr] (MSC service thread 1-3) at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:70) > 12:55:43,885 ERROR [stderr] (MSC service thread 1-3) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) > 12:55:43,885 ERROR [stderr] (MSC service thread 1-3) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) > 12:55:43,885 ERROR [stderr] (MSC service thread 1-3) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > 12:55:43,885 ERROR [stderr] (MSC service thread 1-3) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > 12:55:43,885 ERROR [stderr] (MSC service thread 1-3) at java.lang.Thread.run(Thread.java:662) > {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 Jan 18 07:44:18 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 18 Jan 2012 07:44:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11894) PushHandlerFilter initialization fails when PushServlet registered manually In-Reply-To: <487983712.7487.1326890418351.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <2093682193.7508.1326890658499.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved RF-11894. ----------------------------- Resolution: Done > PushHandlerFilter initialization fails when PushServlet registered manually > --------------------------------------------------------------------------- > > Key: RF-11894 > URL: https://issues.jboss.org/browse/RF-11894 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 4.1.0.Final > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 4.2.0.CR1 > > > When {{PushContext}} is not touched before the {{PushHandlerImpl}} is initialized, {{SessionManager}} is not stored in the {{ServletContext}} attributes and initialization fails. > {{NullPointerException}} is thrown in this case: > {code} > 12:55:43,883 ERROR [stderr] (MSC service thread 1-3) java.lang.NullPointerException > 12:55:43,883 ERROR [stderr] (MSC service thread 1-3) at org.richfaces.webapp.PushHandlerFilter.init(PushHandlerFilter.java:64) > 12:55:43,883 ERROR [stderr] (MSC service thread 1-3) at org.atmosphere.util.AtmosphereFilterChain.init(AtmosphereFilterChain.java:105) > 12:55:43,884 ERROR [stderr] (MSC service thread 1-3) at org.atmosphere.handler.ReflectorServletProcessor$FilterChainServletWrapper.init(ReflectorServletProcessor.java:273) > 12:55:43,884 ERROR [stderr] (MSC service thread 1-3) at org.atmosphere.handler.ReflectorServletProcessor.init(ReflectorServletProcessor.java:164) > 12:55:43,884 ERROR [stderr] (MSC service thread 1-3) at org.atmosphere.cpr.AtmosphereServlet.initAtmosphereHandler(AtmosphereServlet.java:813) > 12:55:43,884 ERROR [stderr] (MSC service thread 1-3) at org.atmosphere.cpr.AtmosphereServlet.init(AtmosphereServlet.java:566) > 12:55:43,884 ERROR [stderr] (MSC service thread 1-3) at org.richfaces.webapp.PushServlet.init(PushServlet.java:98) > 12:55:43,884 ERROR [stderr] (MSC service thread 1-3) at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1202) > 12:55:43,884 ERROR [stderr] (MSC service thread 1-3) at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1102) > 12:55:43,884 ERROR [stderr] (MSC service thread 1-3) at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3631) > 12:55:43,885 ERROR [stderr] (MSC service thread 1-3) at org.apache.catalina.core.StandardContext.start(StandardContext.java:3844) > 12:55:43,885 ERROR [stderr] (MSC service thread 1-3) at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:70) > 12:55:43,885 ERROR [stderr] (MSC service thread 1-3) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) > 12:55:43,885 ERROR [stderr] (MSC service thread 1-3) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) > 12:55:43,885 ERROR [stderr] (MSC service thread 1-3) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > 12:55:43,885 ERROR [stderr] (MSC service thread 1-3) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > 12:55:43,885 ERROR [stderr] (MSC service thread 1-3) at java.lang.Thread.run(Thread.java:662) > {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 Jan 18 07:44:19 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 18 Jan 2012 07:44:19 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11483) Elegant way for Push topic creating In-Reply-To: <11494155.16954.1318245975997.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <398946342.7509.1326890659525.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated RF-11483: ---------------------------- Comment: was deleted (was: Scheduled to {{4.2.0.CR1}} and increased priority to {{critical}}.) > Elegant way for Push topic creating > ----------------------------------- > > Key: RF-11483 > URL: https://issues.jboss.org/browse/RF-11483 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-push/poll, core > Affects Versions: 4.1.0.Milestone1 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Priority: Critical > Fix For: 4.3-Tracking > > > Currently, topics have to be initialized with similar class: > https://github.com/richfaces/showcase/blob/4.1.0.20110910-M2/src/main/java/org/richfaces/demo/push/TopicsInitializer.java > I suggest to create topic on demand (lazily), when it is accessed first. > It needs following changes: > * {{PushRendererBase}} - will create Topic for @address attribute > * {{JMSTopicsContextImpl}} - will create topic when JMS message received > * {{PushObserverMethod}} - will create topic when @Push event for given topic observed > * ... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 18 07:44:19 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 18 Jan 2012 07:44:19 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11483) Elegant way for Push topic creating In-Reply-To: <11494155.16954.1318245975997.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1108483050.7512.1326890659714.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated RF-11483: ---------------------------- Comment: was deleted (was: This issue is much more critical, because the {{PushContext}} is not initialized properly in time when needs to be used in order to initialize {{PushServlet}} properly. {{PushContext}} is initialized in Showcase when {{TopicsContext#lookup()}} is called, which is called by {{TopicsInitializer}} at JSF application startup. So following {{NullPointerException}} is thrown because {{PushContextImpl#init(...)}} wasn't called yet. {code} 12:55:43,883 ERROR [stderr] (MSC service thread 1-3) java.lang.NullPointerException 12:55:43,883 ERROR [stderr] (MSC service thread 1-3) at org.richfaces.webapp.PushHandlerFilter.init(PushHandlerFilter.java:64) 12:55:43,883 ERROR [stderr] (MSC service thread 1-3) at org.atmosphere.util.AtmosphereFilterChain.init(AtmosphereFilterChain.java:105) 12:55:43,884 ERROR [stderr] (MSC service thread 1-3) at org.atmosphere.handler.ReflectorServletProcessor$FilterChainServletWrapper.init(ReflectorServletProcessor.java:273) 12:55:43,884 ERROR [stderr] (MSC service thread 1-3) at org.atmosphere.handler.ReflectorServletProcessor.init(ReflectorServletProcessor.java:164) 12:55:43,884 ERROR [stderr] (MSC service thread 1-3) at org.atmosphere.cpr.AtmosphereServlet.initAtmosphereHandler(AtmosphereServlet.java:813) 12:55:43,884 ERROR [stderr] (MSC service thread 1-3) at org.atmosphere.cpr.AtmosphereServlet.init(AtmosphereServlet.java:566) 12:55:43,884 ERROR [stderr] (MSC service thread 1-3) at org.richfaces.webapp.PushServlet.init(PushServlet.java:98) 12:55:43,884 ERROR [stderr] (MSC service thread 1-3) at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1202) 12:55:43,884 ERROR [stderr] (MSC service thread 1-3) at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1102) 12:55:43,884 ERROR [stderr] (MSC service thread 1-3) at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3631) 12:55:43,885 ERROR [stderr] (MSC service thread 1-3) at org.apache.catalina.core.StandardContext.start(StandardContext.java:3844) 12:55:43,885 ERROR [stderr] (MSC service thread 1-3) at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:70) 12:55:43,885 ERROR [stderr] (MSC service thread 1-3) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) 12:55:43,885 ERROR [stderr] (MSC service thread 1-3) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) 12:55:43,885 ERROR [stderr] (MSC service thread 1-3) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) 12:55:43,885 ERROR [stderr] (MSC service thread 1-3) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) 12:55:43,885 ERROR [stderr] (MSC service thread 1-3) at java.lang.Thread.run(Thread.java:662) {code} Exception above is hidden behind following meaningless exception: {code} 12:52:47,369 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/new_project]] (MSC service thread 1-3) Servlet /new_project threw load() exception: javax.servlet.ServletException at org.atmosphere.cpr.AtmosphereServlet.init(AtmosphereServlet.java:577) [atmosphere-runtime-0.8.0-RC1.jar:] at org.richfaces.webapp.PushServlet.init(PushServlet.java:98) [richfaces-core-impl-4.1.0.Final.jar:] at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1202) [jbossweb-7.0.1.Final.jar:7.0.2.Final] at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1102) [jbossweb-7.0.1.Final.jar:7.0.2.Final] at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3631) [jbossweb-7.0.1.Final.jar:7.0.2.Final] at org.apache.catalina.core.StandardContext.start(StandardContext.java:3844) [jbossweb-7.0.1.Final.jar:7.0.2.Final] at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:70) [jboss-as-web-7.0.2.Final.jar:7.0.2.Final] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_26] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_26] at java.lang.Thread.run(Thread.java:662) [:1.6.0_26] {code} ) > Elegant way for Push topic creating > ----------------------------------- > > Key: RF-11483 > URL: https://issues.jboss.org/browse/RF-11483 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-push/poll, core > Affects Versions: 4.1.0.Milestone1 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Priority: Critical > Fix For: 4.3-Tracking > > > Currently, topics have to be initialized with similar class: > https://github.com/richfaces/showcase/blob/4.1.0.20110910-M2/src/main/java/org/richfaces/demo/push/TopicsInitializer.java > I suggest to create topic on demand (lazily), when it is accessed first. > It needs following changes: > * {{PushRendererBase}} - will create Topic for @address attribute > * {{JMSTopicsContextImpl}} - will create topic when JMS message received > * {{PushObserverMethod}} - will create topic when @Push event for given topic observed > * ... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 18 07:44:19 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 18 Jan 2012 07:44:19 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11483) Elegant way for Push topic creating In-Reply-To: <11494155.16954.1318245975997.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <780642877.7516.1326890659939.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated RF-11483: ---------------------------- Assignee: (was: Luk?? Fry?) Fix Version/s: 4.3-Tracking (was: 4.2.0.CR1) Priority: Major (was: Critical) Forum Reference: http://community.jboss.org/message/630871#630871 (was: http://community.jboss.org/message/630871#630871) > Elegant way for Push topic creating > ----------------------------------- > > Key: RF-11483 > URL: https://issues.jboss.org/browse/RF-11483 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-push/poll, core > Affects Versions: 4.1.0.Milestone1 > Reporter: Luk?? Fry? > Fix For: 4.3-Tracking > > > Currently, topics have to be initialized with similar class: > https://github.com/richfaces/showcase/blob/4.1.0.20110910-M2/src/main/java/org/richfaces/demo/push/TopicsInitializer.java > I suggest to create topic on demand (lazily), when it is accessed first. > It needs following changes: > * {{PushRendererBase}} - will create Topic for @address attribute > * {{JMSTopicsContextImpl}} - will create topic when JMS message received > * {{PushObserverMethod}} - will create topic when @Push event for given topic observed > * ... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 18 07:46:20 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 18 Jan 2012 07:46:20 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11894) PushHandlerFilter initialization fails when PushServlet registered manually In-Reply-To: <487983712.7487.1326890418351.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1428016923.7535.1326890780742.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated RF-11894: ---------------------------- Description: When {{PushContext}} is not touched before the {{PushHandlerImpl}} is initialized, {{SessionManager}} is not stored in the {{ServletContext}} attributes and initialization fails. {{NullPointerException}} is thrown in this case: {code} 12:55:43,883 ERROR [stderr] (MSC service thread 1-3) java.lang.NullPointerException 12:55:43,883 ERROR [stderr] (MSC service thread 1-3) at org.richfaces.webapp.PushHandlerFilter.init(PushHandlerFilter.java:64) 12:55:43,883 ERROR [stderr] (MSC service thread 1-3) at org.atmosphere.util.AtmosphereFilterChain.init(AtmosphereFilterChain.java:105) 12:55:43,884 ERROR [stderr] (MSC service thread 1-3) at org.atmosphere.handler.ReflectorServletProcessor$FilterChainServletWrapper.init(ReflectorServletProcessor.java:273) 12:55:43,884 ERROR [stderr] (MSC service thread 1-3) at org.atmosphere.handler.ReflectorServletProcessor.init(ReflectorServletProcessor.java:164) 12:55:43,884 ERROR [stderr] (MSC service thread 1-3) at org.atmosphere.cpr.AtmosphereServlet.initAtmosphereHandler(AtmosphereServlet.java:813) 12:55:43,884 ERROR [stderr] (MSC service thread 1-3) at org.atmosphere.cpr.AtmosphereServlet.init(AtmosphereServlet.java:566) 12:55:43,884 ERROR [stderr] (MSC service thread 1-3) at org.richfaces.webapp.PushServlet.init(PushServlet.java:98) 12:55:43,884 ERROR [stderr] (MSC service thread 1-3) at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1202) 12:55:43,884 ERROR [stderr] (MSC service thread 1-3) at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1102) 12:55:43,884 ERROR [stderr] (MSC service thread 1-3) at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3631) 12:55:43,885 ERROR [stderr] (MSC service thread 1-3) at org.apache.catalina.core.StandardContext.start(StandardContext.java:3844) 12:55:43,885 ERROR [stderr] (MSC service thread 1-3) at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:70) 12:55:43,885 ERROR [stderr] (MSC service thread 1-3) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) 12:55:43,885 ERROR [stderr] (MSC service thread 1-3) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) 12:55:43,885 ERROR [stderr] (MSC service thread 1-3) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) 12:55:43,885 ERROR [stderr] (MSC service thread 1-3) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) 12:55:43,885 ERROR [stderr] (MSC service thread 1-3) at java.lang.Thread.run(Thread.java:662) {code} Exception above can be hidden behind {{ServletException}} bellow: {code} 12:52:47,369 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/new_project]] (MSC service thread 1-3) Servlet /new_project threw load() exception: javax.servlet.ServletException at org.atmosphere.cpr.AtmosphereServlet.init(AtmosphereServlet.java:577) [atmosphere-runtime-0.8.0-RC1.jar:] at org.richfaces.webapp.PushServlet.init(PushServlet.java:98) [richfaces-core-impl-4.1.0.Final.jar:] at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1202) [jbossweb-7.0.1.Final.jar:7.0.2.Final] at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1102) [jbossweb-7.0.1.Final.jar:7.0.2.Final] at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3631) [jbossweb-7.0.1.Final.jar:7.0.2.Final] at org.apache.catalina.core.StandardContext.start(StandardContext.java:3844) [jbossweb-7.0.1.Final.jar:7.0.2.Final] at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:70) [jboss-as-web-7.0.2.Final.jar:7.0.2.Final] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_26] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_26] at java.lang.Thread.run(Thread.java:662) [:1.6.0_26] {code} was: When {{PushContext}} is not touched before the {{PushHandlerImpl}} is initialized, {{SessionManager}} is not stored in the {{ServletContext}} attributes and initialization fails. {{NullPointerException}} is thrown in this case: {code} 12:55:43,883 ERROR [stderr] (MSC service thread 1-3) java.lang.NullPointerException 12:55:43,883 ERROR [stderr] (MSC service thread 1-3) at org.richfaces.webapp.PushHandlerFilter.init(PushHandlerFilter.java:64) 12:55:43,883 ERROR [stderr] (MSC service thread 1-3) at org.atmosphere.util.AtmosphereFilterChain.init(AtmosphereFilterChain.java:105) 12:55:43,884 ERROR [stderr] (MSC service thread 1-3) at org.atmosphere.handler.ReflectorServletProcessor$FilterChainServletWrapper.init(ReflectorServletProcessor.java:273) 12:55:43,884 ERROR [stderr] (MSC service thread 1-3) at org.atmosphere.handler.ReflectorServletProcessor.init(ReflectorServletProcessor.java:164) 12:55:43,884 ERROR [stderr] (MSC service thread 1-3) at org.atmosphere.cpr.AtmosphereServlet.initAtmosphereHandler(AtmosphereServlet.java:813) 12:55:43,884 ERROR [stderr] (MSC service thread 1-3) at org.atmosphere.cpr.AtmosphereServlet.init(AtmosphereServlet.java:566) 12:55:43,884 ERROR [stderr] (MSC service thread 1-3) at org.richfaces.webapp.PushServlet.init(PushServlet.java:98) 12:55:43,884 ERROR [stderr] (MSC service thread 1-3) at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1202) 12:55:43,884 ERROR [stderr] (MSC service thread 1-3) at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1102) 12:55:43,884 ERROR [stderr] (MSC service thread 1-3) at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3631) 12:55:43,885 ERROR [stderr] (MSC service thread 1-3) at org.apache.catalina.core.StandardContext.start(StandardContext.java:3844) 12:55:43,885 ERROR [stderr] (MSC service thread 1-3) at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:70) 12:55:43,885 ERROR [stderr] (MSC service thread 1-3) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) 12:55:43,885 ERROR [stderr] (MSC service thread 1-3) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) 12:55:43,885 ERROR [stderr] (MSC service thread 1-3) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) 12:55:43,885 ERROR [stderr] (MSC service thread 1-3) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) 12:55:43,885 ERROR [stderr] (MSC service thread 1-3) at java.lang.Thread.run(Thread.java:662) {code} > PushHandlerFilter initialization fails when PushServlet registered manually > --------------------------------------------------------------------------- > > Key: RF-11894 > URL: https://issues.jboss.org/browse/RF-11894 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 4.1.0.Final > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 4.2.0.CR1 > > > When {{PushContext}} is not touched before the {{PushHandlerImpl}} is initialized, {{SessionManager}} is not stored in the {{ServletContext}} attributes and initialization fails. > {{NullPointerException}} is thrown in this case: > {code} > 12:55:43,883 ERROR [stderr] (MSC service thread 1-3) java.lang.NullPointerException > 12:55:43,883 ERROR [stderr] (MSC service thread 1-3) at org.richfaces.webapp.PushHandlerFilter.init(PushHandlerFilter.java:64) > 12:55:43,883 ERROR [stderr] (MSC service thread 1-3) at org.atmosphere.util.AtmosphereFilterChain.init(AtmosphereFilterChain.java:105) > 12:55:43,884 ERROR [stderr] (MSC service thread 1-3) at org.atmosphere.handler.ReflectorServletProcessor$FilterChainServletWrapper.init(ReflectorServletProcessor.java:273) > 12:55:43,884 ERROR [stderr] (MSC service thread 1-3) at org.atmosphere.handler.ReflectorServletProcessor.init(ReflectorServletProcessor.java:164) > 12:55:43,884 ERROR [stderr] (MSC service thread 1-3) at org.atmosphere.cpr.AtmosphereServlet.initAtmosphereHandler(AtmosphereServlet.java:813) > 12:55:43,884 ERROR [stderr] (MSC service thread 1-3) at org.atmosphere.cpr.AtmosphereServlet.init(AtmosphereServlet.java:566) > 12:55:43,884 ERROR [stderr] (MSC service thread 1-3) at org.richfaces.webapp.PushServlet.init(PushServlet.java:98) > 12:55:43,884 ERROR [stderr] (MSC service thread 1-3) at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1202) > 12:55:43,884 ERROR [stderr] (MSC service thread 1-3) at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1102) > 12:55:43,884 ERROR [stderr] (MSC service thread 1-3) at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3631) > 12:55:43,885 ERROR [stderr] (MSC service thread 1-3) at org.apache.catalina.core.StandardContext.start(StandardContext.java:3844) > 12:55:43,885 ERROR [stderr] (MSC service thread 1-3) at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:70) > 12:55:43,885 ERROR [stderr] (MSC service thread 1-3) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) > 12:55:43,885 ERROR [stderr] (MSC service thread 1-3) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) > 12:55:43,885 ERROR [stderr] (MSC service thread 1-3) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > 12:55:43,885 ERROR [stderr] (MSC service thread 1-3) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > 12:55:43,885 ERROR [stderr] (MSC service thread 1-3) at java.lang.Thread.run(Thread.java:662) > {code} > Exception above can be hidden behind {{ServletException}} bellow: > {code} > 12:52:47,369 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/new_project]] (MSC service thread 1-3) Servlet /new_project threw load() exception: javax.servlet.ServletException > at org.atmosphere.cpr.AtmosphereServlet.init(AtmosphereServlet.java:577) [atmosphere-runtime-0.8.0-RC1.jar:] > at org.richfaces.webapp.PushServlet.init(PushServlet.java:98) [richfaces-core-impl-4.1.0.Final.jar:] > at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1202) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1102) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3631) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.StandardContext.start(StandardContext.java:3844) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:70) [jboss-as-web-7.0.2.Final.jar:7.0.2.Final] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_26] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_26] > at java.lang.Thread.run(Thread.java:662) [:1.6.0_26] > {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 Jan 18 08:02:18 2012 From: jira-events at lists.jboss.org (Burr Sutter (JIRA)) Date: Wed, 18 Jan 2012 08:02:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11895) Richfaces showcase import into JBoss Tools/JBDS Message-ID: <1507274563.7562.1326891738548.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Burr Sutter created RF-11895: -------------------------------- Summary: Richfaces showcase import into JBoss Tools/JBDS Key: RF-11895 URL: https://issues.jboss.org/browse/RF-11895 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: examples Affects Versions: 4.1.0.Final Reporter: Burr Sutter Importing RichFaces Showcase into JBDS5 M5 has the following error: [ERROR] The project org.richfaces.examples:richfaces-showcase:4.1.0.Final (/Users/burr/Downloads/richfaces-4.1.0.Final/examples/richfaces-showcase/pom.xml) has 1 error [ERROR] Non-resolvable parent POM: Could not find artifact org.richfaces:richfaces-root-parent:pom:4.1.0.Final in central (http://repo1.maven.org/maven2) and 'parent.relativePath' points at wrong local POM @ line 8, column 13 -> [Help 2] [ERROR] Same error on the command line. Also in the readme.txt, it refers to "Jboss" - need to upper case that "b" -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 18 08:25:20 2012 From: jira-events at lists.jboss.org (Jay Balunas (JIRA)) Date: Wed, 18 Jan 2012 08:25:20 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11773) Mobile Showcase and rich:orderingList/rich:pickList - control buttons can't be enabled In-Reply-To: <677171215.62017.1322758002710.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <167134730.7624.1326893120060.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12660145#comment-12660145 ] Jay Balunas commented on RF-11773: ---------------------------------- This should probably function for 2.3.3+ don't you think? The buttons not working would be a big issue. QE can you provide any additional info, and try on Android emulator 2.3.6? > Mobile Showcase and rich:orderingList/rich:pickList - control buttons can't be enabled > -------------------------------------------------------------------------------------- > > Key: RF-11773 > URL: https://issues.jboss.org/browse/RF-11773 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: mobile, showcase > Affects Versions: 4.1.0.CR2 > Environment: JBoss AS 7.1.0.Beta1 > mobile devices: Nexus - Android 2.3.6, iPad > Reporter: Jan Papousek > Assignee: Wesley Hales > Fix For: 4.2.0.CR1 > > > It works correctly on iPhone, Motorola Xoom(Andorid), Android emulator (2.3.3). > It does not work for Nexus mobile device and iPad. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 18 08:50:19 2012 From: jira-events at lists.jboss.org (Rene O (JIRA)) Date: Wed, 18 Jan 2012 08:50:19 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11896) [rich:autocomplete] add attribute maxlength Message-ID: <744278392.7735.1326894619247.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Rene O created RF-11896: --------------------------- Summary: [rich:autocomplete] add attribute maxlength Key: RF-11896 URL: https://issues.jboss.org/browse/RF-11896 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 maxlength to limit the users input. It should be the same as attribute maxlength within the h:input 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 Jan 18 10:19:18 2012 From: jira-events at lists.jboss.org (Wesley Hales (JIRA)) Date: Wed, 18 Jan 2012 10:19:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11773) Mobile Showcase and rich:orderingList/rich:pickList - control buttons can't be enabled In-Reply-To: <677171215.62017.1322758002710.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1383185395.8204.1326899958774.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12660207#comment-12660207 ] Wesley Hales commented on RF-11773: ----------------------------------- Jay - This has been an ongoing issue in multiple environments. Please see: https://issues.jboss.org/browse/RF-11646 If there continues to be a huge difference in Android point releases (i.e. 2.3.3 -> 2.3.6) then we should define a Grade for the browsers and versions to be supported. This doesn't make sense to me as there are not any major browser changes in an Android point release. So, is this a QA environment issue? If this component continues to give us problems we may want to remove it: https://issues.jboss.org/browse/RF-11567 This issue already calls for a re-write due to scrolling incompatibilities. > Mobile Showcase and rich:orderingList/rich:pickList - control buttons can't be enabled > -------------------------------------------------------------------------------------- > > Key: RF-11773 > URL: https://issues.jboss.org/browse/RF-11773 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: mobile, showcase > Affects Versions: 4.1.0.CR2 > Environment: JBoss AS 7.1.0.Beta1 > mobile devices: Nexus - Android 2.3.6, iPad > Reporter: Jan Papousek > Assignee: Wesley Hales > Fix For: 4.2.0.CR1 > > > It works correctly on iPhone, Motorola Xoom(Andorid), Android emulator (2.3.3). > It does not work for Nexus mobile device and iPad. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 18 10:28:18 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 18 Jan 2012 10:28:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11893) Increment version number to 4.2.0-SNAPSHOT In-Reply-To: <1843504770.7002.1326878059466.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <504918927.8235.1326900498572.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved RF-11893. ----------------------------- Resolution: Done > Increment version number to 4.2.0-SNAPSHOT > ------------------------------------------ > > Key: RF-11893 > URL: https://issues.jboss.org/browse/RF-11893 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: build/distribution, qe > Affects Versions: 4.2.0.CR1 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 4.2.0.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 Jan 18 10:28:18 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 18 Jan 2012 10:28:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11893) Increment version number to 4.2.0-SNAPSHOT In-Reply-To: <1843504770.7002.1326878059466.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1876008300.8239.1326900498992.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? reopened RF-11893: ----------------------------- Assignee: Pavol Pitonak (was: Luk?? Fry?) Pavol, framework version has been incremented to 4.2.0-SNAPSHOt, could you please update also QE/CI builds? > Increment version number to 4.2.0-SNAPSHOT > ------------------------------------------ > > Key: RF-11893 > URL: https://issues.jboss.org/browse/RF-11893 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: build/distribution, qe > Affects Versions: 4.2.0.CR1 > Reporter: Luk?? Fry? > Assignee: Pavol Pitonak > Fix For: 4.2.0.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 Jan 18 13:52:18 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 18 Jan 2012 13:52:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11764) Problems with packed resources In-Reply-To: <1531552132.56496.1322674962554.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1361537875.8797.1326912738731.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12660287#comment-12660287 ] Brian Leathem commented on RF-11764: ------------------------------------ Jean ANDRE, has this issue been resolved with RF-11876? > Problems with packed resources > ------------------------------ > > Key: RF-11764 > URL: https://issues.jboss.org/browse/RF-11764 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.1.0.CR1 > Reporter: Jean ANDRE > Labels: material-sent, waiting_on_user > > *Follow up RF-11694.* > We tested the solution by updating the web.xml. We put following code : > {code} > > org.richfaces.resourceMapping.enabled > true > > > org.richfaces.resourceMapping.packedStages > All > > {code} > The workaround does not work well because it triggers many javacript erreur - User Interface seem to be frozen, hanged. > Here are the errors catch under firebug / Mozilla > {code} > jsf is not defined > [Stopper sur une erreur] }(jQuery,RichFaces,jsf));;(function(C,B,D){B.blankFunction=function(){}; > packed.js (ligne 3040) > RichFaces.ui is undefined > [Stopper sur une erreur] 		> index.jsf (ligne 77) > RichFaces.ui is undefined > [Stopper sur une erreur] RichFaces.ui.Menu(...":"MenuForm:mainToolBar"} ); > index.jsf (ligne 77) > RichFaces.ui is undefined > [Stopper sur une erreur]
> index.jsf (ligne 85) > RichFaces.ui is undefined > [Stopper sur une erreur]
> index.jsf (ligne 88) > RichFaces.ui is undefined > [Stopper sur une erreur] > index.jsf (ligne 88) > RichFaces.ui is undefined > [Stopper sur une erreur] > index.jsf (ligne 88) > {code} > more over there is many CSS errors/warning > {code} > L'utilisation de getAttributeNodeNS() est obsol?te. Utilisez getAttributeNS() ? la place. > Une fin de valeur ?tait attendue, mais ? "#E5973E " ? a ?t? trouv?. Erreur d'analyse de la valeur pour ? border ?. D?claration abandonn?e. > *.rf-insl-tt{position:absolute;display..."#E5973E ";background-color:#FAE6B0;} > packed.css (ligne 108) > Erreur d'analyse de la valeur pour ? filter ?. D?claration abandonn?e. > *.rf-fu-inp{filter:alpha(opacity=0);fo...y:0;position:absolute;right:0;top:0;} > packed.css (ligne 158) > Propri?t? ? text-color ? inconnue. D?claration abandonn?e. > *.rf-fu-itm-st{display:none;margin-top...000;background-color:#fff;padding:0;} > packed.css (ligne 164) > Erreur d'analyse de la valeur pour ? filter ?. D?claration abandonn?e. > *.rf-tab-cnt{border:1px solid #C4C0B9;...opacity:.1;filter:alpha(opacity=10);} > packed.css (ligne 184) > Erreur d'analyse de la valeur pour ? filter ?. D?claration abandonn?e. > *.rf-pp-shade{position:fixed;width:100...opacity:.5;filter:alpha(opacity=50);} > packed.css (ligne 185) > Erreur d'analyse de la valeur pour ? filter ?. D?claration abandonn?e. > *.rf-pp-shdw{background-color:#000;opa...6px;left:6px;bottom:-6px;z-index:-1;} > packed.css (ligne 186) > Propri?t? ? repeat-x ? inconnue. D?claration abandonn?e. > *.rf-pp-hdr{background:url(../org.rich...g-left:10px;cursor:move;padding:2px;} > packed.css (ligne 188) > Erreur d'analyse de la valeur pour ? font-size ?. D?claration abandonn?e. > *.rf-cal-sp-inp{border:0;padding:0 0 0...Arial,Verdana,sans-serif;width:18px;} > packed.css (ligne 354) > Erreur d'analyse de la valeur pour ? filter ?. D?claration abandonn?e. > *.rf-cal-edtr-shdw{background:#FFF;opacity:.5;filter:alpha(opacity=50);} > packed.css (ligne 369) > Erreur d'analyse de la valeur pour ? filter ?. D?claration abandonn?e. > *.rf-cal-edtr-layout-shdw{background-c...opacity:.3;filter:alpha(opacity=30);} > {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 Jan 18 15:32:18 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 18 Jan 2012 15:32:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11897) menuItems do not inherit the mode of the parent contextMenu Message-ID: <647787621.8905.1326918738187.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Brian Leathem created RF-11897: ---------------------------------- Summary: menuItems do not inherit the mode of the parent contextMenu Key: RF-11897 URL: https://issues.jboss.org/browse/RF-11897 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-menu Reporter: Brian Leathem Setting the mode of the contextMenu to "client" does not propagate to the child menuItems. The mode of the menuItem must be set explicitly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 18 15:36:18 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 18 Jan 2012 15:36:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11898) Attaching a contextMenu to a h:graphicImage results in a contextMenu that does not display Message-ID: <1893634399.8909.1326918978241.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Brian Leathem created RF-11898: ---------------------------------- Summary: Attaching a contextMenu to a h:graphicImage results in a contextMenu that does not display Key: RF-11898 URL: https://issues.jboss.org/browse/RF-11898 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Brian Leathem Attaching a contextMenu to a h:graphicImage results in a contextMenu that does not display. Wrapping the image with a panelGroup, and attaching the contextMenu to that panelGroup instead does not cause a 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 Jan 18 15:36:18 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 18 Jan 2012 15:36:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11898) Attaching a contextMenu to a h:graphicImage results in a contextMenu that does not display In-Reply-To: <1893634399.8909.1326918978241.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1590922519.8910.1326918978674.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-11898: ------------------------------- Component/s: component-menu > Attaching a contextMenu to a h:graphicImage results in a contextMenu that does not display > ------------------------------------------------------------------------------------------ > > Key: RF-11898 > URL: https://issues.jboss.org/browse/RF-11898 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-menu > Reporter: Brian Leathem > > Attaching a contextMenu to a h:graphicImage results in a contextMenu that does not display. Wrapping the image with a panelGroup, and attaching the contextMenu to that panelGroup instead does not cause a 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 Jan 18 15:46:18 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 18 Jan 2012 15:46:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11899) the attachId of the contextMenu requires the fully qualified path Message-ID: <130287168.8929.1326919578474.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Brian Leathem created RF-11899: ---------------------------------- Summary: the attachId of the contextMenu requires the fully qualified path Key: RF-11899 URL: https://issues.jboss.org/browse/RF-11899 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-menu Reporter: Brian Leathem Providing an attachId of "pic" for instance is insufficient, one must provide "form:pic". -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 18 16:24:18 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 18 Jan 2012 16:24:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11900) contextMenu has to be defined after the extendedDatatable, or it cannot attach Message-ID: <1920914566.9002.1326921858188.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Brian Leathem created RF-11900: ---------------------------------- Summary: contextMenu has to be defined after the extendedDatatable, or it cannot attach Key: RF-11900 URL: https://issues.jboss.org/browse/RF-11900 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-menu Reporter: 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 Jan 18 18:44:19 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 18 Jan 2012 18:44:19 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11901) Review the "new" label on showcase compnents Message-ID: <1378292109.9479.1326930259921.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Brian Leathem created RF-11901: ---------------------------------- Summary: Review the "new" label on showcase compnents Key: RF-11901 URL: https://issues.jboss.org/browse/RF-11901 Project: RichFaces Issue Type: Task Security Level: Public (Everyone can see) Components: showcase Reporter: Brian Leathem Assignee: Brian Leathem Priority: Trivial Fix For: 4.2.0.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 Jan 18 19:02:21 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 18 Jan 2012 19:02:21 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-10197) Right click menu - rich:contextMenu - should be ported from RF 3 In-Reply-To: <1371525318.9293.1294869109676.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <2004935848.9588.1326931341124.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-10197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-10197. -------------------------------- Labels: (was: sandbox) Assignee: Brian Leathem (was: J?n Jamrich) Resolution: Done > Right click menu - rich:contextMenu - should be ported from RF 3 > ---------------------------------------------------------------- > > Key: RF-10197 > URL: https://issues.jboss.org/browse/RF-10197 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-menu > Affects Versions: 4.0.0.Milestone5 > Environment: Windows > Reporter: Devinder Singh > Assignee: Brian Leathem > Priority: Blocker > Fix For: 4.2.0.CR1 > > > rich:contextMenu is available in 3.x release but not yet supported in 4.0. > As it enables right click menus on JSF components, it's a very useful feature that can be used in wide variety of applications -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 19 03:41:19 2012 From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA)) Date: Thu, 19 Jan 2012 03:41:19 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11893) Increment version number to 4.2.0-SNAPSHOT In-Reply-To: <1843504770.7002.1326878059466.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <379771525.10024.1326962479708.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavol Pitonak reassigned RF-11893: ---------------------------------- Assignee: Juraj Huska (was: Pavol Pitonak) > Increment version number to 4.2.0-SNAPSHOT > ------------------------------------------ > > Key: RF-11893 > URL: https://issues.jboss.org/browse/RF-11893 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: build/distribution, qe > Affects Versions: 4.2.0.CR1 > Reporter: Luk?? Fry? > Assignee: Juraj Huska > Fix For: 4.2.0.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 Thu Jan 19 05:32:18 2012 From: jira-events at lists.jboss.org (Rene O (JIRA)) Date: Thu, 19 Jan 2012 05:32:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11902) [rich:autocomplete] add attribute queueId Message-ID: <1022848615.10266.1326969138391.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Rene O created RF-11902: --------------------------- Summary: [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 Jan 19 07:25:18 2012 From: jira-events at lists.jboss.org (Juraj Huska (JIRA)) Date: Thu, 19 Jan 2012 07:25:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11893) Increment version number to 4.2.0-SNAPSHOT In-Reply-To: <1843504770.7002.1326878059466.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <546501655.10523.1326975918383.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj Huska resolved RF-11893. ------------------------------ Resolution: Done I have changed richfaces version to 4.2.0-SNAPSHOT on all modules in the repository qa And also changed that the *only* places where the *version is defined* are in the *parent pom version*, and also in the *definition of parent* in the submodules. > Increment version number to 4.2.0-SNAPSHOT > ------------------------------------------ > > Key: RF-11893 > URL: https://issues.jboss.org/browse/RF-11893 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: build/distribution, qe > Affects Versions: 4.2.0.CR1 > Reporter: Luk?? Fry? > Assignee: Juraj Huska > Fix For: 4.2.0.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 Thu Jan 19 07:51:18 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 19 Jan 2012 07:51:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11892) Push: turn off JMS integration by default In-Reply-To: <985205215.6984.1326877458621.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1251499046.10554.1326977478269.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated RF-11892: ---------------------------- Summary: Push: turn off JMS integration by default (was: Push: turn on JMS integration by default) > Push: turn off JMS integration by default > ----------------------------------------- > > Key: RF-11892 > URL: https://issues.jboss.org/browse/RF-11892 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: component-push/poll > Affects Versions: 4.0.0.Final, 4.1.0.Final > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 4.2.0.CR1 > > > On team meeting [1], we have discussed necessity to simplify configuration of Push in order to simplify starting with push for new users. > I suggest to replace current configuration {{org.richfaces.push.jms.disable}} > with {{org.richfaces.push.jms.enable}}, leaving previous one with no effect > or providing warning. > [1] https://community.jboss.org/wiki/RichFacesTeamMeetingAgenda2012-01-17 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 19 08:46:20 2012 From: jira-events at lists.jboss.org (Jan Papousek (JIRA)) Date: Thu, 19 Jan 2012 08:46:20 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11773) Mobile Showcase and rich:orderingList/rich:pickList - control buttons can't be enabled In-Reply-To: <677171215.62017.1322758002710.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1630178280.10733.1326980780347.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Papousek reopened RF-11773: ------------------------------- > Mobile Showcase and rich:orderingList/rich:pickList - control buttons can't be enabled > -------------------------------------------------------------------------------------- > > Key: RF-11773 > URL: https://issues.jboss.org/browse/RF-11773 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: mobile, showcase > Affects Versions: 4.1.0.CR2 > Environment: JBoss AS 7.1.0.Beta1 > mobile devices: Nexus - Android 2.3.6, iPad > Reporter: Jan Papousek > Assignee: Wesley Hales > Fix For: 4.2.0.CR1 > > > It works correctly on iPhone, Motorola Xoom(Andorid), Android emulator (2.3.3). > It does not work for Nexus mobile device and iPad. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 19 08:46:20 2012 From: jira-events at lists.jboss.org (Jan Papousek (JIRA)) Date: Thu, 19 Jan 2012 08:46:20 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11773) Mobile Showcase and rich:orderingList/rich:pickList - control buttons can't be enabled In-Reply-To: <677171215.62017.1322758002710.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <629632775.10738.1326980780683.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Papousek resolved RF-11773. ------------------------------- Resolution: Cannot Reproduce Bug > Mobile Showcase and rich:orderingList/rich:pickList - control buttons can't be enabled > -------------------------------------------------------------------------------------- > > Key: RF-11773 > URL: https://issues.jboss.org/browse/RF-11773 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: mobile, showcase > Affects Versions: 4.1.0.CR2 > Environment: JBoss AS 7.1.0.Beta1 > mobile devices: Nexus - Android 2.3.6, iPad > Reporter: Jan Papousek > Assignee: Wesley Hales > Fix For: 4.2.0.CR1 > > > It works correctly on iPhone, Motorola Xoom(Andorid), Android emulator (2.3.3). > It does not work for Nexus mobile device and iPad. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 19 08:46:20 2012 From: jira-events at lists.jboss.org (Jan Papousek (JIRA)) Date: Thu, 19 Jan 2012 08:46:20 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11773) Mobile Showcase and rich:orderingList/rich:pickList - control buttons can't be enabled In-Reply-To: <677171215.62017.1322758002710.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1406776420.10742.1326980780808.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Papousek closed RF-11773. ----------------------------- I've tried to reproduce the bug and it's working on 4.1.0.Final. Jay: Android SDK doesn't provide emulator in version 2.3.6 Wesley: I agree we should define supported versions. Tests are currently executed on 2.2. There can be executed on 3.1 too, but it's slower. > Mobile Showcase and rich:orderingList/rich:pickList - control buttons can't be enabled > -------------------------------------------------------------------------------------- > > Key: RF-11773 > URL: https://issues.jboss.org/browse/RF-11773 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: mobile, showcase > Affects Versions: 4.1.0.CR2 > Environment: JBoss AS 7.1.0.Beta1 > mobile devices: Nexus - Android 2.3.6, iPad > Reporter: Jan Papousek > Assignee: Wesley Hales > Fix For: 4.2.0.CR1 > > > It works correctly on iPhone, Motorola Xoom(Andorid), Android emulator (2.3.3). > It does not work for Nexus mobile device and iPad. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 19 09:11:18 2012 From: jira-events at lists.jboss.org (Juraj Huska (JIRA)) Date: Thu, 19 Jan 2012 09:11:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11903) showcase - a4j:push - error on the server side, Unable to resume the suspended connection with latchId Message-ID: <1647203784.10826.1326982278758.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Juraj Huska created RF-11903: -------------------------------- Summary: showcase - a4j:push - error on the server side, Unable to resume the suspended connection with latchId Key: RF-11903 URL: https://issues.jboss.org/browse/RF-11903 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-push/poll, showcase, third-party Affects Versions: 4.1.0.Final Environment: container: JBoss AS 6.0.0.Final browsers: all application: showcase 4.2.0-SNAPSHOT Reporter: Juraj Huska *All* demos for 14j:push are causing *error* on the server side when it is pushing something to them: {code} 15:03:42,962 ERROR [org.atmosphere.container.BlockingIOCometSupport] Unable to resume the suspended connection with latchId: 11597405 {code} Note that the latchId is for each push different. *The functionality* however remains *ok*, at least for Topics context usage and JMS push. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 19 09:25:18 2012 From: jira-events at lists.jboss.org (Juraj Huska (JIRA)) Date: Thu, 19 Jan 2012 09:25:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11903) showcase - a4j:push - error on the server side, Unable to resume the suspended connection with latchId In-Reply-To: <1647203784.10826.1326982278758.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <776611634.10918.1326983118497.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12660513#comment-12660513 ] Juraj Huska commented on RF-11903: ---------------------------------- This excepion is thrown after some time of not using push, IMHO it is thrown after timeout set on Atmosphere: {code} 15:22:50,797 ERROR [org.atmosphere.container.BlockingIOCometSupport] Unable to resume the suspended connection with latchId: 17509802 15:22:50,798 SEVERE [org.richfaces.log.Application] null: java.lang.NullPointerException at org.atmosphere.cpr.AtmosphereResourceEventImpl.isResuming(AtmosphereResourceEventImpl.java:89) [:0.8.3] at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:599) [:0.8.3] at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:584) [:0.8.3] at org.atmosphere.cpr.AsynchronousProcessor.timedout(AsynchronousProcessor.java:380) [:0.8.3] at org.atmosphere.container.BlockingIOCometSupport.suspend(BlockingIOCometSupport.java:165) [:0.8.3] at org.atmosphere.container.BlockingIOCometSupport.service(BlockingIOCometSupport.java:95) [:0.8.3] at org.atmosphere.cpr.AtmosphereServlet.doCometSupport(AtmosphereServlet.java:1212) [:0.8.3] at org.atmosphere.cpr.AtmosphereServlet.doPost(AtmosphereServlet.java:1171) [:0.8.3] at org.atmosphere.cpr.AtmosphereServlet.doGet(AtmosphereServlet.java:1157) [:0.8.3] at javax.servlet.http.HttpServlet.service(HttpServlet.java:734) [:1.0.0.Final] at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [:1.0.0.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:324) [:6.0.0.Final] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242) [:6.0.0.Final] at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:67) [:6.0.0.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:274) [:6.0.0.Final] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242) [:6.0.0.Final] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [:6.0.0.Final] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) [:6.0.0.Final] at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:181) [:6.0.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.0.0.Final] at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:100) [:6.0.0.Final] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) [:6.0.0.Final] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [:6.0.0.Final] at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) [:6.0.0.Final] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [:6.0.0.Final] at org.jboss.web.tomcat.service.request.ActiveRequestResponseCacheValve.invoke(ActiveRequestResponseCacheValve.java:53) [:6.0.0.Final] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) [:6.0.0.Final] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [:6.0.0.Final] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:654) [:6.0.0.Final] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:951) [:6.0.0.Final] at java.lang.Thread.run(Thread.java:662) [:1.6.0_22] {code} > showcase - a4j:push - error on the server side, Unable to resume the suspended connection with latchId > ------------------------------------------------------------------------------------------------------- > > Key: RF-11903 > URL: https://issues.jboss.org/browse/RF-11903 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll, showcase, third-party > Affects Versions: 4.1.0.Final > Environment: container: JBoss AS 6.0.0.Final > browsers: all > application: showcase 4.2.0-SNAPSHOT > Reporter: Juraj Huska > > *All* demos for 14j:push are causing *error* on the server side when it is pushing something to them: > {code} > 15:03:42,962 ERROR [org.atmosphere.container.BlockingIOCometSupport] Unable to resume the suspended connection with latchId: 11597405 > {code} > Note that the latchId is for each push different. *The functionality* however remains *ok*, at least for Topics context usage and JMS push. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 19 09:33:18 2012 From: jira-events at lists.jboss.org (Juraj Huska (JIRA)) Date: Thu, 19 Jan 2012 09:33:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11903) showcase - a4j:push - error on the server side, Unable to resume the suspended connection with latchId In-Reply-To: <1647203784.10826.1326982278758.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1000327676.10931.1326983598601.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12660513#comment-12660513 ] Juraj Huska edited comment on RF-11903 at 1/19/12 9:32 AM: ----------------------------------------------------------- This excepion is thrown after some time of not using push, *before it had to be used CDI example*, IMHO it is thrown after timeout set on Atmosphere: {code} 15:22:50,797 ERROR [org.atmosphere.container.BlockingIOCometSupport] Unable to resume the suspended connection with latchId: 17509802 15:22:50,798 SEVERE [org.richfaces.log.Application] null: java.lang.NullPointerException at org.atmosphere.cpr.AtmosphereResourceEventImpl.isResuming(AtmosphereResourceEventImpl.java:89) [:0.8.3] at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:599) [:0.8.3] at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:584) [:0.8.3] at org.atmosphere.cpr.AsynchronousProcessor.timedout(AsynchronousProcessor.java:380) [:0.8.3] at org.atmosphere.container.BlockingIOCometSupport.suspend(BlockingIOCometSupport.java:165) [:0.8.3] at org.atmosphere.container.BlockingIOCometSupport.service(BlockingIOCometSupport.java:95) [:0.8.3] at org.atmosphere.cpr.AtmosphereServlet.doCometSupport(AtmosphereServlet.java:1212) [:0.8.3] at org.atmosphere.cpr.AtmosphereServlet.doPost(AtmosphereServlet.java:1171) [:0.8.3] at org.atmosphere.cpr.AtmosphereServlet.doGet(AtmosphereServlet.java:1157) [:0.8.3] at javax.servlet.http.HttpServlet.service(HttpServlet.java:734) [:1.0.0.Final] at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [:1.0.0.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:324) [:6.0.0.Final] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242) [:6.0.0.Final] at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:67) [:6.0.0.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:274) [:6.0.0.Final] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242) [:6.0.0.Final] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [:6.0.0.Final] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) [:6.0.0.Final] at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:181) [:6.0.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.0.0.Final] at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:100) [:6.0.0.Final] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) [:6.0.0.Final] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [:6.0.0.Final] at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) [:6.0.0.Final] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [:6.0.0.Final] at org.jboss.web.tomcat.service.request.ActiveRequestResponseCacheValve.invoke(ActiveRequestResponseCacheValve.java:53) [:6.0.0.Final] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) [:6.0.0.Final] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [:6.0.0.Final] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:654) [:6.0.0.Final] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:951) [:6.0.0.Final] at java.lang.Thread.run(Thread.java:662) [:1.6.0_22] {code} was (Author: jhuska): This excepion is thrown after some time of not using push, IMHO it is thrown after timeout set on Atmosphere: {code} 15:22:50,797 ERROR [org.atmosphere.container.BlockingIOCometSupport] Unable to resume the suspended connection with latchId: 17509802 15:22:50,798 SEVERE [org.richfaces.log.Application] null: java.lang.NullPointerException at org.atmosphere.cpr.AtmosphereResourceEventImpl.isResuming(AtmosphereResourceEventImpl.java:89) [:0.8.3] at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:599) [:0.8.3] at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:584) [:0.8.3] at org.atmosphere.cpr.AsynchronousProcessor.timedout(AsynchronousProcessor.java:380) [:0.8.3] at org.atmosphere.container.BlockingIOCometSupport.suspend(BlockingIOCometSupport.java:165) [:0.8.3] at org.atmosphere.container.BlockingIOCometSupport.service(BlockingIOCometSupport.java:95) [:0.8.3] at org.atmosphere.cpr.AtmosphereServlet.doCometSupport(AtmosphereServlet.java:1212) [:0.8.3] at org.atmosphere.cpr.AtmosphereServlet.doPost(AtmosphereServlet.java:1171) [:0.8.3] at org.atmosphere.cpr.AtmosphereServlet.doGet(AtmosphereServlet.java:1157) [:0.8.3] at javax.servlet.http.HttpServlet.service(HttpServlet.java:734) [:1.0.0.Final] at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [:1.0.0.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:324) [:6.0.0.Final] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242) [:6.0.0.Final] at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:67) [:6.0.0.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:274) [:6.0.0.Final] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242) [:6.0.0.Final] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [:6.0.0.Final] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) [:6.0.0.Final] at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:181) [:6.0.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.0.0.Final] at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:100) [:6.0.0.Final] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) [:6.0.0.Final] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [:6.0.0.Final] at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) [:6.0.0.Final] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [:6.0.0.Final] at org.jboss.web.tomcat.service.request.ActiveRequestResponseCacheValve.invoke(ActiveRequestResponseCacheValve.java:53) [:6.0.0.Final] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) [:6.0.0.Final] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [:6.0.0.Final] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:654) [:6.0.0.Final] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:951) [:6.0.0.Final] at java.lang.Thread.run(Thread.java:662) [:1.6.0_22] {code} > showcase - a4j:push - error on the server side, Unable to resume the suspended connection with latchId > ------------------------------------------------------------------------------------------------------- > > Key: RF-11903 > URL: https://issues.jboss.org/browse/RF-11903 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll, showcase, third-party > Affects Versions: 4.1.0.Final > Environment: container: JBoss AS 6.0.0.Final > browsers: all > application: showcase 4.2.0-SNAPSHOT > Reporter: Juraj Huska > > *All* demos for 14j:push are causing *error* on the server side when it is pushing something to them: > {code} > 15:03:42,962 ERROR [org.atmosphere.container.BlockingIOCometSupport] Unable to resume the suspended connection with latchId: 11597405 > {code} > Note that the latchId is for each push different. *The functionality* however remains *ok*, at least for Topics context usage and JMS push. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 19 09:39:18 2012 From: jira-events at lists.jboss.org (Juraj Huska (JIRA)) Date: Thu, 19 Jan 2012 09:39:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11903) showcase - a4j:push - error on the server side, Unable to resume the suspended connection with latchId In-Reply-To: <1647203784.10826.1326982278758.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <438720814.10948.1326983958334.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12660517#comment-12660517 ] Juraj Huska commented on RF-11903: ---------------------------------- Another error thrown when server is shutting down, note that it is also thrown *after using of CDI push demo.* {code} 15:36:49,800 ERROR [org.atmosphere.container.BlockingIOCometSupport] : java.lang.NullPointerException at org.atmosphere.container.BlockingIOCometSupport.action(BlockingIOCometSupport.java:199) [:0.8.3] at org.atmosphere.container.BlockingIOCometSupport.action(BlockingIOCometSupport.java:71) [:0.8.3] at org.atmosphere.cpr.AtmosphereResourceImpl.resume(AtmosphereResourceImpl.java:218) [:0.8.3] at org.atmosphere.cpr.Meteor.resume(Meteor.java:240) [:0.8.3] at org.richfaces.application.push.impl.RequestImpl.resume(RequestImpl.java:68) [:4.2.0-SNAPSHOT] at org.richfaces.application.push.impl.SessionImpl.releaseRequest(SessionImpl.java:112) [:4.2.0-SNAPSHOT] at org.richfaces.application.push.impl.SessionImpl.disconnect(SessionImpl.java:117) [:4.2.0-SNAPSHOT] at org.richfaces.application.push.impl.SessionImpl.destroy(SessionImpl.java:156) [:4.2.0-SNAPSHOT] at org.richfaces.application.push.impl.SessionManagerImpl.destroy(SessionManagerImpl.java:84) [:4.2.0-SNAPSHOT] at org.richfaces.application.push.impl.PushContextImpl.destroy(PushContextImpl.java:90) [:4.2.0-SNAPSHOT] at org.richfaces.application.push.impl.PushContextImpl.processEvent(PushContextImpl.java:106) [:4.2.0-SNAPSHOT] at javax.faces.event.SystemEvent.processListener(SystemEvent.java:102) [:2.0.3-] at com.sun.faces.application.ApplicationImpl.processListeners(ApplicationImpl.java:2040) [:2.0.3-] at com.sun.faces.application.ApplicationImpl.invokeListenersFor(ApplicationImpl.java:2016) [:2.0.3-] at com.sun.faces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:298) [:2.0.3-] at org.jboss.weld.integration.webtier.jsf.ForwardingApplication.publishEvent(ForwardingApplication.java:330) [:6.0.0.Final] at com.sun.faces.config.ConfigureListener.contextDestroyed(ConfigureListener.java:316) [:2.0.3-] at org.apache.catalina.core.StandardContext.listenerStop(StandardContext.java:3466) [:6.0.0.Final] at org.apache.catalina.core.StandardContext.stop(StandardContext.java:3975) [:6.0.0.Final] at org.apache.catalina.core.ContainerBase.destroy(ContainerBase.java:1162) [:6.0.0.Final] at org.apache.catalina.core.StandardContext.destroy(StandardContext.java:4062) [:6.0.0.Final] 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.tomcat.util.modeler.BaseModelMBean.invoke(BaseModelMBean.java:300) [:6.0.0.Final] at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164) [:6.0.0.GA] at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:670) [:6.0.0.GA] at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performUndeployInternal(TomcatDeployment.java:551) [:6.0.0.Final] at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performUndeploy(TomcatDeployment.java:526) [:6.0.0.Final] at org.jboss.web.deployers.AbstractWarDeployment.stop(AbstractWarDeployment.java:496) [:6.0.0.Final] at org.jboss.web.deployers.WebModule.stopModule(WebModule.java:133) [:6.0.0.Final] at org.jboss.web.deployers.WebModule.stop(WebModule.java:100) [:6.0.0.Final] 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.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157) [:6.0.0.GA] at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) [:6.0.0.GA] at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) [:6.0.0.GA] at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:271) [:6.0.0.GA] at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:670) [:6.0.0.GA] at org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:206) [:2.2.0.GA] at $Proxy41.stop(Unknown Source) at org.jboss.system.microcontainer.StartStopLifecycleAction.uninstallAction(StartStopLifecycleAction.java:74) [:2.2.0.GA] at org.jboss.system.microcontainer.StartStopLifecycleAction.uninstallAction(StartStopLifecycleAction.java:41) [:2.2.0.GA] at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleUninstallAction(SimpleControllerContextAction.java:79) [jboss-dependency.jar:2.2.0.GA] at org.jboss.dependency.plugins.action.AccessControllerContextAction.uninstall(AccessControllerContextAction.java:131) [jboss-dependency.jar:2.2.0.GA] at org.jboss.dependency.plugins.AbstractControllerContextActions.uninstall(AbstractControllerContextActions.java:58) [jboss-dependency.jar:2.2.0.GA] at org.jboss.dependency.plugins.AbstractControllerContext.uninstall(AbstractControllerContext.java:385) [jboss-dependency.jar:2.2.0.GA] at org.jboss.dependency.plugins.AbstractController.uninstall(AbstractController.java:2078) [jboss-dependency.jar:2.2.0.GA] at org.jboss.dependency.plugins.AbstractController.uninstallContext(AbstractController.java:1624) [jboss-dependency.jar:2.2.0.GA] at org.jboss.dependency.plugins.AbstractController.uninstallContext(AbstractController.java:1472) [jboss-dependency.jar:2.2.0.GA] at org.jboss.dependency.plugins.AbstractController.uninstallContext(AbstractController.java:1537) [jboss-dependency.jar:2.2.0.GA] at org.jboss.dependency.plugins.AbstractController.uninstallContext(AbstractController.java:1472) [jboss-dependency.jar:2.2.0.GA] at org.jboss.dependency.plugins.AbstractController.uninstallContext(AbstractController.java:1537) [jboss-dependency.jar:2.2.0.GA] at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:948) [jboss-dependency.jar:2.2.0.GA] at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:654) [jboss-dependency.jar:2.2.0.GA] at org.jboss.deployers.plugins.deployers.DeployersImpl.change(DeployersImpl.java:1983) [:2.2.0.GA] at org.jboss.deployers.plugins.deployers.DeployersImpl.change(DeployersImpl.java:1968) [:2.2.0.GA] at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:1001) [:2.2.0.GA] at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:656) [:2.2.0.GA] at org.jboss.system.server.profileservice.deployers.MainDeployerPlugin.process(MainDeployerPlugin.java:106) [:6.0.0.Final] at org.jboss.profileservice.dependency.ProfileControllerContext$DelegateDeployer.process(ProfileControllerContext.java:143) [:0.2.2] at org.jboss.profileservice.dependency.ProfileDeployAction.undeploy(ProfileDeployAction.java:195) [:0.2.2] at org.jboss.profileservice.dependency.ProfileDeployAction.uninstallActionInternal(ProfileDeployAction.java:112) [:0.2.2] at org.jboss.kernel.plugins.dependency.InstallsAwareAction.uninstallAction(InstallsAwareAction.java:175) [jboss-kernel.jar:2.2.0.GA] at org.jboss.kernel.plugins.dependency.InstallsAwareAction.uninstallAction(InstallsAwareAction.java:42) [jboss-kernel.jar:2.2.0.GA] at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleUninstallAction(SimpleControllerContextAction.java:79) [jboss-dependency.jar:2.2.0.GA] at org.jboss.dependency.plugins.action.AccessControllerContextAction.uninstall(AccessControllerContextAction.java:131) [jboss-dependency.jar:2.2.0.GA] at org.jboss.dependency.plugins.AbstractControllerContextActions.uninstall(AbstractControllerContextActions.java:58) [jboss-dependency.jar:2.2.0.GA] at org.jboss.dependency.plugins.AbstractControllerContext.uninstall(AbstractControllerContext.java:385) [jboss-dependency.jar:2.2.0.GA] at org.jboss.dependency.plugins.AbstractController.uninstall(AbstractController.java:2078) [jboss-dependency.jar:2.2.0.GA] at org.jboss.dependency.plugins.AbstractController.uninstallContext(AbstractController.java:1624) [jboss-dependency.jar:2.2.0.GA] at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:948) [jboss-dependency.jar:2.2.0.GA] at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:654) [jboss-dependency.jar:2.2.0.GA] at org.jboss.profileservice.dependency.ProfileActivationWrapper$BasicProfileActivation.stop(ProfileActivationWrapper.java:210) [:0.2.2] at org.jboss.profileservice.dependency.ProfileActivationWrapper.stop(ProfileActivationWrapper.java:101) [:0.2.2] at org.jboss.profileservice.dependency.ProfileActivationService.deactivateProfile(ProfileActivationService.java:220) [:0.2.2] at org.jboss.profileservice.dependency.ProfileActivationService.deactivate(ProfileActivationService.java:170) [:0.2.2] at org.jboss.profileservice.bootstrap.AbstractProfileServiceBootstrap.stop(AbstractProfileServiceBootstrap.java:130) [:0.2.2] at org.jboss.system.server.profileservice.bootstrap.BasicProfileServiceBootstrap.shutdown(BasicProfileServiceBootstrap.java:160) [:6.0.0.Final] at org.jboss.system.server.profileservice.bootstrap.BasicProfileServiceBootstrap.shutdown(BasicProfileServiceBootstrap.java:56) [:6.0.0.Final] at org.jboss.bootstrap.impl.base.server.AbstractServer.shutdownBootstraps(AbstractServer.java:859) [jboss-bootstrap-impl-base.jar:2.1.0-alpha-5] at org.jboss.bootstrap.impl.base.server.AbstractServer.shutdown(AbstractServer.java:300) [jboss-bootstrap-impl-base.jar:2.1.0-alpha-5] at org.jboss.Main$ShutdownHook$1.run(Main.java:994) [run.jar:6.0.0.Final (Build SVNTag:JBoss_6.0.0.Final date: 20101228)] {code} > showcase - a4j:push - error on the server side, Unable to resume the suspended connection with latchId > ------------------------------------------------------------------------------------------------------- > > Key: RF-11903 > URL: https://issues.jboss.org/browse/RF-11903 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll, showcase, third-party > Affects Versions: 4.1.0.Final > Environment: container: JBoss AS 6.0.0.Final > browsers: all > application: showcase 4.2.0-SNAPSHOT > Reporter: Juraj Huska > > *All* demos for 14j:push are causing *error* on the server side when it is pushing something to them: > {code} > 15:03:42,962 ERROR [org.atmosphere.container.BlockingIOCometSupport] Unable to resume the suspended connection with latchId: 11597405 > {code} > Note that the latchId is for each push different. *The functionality* however remains *ok*, at least for Topics context usage and JMS push. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 19 09:41:18 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?J=C3=A1n_Jamrich_=28JIRA=29?=) Date: Thu, 19 Jan 2012 09:41:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11904) rich:contextMenu @mode doesn't affect request type Message-ID: <1470389961.10951.1326984078257.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> J?n Jamrich created RF-11904: -------------------------------- Summary: rich:contextMenu @mode doesn't affect request type Key: RF-11904 URL: https://issues.jboss.org/browse/RF-11904 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-misc Environment: RichFaces 4.2.0-SNAPSHOT Metamer 4.1.1-SNAPSHOT r.${buildNumber} Mojarra 2.1.3-SNAPSHOT JBoss AS 7.0.2.Final Java(TM) SE Runtime Environment 1.6.0_26-b03 @ Linux Firefox 10.0 @ Linux i686 ----- Richfaces component module built after merge to develop branch Reporter: J?n Jamrich Since contextMenu should be similar to dropDownMenu, I'm missing behavior controlled by @mode in contextMenu like dropDownMenu. In dropDownMenu @mode=ajax causes just one request performed when click menu item. No request for @mode=client and only for @mode=server multiple requests (first POST request for page where dropDownMenu triggered request and then multiple GET requests for all associated (referenced) resources such as CSS, JS... But not for contextMenu. @mode set to client neither ajax doesn't change request type, always is full page refresh performed when click on contextMenu item. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 19 09:43:18 2012 From: jira-events at lists.jboss.org (Juraj Huska (JIRA)) Date: Thu, 19 Jan 2012 09:43:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11903) showcase - a4j:push - error on the server side, Unable to resume the suspended connection with latchId In-Reply-To: <1647203784.10826.1326982278758.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <2075974577.10954.1326984198340.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12660513#comment-12660513 ] Juraj Huska edited comment on RF-11903 at 1/19/12 9:43 AM: ----------------------------------------------------------- This excepion is thrown after some time of not using push, *before it had to be used CDI example*, IMHO it is thrown after timeout set on Atmosphere: Note that this behavior is also occurring on JBoss AS 7.0.2.Final. {code} 15:22:50,797 ERROR [org.atmosphere.container.BlockingIOCometSupport] Unable to resume the suspended connection with latchId: 17509802 15:22:50,798 SEVERE [org.richfaces.log.Application] null: java.lang.NullPointerException at org.atmosphere.cpr.AtmosphereResourceEventImpl.isResuming(AtmosphereResourceEventImpl.java:89) [:0.8.3] at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:599) [:0.8.3] at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:584) [:0.8.3] at org.atmosphere.cpr.AsynchronousProcessor.timedout(AsynchronousProcessor.java:380) [:0.8.3] at org.atmosphere.container.BlockingIOCometSupport.suspend(BlockingIOCometSupport.java:165) [:0.8.3] at org.atmosphere.container.BlockingIOCometSupport.service(BlockingIOCometSupport.java:95) [:0.8.3] at org.atmosphere.cpr.AtmosphereServlet.doCometSupport(AtmosphereServlet.java:1212) [:0.8.3] at org.atmosphere.cpr.AtmosphereServlet.doPost(AtmosphereServlet.java:1171) [:0.8.3] at org.atmosphere.cpr.AtmosphereServlet.doGet(AtmosphereServlet.java:1157) [:0.8.3] at javax.servlet.http.HttpServlet.service(HttpServlet.java:734) [:1.0.0.Final] at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [:1.0.0.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:324) [:6.0.0.Final] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242) [:6.0.0.Final] at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:67) [:6.0.0.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:274) [:6.0.0.Final] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242) [:6.0.0.Final] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [:6.0.0.Final] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) [:6.0.0.Final] at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:181) [:6.0.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.0.0.Final] at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:100) [:6.0.0.Final] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) [:6.0.0.Final] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [:6.0.0.Final] at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) [:6.0.0.Final] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [:6.0.0.Final] at org.jboss.web.tomcat.service.request.ActiveRequestResponseCacheValve.invoke(ActiveRequestResponseCacheValve.java:53) [:6.0.0.Final] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) [:6.0.0.Final] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [:6.0.0.Final] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:654) [:6.0.0.Final] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:951) [:6.0.0.Final] at java.lang.Thread.run(Thread.java:662) [:1.6.0_22] {code} was (Author: jhuska): This excepion is thrown after some time of not using push, *before it had to be used CDI example*, IMHO it is thrown after timeout set on Atmosphere: {code} 15:22:50,797 ERROR [org.atmosphere.container.BlockingIOCometSupport] Unable to resume the suspended connection with latchId: 17509802 15:22:50,798 SEVERE [org.richfaces.log.Application] null: java.lang.NullPointerException at org.atmosphere.cpr.AtmosphereResourceEventImpl.isResuming(AtmosphereResourceEventImpl.java:89) [:0.8.3] at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:599) [:0.8.3] at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:584) [:0.8.3] at org.atmosphere.cpr.AsynchronousProcessor.timedout(AsynchronousProcessor.java:380) [:0.8.3] at org.atmosphere.container.BlockingIOCometSupport.suspend(BlockingIOCometSupport.java:165) [:0.8.3] at org.atmosphere.container.BlockingIOCometSupport.service(BlockingIOCometSupport.java:95) [:0.8.3] at org.atmosphere.cpr.AtmosphereServlet.doCometSupport(AtmosphereServlet.java:1212) [:0.8.3] at org.atmosphere.cpr.AtmosphereServlet.doPost(AtmosphereServlet.java:1171) [:0.8.3] at org.atmosphere.cpr.AtmosphereServlet.doGet(AtmosphereServlet.java:1157) [:0.8.3] at javax.servlet.http.HttpServlet.service(HttpServlet.java:734) [:1.0.0.Final] at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [:1.0.0.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:324) [:6.0.0.Final] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242) [:6.0.0.Final] at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:67) [:6.0.0.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:274) [:6.0.0.Final] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242) [:6.0.0.Final] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [:6.0.0.Final] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) [:6.0.0.Final] at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:181) [:6.0.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.0.0.Final] at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:100) [:6.0.0.Final] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) [:6.0.0.Final] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [:6.0.0.Final] at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) [:6.0.0.Final] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [:6.0.0.Final] at org.jboss.web.tomcat.service.request.ActiveRequestResponseCacheValve.invoke(ActiveRequestResponseCacheValve.java:53) [:6.0.0.Final] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) [:6.0.0.Final] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [:6.0.0.Final] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:654) [:6.0.0.Final] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:951) [:6.0.0.Final] at java.lang.Thread.run(Thread.java:662) [:1.6.0_22] {code} > showcase - a4j:push - error on the server side, Unable to resume the suspended connection with latchId > ------------------------------------------------------------------------------------------------------- > > Key: RF-11903 > URL: https://issues.jboss.org/browse/RF-11903 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll, showcase, third-party > Affects Versions: 4.1.0.Final > Environment: container: JBoss AS 6.0.0.Final > browsers: all > application: showcase 4.2.0-SNAPSHOT > Reporter: Juraj Huska > > *All* demos for 14j:push are causing *error* on the server side when it is pushing something to them: > {code} > 15:03:42,962 ERROR [org.atmosphere.container.BlockingIOCometSupport] Unable to resume the suspended connection with latchId: 11597405 > {code} > Note that the latchId is for each push different. *The functionality* however remains *ok*, at least for Topics context usage and JMS push. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 19 09:49:19 2012 From: jira-events at lists.jboss.org (Juraj Huska (JIRA)) Date: Thu, 19 Jan 2012 09:49:19 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11903) showcase - a4j:push - error on the server side, Unable to resume the suspended connection with latchId In-Reply-To: <1647203784.10826.1326982278758.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1058039597.10968.1326984559814.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12660513#comment-12660513 ] Juraj Huska edited comment on RF-11903 at 1/19/12 9:48 AM: ----------------------------------------------------------- This excepion is thrown after some time of not using push, *before it had to be used CDI example*, IMHO it is thrown after timeout set on Atmosphere: Note that this behavior is also occurring on *JBoss AS 7.0.2.Final*. {code} 15:22:50,797 ERROR [org.atmosphere.container.BlockingIOCometSupport] Unable to resume the suspended connection with latchId: 17509802 15:22:50,798 SEVERE [org.richfaces.log.Application] null: java.lang.NullPointerException at org.atmosphere.cpr.AtmosphereResourceEventImpl.isResuming(AtmosphereResourceEventImpl.java:89) [:0.8.3] at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:599) [:0.8.3] at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:584) [:0.8.3] at org.atmosphere.cpr.AsynchronousProcessor.timedout(AsynchronousProcessor.java:380) [:0.8.3] at org.atmosphere.container.BlockingIOCometSupport.suspend(BlockingIOCometSupport.java:165) [:0.8.3] at org.atmosphere.container.BlockingIOCometSupport.service(BlockingIOCometSupport.java:95) [:0.8.3] at org.atmosphere.cpr.AtmosphereServlet.doCometSupport(AtmosphereServlet.java:1212) [:0.8.3] at org.atmosphere.cpr.AtmosphereServlet.doPost(AtmosphereServlet.java:1171) [:0.8.3] at org.atmosphere.cpr.AtmosphereServlet.doGet(AtmosphereServlet.java:1157) [:0.8.3] at javax.servlet.http.HttpServlet.service(HttpServlet.java:734) [:1.0.0.Final] at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [:1.0.0.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:324) [:6.0.0.Final] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242) [:6.0.0.Final] at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:67) [:6.0.0.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:274) [:6.0.0.Final] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242) [:6.0.0.Final] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [:6.0.0.Final] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) [:6.0.0.Final] at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:181) [:6.0.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.0.0.Final] at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:100) [:6.0.0.Final] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) [:6.0.0.Final] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [:6.0.0.Final] at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) [:6.0.0.Final] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [:6.0.0.Final] at org.jboss.web.tomcat.service.request.ActiveRequestResponseCacheValve.invoke(ActiveRequestResponseCacheValve.java:53) [:6.0.0.Final] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) [:6.0.0.Final] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [:6.0.0.Final] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:654) [:6.0.0.Final] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:951) [:6.0.0.Final] at java.lang.Thread.run(Thread.java:662) [:1.6.0_22] {code} was (Author: jhuska): This excepion is thrown after some time of not using push, *before it had to be used CDI example*, IMHO it is thrown after timeout set on Atmosphere: Note that this behavior is also occurring on JBoss AS 7.0.2.Final. {code} 15:22:50,797 ERROR [org.atmosphere.container.BlockingIOCometSupport] Unable to resume the suspended connection with latchId: 17509802 15:22:50,798 SEVERE [org.richfaces.log.Application] null: java.lang.NullPointerException at org.atmosphere.cpr.AtmosphereResourceEventImpl.isResuming(AtmosphereResourceEventImpl.java:89) [:0.8.3] at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:599) [:0.8.3] at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:584) [:0.8.3] at org.atmosphere.cpr.AsynchronousProcessor.timedout(AsynchronousProcessor.java:380) [:0.8.3] at org.atmosphere.container.BlockingIOCometSupport.suspend(BlockingIOCometSupport.java:165) [:0.8.3] at org.atmosphere.container.BlockingIOCometSupport.service(BlockingIOCometSupport.java:95) [:0.8.3] at org.atmosphere.cpr.AtmosphereServlet.doCometSupport(AtmosphereServlet.java:1212) [:0.8.3] at org.atmosphere.cpr.AtmosphereServlet.doPost(AtmosphereServlet.java:1171) [:0.8.3] at org.atmosphere.cpr.AtmosphereServlet.doGet(AtmosphereServlet.java:1157) [:0.8.3] at javax.servlet.http.HttpServlet.service(HttpServlet.java:734) [:1.0.0.Final] at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [:1.0.0.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:324) [:6.0.0.Final] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242) [:6.0.0.Final] at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:67) [:6.0.0.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:274) [:6.0.0.Final] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242) [:6.0.0.Final] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [:6.0.0.Final] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) [:6.0.0.Final] at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:181) [:6.0.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.0.0.Final] at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:100) [:6.0.0.Final] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) [:6.0.0.Final] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [:6.0.0.Final] at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) [:6.0.0.Final] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [:6.0.0.Final] at org.jboss.web.tomcat.service.request.ActiveRequestResponseCacheValve.invoke(ActiveRequestResponseCacheValve.java:53) [:6.0.0.Final] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) [:6.0.0.Final] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [:6.0.0.Final] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:654) [:6.0.0.Final] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:951) [:6.0.0.Final] at java.lang.Thread.run(Thread.java:662) [:1.6.0_22] {code} > showcase - a4j:push - error on the server side, Unable to resume the suspended connection with latchId > ------------------------------------------------------------------------------------------------------- > > Key: RF-11903 > URL: https://issues.jboss.org/browse/RF-11903 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll, showcase, third-party > Affects Versions: 4.1.0.Final > Environment: container: JBoss AS 6.0.0.Final > browsers: all > application: showcase 4.2.0-SNAPSHOT > Reporter: Juraj Huska > > *All* demos for 14j:push are causing *error* on the server side when it is pushing something to them: > {code} > 15:03:42,962 ERROR [org.atmosphere.container.BlockingIOCometSupport] Unable to resume the suspended connection with latchId: 11597405 > {code} > Note that the latchId is for each push different. *The functionality* however remains *ok*, at least for Topics context usage and JMS push. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 19 10:03:18 2012 From: jira-events at lists.jboss.org (Juraj Huska (JIRA)) Date: Thu, 19 Jan 2012 10:03:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11903) showcase - a4j:push - error on the server side, Unable to resume the suspended connection with latchId In-Reply-To: <1647203784.10826.1326982278758.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <74728147.11013.1326985398419.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12660522#comment-12660522 ] Juraj Huska commented on RF-11903: ---------------------------------- On *Jboss AS 7.1.0.CR1b* similar NullPointerException is thrown, but not after timeout but after *canceling* of the atmosphere connection(so it is enough to switch between various push demos): {code} 15:58:29,170 SEVERE [org.richfaces.log.Application] (http-localhost.localdomain-127.0.0.1-8080-2) null: java.lang.NullPointerException at org.atmosphere.cpr.AtmosphereResourceEventImpl.isResuming(AtmosphereResourceEventImpl.java:89) [atmosphere-runtime-0.8.3.jar:] at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:599) [atmosphere-runtime-0.8.3.jar:] at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:584) [atmosphere-runtime-0.8.3.jar:] at org.atmosphere.cpr.AsynchronousProcessor.cancelled(AsynchronousProcessor.java:505) [atmosphere-runtime-0.8.3.jar:] at org.atmosphere.container.JBossWebCometSupport.cancelled(JBossWebCometSupport.java:151) [atmosphere-runtime-0.8.3.jar:] at org.atmosphere.container.JBossWebCometSupport.service(JBossWebCometSupport.java:124) [atmosphere-runtime-0.8.3.jar:] at org.atmosphere.cpr.AtmosphereServlet.doCometSupport(AtmosphereServlet.java:1212) [atmosphere-runtime-0.8.3.jar:] at org.atmosphere.cpr.AtmosphereServlet.event(AtmosphereServlet.java:1305) [atmosphere-runtime-0.8.3.jar:] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilterEvent(ApplicationFilterChain.java:494) [jbossweb-7.0.7.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilterEvent(ApplicationFilterChain.java:399) [jbossweb-7.0.7.Final.jar:] at org.apache.catalina.core.StandardWrapperValve.event(StandardWrapperValve.java:464) [jbossweb-7.0.7.Final.jar:] at org.apache.catalina.core.StandardContextValve.event(StandardContextValve.java:183) [jbossweb-7.0.7.Final.jar:] at org.apache.catalina.valves.ValveBase.event(ValveBase.java:193) [jbossweb-7.0.7.Final.jar:] at org.apache.catalina.valves.ValveBase.event(ValveBase.java:193) [jbossweb-7.0.7.Final.jar:] at org.apache.catalina.core.StandardHostValve.event(StandardHostValve.java:259) [jbossweb-7.0.7.Final.jar:] at org.apache.catalina.valves.ValveBase.event(ValveBase.java:193) [jbossweb-7.0.7.Final.jar:] at org.apache.catalina.core.StandardEngineValve.event(StandardEngineValve.java:128) [jbossweb-7.0.7.Final.jar:] at org.apache.catalina.connector.CoyoteAdapter.event(CoyoteAdapter.java:265) [jbossweb-7.0.7.Final.jar:] at org.apache.coyote.http11.Http11AprProcessor.event(Http11AprProcessor.java:780) [jbossweb-7.0.7.Final.jar:] at org.apache.coyote.http11.Http11AprProtocol$Http11ConnectionHandler.event(Http11AprProtocol.java:579) [jbossweb-7.0.7.Final.jar:] at org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:2027) [jbossweb-7.0.7.Final.jar:] at java.lang.Thread.run(Thread.java:662) [:1.6.0_22] {code} > showcase - a4j:push - error on the server side, Unable to resume the suspended connection with latchId > ------------------------------------------------------------------------------------------------------- > > Key: RF-11903 > URL: https://issues.jboss.org/browse/RF-11903 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll, showcase, third-party > Affects Versions: 4.1.0.Final > Environment: container: JBoss AS 6.0.0.Final > browsers: all > application: showcase 4.2.0-SNAPSHOT > Reporter: Juraj Huska > > *All* demos for 14j:push are causing *error* on the server side when it is pushing something to them: > {code} > 15:03:42,962 ERROR [org.atmosphere.container.BlockingIOCometSupport] Unable to resume the suspended connection with latchId: 11597405 > {code} > Note that the latchId is for each push different. *The functionality* however remains *ok*, at least for Topics context usage and JMS push. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 19 10:07:18 2012 From: jira-events at lists.jboss.org (Juraj Huska (JIRA)) Date: Thu, 19 Jan 2012 10:07:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11903) showcase - a4j:push - error on the server side, Unable to resume the suspended connection with latchId In-Reply-To: <1647203784.10826.1326982278758.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1511030665.11034.1326985638337.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj Huska updated RF-11903: ----------------------------- Description: *All* demos for 14j:push are causing *error* on the server side when it is pushing something to them: {code} 15:03:42,962 ERROR [org.atmosphere.container.BlockingIOCometSupport] Unable to resume the suspended connection with latchId: 11597405 {code} Note that the latchId is for each push different. *The functionality* however remains *ok*, at least for Topics context usage and JMS push. This particular error is thrown only on *JBoss AS 6*, *other containers* throws also some errors, please see the comments below. was: *All* demos for 14j:push are causing *error* on the server side when it is pushing something to them: {code} 15:03:42,962 ERROR [org.atmosphere.container.BlockingIOCometSupport] Unable to resume the suspended connection with latchId: 11597405 {code} Note that the latchId is for each push different. *The functionality* however remains *ok*, at least for Topics context usage and JMS push. Environment: container: JBoss AS 6.0.0.Final, JBoss AS 7.0.2.Final, JBoss AS 7.1.0.CR1b browsers: all application: showcase 4.2.0-SNAPSHOT was: container: JBoss AS 6.0.0.Final browsers: all application: showcase 4.2.0-SNAPSHOT > showcase - a4j:push - error on the server side, Unable to resume the suspended connection with latchId > ------------------------------------------------------------------------------------------------------- > > Key: RF-11903 > URL: https://issues.jboss.org/browse/RF-11903 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll, showcase, third-party > Affects Versions: 4.1.0.Final > Environment: container: JBoss AS 6.0.0.Final, JBoss AS 7.0.2.Final, JBoss AS 7.1.0.CR1b > browsers: all > application: showcase 4.2.0-SNAPSHOT > Reporter: Juraj Huska > > *All* demos for 14j:push are causing *error* on the server side when it is pushing something to them: > {code} > 15:03:42,962 ERROR [org.atmosphere.container.BlockingIOCometSupport] Unable to resume the suspended connection with latchId: 11597405 > {code} > Note that the latchId is for each push different. *The functionality* however remains *ok*, at least for Topics context usage and JMS push. > This particular error is thrown only on *JBoss AS 6*, *other containers* throws also some errors, please see the comments below. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 19 10:15:19 2012 From: jira-events at lists.jboss.org (Juraj Huska (JIRA)) Date: Thu, 19 Jan 2012 10:15:19 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11905) showcase - shutdown of the JBoss AS server throws DB error Message-ID: <567082387.11072.1326986119167.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Juraj Huska created RF-11905: -------------------------------- Summary: showcase - shutdown of the JBoss AS server 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 app: showcase 4.2.0-SNAPSHOT Reporter: Juraj Huska Priority: Minor When shutting down JBoss AS 7.1.0.CR1b 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 Thu Jan 19 10:15:19 2012 From: jira-events at lists.jboss.org (Juraj Huska (JIRA)) Date: Thu, 19 Jan 2012 10:15:19 -0500 (EST) 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: <973231784.11076.1326986119347.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 updated RF-11905: ----------------------------- Summary: showcase - shutdown of the JBoss AS with showcase deployed throws DB error (was: showcase - shutdown of the JBoss AS server throws DB error) > 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 > app: showcase 4.2.0-SNAPSHOT > Reporter: Juraj Huska > Priority: Minor > > When shutting down JBoss AS 7.1.0.CR1b 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 Thu Jan 19 10:19:18 2012 From: jira-events at lists.jboss.org (Juraj Huska (JIRA)) Date: Thu, 19 Jan 2012 10:19:18 -0500 (EST) 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: <2018133944.11112.1326986358278.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 updated RF-11905: ----------------------------- Description: 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} was: When shutting down JBoss AS 7.1.0.CR1b 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} Environment: container: JBoss AS 7.1.0.CR1b, 7.0.2.Final app: showcase 4.2.0-SNAPSHOT was: container: JBoss AS 7.1.0.CR1b app: showcase 4.2.0-SNAPSHOT > 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 > Priority: Minor > > 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 Thu Jan 19 11:07:18 2012 From: jira-events at lists.jboss.org (Juraj Huska (JIRA)) Date: Thu, 19 Jan 2012 11:07:18 -0500 (EST) 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: <317936770.11282.1326989238604.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=12660547#comment-12660547 ] Juraj Huska commented on RF-11905: ---------------------------------- I was able to *get rid of this exception* when I set the database create-update-drop policy (hibernate.hbm2ddl.auto property of persistence.xml) to *create* instead of create-drop. It is probably just workaround. > 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 > Priority: Minor > > 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 Thu Jan 19 12:04:18 2012 From: jira-events at lists.jboss.org (Jean ANDRE (JIRA)) Date: Thu, 19 Jan 2012 12:04:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11764) Problems with packed resources In-Reply-To: <1531552132.56496.1322674962554.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <252957118.11498.1326992658945.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12660573#comment-12660573 ] Jean ANDRE commented on RF-11764: --------------------------------- Well, I've made the modification in our web.xml and all the UI is completly scrapped. CSS is partially rendered and we got strange characters on the screen - See screen capture - We still got a bunch of javascript error such as: jsf is not defined line 2833 [Stopper sur une erreur] - }(jQuery,RichFaces,jsf));;(function(F,N){N.csv=N.csv||{}; RichFaces.ui is undefined line 59 [Stopper sur une erreur] - ..f-ddm-itm rf-ddm-itm-unsel " id="MenuForm:item-search"> CRM-Enterprise index.html index.htm index.jsp default.html default.htm default.jsp index.jsf org.richfaces.skin crm-enterprise org.richfaces.CONTROL_SKINNING enable org.richfaces.resourceMapping.enabled true org.richfaces.resourceMapping.packedStages All Faces Servlet javax.faces.webapp.FacesServlet 1 Faces Servlet *.jsf State saving method: 'client' or 'server' (=default). See JSF Specification 2.5.2 javax.faces.STATE_SAVING_METHOD client javax.servlet.jsp.jstl.fmt.localizationContext resources.application javax.faces.DEFAULT_SUFFIX .xhtml com.sun.faces.responseBufferSize 49536 com.sun.faces.clientStateWriteBufferSize 16384 org.springframework.web.context.ContextLoaderListener org.springframework.web.context.request.RequestContextListener BASIC 15 Login Filter com.intact.crm.web.filter.LoginFilter Login Filter /pages/* > Problems with packed resources > ------------------------------ > > Key: RF-11764 > URL: https://issues.jboss.org/browse/RF-11764 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.1.0.CR1 > Reporter: Jean ANDRE > Labels: material-sent, waiting_on_user > > *Follow up RF-11694.* > We tested the solution by updating the web.xml. We put following code : > {code} > > org.richfaces.resourceMapping.enabled > true > > > org.richfaces.resourceMapping.packedStages > All > > {code} > The workaround does not work well because it triggers many javacript erreur - User Interface seem to be frozen, hanged. > Here are the errors catch under firebug / Mozilla > {code} > jsf is not defined > [Stopper sur une erreur] }(jQuery,RichFaces,jsf));;(function(C,B,D){B.blankFunction=function(){}; > packed.js (ligne 3040) > RichFaces.ui is undefined > [Stopper sur une erreur] 		> index.jsf (ligne 77) > RichFaces.ui is undefined > [Stopper sur une erreur] RichFaces.ui.Menu(...":"MenuForm:mainToolBar"} ); > index.jsf (ligne 77) > RichFaces.ui is undefined > [Stopper sur une erreur]
> index.jsf (ligne 85) > RichFaces.ui is undefined > [Stopper sur une erreur]
> index.jsf (ligne 88) > RichFaces.ui is undefined > [Stopper sur une erreur] > index.jsf (ligne 88) > RichFaces.ui is undefined > [Stopper sur une erreur] > index.jsf (ligne 88) > {code} > more over there is many CSS errors/warning > {code} > L'utilisation de getAttributeNodeNS() est obsol?te. Utilisez getAttributeNS() ? la place. > Une fin de valeur ?tait attendue, mais ? "#E5973E " ? a ?t? trouv?. Erreur d'analyse de la valeur pour ? border ?. D?claration abandonn?e. > *.rf-insl-tt{position:absolute;display..."#E5973E ";background-color:#FAE6B0;} > packed.css (ligne 108) > Erreur d'analyse de la valeur pour ? filter ?. D?claration abandonn?e. > *.rf-fu-inp{filter:alpha(opacity=0);fo...y:0;position:absolute;right:0;top:0;} > packed.css (ligne 158) > Propri?t? ? text-color ? inconnue. D?claration abandonn?e. > *.rf-fu-itm-st{display:none;margin-top...000;background-color:#fff;padding:0;} > packed.css (ligne 164) > Erreur d'analyse de la valeur pour ? filter ?. D?claration abandonn?e. > *.rf-tab-cnt{border:1px solid #C4C0B9;...opacity:.1;filter:alpha(opacity=10);} > packed.css (ligne 184) > Erreur d'analyse de la valeur pour ? filter ?. D?claration abandonn?e. > *.rf-pp-shade{position:fixed;width:100...opacity:.5;filter:alpha(opacity=50);} > packed.css (ligne 185) > Erreur d'analyse de la valeur pour ? filter ?. D?claration abandonn?e. > *.rf-pp-shdw{background-color:#000;opa...6px;left:6px;bottom:-6px;z-index:-1;} > packed.css (ligne 186) > Propri?t? ? repeat-x ? inconnue. D?claration abandonn?e. > *.rf-pp-hdr{background:url(../org.rich...g-left:10px;cursor:move;padding:2px;} > packed.css (ligne 188) > Erreur d'analyse de la valeur pour ? font-size ?. D?claration abandonn?e. > *.rf-cal-sp-inp{border:0;padding:0 0 0...Arial,Verdana,sans-serif;width:18px;} > packed.css (ligne 354) > Erreur d'analyse de la valeur pour ? filter ?. D?claration abandonn?e. > *.rf-cal-edtr-shdw{background:#FFF;opacity:.5;filter:alpha(opacity=50);} > packed.css (ligne 369) > Erreur d'analyse de la valeur pour ? filter ?. D?claration abandonn?e. > *.rf-cal-edtr-layout-shdw{background-c...opacity:.3;filter:alpha(opacity=30);} > {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 Jan 19 12:06:18 2012 From: jira-events at lists.jboss.org (Jean ANDRE (JIRA)) Date: Thu, 19 Jan 2012 12:06:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11764) Problems with packed resources In-Reply-To: <1531552132.56496.1322674962554.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1161991553.11503.1326992778320.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12660573#comment-12660573 ] Jean ANDRE edited comment on RF-11764 at 1/19/12 12:04 PM: ----------------------------------------------------------- NOP - ERROR was (Author: jorelia64): Well, I've made the modification in our web.xml and all the UI is completly scrapped. CSS is partially rendered and we got strange characters on the screen - See screen capture - We still got a bunch of javascript error such as: jsf is not defined line 2833 [Stopper sur une erreur] - }(jQuery,RichFaces,jsf));;(function(F,N){N.csv=N.csv||{}; RichFaces.ui is undefined line 59 [Stopper sur une erreur] - ..f-ddm-itm rf-ddm-itm-unsel " id="MenuForm:item-search"> CRM-Enterprise index.html index.htm index.jsp default.html default.htm default.jsp index.jsf org.richfaces.skin crm-enterprise org.richfaces.CONTROL_SKINNING enable org.richfaces.resourceMapping.enabled true org.richfaces.resourceMapping.packedStages All Faces Servlet javax.faces.webapp.FacesServlet 1 Faces Servlet *.jsf State saving method: 'client' or 'server' (=default). See JSF Specification 2.5.2 javax.faces.STATE_SAVING_METHOD client javax.servlet.jsp.jstl.fmt.localizationContext resources.application javax.faces.DEFAULT_SUFFIX .xhtml com.sun.faces.responseBufferSize 49536 com.sun.faces.clientStateWriteBufferSize 16384 org.springframework.web.context.ContextLoaderListener org.springframework.web.context.request.RequestContextListener BASIC 15 Login Filter com.intact.crm.web.filter.LoginFilter Login Filter /pages/* > Problems with packed resources > ------------------------------ > > Key: RF-11764 > URL: https://issues.jboss.org/browse/RF-11764 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.1.0.CR1 > Reporter: Jean ANDRE > Labels: material-sent, waiting_on_user > > *Follow up RF-11694.* > We tested the solution by updating the web.xml. We put following code : > {code} > > org.richfaces.resourceMapping.enabled > true > > > org.richfaces.resourceMapping.packedStages > All > > {code} > The workaround does not work well because it triggers many javacript erreur - User Interface seem to be frozen, hanged. > Here are the errors catch under firebug / Mozilla > {code} > jsf is not defined > [Stopper sur une erreur] }(jQuery,RichFaces,jsf));;(function(C,B,D){B.blankFunction=function(){}; > packed.js (ligne 3040) > RichFaces.ui is undefined > [Stopper sur une erreur] 		> index.jsf (ligne 77) > RichFaces.ui is undefined > [Stopper sur une erreur] RichFaces.ui.Menu(...":"MenuForm:mainToolBar"} ); > index.jsf (ligne 77) > RichFaces.ui is undefined > [Stopper sur une erreur]
> index.jsf (ligne 85) > RichFaces.ui is undefined > [Stopper sur une erreur]
> index.jsf (ligne 88) > RichFaces.ui is undefined > [Stopper sur une erreur] > index.jsf (ligne 88) > RichFaces.ui is undefined > [Stopper sur une erreur] > index.jsf (ligne 88) > {code} > more over there is many CSS errors/warning > {code} > L'utilisation de getAttributeNodeNS() est obsol?te. Utilisez getAttributeNS() ? la place. > Une fin de valeur ?tait attendue, mais ? "#E5973E " ? a ?t? trouv?. Erreur d'analyse de la valeur pour ? border ?. D?claration abandonn?e. > *.rf-insl-tt{position:absolute;display..."#E5973E ";background-color:#FAE6B0;} > packed.css (ligne 108) > Erreur d'analyse de la valeur pour ? filter ?. D?claration abandonn?e. > *.rf-fu-inp{filter:alpha(opacity=0);fo...y:0;position:absolute;right:0;top:0;} > packed.css (ligne 158) > Propri?t? ? text-color ? inconnue. D?claration abandonn?e. > *.rf-fu-itm-st{display:none;margin-top...000;background-color:#fff;padding:0;} > packed.css (ligne 164) > Erreur d'analyse de la valeur pour ? filter ?. D?claration abandonn?e. > *.rf-tab-cnt{border:1px solid #C4C0B9;...opacity:.1;filter:alpha(opacity=10);} > packed.css (ligne 184) > Erreur d'analyse de la valeur pour ? filter ?. D?claration abandonn?e. > *.rf-pp-shade{position:fixed;width:100...opacity:.5;filter:alpha(opacity=50);} > packed.css (ligne 185) > Erreur d'analyse de la valeur pour ? filter ?. D?claration abandonn?e. > *.rf-pp-shdw{background-color:#000;opa...6px;left:6px;bottom:-6px;z-index:-1;} > packed.css (ligne 186) > Propri?t? ? repeat-x ? inconnue. D?claration abandonn?e. > *.rf-pp-hdr{background:url(../org.rich...g-left:10px;cursor:move;padding:2px;} > packed.css (ligne 188) > Erreur d'analyse de la valeur pour ? font-size ?. D?claration abandonn?e. > *.rf-cal-sp-inp{border:0;padding:0 0 0...Arial,Verdana,sans-serif;width:18px;} > packed.css (ligne 354) > Erreur d'analyse de la valeur pour ? filter ?. D?claration abandonn?e. > *.rf-cal-edtr-shdw{background:#FFF;opacity:.5;filter:alpha(opacity=50);} > packed.css (ligne 369) > Erreur d'analyse de la valeur pour ? filter ?. D?claration abandonn?e. > *.rf-cal-edtr-layout-shdw{background-c...opacity:.3;filter:alpha(opacity=30);} > {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 Jan 19 12:06:18 2012 From: jira-events at lists.jboss.org (Jean ANDRE (JIRA)) Date: Thu, 19 Jan 2012 12:06:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11764) Problems with packed resources In-Reply-To: <1531552132.56496.1322674962554.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1294983185.11509.1326992778608.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12660573#comment-12660573 ] Jean ANDRE edited comment on RF-11764 at 1/19/12 12:06 PM: ----------------------------------------------------------- NOP - Oups.. need to apply the fix before... was (Author: jorelia64): NOP - ERROR > Problems with packed resources > ------------------------------ > > Key: RF-11764 > URL: https://issues.jboss.org/browse/RF-11764 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.1.0.CR1 > Reporter: Jean ANDRE > Labels: material-sent, waiting_on_user > > *Follow up RF-11694.* > We tested the solution by updating the web.xml. We put following code : > {code} > > org.richfaces.resourceMapping.enabled > true > > > org.richfaces.resourceMapping.packedStages > All > > {code} > The workaround does not work well because it triggers many javacript erreur - User Interface seem to be frozen, hanged. > Here are the errors catch under firebug / Mozilla > {code} > jsf is not defined > [Stopper sur une erreur] }(jQuery,RichFaces,jsf));;(function(C,B,D){B.blankFunction=function(){}; > packed.js (ligne 3040) > RichFaces.ui is undefined > [Stopper sur une erreur] 		> index.jsf (ligne 77) > RichFaces.ui is undefined > [Stopper sur une erreur] RichFaces.ui.Menu(...":"MenuForm:mainToolBar"} ); > index.jsf (ligne 77) > RichFaces.ui is undefined > [Stopper sur une erreur]
> index.jsf (ligne 85) > RichFaces.ui is undefined > [Stopper sur une erreur]
> index.jsf (ligne 88) > RichFaces.ui is undefined > [Stopper sur une erreur] > index.jsf (ligne 88) > RichFaces.ui is undefined > [Stopper sur une erreur] > index.jsf (ligne 88) > {code} > more over there is many CSS errors/warning > {code} > L'utilisation de getAttributeNodeNS() est obsol?te. Utilisez getAttributeNS() ? la place. > Une fin de valeur ?tait attendue, mais ? "#E5973E " ? a ?t? trouv?. Erreur d'analyse de la valeur pour ? border ?. D?claration abandonn?e. > *.rf-insl-tt{position:absolute;display..."#E5973E ";background-color:#FAE6B0;} > packed.css (ligne 108) > Erreur d'analyse de la valeur pour ? filter ?. D?claration abandonn?e. > *.rf-fu-inp{filter:alpha(opacity=0);fo...y:0;position:absolute;right:0;top:0;} > packed.css (ligne 158) > Propri?t? ? text-color ? inconnue. D?claration abandonn?e. > *.rf-fu-itm-st{display:none;margin-top...000;background-color:#fff;padding:0;} > packed.css (ligne 164) > Erreur d'analyse de la valeur pour ? filter ?. D?claration abandonn?e. > *.rf-tab-cnt{border:1px solid #C4C0B9;...opacity:.1;filter:alpha(opacity=10);} > packed.css (ligne 184) > Erreur d'analyse de la valeur pour ? filter ?. D?claration abandonn?e. > *.rf-pp-shade{position:fixed;width:100...opacity:.5;filter:alpha(opacity=50);} > packed.css (ligne 185) > Erreur d'analyse de la valeur pour ? filter ?. D?claration abandonn?e. > *.rf-pp-shdw{background-color:#000;opa...6px;left:6px;bottom:-6px;z-index:-1;} > packed.css (ligne 186) > Propri?t? ? repeat-x ? inconnue. D?claration abandonn?e. > *.rf-pp-hdr{background:url(../org.rich...g-left:10px;cursor:move;padding:2px;} > packed.css (ligne 188) > Erreur d'analyse de la valeur pour ? font-size ?. D?claration abandonn?e. > *.rf-cal-sp-inp{border:0;padding:0 0 0...Arial,Verdana,sans-serif;width:18px;} > packed.css (ligne 354) > Erreur d'analyse de la valeur pour ? filter ?. D?claration abandonn?e. > *.rf-cal-edtr-shdw{background:#FFF;opacity:.5;filter:alpha(opacity=50);} > packed.css (ligne 369) > Erreur d'analyse de la valeur pour ? filter ?. D?claration abandonn?e. > *.rf-cal-edtr-layout-shdw{background-c...opacity:.3;filter:alpha(opacity=30);} > {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 Jan 19 18:48:18 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Thu, 19 Jan 2012 18:48:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11783) disabled a4j:commandButton with nested tooltip disappears when enabled with ajax render In-Reply-To: <1145377794.68082.1322915200637.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <2086457959.12320.1327016898514.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-11783: ------------------------------- Fix Version/s: 4.3-Tracking > disabled a4j:commandButton with nested tooltip disappears when enabled with ajax render > --------------------------------------------------------------------------------------- > > Key: RF-11783 > URL: https://issues.jboss.org/browse/RF-11783 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.1.0.Milestone4 > Environment: Mojarra 2.1.3, Glassfish 3.1.1. > Reporter: Brendan Healey > Fix For: 4.3-Tracking > > > The following code resides in the footer of an extendedDataTable, although my > guess is that this is not relevant. The button is initially disabled, then > bean.property is set true and we do ajax render="myButton". The button > disappears from the screen. Removing the tooltip makes it work as expected. > id="myButton" > value=" test " > action="apage?faces-redirect=true" > disabled="#{empty bean.property}"> > > > > > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 20 03:45:19 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 20 Jan 2012 03:45:19 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11533) Notify and IE 8: can't close a message In-Reply-To: <1754239113.29618.1318507637333.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <442710687.12629.1327049119353.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12660713#comment-12660713 ] Luk?? Fry? commented on RF-11533: --------------------------------- Note: This can be solved after feature freeze. I have found following behavior: When initializing closer button as follows, the event is not caught: {code} $("
", { "click" : function() { ... } } {code} but when using following handler, it works as expected: {code} $("
") {code} But that principle would need expose the pnotify object globally. What can we try additionally: * what code breaks "click" event triggering/handling - remove other components when resource mapping off * try dev-example with resource mapping on > Notify and IE 8: can't close a message > -------------------------------------- > > Key: RF-11533 > URL: https://issues.jboss.org/browse/RF-11533 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.1.0.Milestone3 > Environment: ?RichFaces 4.1.0.20111011-M3 r.68406156c3d647eee75816d4bd6a29a66b0b5a2f > ?Metamer 4.1.0.20111011-M3 r.22776 > ?Mojarra 2.1.3-SNAPSHOT > ?Apache Tomcat 7.0.22 > ?Java(TM) SE Runtime Environment 1.6.0_27-b07 @ Windows Server 2008 > ?Internet Explorer 8.0 @ Win32 > Reporter: Jan Papousek > Assignee: Luk?? Fry? > Fix For: 4.2.0.CR1 > > > Notify messages can't be closed in IE 8. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 20 03:52:18 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 20 Jan 2012 03:52:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11483) Elegant way for Push topic creating In-Reply-To: <11494155.16954.1318245975997.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1039538878.12633.1327049538486.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated RF-11483: ---------------------------- Assignee: Luk?? Fry? Fix Version/s: 4.2.0.CR1 (was: 4.3-Tracking) Forum Reference: http://community.jboss.org/message/630871#630871 (was: http://community.jboss.org/message/630871#630871) > Elegant way for Push topic creating > ----------------------------------- > > Key: RF-11483 > URL: https://issues.jboss.org/browse/RF-11483 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-push/poll, core > Affects Versions: 4.1.0.Milestone1 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 4.2.0.CR1 > > > Currently, topics have to be initialized with similar class: > https://github.com/richfaces/showcase/blob/4.1.0.20110910-M2/src/main/java/org/richfaces/demo/push/TopicsInitializer.java > I suggest to create topic on demand (lazily), when it is accessed first. > It needs following changes: > * {{PushRendererBase}} - will create Topic for @address attribute > * {{JMSTopicsContextImpl}} - will create topic when JMS message received > * {{PushObserverMethod}} - will create topic when @Push event for given topic observed > * ... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 20 03:54:18 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 20 Jan 2012 03:54:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11906) Warning when JMS integration is off but JMS is available Message-ID: <655659084.12635.1327049658286.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Luk?? Fry? created RF-11906: ------------------------------- Summary: Warning when JMS integration is off but JMS is available Key: RF-11906 URL: https://issues.jboss.org/browse/RF-11906 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Components: core Reporter: Luk?? Fry? Fix For: 4.2.0.CR1 For JMS detection, following algorithms can be used: * JMS API class detection * JNDI binding {{java://ConnectionFactory}} can be checked {{PushServlet}} can be used as place for triggering detection. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 20 06:12:19 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 20 Jan 2012 06:12:19 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11297) Upgrade to Atmosphere 0.8 In-Reply-To: <2095736598.451.1313071442606.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1185258972.12849.1327057939857.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved RF-11297. ----------------------------- Fix Version/s: (was: 4.3-Tracking) Resolution: Duplicate Issue > Upgrade to Atmosphere 0.8 > ------------------------- > > Key: RF-11297 > URL: https://issues.jboss.org/browse/RF-11297 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 4.1.0.Milestone1 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Priority: Critical > > Upgrade to Atmosphere 0.8 once available. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 20 06:12:20 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 20 Jan 2012 06:12:20 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11471) Upgrade to Atmosphere 0.8.3 In-Reply-To: <1090154337.14335.1318029736037.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <386967480.12850.1327057940574.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? reopened RF-11471: ----------------------------- > Upgrade to Atmosphere 0.8.3 > --------------------------- > > Key: RF-11471 > URL: https://issues.jboss.org/browse/RF-11471 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: component-push/poll, third-party > Affects Versions: 4.1.0.Milestone3 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Priority: Critical > Fix For: 4.2.0.CR1 > > > Atmosphere 0.8.0-RC2 is planned to be released [1] on right on 4.1.0.M3 code-freeze, we will wait before start of QE cycle to grab this release. > [1] http://groups.google.com/group/atmosphere-framework/browse_thread/thread/caffae0c616c250a -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 20 06:14:18 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 20 Jan 2012 06:14:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11471) Upgrade to Atmosphere 0.8.3 In-Reply-To: <1090154337.14335.1318029736037.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <926546579.12853.1327058058268.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12660737#comment-12660737 ] Luk?? Fry? commented on RF-11471: --------------------------------- I can reproduce this issue again with Atmosphere {{0.8.3}} on JBoss AS {{7.0.2.Final}}, {{7.1.0.CR1b}}, when switching between samples of Push demo in Showcase: {code} 12:12:31,533 SEVERE [org.richfaces.log.Application] (http-localhost.localdomain-127.0.0.1-8080-1) null: java.lang.NullPointerException at org.atmosphere.cpr.AtmosphereResourceEventImpl.isResuming(AtmosphereResourceEventImpl.java:89) [atmosphere-runtime-0.8.3.jar:] at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:599) [atmosphere-runtime-0.8.3.jar:] at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:584) [atmosphere-runtime-0.8.3.jar:] at org.atmosphere.cpr.AsynchronousProcessor.cancelled(AsynchronousProcessor.java:505) [atmosphere-runtime-0.8.3.jar:] at org.atmosphere.container.JBossWebCometSupport.cancelled(JBossWebCometSupport.java:151) [atmosphere-runtime-0.8.3.jar:] at org.atmosphere.container.JBossWebCometSupport.service(JBossWebCometSupport.java:124) [atmosphere-runtime-0.8.3.jar:] at org.atmosphere.cpr.AtmosphereServlet.doCometSupport(AtmosphereServlet.java:1212) [atmosphere-runtime-0.8.3.jar:] at org.atmosphere.cpr.AtmosphereServlet.event(AtmosphereServlet.java:1305) [atmosphere-runtime-0.8.3.jar:] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilterEvent(ApplicationFilterChain.java:494) [jbossweb-7.0.7.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilterEvent(ApplicationFilterChain.java:399) [jbossweb-7.0.7.Final.jar:] at org.apache.catalina.core.StandardWrapperValve.event(StandardWrapperValve.java:464) [jbossweb-7.0.7.Final.jar:] at org.apache.catalina.core.StandardContextValve.event(StandardContextValve.java:183) [jbossweb-7.0.7.Final.jar:] at org.apache.catalina.valves.ValveBase.event(ValveBase.java:193) [jbossweb-7.0.7.Final.jar:] at org.apache.catalina.valves.ValveBase.event(ValveBase.java:193) [jbossweb-7.0.7.Final.jar:] at org.apache.catalina.core.StandardHostValve.event(StandardHostValve.java:259) [jbossweb-7.0.7.Final.jar:] at org.apache.catalina.valves.ValveBase.event(ValveBase.java:193) [jbossweb-7.0.7.Final.jar:] at org.apache.catalina.core.StandardEngineValve.event(StandardEngineValve.java:128) [jbossweb-7.0.7.Final.jar:] at org.apache.catalina.connector.CoyoteAdapter.event(CoyoteAdapter.java:265) [jbossweb-7.0.7.Final.jar:] at org.apache.coyote.http11.Http11AprProcessor.event(Http11AprProcessor.java:780) [jbossweb-7.0.7.Final.jar:] at org.apache.coyote.http11.Http11AprProtocol$Http11ConnectionHandler.event(Http11AprProtocol.java:579) [jbossweb-7.0.7.Final.jar:] at org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:2027) [jbossweb-7.0.7.Final.jar:] at java.lang.Thread.run(Thread.java:662) [:1.6.0_26] {code} > Upgrade to Atmosphere 0.8.3 > --------------------------- > > Key: RF-11471 > URL: https://issues.jboss.org/browse/RF-11471 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: component-push/poll, third-party > Affects Versions: 4.1.0.Milestone3 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Priority: Critical > Fix For: 4.2.0.CR1 > > > Atmosphere 0.8.0-RC2 is planned to be released [1] on right on 4.1.0.M3 code-freeze, we will wait before start of QE cycle to grab this release. > [1] http://groups.google.com/group/atmosphere-framework/browse_thread/thread/caffae0c616c250a -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 20 07:01:18 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 20 Jan 2012 07:01:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11471) Upgrade to Atmosphere 0.8.3 In-Reply-To: <1090154337.14335.1318029736037.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <2129976173.12953.1327060878348.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12660748#comment-12660748 ] Luk?? Fry? commented on RF-11471: --------------------------------- Trying to upgrade to {{0.8.4}}. > Upgrade to Atmosphere 0.8.3 > --------------------------- > > Key: RF-11471 > URL: https://issues.jboss.org/browse/RF-11471 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: component-push/poll, third-party > Affects Versions: 4.1.0.Milestone3 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Priority: Critical > Fix For: 4.2.0.CR1 > > > Atmosphere 0.8.0-RC2 is planned to be released [1] on right on 4.1.0.M3 code-freeze, we will wait before start of QE cycle to grab this release. > [1] http://groups.google.com/group/atmosphere-framework/browse_thread/thread/caffae0c616c250a -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 20 07:04:18 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 20 Jan 2012 07:04:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11471) Upgrade to Atmosphere 0.8.4 In-Reply-To: <1090154337.14335.1318029736037.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1614083930.12956.1327061058336.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated RF-11471: ---------------------------- Summary: Upgrade to Atmosphere 0.8.4 (was: Upgrade to Atmosphere 0.8.3) > Upgrade to Atmosphere 0.8.4 > --------------------------- > > Key: RF-11471 > URL: https://issues.jboss.org/browse/RF-11471 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: component-push/poll, third-party > Affects Versions: 4.1.0.Milestone3 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Priority: Critical > Fix For: 4.2.0.CR1 > > > Atmosphere 0.8.0-RC2 is planned to be released [1] on right on 4.1.0.M3 code-freeze, we will wait before start of QE cycle to grab this release. > [1] http://groups.google.com/group/atmosphere-framework/browse_thread/thread/caffae0c616c250a -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 20 07:08:18 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 20 Jan 2012 07:08:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11903) showcase - a4j:push - error on the server side, Unable to resume the suspended connection with latchId In-Reply-To: <1647203784.10826.1326982278758.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <233089307.12962.1327061298443.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12660750#comment-12660750 ] Luk?? Fry? commented on RF-11903: --------------------------------- Hi Juraj, as I mentioned in RF-11471, there were issues with {{0.8.3}}, so I have upgraded to {{0.8.4}}, could you please check that you are not experiencing these issues anymore? (Please coordinate with Jan, since he has assigned RFPL-1978) > showcase - a4j:push - error on the server side, Unable to resume the suspended connection with latchId > ------------------------------------------------------------------------------------------------------- > > Key: RF-11903 > URL: https://issues.jboss.org/browse/RF-11903 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll, showcase, third-party > Affects Versions: 4.1.0.Final > Environment: container: JBoss AS 6.0.0.Final, JBoss AS 7.0.2.Final, JBoss AS 7.1.0.CR1b > browsers: all > application: showcase 4.2.0-SNAPSHOT > Reporter: Juraj Huska > Fix For: 4.2.0.CR1 > > > *All* demos for 14j:push are causing *error* on the server side when it is pushing something to them: > {code} > 15:03:42,962 ERROR [org.atmosphere.container.BlockingIOCometSupport] Unable to resume the suspended connection with latchId: 11597405 > {code} > Note that the latchId is for each push different. *The functionality* however remains *ok*, at least for Topics context usage and JMS push. > This particular error is thrown only on *JBoss AS 6*, *other containers* throws also some errors, please see the comments below. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 20 07:08:18 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 20 Jan 2012 07:08:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11903) showcase - a4j:push - error on the server side, Unable to resume the suspended connection with latchId In-Reply-To: <1647203784.10826.1326982278758.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <75239559.12965.1327061298562.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? reassigned RF-11903: ------------------------------- Assignee: Juraj Huska > showcase - a4j:push - error on the server side, Unable to resume the suspended connection with latchId > ------------------------------------------------------------------------------------------------------- > > Key: RF-11903 > URL: https://issues.jboss.org/browse/RF-11903 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll, showcase, third-party > Affects Versions: 4.1.0.Final > Environment: container: JBoss AS 6.0.0.Final, JBoss AS 7.0.2.Final, JBoss AS 7.1.0.CR1b > browsers: all > application: showcase 4.2.0-SNAPSHOT > Reporter: Juraj Huska > Assignee: Juraj Huska > Fix For: 4.2.0.CR1 > > > *All* demos for 14j:push are causing *error* on the server side when it is pushing something to them: > {code} > 15:03:42,962 ERROR [org.atmosphere.container.BlockingIOCometSupport] Unable to resume the suspended connection with latchId: 11597405 > {code} > Note that the latchId is for each push different. *The functionality* however remains *ok*, at least for Topics context usage and JMS push. > This particular error is thrown only on *JBoss AS 6*, *other containers* throws also some errors, please see the comments below. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 20 07:08:18 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 20 Jan 2012 07:08:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11903) showcase - a4j:push - error on the server side, Unable to resume the suspended connection with latchId In-Reply-To: <1647203784.10826.1326982278758.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <470443374.12967.1327061298651.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated RF-11903: ---------------------------- Fix Version/s: 4.2.0.CR1 > showcase - a4j:push - error on the server side, Unable to resume the suspended connection with latchId > ------------------------------------------------------------------------------------------------------- > > Key: RF-11903 > URL: https://issues.jboss.org/browse/RF-11903 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll, showcase, third-party > Affects Versions: 4.1.0.Final > Environment: container: JBoss AS 6.0.0.Final, JBoss AS 7.0.2.Final, JBoss AS 7.1.0.CR1b > browsers: all > application: showcase 4.2.0-SNAPSHOT > Reporter: Juraj Huska > Assignee: Juraj Huska > Fix For: 4.2.0.CR1 > > > *All* demos for 14j:push are causing *error* on the server side when it is pushing something to them: > {code} > 15:03:42,962 ERROR [org.atmosphere.container.BlockingIOCometSupport] Unable to resume the suspended connection with latchId: 11597405 > {code} > Note that the latchId is for each push different. *The functionality* however remains *ok*, at least for Topics context usage and JMS push. > This particular error is thrown only on *JBoss AS 6*, *other containers* throws also some errors, please see the comments below. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 20 07:10:19 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 20 Jan 2012 07:10:19 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11471) Upgrade to Atmosphere 0.8.4 In-Reply-To: <1090154337.14335.1318029736037.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1060857186.12972.1327061419074.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved RF-11471. ----------------------------- Resolution: Done It seems bug was resolved with upgrading to {{0.8.4}}, needs to be checked in RF-11903 and RFPL-1978 > Upgrade to Atmosphere 0.8.4 > --------------------------- > > Key: RF-11471 > URL: https://issues.jboss.org/browse/RF-11471 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: component-push/poll, third-party > Affects Versions: 4.1.0.Milestone3 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Priority: Critical > Fix For: 4.2.0.CR1 > > > Atmosphere 0.8.0-RC2 is planned to be released [1] on right on 4.1.0.M3 code-freeze, we will wait before start of QE cycle to grab this release. > [1] http://groups.google.com/group/atmosphere-framework/browse_thread/thread/caffae0c616c250a -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 20 07:12:18 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 20 Jan 2012 07:12:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11483) Elegant way for Push topic creating In-Reply-To: <11494155.16954.1318245975997.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <395362621.12975.1327061538319.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated RF-11483: ---------------------------- Priority: Critical (was: Major) Forum Reference: http://community.jboss.org/message/630871#630871 (was: http://community.jboss.org/message/630871#630871) > Elegant way for Push topic creating > ----------------------------------- > > Key: RF-11483 > URL: https://issues.jboss.org/browse/RF-11483 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-push/poll, core > Affects Versions: 4.1.0.Milestone1 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Priority: Critical > Fix For: 4.2.0.CR1 > > > Currently, topics have to be initialized with similar class: > https://github.com/richfaces/showcase/blob/4.1.0.20110910-M2/src/main/java/org/richfaces/demo/push/TopicsInitializer.java > I suggest to create topic on demand (lazily), when it is accessed first. > It needs following changes: > * {{PushRendererBase}} - will create Topic for @address attribute > * {{JMSTopicsContextImpl}} - will create topic when JMS message received > * {{PushObserverMethod}} - will create topic when @Push event for given topic observed > * ... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 20 07:17:18 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 20 Jan 2012 07:17:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11907) Push: add configuration switch for PushContext initialization on startup (org.richfaces.push.initializeOnStartup) In-Reply-To: <377172022.12977.1327061838297.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1152490790.12978.1327061838339.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated RF-11907: ---------------------------- Summary: Push: add configuration switch for PushContext initialization on startup (org.richfaces.push.initializeOnStartup) (was: Push: added context-param switch for PushContext initialization on startup (org.richfaces.push.initializeOnStartup)) > Push: add configuration switch for PushContext initialization on startup (org.richfaces.push.initializeOnStartup) > ----------------------------------------------------------------------------------------------------------------- > > Key: RF-11907 > URL: https://issues.jboss.org/browse/RF-11907 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 4.2.0.CR1 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 4.2.0.CR1 > > > For applications like Showcase which are accessing {{TopicsContext}} from non-{{FacesContext}} threads, > {{PushContext}} needs to be initialized from the thread which have {{FacesContext}}/{{ExternalContext}} > accessible. > These applications are typically pushing messages to the topic periodically > or they receive messages externally (JMS). > New switch {{org.richfaces.push.initializeOnStartup}} should be {{false}} by default, > since regular usage of Push does not require so early initialization. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 20 07:17:18 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 20 Jan 2012 07:17:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11907) Push: added context-param switch for PushContext initialization on startup (org.richfaces.push.initializeOnStartup) Message-ID: <377172022.12977.1327061838297.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Luk?? Fry? created RF-11907: ------------------------------- Summary: Push: added context-param switch for PushContext initialization on startup (org.richfaces.push.initializeOnStartup) Key: RF-11907 URL: https://issues.jboss.org/browse/RF-11907 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Components: core Affects Versions: 4.2.0.CR1 Reporter: Luk?? Fry? Assignee: Luk?? Fry? Fix For: 4.2.0.CR1 For applications like Showcase which are accessing {{TopicsContext}} from non-{{FacesContext}} threads, {{PushContext}} needs to be initialized from the thread which have {{FacesContext}}/{{ExternalContext}} accessible. These applications are typically pushing messages to the topic periodically or they receive messages externally (JMS). New switch {{org.richfaces.push.initializeOnStartup}} should be {{false}} by default, since regular usage of Push does not require so early initialization. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 20 07:48:18 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 20 Jan 2012 07:48:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11483) Elegant way for Push topic creating In-Reply-To: <11494155.16954.1318245975997.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <734206515.13017.1327063698236.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved RF-11483. ----------------------------- Resolution: Done > Elegant way for Push topic creating > ----------------------------------- > > Key: RF-11483 > URL: https://issues.jboss.org/browse/RF-11483 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-push/poll, core > Affects Versions: 4.1.0.Milestone1 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Priority: Critical > Fix For: 4.2.0.CR1 > > > Currently, topics have to be initialized with similar class: > https://github.com/richfaces/showcase/blob/4.1.0.20110910-M2/src/main/java/org/richfaces/demo/push/TopicsInitializer.java > I suggest to create topic on demand (lazily), when it is accessed first. > It needs following changes: > * {{PushRendererBase}} - will create Topic for @address attribute > * {{JMSTopicsContextImpl}} - will create topic when JMS message received > * {{PushObserverMethod}} - will create topic when @Push event for given topic observed > * ... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 20 07:50:18 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 20 Jan 2012 07:50:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11907) Push: add configuration switch for PushContext initialization on startup (org.richfaces.push.initializeOnStartup) In-Reply-To: <377172022.12977.1327061838297.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <519990275.13019.1327063818320.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved RF-11907. ----------------------------- Resolution: Done > Push: add configuration switch for PushContext initialization on startup (org.richfaces.push.initializeOnStartup) > ----------------------------------------------------------------------------------------------------------------- > > Key: RF-11907 > URL: https://issues.jboss.org/browse/RF-11907 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 4.2.0.CR1 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 4.2.0.CR1 > > > For applications like Showcase which are accessing {{TopicsContext}} from non-{{FacesContext}} threads, > {{PushContext}} needs to be initialized from the thread which have {{FacesContext}}/{{ExternalContext}} > accessible. > These applications are typically pushing messages to the topic periodically > or they receive messages externally (JMS). > New switch {{org.richfaces.push.initializeOnStartup}} should be {{false}} by default, > since regular usage of Push does not require so early initialization. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 20 07:50:18 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 20 Jan 2012 07:50:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11906) Warning when JMS integration is off but JMS is available In-Reply-To: <655659084.12635.1327049658286.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <760707670.13020.1327063818362.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? reassigned RF-11906: ------------------------------- Assignee: Luk?? Fry? > Warning when JMS integration is off but JMS is available > -------------------------------------------------------- > > Key: RF-11906 > URL: https://issues.jboss.org/browse/RF-11906 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: core > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 4.2.0.CR1 > > > For JMS detection, following algorithms can be used: > * JMS API class detection > * JNDI binding {{java://ConnectionFactory}} can be checked > {{PushServlet}} can be used as place for triggering detection. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 20 08:16:18 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 20 Jan 2012 08:16:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11892) Push: turn off JMS integration by default In-Reply-To: <985205215.6984.1326877458621.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <2083039711.13099.1327065378473.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated RF-11892: ---------------------------- Description: On team meeting [1], we have discussed necessity to simplify configuration of Push in order to simplify starting with push for new users. I suggest to replace current configuration {{org.richfaces.push.jms.disable}} with {{org.richfaces.push.jms.enabled}}, leaving previous one with no effect or providing warning. [1] https://community.jboss.org/wiki/RichFacesTeamMeetingAgenda2012-01-17 was: On team meeting [1], we have discussed necessity to simplify configuration of Push in order to simplify starting with push for new users. I suggest to replace current configuration {{org.richfaces.push.jms.disable}} with {{org.richfaces.push.jms.enable}}, leaving previous one with no effect or providing warning. [1] https://community.jboss.org/wiki/RichFacesTeamMeetingAgenda2012-01-17 > Push: turn off JMS integration by default > ----------------------------------------- > > Key: RF-11892 > URL: https://issues.jboss.org/browse/RF-11892 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: component-push/poll > Affects Versions: 4.0.0.Final, 4.1.0.Final > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 4.2.0.CR1 > > > On team meeting [1], we have discussed necessity to simplify configuration of Push in order to simplify starting with push for new users. > I suggest to replace current configuration {{org.richfaces.push.jms.disable}} > with {{org.richfaces.push.jms.enabled}}, leaving previous one with no effect > or providing warning. > [1] https://community.jboss.org/wiki/RichFacesTeamMeetingAgenda2012-01-17 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 20 08:23:18 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 20 Jan 2012 08:23:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11892) Push: turn off JMS integration by default In-Reply-To: <985205215.6984.1326877458621.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <572867013.13111.1327065798517.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved RF-11892. ----------------------------- Resolution: Done > Push: turn off JMS integration by default > ----------------------------------------- > > Key: RF-11892 > URL: https://issues.jboss.org/browse/RF-11892 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: component-push/poll > Affects Versions: 4.0.0.Final, 4.1.0.Final > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 4.2.0.CR1 > > > On team meeting [1], we have discussed necessity to simplify configuration of Push in order to simplify starting with push for new users. > I suggest to replace current configuration {{org.richfaces.push.jms.disable}} > with {{org.richfaces.push.jms.enabled}}, leaving previous one with no effect > or providing warning. > [1] https://community.jboss.org/wiki/RichFacesTeamMeetingAgenda2012-01-17 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 20 09:02:18 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 20 Jan 2012 09:02:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11906) Warning when JMS integration is off but JMS is available In-Reply-To: <655659084.12635.1327049658286.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <2040008678.13186.1327068138215.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved RF-11906. ----------------------------- Resolution: Done > Warning when JMS integration is off but JMS is available > -------------------------------------------------------- > > Key: RF-11906 > URL: https://issues.jboss.org/browse/RF-11906 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: core > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 4.2.0.CR1 > > > For JMS detection, following algorithms can be used: > * JMS API class detection > * JNDI binding {{java://ConnectionFactory}} can be checked > {{PushServlet}} can be used as place for triggering detection. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 20 09:58:18 2012 From: jira-events at lists.jboss.org (Todd Gould (JIRA)) Date: Fri, 20 Jan 2012 09:58:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11908) rich:datascroller not scrolling rich:dataGrid Message-ID: <938472980.13390.1327071498619.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Todd Gould created RF-11908: ------------------------------- Summary: rich:datascroller not scrolling rich:dataGrid Key: RF-11908 URL: https://issues.jboss.org/browse/RF-11908 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component Affects Versions: 3.3.3.Final Environment: Windows OS in JBoss 5.1 Reporter: Todd Gould The rich:dataScroller does not work with the rich:dataGrid component. The datascroller represents the proper number of pages for the data in the dataGrid. However, when I select any of the datascroller controlls, the ajax request processes (as witnessed via the associated status), but the dataGrid remains on the first page. Nothing seems to be able to make it progress to another page. No ajax or other errors are generated and all appears to function well except that the datGrid does not scroll. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 20 10:06:18 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 20 Jan 2012 10:06:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11909) Custom resource mapping can't simply reuse pre-generated RichFaces resources Message-ID: <42430590.13417.1327071978848.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Luk?? Fry? created RF-11909: ------------------------------- Summary: Custom resource mapping can't simply reuse pre-generated RichFaces resources Key: RF-11909 URL: https://issues.jboss.org/browse/RF-11909 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: core Affects Versions: 4.1.0.Final Reporter: Luk?? Fry? Assignee: Luk?? Fry? Fix For: 4.2.0.CR1 Following configuration of location is needed: {code} org.richfaces.resourceMapping.location #{facesContext.externalContext.requestContextPath}/org.richfaces.resources/javax.faces.resource/org.richfaces.staticResource/#{a4j.version.implementationVersion}/%Features%/#{resourceLocation} {code} But that means you need to place custom resources to directory called specifically for RF: {code} ${WAR}/resources/org.richfaces.staticResource/4.1.0.Final/Packed/. {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 Jan 20 10:06:21 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 20 Jan 2012 10:06:21 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11909) Custom resource mapping can't simply reuse pre-generated RichFaces resources In-Reply-To: <42430590.13417.1327071978848.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <932870533.13440.1327071981219.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12660796#comment-12660796 ] Luk?? Fry? commented on RF-11909: --------------------------------- This will just need change of default values and pre-generated resource mapping files. > Custom resource mapping can't simply reuse pre-generated RichFaces resources > ---------------------------------------------------------------------------- > > Key: RF-11909 > URL: https://issues.jboss.org/browse/RF-11909 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 4.1.0.Final > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 4.2.0.CR1 > > > Following configuration of location is needed: > {code} > > org.richfaces.resourceMapping.location > #{facesContext.externalContext.requestContextPath}/org.richfaces.resources/javax.faces.resource/org.richfaces.staticResource/#{a4j.version.implementationVersion}/%Features%/#{resourceLocation} > > {code} > But that means you need to place custom resources to directory called specifically for RF: > {code} > ${WAR}/resources/org.richfaces.staticResource/4.1.0.Final/Packed/. > {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 Jan 20 10:08:18 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 20 Jan 2012 10:08:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11909) Custom resource mapping can't simply reuse pre-generated RichFaces resources In-Reply-To: <42430590.13417.1327071978848.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <806081353.13445.1327072098596.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated RF-11909: ---------------------------- Forum Reference: https://community.jboss.org/message/647859#647859 > Custom resource mapping can't simply reuse pre-generated RichFaces resources > ---------------------------------------------------------------------------- > > Key: RF-11909 > URL: https://issues.jboss.org/browse/RF-11909 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 4.1.0.Final > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 4.2.0.CR1 > > > Following configuration of location is needed: > {code} > > org.richfaces.resourceMapping.location > #{facesContext.externalContext.requestContextPath}/org.richfaces.resources/javax.faces.resource/org.richfaces.staticResource/#{a4j.version.implementationVersion}/%Features%/#{resourceLocation} > > {code} > But that means you need to place custom resources to directory called specifically for RF: > {code} > ${WAR}/resources/org.richfaces.staticResource/4.1.0.Final/Packed/. > {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 Jan 20 10:18:19 2012 From: jira-events at lists.jboss.org (Jean ANDRE (JIRA)) Date: Fri, 20 Jan 2012 10:18:19 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11750) onter() on nested tab In-Reply-To: <1869736783.50711.1322577760839.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <2013623411.13512.1327072699725.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean ANDRE updated RF-11750: ---------------------------- Summary: onter() on nested tab (was: onter() with nested tab) > onter() on nested tab > --------------------- > > Key: RF-11750 > URL: https://issues.jboss.org/browse/RF-11750 > 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 > Fix For: 4.Future > > Attachments: screenshot-1.jpg, screenshot-2.jpg, screenshot-3.jpg > > > We put onenter() on tabs, because the actionlistener does not work very well on the first click. Some tabs are static while other are dynamically constructed. Tabs are created after a search and a new tab is created with a list of items. When a user click on item list, the content of the tab is refreshed to display detailed information. These information are displayed also inside 6 static tabs. > The problems comes when we click/select these static tabs. Selecting theses tabs, trigger the onter() of the parent tab even if we stay all the time on the parent tab.... > We do not known if this behavior is normal or not. > The following code is the dynamic tab construction - Note the onenter() > {code} > > > > > > > > > > > > > > > value="#{msg[desktopTabController.toggleSearchLabel]}" > actionListener="#{desktopTabController.doToggleSearch}" > render="toggleSearchOutput" > immediate="true"> > >
>
> > > > > > > > > > > > > > > > > > > styleClass="closeButton" > action="#{desktopTabController.doCloseTab(tab.id)}" /> > > > > > > > > > > > > > > > > > > > {code} > The onenter function definition. This function set only the selectedTab variable in the backing bean > {code} > > > > {code} > The onenter function inside the backing-bean > {code} > public String doEnterTab() { > // we just need to set the activeTab because actionListener is not working > // for the first click - Bug has been reported by other users. > return OUTCOME_DESKTOP; > } > {code} > The following code is the nested tabs - Those tabs appears when the use click on the item from a list. > {code} > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > {code} > Then, each time we click on these nested tabs, the parent tab call the onenter(). > See the screen capture for better understanding of the scenario. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 20 10:20:19 2012 From: jira-events at lists.jboss.org (Jean ANDRE (JIRA)) Date: Fri, 20 Jan 2012 10:20:19 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11750) onter() on nested tab In-Reply-To: <1869736783.50711.1322577760839.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <804076124.13540.1327072819317.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean ANDRE updated RF-11750: ---------------------------- Description: We put onenter() on tabs, because the actionlistener does not work very well on the first click. Some tabs are static while other are dynamically constructed. Tabs are created after a search and a new tab is created with a list of items. When a user click on item list, the content of the tab is refreshed to display detailed information. These information are displayed also inside 6 static tabs. The problems comes when we click/select these static tabs. Selecting theses tabs, trigger the onter() of the parent tab even if we stay all the time on the parent tab.... The expected behavior is to receive the event on the sub-tab instead of its parent. We do not known if this behavior is normal or not. The following code is the dynamic tab construction - Note the onenter() {code}

{code} The onenter function definition. This function set only the selectedTab variable in the backing bean {code} {code} The onenter function inside the backing-bean {code} public String doEnterTab() { // we just need to set the activeTab because actionListener is not working // for the first click - Bug has been reported by other users. return OUTCOME_DESKTOP; } {code} The following code is the nested tabs - Those tabs appears when the use click on the item from a list. {code} {code} Then, each time we click on these nested tabs, the parent tab call the onenter(). See the screen capture for better understanding of the scenario. was: We put onenter() on tabs, because the actionlistener does not work very well on the first click. Some tabs are static while other are dynamically constructed. Tabs are created after a search and a new tab is created with a list of items. When a user click on item list, the content of the tab is refreshed to display detailed information. These information are displayed also inside 6 static tabs. The problems comes when we click/select these static tabs. Selecting theses tabs, trigger the onter() of the parent tab even if we stay all the time on the parent tab.... We do not known if this behavior is normal or not. The following code is the dynamic tab construction - Note the onenter() {code}

{code} The onenter function definition. This function set only the selectedTab variable in the backing bean {code} {code} The onenter function inside the backing-bean {code} public String doEnterTab() { // we just need to set the activeTab because actionListener is not working // for the first click - Bug has been reported by other users. return OUTCOME_DESKTOP; } {code} The following code is the nested tabs - Those tabs appears when the use click on the item from a list. {code} {code} Then, each time we click on these nested tabs, the parent tab call the onenter(). See the screen capture for better understanding of the scenario. > onter() on nested tab > --------------------- > > Key: RF-11750 > URL: https://issues.jboss.org/browse/RF-11750 > 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 > Fix For: 4.Future > > Attachments: screenshot-1.jpg, screenshot-2.jpg, screenshot-3.jpg > > > We put onenter() on tabs, because the actionlistener does not work very well on the first click. Some tabs are static while other are dynamically constructed. Tabs are created after a search and a new tab is created with a list of items. When a user click on item list, the content of the tab is refreshed to display detailed information. These information are displayed also inside 6 static tabs. > The problems comes when we click/select these static tabs. Selecting theses tabs, trigger the onter() of the parent tab even if we stay all the time on the parent tab.... The expected behavior is to receive the event on the sub-tab instead of its parent. > We do not known if this behavior is normal or not. > The following code is the dynamic tab construction - Note the onenter() > {code} > > > > > > > > > > > > > > > value="#{msg[desktopTabController.toggleSearchLabel]}" > actionListener="#{desktopTabController.doToggleSearch}" > render="toggleSearchOutput" > immediate="true"> > >
>
> > > > > > > > > > > > > > > > > > > styleClass="closeButton" > action="#{desktopTabController.doCloseTab(tab.id)}" /> > > > > > > > > > > > > > > > > > > > {code} > The onenter function definition. This function set only the selectedTab variable in the backing bean > {code} > > > > {code} > The onenter function inside the backing-bean > {code} > public String doEnterTab() { > // we just need to set the activeTab because actionListener is not working > // for the first click - Bug has been reported by other users. > return OUTCOME_DESKTOP; > } > {code} > The following code is the nested tabs - Those tabs appears when the use click on the item from a list. > {code} > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > {code} > Then, each time we click on these nested tabs, the parent tab call the onenter(). > See the screen capture for better understanding of the scenario. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 20 10:26:18 2012 From: jira-events at lists.jboss.org (Jean ANDRE (JIRA)) Date: Fri, 20 Jan 2012 10:26:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11750) onter() on nested tab In-Reply-To: <1869736783.50711.1322577760839.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1901615713.13589.1327073178743.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12660807#comment-12660807 ] Jean ANDRE commented on RF-11750: --------------------------------- With the 4.1.0 final, the behavior seems to be changed - The onenter on a sub-tab is not working anymore - We have to choose a different event such as onheaderclick. Does it means that we cannot use the same event on tabPanel and its sub-TabPanel ???? However onheaderclick is not an equivalent to onenter since a tab can be selected other than a click.... > onter() on nested tab > --------------------- > > Key: RF-11750 > URL: https://issues.jboss.org/browse/RF-11750 > 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 > Fix For: 4.Future > > Attachments: screenshot-1.jpg, screenshot-2.jpg, screenshot-3.jpg > > > We put onenter() on tabs, because the actionlistener does not work very well on the first click. Some tabs are static while other are dynamically constructed. Tabs are created after a search and a new tab is created with a list of items. When a user click on item list, the content of the tab is refreshed to display detailed information. These information are displayed also inside 6 static tabs. > The problems comes when we click/select these static tabs. Selecting theses tabs, trigger the onter() of the parent tab even if we stay all the time on the parent tab.... The expected behavior is to receive the event on the sub-tab instead of its parent. > We do not known if this behavior is normal or not. > The following code is the dynamic tab construction - Note the onenter() > {code} > > > > > > > > > > > > > > > value="#{msg[desktopTabController.toggleSearchLabel]}" > actionListener="#{desktopTabController.doToggleSearch}" > render="toggleSearchOutput" > immediate="true"> > >
>
> > > > > > > > > > > > > > > > > > > styleClass="closeButton" > action="#{desktopTabController.doCloseTab(tab.id)}" /> > > > > > > > > > > > > > > > > > > > {code} > The onenter function definition. This function set only the selectedTab variable in the backing bean > {code} > > > > {code} > The onenter function inside the backing-bean > {code} > public String doEnterTab() { > // we just need to set the activeTab because actionListener is not working > // for the first click - Bug has been reported by other users. > return OUTCOME_DESKTOP; > } > {code} > The following code is the nested tabs - Those tabs appears when the use click on the item from a list. > {code} > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > {code} > Then, each time we click on these nested tabs, the parent tab call the onenter(). > See the screen capture for better understanding of the scenario. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 20 11:18:18 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 20 Jan 2012 11:18:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11910) Showcase: reduntant MANIFEST.MF, it is configured in pom.xml and also in resources Message-ID: <850752854.13850.1327076298214.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Luk?? Fry? created RF-11910: ------------------------------- Summary: Showcase: reduntant MANIFEST.MF, it is configured in pom.xml and also in resources Key: RF-11910 URL: https://issues.jboss.org/browse/RF-11910 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: showcase Affects Versions: 4.1.0.Final Reporter: Luk?? Fry? These files should be merged, and only {{pom.xml}} should be used preferably. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 20 11:30:18 2012 From: jira-events at lists.jboss.org (Ronan Silva (JIRA)) Date: Fri, 20 Jan 2012 11:30:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-10930) calendar: decode of the behavior not occurs for custom events In-Reply-To: <293799868.33581.1303119933220.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <905546232.13864.1327077018529.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-10930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12660835#comment-12660835 ] Ronan Silva commented on RF-10930: ---------------------------------- What workAround this issue??? Please, Can do you post an exempla??? I tried, but don't work the event inputchange: -------------------------------------------------------------------------------------------------- --------------------------------------------------------------------------------------- Thank's... > calendar: decode of the behavior not occurs for custom events > ------------------------------------------------------------- > > Key: RF-10930 > URL: https://issues.jboss.org/browse/RF-10930 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: base functionality , component-input > Affects Versions: 4.0.0.Final > Reporter: Ilya Shaikovsky > Fix For: 4.Future > > > see forum post. checked at rf-showcase and confirmed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 20 12:08:18 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 20 Jan 2012 12:08:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11909) Custom resource mapping can't simply reuse pre-generated RichFaces resources In-Reply-To: <42430590.13417.1327071978848.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <657506238.13898.1327079298875.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12660839#comment-12660839 ] Luk?? Fry? commented on RF-11909: --------------------------------- pushed to {{feature/RF-11909}} > Custom resource mapping can't simply reuse pre-generated RichFaces resources > ---------------------------------------------------------------------------- > > Key: RF-11909 > URL: https://issues.jboss.org/browse/RF-11909 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 4.1.0.Final > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 4.2.0.CR1 > > > Following configuration of location is needed: > {code} > > org.richfaces.resourceMapping.location > #{facesContext.externalContext.requestContextPath}/org.richfaces.resources/javax.faces.resource/org.richfaces.staticResource/#{a4j.version.implementationVersion}/%Features%/#{resourceLocation} > > {code} > But that means you need to place custom resources to directory called specifically for RF: > {code} > ${WAR}/resources/org.richfaces.staticResource/4.1.0.Final/Packed/. > {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 Jan 20 12:29:18 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Fri, 20 Jan 2012 12:29:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11886) Style of the panelMenu changed from 4.1 In-Reply-To: <383594832.626.1326705438390.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <872703361.13912.1327080558308.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-11886: ------------------------------- Fix Version/s: (was: 4.2.0.CR1) Labels: (was: regression) > Style of the panelMenu changed from 4.1 > --------------------------------------- > > Key: RF-11886 > URL: https://issues.jboss.org/browse/RF-11886 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: showcase > Affects Versions: 4.1.0.Final > Environment: Showcase > Reporter: Luk?? Fry? > Priority: Minor > Attachments: new.png, old.png > > > On the screenshots, there is visual change of panelMenu from 4.1 (http://showcase.richfaces.org/), > the border around the panelMenu has been 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 Jan 20 12:29:18 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Fri, 20 Jan 2012 12:29:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11850) RF 4.1.0.Final: Problem using columnResize with more than one extendedDataTable on the same page. In-Reply-To: <1719236551.29235.1324550769802.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1811182525.13915.1327080558472.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem reassigned RF-11850: ---------------------------------- Assignee: Brian Leathem > RF 4.1.0.Final: Problem using columnResize with more than one extendedDataTable on the same page. > ------------------------------------------------------------------------------------------------- > > Key: RF-11850 > URL: https://issues.jboss.org/browse/RF-11850 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.1.0.Final > Environment: Windows 7 x64 or arch linux x86 > JBoss 7.0.1 Final or Glassfish 3.1 > Reporter: Christian Peter > Assignee: Brian Leathem > Priority: Minor > Fix For: 4.2.0.CR1 > > > Hello, > I've encountered some problems using richfaces extendedDataTables in RichFace 4.1.0.Final > Here is the facelet: > {code:title=facelet} > > > > Header7 > #{item.name} > > > > Header8 > #{item.uuid} > > > > Header9 > #{item.uuid} > > > > Header10 > #{item.uuid} > > > > > > > > > > Header7 > #{item.name} > > > > Header8 > #{item.uuid} > > > Header9 > #{item.uuid} > > > > Header10 > #{item.uuid} > > > > > > {code} > > Resizing the columns on the first table works perfectly, but if someone tries to resize the second tables' columns as well, I've got NullPointer exceptions like: > {code:title=stacktrace} > java.lang.NullPointerException > at org.richfaces.renderkit.SortingFilteringRowsRenderer.updateAttribute(SortingFilteringRowsRenderer.java:135) [richfaces-components-ui-4.1.0.Final.jar: > at org.richfaces.renderkit.ExtendedDataTableRenderer.updateWidthOfColumns(ExtendedDataTableRenderer.java:825) [richfaces-components-ui-4.1.0.Final.jar:] > at org.richfaces.renderkit.ExtendedDataTableRenderer.doDecode(ExtendedDataTableRenderer.java:808) [richfaces-components-ui-4.1.0.Final.jar:] > at org.richfaces.renderkit.RendererBase.decode(RendererBase.java:80) [richfaces-components-ui-4.1.0.Final.jar:] > at javax.faces.component.UIComponentBase.decode(UIComponentBase.java:787) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at org.richfaces.component.UIDataAdaptor.processDecodes(UIDataAdaptor.java:819) [richfaces-components-ui-4.1.0.Final.jar:] > at org.richfaces.context.PartialViewExecuteVisitCallback.visit(PartialViewExecuteVisitCallback.java:53) [richfaces-core-impl-4.1.0.Final.jar:] > at org.richfaces.context.BaseExtendedVisitContext.invokeVisitCallback(BaseExtendedVisitContext.java:321) [richfaces-core-impl-4.1.0.Final.jar:] > at org.richfaces.component.UIDataAdaptor.visitTree(UIDataAdaptor.java:1319) [richfaces-components-ui-4.1.0.Final.jar:] > at javax.faces.component.UIComponent.visitTree(UIComponent.java:1600) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at javax.faces.component.UIForm.visitTree(UIForm.java:344) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at javax.faces.component.UIComponent.visitTree(UIComponent.java:1600) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at javax.faces.component.UIComponent.visitTree(UIComponent.java:1600) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at org.richfaces.context.ExtendedPartialViewContextImpl.executeComponents(ExtendedPartialViewContextImpl.java:237) [richfaces-core-impl-4.1.0.Final.jar: > at org.richfaces.context.ExtendedPartialViewContextImpl.processPartialExecutePhase(ExtendedPartialViewContextImpl.java:217) [richfaces-core-impl-4.1.0.F > at org.richfaces.context.ExtendedPartialViewContextImpl.processPartial(ExtendedPartialViewContextImpl.java:196) [richfaces-core-impl-4.1.0.Final.jar:] > at javax.faces.component.UIViewRoot.processDecodes(UIViewRoot.java:931) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] > at com.sun.faces.lifecycle.ApplyRequestValuesPhase.execute(ApplyRequestValuesPhase.java:78) [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 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] > {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 Jan 20 12:29:18 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Fri, 20 Jan 2012 12:29:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11765) Datatable footer cell doesn't use all columns (wrong colspan generated) In-Reply-To: <249178125.59139.1322705200743.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <75686927.13917.1327080558760.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem reassigned RF-11765: ---------------------------------- Assignee: Brian Leathem > Datatable footer cell doesn't use all columns (wrong colspan generated) > ----------------------------------------------------------------------- > > Key: RF-11765 > URL: https://issues.jboss.org/browse/RF-11765 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.1.0.CR1 > Reporter: Karsten Wutzke > Assignee: Brian Leathem > Labels: colspan, dataTable, footer > Fix For: 4.2.0.CR1 > > > When specifying a datatable's header with rich:columnGroup and a rich:column in the tbody that has rendered="#{rowKeyNbr eq 0}" the wrong colspan for the table footer cell is generated. > For more details, code, and images please see the forum thread: > http://community.jboss.org/message/639211 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 20 12:44:18 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Fri, 20 Jan 2012 12:44:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11836) Replace ${project.version} definitions in the poms with actual version In-Reply-To: <150403957.24272.1324386369523.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <842489158.13925.1327081458508.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-11836: ------------------------------- Fix Version/s: (was: 4.2.0.CR1) The description of this issue says it's a requirement for getting into maven central. From where was this requirement determined? On a related note, RichFaces is now in maven central: http://search.maven.org/#search|richfaces > Replace ${project.version} definitions in the poms with actual version > ---------------------------------------------------------------------- > > Key: RF-11836 > URL: https://issues.jboss.org/browse/RF-11836 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 4.1.0.Final > Reporter: Luk?? Fry? > Assignee: Brian Leathem > > This is requirement for uploading to Maven Central. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 20 14:08:18 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Fri, 20 Jan 2012 14:08:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11898) Attaching a contextMenu to a h:graphicImage results in a contextMenu that does not display In-Reply-To: <1893634399.8909.1326918978241.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <222308115.14119.1327086498194.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12660850#comment-12660850 ] Brian Leathem commented on RF-11898: ------------------------------------ ContextMenu works with graphicImage when you set _attached="false"_ on the contextMenu. > Attaching a contextMenu to a h:graphicImage results in a contextMenu that does not display > ------------------------------------------------------------------------------------------ > > Key: RF-11898 > URL: https://issues.jboss.org/browse/RF-11898 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-menu > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 4.2.0.CR1 > > > Attaching a contextMenu to a h:graphicImage results in a contextMenu that does not display. Wrapping the image with a panelGroup, and attaching the contextMenu to that panelGroup instead does not cause a 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 Fri Jan 20 15:04:18 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Fri, 20 Jan 2012 15:04:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11898) Attaching a contextMenu to a h:graphicImage results in a contextMenu that does not display In-Reply-To: <1893634399.8909.1326918978241.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <874109598.14190.1327089858215.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12660861#comment-12660861 ] Brian Leathem commented on RF-11898: ------------------------------------ The initial contextMenu implementation used _attached_ to determine whether or not to attach the contextMenu to the attachId DOM. This is different than the RF3 contextMenu, where the _attached_ attribute determines whether or not the context menu is attached to the event of the parent menu. Resolving this issue, by adjusting the _attached_ semantics of the RichFaces 4 contextMenu to match that of the RichFaces 3 one. > Attaching a contextMenu to a h:graphicImage results in a contextMenu that does not display > ------------------------------------------------------------------------------------------ > > Key: RF-11898 > URL: https://issues.jboss.org/browse/RF-11898 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-menu > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 4.2.0.CR1 > > > Attaching a contextMenu to a h:graphicImage results in a contextMenu that does not display. Wrapping the image with a panelGroup, and attaching the contextMenu to that panelGroup instead does not cause a 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 Fri Jan 20 15:13:18 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Fri, 20 Jan 2012 15:13:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11898) Attaching a contextMenu to a h:graphicImage results in a contextMenu that does not display In-Reply-To: <1893634399.8909.1326918978241.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1513227572.14199.1327090398691.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-11898. -------------------------------- Resolution: Done Changed the _attached_ semantics of the contextMenu > Attaching a contextMenu to a h:graphicImage results in a contextMenu that does not display > ------------------------------------------------------------------------------------------ > > Key: RF-11898 > URL: https://issues.jboss.org/browse/RF-11898 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-menu > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 4.2.0.CR1 > > > Attaching a contextMenu to a h:graphicImage results in a contextMenu that does not display. Wrapping the image with a panelGroup, and attaching the contextMenu to that panelGroup instead does not cause a 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 Fri Jan 20 16:39:18 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Fri, 20 Jan 2012 16:39:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11900) contextMenu has to be defined after the extendedDatatable, or it cannot attach In-Reply-To: <1920914566.9002.1326921858188.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <377415249.14506.1327095558415.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12660898#comment-12660898 ] Brian Leathem commented on RF-11900: ------------------------------------ The event listener is registered during the component initialisation. If it cannot find the attachId dom element, the listener does not get registered. A solution is to register the listener in a $(document).ready() handler. > contextMenu has to be defined after the extendedDatatable, or it cannot attach > ------------------------------------------------------------------------------ > > Key: RF-11900 > URL: https://issues.jboss.org/browse/RF-11900 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-menu > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 4.2.0.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 Jan 20 16:39:18 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Fri, 20 Jan 2012 16:39:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11900) contextMenu has to be defined after the extendedDatatable, or it cannot attach In-Reply-To: <1920914566.9002.1326921858188.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <293516220.14517.1327095558917.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-11900. -------------------------------- Resolution: Done > contextMenu has to be defined after the extendedDatatable, or it cannot attach > ------------------------------------------------------------------------------ > > Key: RF-11900 > URL: https://issues.jboss.org/browse/RF-11900 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-menu > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 4.2.0.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 Jan 20 17:33:18 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Fri, 20 Jan 2012 17:33:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11899) the attachId of the contextMenu requires the fully qualified path In-Reply-To: <130287168.8929.1326919578474.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1364827075.14648.1327098798205.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12660919#comment-12660919 ] Brian Leathem commented on RF-11899: ------------------------------------ Resolution: In the template, when passing the _target/attachTo_ id via the _scriptObject_, first pass the _target/attachTo_ id through {code} RENDERER_UTILS.findComponentFor(component, target) {code} > the attachId of the contextMenu requires the fully qualified path > ----------------------------------------------------------------- > > Key: RF-11899 > URL: https://issues.jboss.org/browse/RF-11899 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-menu > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 4.2.0.CR1 > > > Providing an attachId of "pic" for instance is insufficient, one must provide "form:pic". -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 20 17:35:18 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Fri, 20 Jan 2012 17:35:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11899) the attachId of the contextMenu requires the fully qualified path In-Reply-To: <130287168.8929.1326919578474.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1589190857.14649.1327098918215.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-11899. -------------------------------- Resolution: Done > the attachId of the contextMenu requires the fully qualified path > ----------------------------------------------------------------- > > Key: RF-11899 > URL: https://issues.jboss.org/browse/RF-11899 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-menu > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 4.2.0.CR1 > > > Providing an attachId of "pic" for instance is insufficient, one must provide "form:pic". -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 20 17:41:18 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Fri, 20 Jan 2012 17:41:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11911) contextMenu API for attaching to components should match that of tooltip Message-ID: <682996182.14650.1327099278196.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Brian Leathem created RF-11911: ---------------------------------- Summary: contextMenu API for attaching to components should match that of tooltip Key: RF-11911 URL: https://issues.jboss.org/browse/RF-11911 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-menu Reporter: Brian Leathem Assignee: Brian Leathem Priority: Minor Fix For: 4.2.0.CR1 in it's initial implementation, contextMenu uses the _attachTo_ (from RichFaces 3) attribute to target another component and tooltip uses the _target_ attribute for the same purpose. The contextMenu _attachTo_ attribute should be renamed to _target_ to have a consistent API with 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 Fri Jan 20 18:08:18 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Fri, 20 Jan 2012 18:08:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11911) contextMenu API for attaching to components should match that of tooltip In-Reply-To: <682996182.14650.1327099278196.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <275401649.14686.1327100898188.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-11911. -------------------------------- Resolution: Done > contextMenu API for attaching to components should match that of tooltip > ------------------------------------------------------------------------ > > Key: RF-11911 > URL: https://issues.jboss.org/browse/RF-11911 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-menu > Reporter: Brian Leathem > Assignee: Brian Leathem > Priority: Minor > Fix For: 4.2.0.CR1 > > > in it's initial implementation, contextMenu uses the _attachTo_ (from RichFaces 3) attribute to target another component and tooltip uses the _target_ attribute for the same purpose. > The contextMenu _attachTo_ attribute should be renamed to _target_ to have a consistent API with 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 Fri Jan 20 21:07:18 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Fri, 20 Jan 2012 21:07:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11897) menuItems do not inherit the mode of the parent contextMenu In-Reply-To: <647787621.8905.1326918738187.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1883547265.14750.1327111638299.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-11897. -------------------------------- Resolution: Done Abstracted MenuContainer out of ContextMenu and DropDownMenu, so that the menuItem parent lookup code worked with both types of parent. > menuItems do not inherit the mode of the parent contextMenu > ----------------------------------------------------------- > > Key: RF-11897 > URL: https://issues.jboss.org/browse/RF-11897 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-menu > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 4.2.0.CR1 > > > Setting the mode of the contextMenu to "client" does not propagate to the child menuItems. The mode of the menuItem must be set explicitly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 20 21:09:18 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Fri, 20 Jan 2012 21:09:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11904) rich:contextMenu @mode doesn't affect request type In-Reply-To: <1470389961.10951.1326984078257.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1361500944.14752.1327111758231.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem reassigned RF-11904: ---------------------------------- Assignee: J?n Jamrich I believe this is indeed a duplicate of RF-11897. Can you give this a try again, now that RF-11897 has been resolved? > rich:contextMenu @mode doesn't affect request type > -------------------------------------------------- > > Key: RF-11904 > URL: https://issues.jboss.org/browse/RF-11904 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-misc > Environment: RichFaces 4.2.0-SNAPSHOT > Metamer 4.1.1-SNAPSHOT r.${buildNumber} > Mojarra 2.1.3-SNAPSHOT > JBoss AS 7.0.2.Final > Java(TM) SE Runtime Environment 1.6.0_26-b03 @ Linux > Firefox 10.0 @ Linux i686 > ----- > Richfaces component module built after merge to develop branch > Reporter: J?n Jamrich > Assignee: J?n Jamrich > > Since contextMenu should be similar to dropDownMenu, I'm missing behavior controlled by @mode in contextMenu like dropDownMenu. > In dropDownMenu @mode=ajax causes just one request performed when click menu item. No request for @mode=client and only for @mode=server multiple requests (first POST request for page where dropDownMenu triggered request and then multiple GET requests for all associated (referenced) resources such as CSS, JS... > But not for contextMenu. @mode set to client neither ajax doesn't change request type, always is full page refresh performed when click on contextMenu item. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 21 00:02:18 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Sat, 21 Jan 2012 00:02:18 -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: <576361578.14807.1327122138398.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=12660944#comment-12660944 ] Brian Leathem commented on RF-11884: ------------------------------------ Have you tried enabling ie8/9 compatibility mode? This can be done with a tag in your page template. see: http://msdn.microsoft.com/en-us/library/cc288325.aspx > 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 > Labels: waiting_on_user > > 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 Sat Jan 21 00:12:19 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Sat, 21 Jan 2012 00:12:19 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11865) Partial build of component tree for lazy loaded components In-Reply-To: <624327655.47030.1325900949445.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <841003623.14812.1327122739040.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-11865: ------------------------------- Fix Version/s: 4.3-Tracking Forum Reference: http://community.jboss.org/thread/177011 (was: http://community.jboss.org/thread/177011) > Partial build of component tree for lazy loaded components > ---------------------------------------------------------- > > Key: RF-11865 > URL: https://issues.jboss.org/browse/RF-11865 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 4.1.0.Final > Environment: Any > Reporter: Andrew Wheeler > Priority: Minor > Labels: lazy-loaded > Fix For: 4.3-Tracking > > > I often use collapsible panel with switchType="ajax". This prevents the rendering of the content until it is requested by the user. This however does not prevent the component tree from being constructed. In one use-case the panel hides expensive to construct output from a JCR query. It would be nice if RichFaces could place a marker in the component tree and only construct the child elements on the first request. This would improve page rendering and memory usage considerably. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 21 00:12:18 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Sat, 21 Jan 2012 00:12:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11869) showcase - JS warning - Use of getAttributeNodeNS() is deprecated. Use getAttributeNS() instead. In-Reply-To: <905845731.48184.1326107710988.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1850338212.14809.1327122738782.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-11869. -------------------------------- Assignee: Brian Leathem Resolution: Rejected This is an internal error to Firefox, with it's own XUL markup/rendering. > showcase - JS warning - Use of getAttributeNodeNS() is deprecated. Use getAttributeNS() instead. > ------------------------------------------------------------------------------------------------ > > Key: RF-11869 > URL: https://issues.jboss.org/browse/RF-11869 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: showcase > Environment: Firefox 8,9 > Reporter: Juraj Huska > Assignee: Brian Leathem > Priority: Minor > > When the welcome file of showcase is loaded the JS warning is generated: > {code} > Use of getAttributeNodeNS() is deprecated. Use getAttributeNS() instead. > {code} > I was not able to find where the function getAttributeNodeNS() is called. And I have not found any issues which are possibly affected by 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 Jan 21 00:12:19 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Sat, 21 Jan 2012 00:12:19 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11885) RF 4.1 final a4j:push CDI topic is configured In-Reply-To: <880165753.172.1326637038332.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <958909626.14817.1327122739488.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem reassigned RF-11885: ---------------------------------- Assignee: Luk?? Fry? Lukas, has this been covered by your recent fixes to Topic initialisation? > RF 4.1 final a4j:push CDI topic is configured > --------------------------------------------- > > Key: RF-11885 > URL: https://issues.jboss.org/browse/RF-11885 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Affects Versions: 4.1.0.Final > Environment: JBoss 6.0 final > JDK 1.6.0_24 > Reporter: Ibrahim Abu Ghosh > Assignee: Luk?? Fry? > Labels: a4j:push, cdi > > i tried to use a4j:push cdi as in showcase, but my consumer page shows a message (topic 'my topic name' is not configured). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 21 00:14:18 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Sat, 21 Jan 2012 00:14:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11908) rich:datascroller not scrolling rich:dataGrid In-Reply-To: <938472980.13390.1327071498619.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1156948957.14820.1327122858245.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-11908: ------------------------------- Steps to Reproduce: Here is the complete form. As presented the rich:DataGrid will not be scrolled by the scroller. Simply swapping to the very similar rich:dataTable version enclosed in the ui:remove tags will demonstrate that it works properly with that component. Swapping back to the dataGrid version, the datascroller no longer functions. The bug appears to be with either thet datGrid itself and/or the datascroller: {code} {code} was: Here is the complete form. As presented the rich:DataGrid will not be scrolled by the scroller. Simply swapping to the very similar rich:dataTable version enclosed in the ui:remove tags will demonstrate that it works properly with that component. Swapping back to the dataGrid version, the datascroller no longer functions. The bug appears to be with either thet datGrid itself and/or the datascroller: Forum Reference: https://community.jboss.org/message/647269#647269 (was: https://community.jboss.org/message/647269#647269) > rich:datascroller not scrolling rich:dataGrid > --------------------------------------------- > > Key: RF-11908 > URL: https://issues.jboss.org/browse/RF-11908 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component > Affects Versions: 3.3.3.Final > Environment: Windows OS in JBoss 5.1 > Reporter: Todd Gould > > The rich:dataScroller does not work with the rich:dataGrid component. The datascroller represents the proper number of pages for the data in the dataGrid. However, when I select any of the datascroller controlls, the ajax request processes (as witnessed via the associated status), but the dataGrid remains on the first page. Nothing seems to be able to make it progress to another page. No ajax or other errors are generated and all appears to function well except that the datGrid does not scroll. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 21 00:16:18 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Sat, 21 Jan 2012 00:16:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11908) rich:datascroller not scrolling rich:dataGrid In-Reply-To: <938472980.13390.1327071498619.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <2032891094.14823.1327122978396.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem reassigned RF-11908: ---------------------------------- Assignee: Pavol Pitonak QE, please confirm > rich:datascroller not scrolling rich:dataGrid > --------------------------------------------- > > Key: RF-11908 > URL: https://issues.jboss.org/browse/RF-11908 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component > Affects Versions: 3.3.3.Final > Environment: Windows OS in JBoss 5.1 > Reporter: Todd Gould > Assignee: Pavol Pitonak > > The rich:dataScroller does not work with the rich:dataGrid component. The datascroller represents the proper number of pages for the data in the dataGrid. However, when I select any of the datascroller controlls, the ajax request processes (as witnessed via the associated status), but the dataGrid remains on the first page. Nothing seems to be able to make it progress to another page. No ajax or other errors are generated and all appears to function well except that the datGrid does not scroll. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 21 00:20:18 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Sat, 21 Jan 2012 00:20:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11881) Rich Faces 4 can't change jQuery selector In-Reply-To: <1628113380.4505.1326403041921.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <941727031.14825.1327123218262.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-11881: ------------------------------- Fix Version/s: 4.3-Tracking We should namespace our use of jQuery. For instance, put a referernce to it in our RichFaces global: {code} RichFaces.jQuery = jQuery.noConflict(); {code} Unfortunately, RichFaces.$ is already taken... > Rich Faces 4 can't change jQuery selector > ------------------------------------------ > > Key: RF-11881 > URL: https://issues.jboss.org/browse/RF-11881 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Nicola Nick > Fix For: 4.3-Tracking > > > I used Rich Faces 4 in my project. Morover i have to use prototype functionality. > In the last version of rich faces is used only jQuery. The my problem is that i have to reserve $ selector to prototype but i can't do it because i don't know how to change the selector inside richfaces library. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 21 00:22:18 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Sat, 21 Jan 2012 00:22:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11861) richfaces 4.1.Final showcase: Non-resolvable parent POM: Could not find artifact org.richfaces:richfaces-root-parent:pom:4.1.0.Final In-Reply-To: <1704236441.36501.1325599509914.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <914352631.14829.1327123338449.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12660949#comment-12660949 ] Brian Leathem edited comment on RF-11861 at 1/21/12 12:22 AM: -------------------------------------------------------------- RichFaces artifacts are now in maven central. See: http://search.maven.org/#search%7Cga%7Crichfaces was (Author: bleathem): RichFaces artifacts are now in maven central. See: http://search.maven.org/#search|ga > richfaces 4.1.Final showcase: Non-resolvable parent POM: Could not find artifact org.richfaces:richfaces-root-parent:pom:4.1.0.Final > ------------------------------------------------------------------------------------------------------------------------------------ > > Key: RF-11861 > URL: https://issues.jboss.org/browse/RF-11861 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Peter B > Assignee: Brian Leathem > Labels: richfaces > Fix For: 4.2.0.CR1 > > > richfaces showcase for Richfaces 4.1 Final doesn't build. > Problem is that: > {code} > org.richfaces > richfaces-root-parent > 4.1.0.Final > {code} > is not in central maven repository. > Console output: > {code} > [INFO] Scanning for projects... > Downloading: http://repo1.maven.org/maven2/org/richfaces/richfaces-root-parent/4.1.0.Final/richfaces-root-parent-4.1.0.F > inal.pom > [ERROR] The build could not read 1 project -> [Help 1] > [ERROR] > [ERROR] The project org.richfaces.examples:richfaces-showcase:4.1.0.Final (D:\tmp\richfaces-showcase-77c6701\pom.xml) > has 1 error > [ERROR] Non-resolvable parent POM: Could not find artifact org.richfaces:richfaces-root-parent:pom:4.1.0.Final in ce > ntral (http://repo1.maven.org/maven2) and 'parent.relativePath' points at wrong local POM @ line 8, column 13 -> [Help 2 > ] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please read the following articles: > [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException > [ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException > {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 Jan 21 00:22:18 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Sat, 21 Jan 2012 00:22:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11861) richfaces 4.1.Final showcase: Non-resolvable parent POM: Could not find artifact org.richfaces:richfaces-root-parent:pom:4.1.0.Final In-Reply-To: <1704236441.36501.1325599509914.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1034800112.14827.1327123338378.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-11861. -------------------------------- Assignee: Brian Leathem Fix Version/s: 4.2.0.CR1 Resolution: Done RichFaces artifacts are now in maven central. See: http://search.maven.org/#search|ga > richfaces 4.1.Final showcase: Non-resolvable parent POM: Could not find artifact org.richfaces:richfaces-root-parent:pom:4.1.0.Final > ------------------------------------------------------------------------------------------------------------------------------------ > > Key: RF-11861 > URL: https://issues.jboss.org/browse/RF-11861 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Peter B > Assignee: Brian Leathem > Labels: richfaces > Fix For: 4.2.0.CR1 > > > richfaces showcase for Richfaces 4.1 Final doesn't build. > Problem is that: > {code} > org.richfaces > richfaces-root-parent > 4.1.0.Final > {code} > is not in central maven repository. > Console output: > {code} > [INFO] Scanning for projects... > Downloading: http://repo1.maven.org/maven2/org/richfaces/richfaces-root-parent/4.1.0.Final/richfaces-root-parent-4.1.0.F > inal.pom > [ERROR] The build could not read 1 project -> [Help 1] > [ERROR] > [ERROR] The project org.richfaces.examples:richfaces-showcase:4.1.0.Final (D:\tmp\richfaces-showcase-77c6701\pom.xml) > has 1 error > [ERROR] Non-resolvable parent POM: Could not find artifact org.richfaces:richfaces-root-parent:pom:4.1.0.Final in ce > ntral (http://repo1.maven.org/maven2) and 'parent.relativePath' points at wrong local POM @ line 8, column 13 -> [Help 2 > ] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please read the following articles: > [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException > [ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException > {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 Jan 21 00:24:18 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Sat, 21 Jan 2012 00:24:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11895) Richfaces showcase import into JBoss Tools/JBDS In-Reply-To: <1507274563.7562.1326891738548.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1743605553.14831.1327123458276.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-11895. -------------------------------- Assignee: Brian Leathem Fix Version/s: 4.2.0.CR1 Resolution: Done RichFaces has just recently been added to maven central. See: http://search.maven.org/#search%7Cga%7Crichfaces > Richfaces showcase import into JBoss Tools/JBDS > ----------------------------------------------- > > Key: RF-11895 > URL: https://issues.jboss.org/browse/RF-11895 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: examples > Affects Versions: 4.1.0.Final > Reporter: Burr Sutter > Assignee: Brian Leathem > Fix For: 4.2.0.CR1 > > > Importing RichFaces Showcase into JBDS5 M5 has the following error: > [ERROR] The project org.richfaces.examples:richfaces-showcase:4.1.0.Final (/Users/burr/Downloads/richfaces-4.1.0.Final/examples/richfaces-showcase/pom.xml) has 1 error > [ERROR] Non-resolvable parent POM: Could not find artifact org.richfaces:richfaces-root-parent:pom:4.1.0.Final in central (http://repo1.maven.org/maven2) and 'parent.relativePath' points at wrong local POM @ line 8, column 13 -> [Help 2] > [ERROR] > Same error on the command line. > Also in the readme.txt, it refers to "Jboss" - need to upper case that "b" -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 21 00:26:18 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Sat, 21 Jan 2012 00:26:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11896) [rich:autocomplete] add attribute maxlength In-Reply-To: <744278392.7735.1326894619247.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <954227262.14833.1327123578348.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-11896: ------------------------------- Fix Version/s: 4.2-Tracking Priority: Minor (was: Major) Component/s: component-input > [rich:autocomplete] add attribute maxlength > ------------------------------------------- > > Key: RF-11896 > URL: https://issues.jboss.org/browse/RF-11896 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.1.0.Final > Reporter: Rene O > Priority: Minor > Fix For: 4.2-Tracking > > > It would be nice, if rich:autocomplete has an attribute maxlength to limit the users input. > It should be the same as attribute maxlength within the h:input 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 Sat Jan 21 00:28:18 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Sat, 21 Jan 2012 00:28:18 -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: <397503324.14835.1327123698322.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12660951#comment-12660951 ] Brian Leathem commented on RF-11902: ------------------------------------ Is it not sufficient to nest a [a4j:attachQueue|http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=attachQueue&skin=blueSky] within the component? > [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 > Labels: waiting_on_user > > 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 Sat Jan 21 22:55:19 2012 From: jira-events at lists.jboss.org (oday qasim (JIRA)) Date: Sat, 21 Jan 2012 22:55:19 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-8201) Print RichFaces module information at start up In-Reply-To: <1329040258.1260548489621.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com> Message-ID: <496616693.15088.1327204519287.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-8201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12660991#comment-12660991 ] oday qasim commented on RF-8201: -------------------------------- thnx > Print RichFaces module information at start up > ---------------------------------------------- > > Key: RF-8201 > URL: https://issues.jboss.org/browse/RF-8201 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: build/distribution, core > Affects Versions: 4.0.0.Alpha2 > Reporter: Jay Balunas > Assignee: Nick Belaevski > Fix For: 4.Future > > > During start up all RichFaces modules should printout meta data into the log. This would be for each module api, ui, impl, themes, etc.... > This will be more important as we allow for module releases that may not always be 100% in sync. It will also help with debugging issues. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 22 18:22:18 2012 From: jira-events at lists.jboss.org (Brendan Healey (JIRA)) Date: Sun, 22 Jan 2012 18:22:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11888) Resource Servlet can't handle query string appended to resource url In-Reply-To: <787852126.1337.1326719298230.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <365390081.15423.1327274538297.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12661027#comment-12661027 ] Brendan Healey commented on RF-11888: ------------------------------------- I'm really starting to see this as a critical problem. I've got everything setup so that my static resources cache properly. In web.xml I set com.sun.faces.defaultResourceMaxAge to 31536000000 (a year), and in a filter I set the response header Cache-Control to "max-age=31536000, public, must-revalidate". I then see the browser using the cache rather than issuing a request. The browser has calculated an expiry date for the cached resource, and I expect that it will carry on using the cache rather than issuing a new request for the resource until the expiry date is reached. Which raises the question how do I invalidate the browser cache in the case that I've upgraded richfaces? I clearly don't want to be using an old version of packed.js if I've upgraded from RF 4.1 to 4.2. For all my other resources I will just increment the version string in my resource handler whenever necessary, but I don't see any way to achieve the same for the richfaces resources because of this problem. > Resource Servlet can't handle query string appended to resource url > ------------------------------------------------------------------- > > Key: RF-11888 > URL: https://issues.jboss.org/browse/RF-11888 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: resource handling > Affects Versions: 4.1.0.Final > Environment: Glassfish 3.1.1 (NO Tomcat)/Mojarra 2.1.3 Chrome browser - > Reporter: Brendan Healey > > A custom resource handler (http://blogs.oracle.com/rlubke/entry/jsf_2_0_new_feature) > can be used to append a version string (i.e. ?v=23) to a resource url to force a > browser to refresh a resource rather than use any cached version. > This is useful as a last resort strategy, perhaps after a major redeployment, and > also in the event that there are other problems setting useful ETag and Last-Modified > http response headers. > At present any appending of a version string causes a 404 response status, for example: > Request URL: > https://localhost:8181/MyApp/org.richfaces.resources/javax.faces.resource/org.richfaces.staticResource/4.1.0.Final/PackedCompressed/blueSky/packed/packed.css?v=23 > Removing the url parameter makes it work ok. As you can see I have resourceMapping > enabled. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 22 18:39:18 2012 From: jira-events at lists.jboss.org (Brendan Healey (JIRA)) Date: Sun, 22 Jan 2012 18:39:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11888) Resource Servlet can't handle query string appended to resource url In-Reply-To: <787852126.1337.1326719298230.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <595159696.15426.1327275558245.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brendan Healey updated RF-11888: -------------------------------- Priority: Critical (was: Major) Description: A custom resource handler (http://blogs.oracle.com/rlubke/entry/jsf_2_0_new_feature) can be used to append a version string (i.e. ?v=23) to a resource url to force a browser to refresh a resource rather than use any cached version. At present any appending of a version string causes a 404 response status, for example: Request URL: https://localhost:8181/MyApp/org.richfaces.resources/javax.faces.resource/org.richfaces.staticResource/4.1.0.Final/PackedCompressed/blueSky/packed/packed.css?v=23 Removing the url parameter makes it work ok. As you can see I have resourceMapping enabled. This is essential to cause a browser to issue a request to the server if a static resource is held in a browser cache and is not expired, but you've upgraded the richfaces version. You have to have a way to invalidate the cache, and I'm not seeing how this can be done. was: A custom resource handler (http://blogs.oracle.com/rlubke/entry/jsf_2_0_new_feature) can be used to append a version string (i.e. ?v=23) to a resource url to force a browser to refresh a resource rather than use any cached version. This is useful as a last resort strategy, perhaps after a major redeployment, and also in the event that there are other problems setting useful ETag and Last-Modified http response headers. At present any appending of a version string causes a 404 response status, for example: Request URL: https://localhost:8181/MyApp/org.richfaces.resources/javax.faces.resource/org.richfaces.staticResource/4.1.0.Final/PackedCompressed/blueSky/packed/packed.css?v=23 Removing the url parameter makes it work ok. As you can see I have resourceMapping enabled. > Resource Servlet can't handle query string appended to resource url > ------------------------------------------------------------------- > > Key: RF-11888 > URL: https://issues.jboss.org/browse/RF-11888 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: resource handling > Affects Versions: 4.1.0.Final > Environment: Glassfish 3.1.1 (NO Tomcat)/Mojarra 2.1.3 Chrome browser - > Reporter: Brendan Healey > Priority: Critical > > A custom resource handler (http://blogs.oracle.com/rlubke/entry/jsf_2_0_new_feature) > can be used to append a version string (i.e. ?v=23) to a resource url to force a > browser to refresh a resource rather than use any cached version. > At present any appending of a version string causes a 404 response status, for example: > Request URL: > https://localhost:8181/MyApp/org.richfaces.resources/javax.faces.resource/org.richfaces.staticResource/4.1.0.Final/PackedCompressed/blueSky/packed/packed.css?v=23 > Removing the url parameter makes it work ok. As you can see I have resourceMapping > enabled. > This is essential to cause a browser to issue a request to the server if a static > resource is held in a browser cache and is not expired, but you've upgraded the > richfaces version. You have to have a way to invalidate the cache, and I'm not > seeing how this can be done. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 22 18:41:18 2012 From: jira-events at lists.jboss.org (Brendan Healey (JIRA)) Date: Sun, 22 Jan 2012 18:41:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11888) Resource Servlet can't handle query string appended to resource url In-Reply-To: <787852126.1337.1326719298230.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1333081058.15430.1327275678390.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brendan Healey updated RF-11888: -------------------------------- Description: A custom resource handler (http://blogs.oracle.com/rlubke/entry/jsf_2_0_new_feature) can be used to append a version string (i.e. ?v=23) to a resource url to force a browser to refresh a resource rather than use any cached version. At present any appending of a version string causes a 404 response status, for example: Request URL: https://localhost:8181/MyApp/org.richfaces.resources/javax.faces.resource/org.richfaces.staticResource/4.1.0.Final/PackedCompressed/blueSky/packed/packed.css?v=23 Removing the url parameter makes it work ok. As you can see I have resourceMapping enabled. This is essential to cause a browser to issue a request to the server if a static resource is held in a browser cache and is not expired, but you've upgraded the richfaces version. You have to have a way to invalidate the cache, and I'm not seeing how this can be done in a sensible way. You can set the Cache-Control no-cache header, but I'd need to do this in a way that says "I've just upgraded richfaces, so don't use the cache, issue a request to the server for the resource, but cache the result and use this until the next time". was: A custom resource handler (http://blogs.oracle.com/rlubke/entry/jsf_2_0_new_feature) can be used to append a version string (i.e. ?v=23) to a resource url to force a browser to refresh a resource rather than use any cached version. At present any appending of a version string causes a 404 response status, for example: Request URL: https://localhost:8181/MyApp/org.richfaces.resources/javax.faces.resource/org.richfaces.staticResource/4.1.0.Final/PackedCompressed/blueSky/packed/packed.css?v=23 Removing the url parameter makes it work ok. As you can see I have resourceMapping enabled. This is essential to cause a browser to issue a request to the server if a static resource is held in a browser cache and is not expired, but you've upgraded the richfaces version. You have to have a way to invalidate the cache, and I'm not seeing how this can be done. > Resource Servlet can't handle query string appended to resource url > ------------------------------------------------------------------- > > Key: RF-11888 > URL: https://issues.jboss.org/browse/RF-11888 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: resource handling > Affects Versions: 4.1.0.Final > Environment: Glassfish 3.1.1 (NO Tomcat)/Mojarra 2.1.3 Chrome browser - > Reporter: Brendan Healey > Priority: Critical > > A custom resource handler (http://blogs.oracle.com/rlubke/entry/jsf_2_0_new_feature) > can be used to append a version string (i.e. ?v=23) to a resource url to force a > browser to refresh a resource rather than use any cached version. > At present any appending of a version string causes a 404 response status, for example: > Request URL: > https://localhost:8181/MyApp/org.richfaces.resources/javax.faces.resource/org.richfaces.staticResource/4.1.0.Final/PackedCompressed/blueSky/packed/packed.css?v=23 > Removing the url parameter makes it work ok. As you can see I have resourceMapping > enabled. > This is essential to cause a browser to issue a request to the server if a static > resource is held in a browser cache and is not expired, but you've upgraded the > richfaces version. You have to have a way to invalidate the cache, and I'm not > seeing how this can be done in a sensible way. You can set the Cache-Control > no-cache header, but I'd need to do this in a way that says "I've just upgraded > richfaces, so don't use the cache, issue a request to the server for the resource, > but cache the result and use this until the next time". -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 23 02:23:18 2012 From: jira-events at lists.jboss.org (Rene O (JIRA)) Date: Mon, 23 Jan 2012 02:23:18 -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: <1977796789.15828.1327303398368.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12661047#comment-12661047 ] Rene O commented on RF-11902: ----------------------------- It is not sufficient, beacause it doesn't work. I have tried the following code within h:form {code} {code} The search starts immediatly after i put in the 2nd character. The search doesn't wait 750ms. Apart from that i think it is not the best solution. Imagine if you have a lot of autocomplete components. Then its better to reuse a global queue. > [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 > Labels: waiting_on_user > > 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 Mon Jan 23 03:08:18 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 23 Jan 2012 03:08:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11836) Replace ${project.version} definitions in the poms with actual version In-Reply-To: <150403957.24272.1324386369523.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <2133747399.15857.1327306098801.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12661053#comment-12661053 ] Luk?? Fry? commented on RF-11836: --------------------------------- I assume this was only misinterpretation of mail we have got from Joel: {quote} * Several sub-groups in org.richfaces contained POMs with variables in the element. This caused our POM validity scripts to fail. These sub-groups appeared to be documentation or example related: {quote} Although some changes were done on feature branch {{productization-changes}}, there were rather focused on clean up. I suggest to reject this issue. > Replace ${project.version} definitions in the poms with actual version > ---------------------------------------------------------------------- > > Key: RF-11836 > URL: https://issues.jboss.org/browse/RF-11836 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 4.1.0.Final > Reporter: Luk?? Fry? > Assignee: Brian Leathem > > This is requirement for uploading to Maven Central. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 23 03:08:18 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 23 Jan 2012 03:08:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11836) Replace ${project.version} definitions in the poms with actual version In-Reply-To: <150403957.24272.1324386369523.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1966904708.15858.1327306098841.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved RF-11836. ----------------------------- Resolution: Done > Replace ${project.version} definitions in the poms with actual version > ---------------------------------------------------------------------- > > Key: RF-11836 > URL: https://issues.jboss.org/browse/RF-11836 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 4.1.0.Final > Reporter: Luk?? Fry? > Assignee: Brian Leathem > > This is requirement for uploading to Maven Central. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 23 03:08:19 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 23 Jan 2012 03:08:19 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11836) Replace ${project.version} definitions in the poms with actual version In-Reply-To: <150403957.24272.1324386369523.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1558117569.15868.1327306099474.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? reopened RF-11836: ----------------------------- > Replace ${project.version} definitions in the poms with actual version > ---------------------------------------------------------------------- > > Key: RF-11836 > URL: https://issues.jboss.org/browse/RF-11836 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 4.1.0.Final > Reporter: Luk?? Fry? > Assignee: Brian Leathem > > This is requirement for uploading to Maven Central. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 23 03:08:19 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 23 Jan 2012 03:08:19 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11836) Replace ${project.version} definitions in the poms with actual version In-Reply-To: <150403957.24272.1324386369523.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1739993334.15869.1327306099503.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved RF-11836. ----------------------------- Resolution: Rejected > Replace ${project.version} definitions in the poms with actual version > ---------------------------------------------------------------------- > > Key: RF-11836 > URL: https://issues.jboss.org/browse/RF-11836 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 4.1.0.Final > Reporter: Luk?? Fry? > Assignee: Brian Leathem > > This is requirement for uploading to Maven Central. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 23 03:15:18 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 23 Jan 2012 03:15:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11885) RF 4.1 final a4j:push CDI topic is configured In-Reply-To: <880165753.172.1326637038332.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <362056758.15894.1327306518452.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12661056#comment-12661056 ] Luk?? Fry? commented on RF-11885: --------------------------------- Currently, topic needs to be initialized by {{TopicsInitializer}}, refer to https://community.jboss.org/wiki/StartingWithRichFacesPushOnVariousServletContainers#Push_Initialization__Topics_Creation This issue should be also fixed by RF-11483 in {{4.2}} cycle. Ibrahim, could you please give a try to latest {{4.2.0-SNAPSHOT}}? > RF 4.1 final a4j:push CDI topic is configured > --------------------------------------------- > > Key: RF-11885 > URL: https://issues.jboss.org/browse/RF-11885 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Affects Versions: 4.1.0.Final > Environment: JBoss 6.0 final > JDK 1.6.0_24 > Reporter: Ibrahim Abu Ghosh > Assignee: Luk?? Fry? > Labels: a4j:push, cdi, waiting_on_user > > i tried to use a4j:push cdi as in showcase, but my consumer page shows a message (topic 'my topic name' is not configured). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 23 03:30:18 2012 From: jira-events at lists.jboss.org (Ibrahim Abu Ghosh (JIRA)) Date: Mon, 23 Jan 2012 03:30:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11885) RF 4.1 final a4j:push CDI topic is configured In-Reply-To: <880165753.172.1326637038332.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <359279784.15901.1327307418624.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12661057#comment-12661057 ] Ibrahim Abu Ghosh commented on RF-11885: ---------------------------------------- please provide me with a download link. > RF 4.1 final a4j:push CDI topic is configured > --------------------------------------------- > > Key: RF-11885 > URL: https://issues.jboss.org/browse/RF-11885 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Affects Versions: 4.1.0.Final > Environment: JBoss 6.0 final > JDK 1.6.0_24 > Reporter: Ibrahim Abu Ghosh > Assignee: Luk?? Fry? > Labels: a4j:push, cdi, waiting_on_user > > i tried to use a4j:push cdi as in showcase, but my consumer page shows a message (topic 'my topic name' is not configured). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 23 06:07:18 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 23 Jan 2012 06:07:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11885) RF 4.1 final a4j:push CDI topic is configured In-Reply-To: <880165753.172.1326637038332.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1084093424.16326.1327316838352.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12661096#comment-12661096 ] Luk?? Fry? commented on RF-11885: --------------------------------- There can be found download links on JBoss repo: https://repository.jboss.org/nexus/index.html#nexus-search;gav~~richfaces-core-*~4.2.0-SNAPSHOT~~ https://repository.jboss.org/nexus/index.html#nexus-search;gav~~richfaces-components-*~4.2.0-SNAPSHOT~~ > RF 4.1 final a4j:push CDI topic is configured > --------------------------------------------- > > Key: RF-11885 > URL: https://issues.jboss.org/browse/RF-11885 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Affects Versions: 4.1.0.Final > Environment: JBoss 6.0 final > JDK 1.6.0_24 > Reporter: Ibrahim Abu Ghosh > Assignee: Luk?? Fry? > Labels: a4j:push, cdi, waiting_on_user > > i tried to use a4j:push cdi as in showcase, but my consumer page shows a message (topic 'my topic name' is not configured). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 23 08:44:18 2012 From: jira-events at lists.jboss.org (Ibrahim Abu Ghosh (JIRA)) Date: Mon, 23 Jan 2012 08:44:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11885) RF 4.1 final a4j:push CDI topic is configured In-Reply-To: <880165753.172.1326637038332.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1536876017.16847.1327326258612.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12661146#comment-12661146 ] Ibrahim Abu Ghosh commented on RF-11885: ---------------------------------------- thanks Lukas, I've tested and it works fine, i removed TopicContext initialization code. i tested against atmosphere 0.8.4 runtime. > RF 4.1 final a4j:push CDI topic is configured > --------------------------------------------- > > Key: RF-11885 > URL: https://issues.jboss.org/browse/RF-11885 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Affects Versions: 4.1.0.Final > Environment: JBoss 6.0 final > JDK 1.6.0_24 > Reporter: Ibrahim Abu Ghosh > Assignee: Luk?? Fry? > Labels: a4j:push, cdi, waiting_on_user > > i tried to use a4j:push cdi as in showcase, but my consumer page shows a message (topic 'my topic name' is not configured). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 23 08:44:19 2012 From: jira-events at lists.jboss.org (Ibrahim Abu Ghosh (JIRA)) Date: Mon, 23 Jan 2012 08:44:19 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11885) RF 4.1 final a4j:push CDI topic is configured In-Reply-To: <880165753.172.1326637038332.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <815755762.16862.1327326259975.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12661146#comment-12661146 ] Ibrahim Abu Ghosh edited comment on RF-11885 at 1/23/12 8:43 AM: ----------------------------------------------------------------- thanks Lukas, I've tested and it works fine, i removed TopicContext initialization code. i tested it with atmosphere 0.8.4 runtime. was (Author: iabughosh): thanks Lukas, I've tested and it works fine, i removed TopicContext initialization code. i tested against atmosphere 0.8.4 runtime. > RF 4.1 final a4j:push CDI topic is configured > --------------------------------------------- > > Key: RF-11885 > URL: https://issues.jboss.org/browse/RF-11885 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Affects Versions: 4.1.0.Final > Environment: JBoss 6.0 final > JDK 1.6.0_24 > Reporter: Ibrahim Abu Ghosh > Assignee: Luk?? Fry? > Labels: a4j:push, cdi, waiting_on_user > > i tried to use a4j:push cdi as in showcase, but my consumer page shows a message (topic 'my topic name' is not configured). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 23 11:17:18 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 23 Jan 2012 11:17:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11885) RF 4.1 final a4j:push CDI topic is configured In-Reply-To: <880165753.172.1326637038332.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <599835644.17325.1327335438531.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-11885. -------------------------------- Labels: a4j:push cdi (was: a4j:push cdi waiting_on_user) Resolution: Out of Date Thanks for confirming the fix! > RF 4.1 final a4j:push CDI topic is configured > --------------------------------------------- > > Key: RF-11885 > URL: https://issues.jboss.org/browse/RF-11885 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Affects Versions: 4.1.0.Final > Environment: JBoss 6.0 final > JDK 1.6.0_24 > Reporter: Ibrahim Abu Ghosh > Assignee: Luk?? Fry? > Labels: a4j:push, cdi > > i tried to use a4j:push cdi as in showcase, but my consumer page shows a message (topic 'my topic name' is not configured). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 23 11:41:18 2012 From: jira-events at lists.jboss.org (Jason Lee (JIRA)) Date: Mon, 23 Jan 2012 11:41:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11912) Improved Maven documentation Message-ID: <343803648.17341.1327336878277.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Jason Lee created RF-11912: ------------------------------ Summary: Improved Maven documentation Key: RF-11912 URL: https://issues.jboss.org/browse/RF-11912 Project: RichFaces Issue Type: Enhancement Security Level: Public (Everyone can see) Components: doc Affects Versions: 4.1.0.Final Reporter: Jason Lee Priority: Minor The Maven documentation in the developers guide could be greatly improved if the relevant pom.xml elements were explicitly listed in the documentation. This information can be gleaned from the showcase app (which I did :), but having that in the docs themselves would make it easier for someone new to the project. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 23 11:56:18 2012 From: jira-events at lists.jboss.org (Cody Lerum (JIRA)) Date: Mon, 23 Jan 2012 11:56:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11913) Simplify Documentation and Process of using Resource Packing with Custom Skins Message-ID: <130703154.17370.1327337778226.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Cody Lerum created RF-11913: ------------------------------- Summary: Simplify Documentation and Process of using Resource Packing with Custom Skins Key: RF-11913 URL: https://issues.jboss.org/browse/RF-11913 Project: RichFaces Issue Type: Enhancement Security Level: Public (Everyone can see) Affects Versions: 4.1.0.Final Reporter: Cody Lerum Once a user creates their own skin the steps to enable resource packing are complex and not all documented in a easy to find manner. At a minimum it would be nice to just pack the 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 Jan 23 12:04:18 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 23 Jan 2012 12:04:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11909) Custom resource mapping can't simply reuse pre-generated RichFaces resources In-Reply-To: <42430590.13417.1327071978848.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <140618293.17384.1327338258473.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated RF-11909: ---------------------------- Description: Custom resource mapping can't simply reuse pre-generated RichFaces resources. Use case: * user wants to use resource mapping for several purposes ** using RichFaces pre-generated resources in {{richfaces-components-ui.jar/META-INF/resources/org.richfaces.staticResources//...}} ** using custom mappings like {{javax.faces:jsf.js=patched-jsf.js}} using e.g. {{my.war/resources/patched-jsf.js}} ---- With {{4.1.0.Final}}, configuration of {{org.richfaces.resourceMapping.location}} is by default referring to root of packed resources: {code}#{facesContext.externalContext.requestContextPath}/org.richfaces.resources/javax.faces.resource/org.richfaces.staticResource/#{a4j.version.implementationVersion}/%Features%/#{resourceLocation} {code} and mapping file looks like: {code} jquery.js=jquery.js {code} When you want to reuse RichFaces mappings, you [need to copy mapping file from {{richfaces-component-ui.jar}}|http://docs.jboss.org/richfaces/latest_4_X/Developer_Guide/en-US/html/chap-Developer_Guide-Advanced_features.html#d0e1692] and extend it by custom properties. and additionally you need to place custom resources to directory called specifically for RF, like: {code} my.war/resources/org.richfaces.staticResource/4.1.0.Final/PackedCompressed/patched-jsf.js {code} Other options: * change all mappings in {{custom-mappings.properties}} at own * copy all resources from {{richfaces-component-ui.jar}} to own location ---- For simplification, I suggest default resource mapping location root be {code} #{facesContext.externalContext.requestContextPath}/org.richfaces.resources/javax.faces.resource/#{resourceLocation} {code} so it would refer to JSF resources root ({{my.war/resources}} or {{some.jar/META-INF/resources}}) by default. Then, we would force {{richfaces-components-ui.jar}} to define mappings which points from JSF resources root, e.g.: {code} jquery.js=org.richfaces.staticResource/4.1.0.Final/PackedCompressed/jquery.js {code} ---- Additionally, Brian suggested support for multiple {{mapping.properties}} files, so their content will be merged. It means user won't be forced to copy&paste RichFaces mapping configuration from {{richfaces-components-ui.jar}}. ---- Finally, the only thing user would need to define is: {code:XML|title=web.xml} org.richfaces.resourceMapping.mappingFile META-INF/custom-mapping.properties {code} {code:title=META-INF/custom-mapping.properties} javax.faces:jsf.js=patched-jsf.js {code} was: Following configuration of location is needed: {code} org.richfaces.resourceMapping.location #{facesContext.externalContext.requestContextPath}/org.richfaces.resources/javax.faces.resource/org.richfaces.staticResource/#{a4j.version.implementationVersion}/%Features%/#{resourceLocation} {code} But that means you need to place custom resources to directory called specifically for RF: {code} ${WAR}/resources/org.richfaces.staticResource/4.1.0.Final/Packed/. {code} Forum Reference: https://community.jboss.org/message/647859#647859 (was: https://community.jboss.org/message/647859#647859) > Custom resource mapping can't simply reuse pre-generated RichFaces resources > ---------------------------------------------------------------------------- > > Key: RF-11909 > URL: https://issues.jboss.org/browse/RF-11909 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 4.1.0.Final > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 4.2.0.CR1 > > > Custom resource mapping can't simply reuse pre-generated RichFaces resources. > Use case: > * user wants to use resource mapping for several purposes > ** using RichFaces pre-generated resources in {{richfaces-components-ui.jar/META-INF/resources/org.richfaces.staticResources//...}} > ** using custom mappings like {{javax.faces:jsf.js=patched-jsf.js}} using e.g. {{my.war/resources/patched-jsf.js}} > ---- > With {{4.1.0.Final}}, configuration of {{org.richfaces.resourceMapping.location}} is by default referring to root of packed resources: > {code}#{facesContext.externalContext.requestContextPath}/org.richfaces.resources/javax.faces.resource/org.richfaces.staticResource/#{a4j.version.implementationVersion}/%Features%/#{resourceLocation} > {code} > and mapping file looks like: > {code} > jquery.js=jquery.js > {code} > When you want to reuse RichFaces mappings, you [need to copy mapping file from {{richfaces-component-ui.jar}}|http://docs.jboss.org/richfaces/latest_4_X/Developer_Guide/en-US/html/chap-Developer_Guide-Advanced_features.html#d0e1692] and extend it by custom properties. > and additionally you need to place custom resources to directory called specifically for RF, like: > {code} > my.war/resources/org.richfaces.staticResource/4.1.0.Final/PackedCompressed/patched-jsf.js > {code} > Other options: > * change all mappings in {{custom-mappings.properties}} at own > * copy all resources from {{richfaces-component-ui.jar}} to own location > ---- > For simplification, I suggest default resource mapping location root be > {code} > #{facesContext.externalContext.requestContextPath}/org.richfaces.resources/javax.faces.resource/#{resourceLocation} > {code} > so it would refer to JSF resources root ({{my.war/resources}} or {{some.jar/META-INF/resources}}) by default. > Then, we would force {{richfaces-components-ui.jar}} to define mappings which points from JSF resources root, e.g.: > {code} > jquery.js=org.richfaces.staticResource/4.1.0.Final/PackedCompressed/jquery.js > {code} > ---- > Additionally, Brian suggested support for multiple {{mapping.properties}} files, so their content will be merged. > It means user won't be forced to copy&paste RichFaces mapping configuration from {{richfaces-components-ui.jar}}. > ---- > Finally, the only thing user would need to define is: > {code:XML|title=web.xml} > > org.richfaces.resourceMapping.mappingFile > META-INF/custom-mapping.properties > > {code} > {code:title=META-INF/custom-mapping.properties} > javax.faces:jsf.js=patched-jsf.js > {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 Jan 23 12:06:18 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 23 Jan 2012 12:06:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11909) Custom resource mapping can't simply reuse pre-generated RichFaces resources In-Reply-To: <42430590.13417.1327071978848.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1992642095.17392.1327338378899.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12660839#comment-12660839 ] Luk?? Fry? edited comment on RF-11909 at 1/23/12 12:06 PM: ----------------------------------------------------------- PoC pushed to {{feature/RF-11909}} was (Author: lfryc): pushed to {{feature/RF-11909}} > Custom resource mapping can't simply reuse pre-generated RichFaces resources > ---------------------------------------------------------------------------- > > Key: RF-11909 > URL: https://issues.jboss.org/browse/RF-11909 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 4.1.0.Final > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 4.2.0.CR1 > > > Custom resource mapping can't simply reuse pre-generated RichFaces resources. > Use case: > * user wants to use resource mapping for several purposes > ** using RichFaces pre-generated resources in {{richfaces-components-ui.jar/META-INF/resources/org.richfaces.staticResources//...}} > ** using custom mappings like {{javax.faces:jsf.js=patched-jsf.js}} using e.g. {{my.war/resources/patched-jsf.js}} > ---- > With {{4.1.0.Final}}, configuration of {{org.richfaces.resourceMapping.location}} is by default referring to root of packed resources: > {code}#{facesContext.externalContext.requestContextPath}/org.richfaces.resources/javax.faces.resource/org.richfaces.staticResource/#{a4j.version.implementationVersion}/%Features%/#{resourceLocation} > {code} > and mapping file looks like: > {code} > jquery.js=jquery.js > {code} > When you want to reuse RichFaces mappings, you [need to copy mapping file from {{richfaces-component-ui.jar}}|http://docs.jboss.org/richfaces/latest_4_X/Developer_Guide/en-US/html/chap-Developer_Guide-Advanced_features.html#d0e1692] and extend it by custom properties. > and additionally you need to place custom resources to directory called specifically for RF, like: > {code} > my.war/resources/org.richfaces.staticResource/4.1.0.Final/PackedCompressed/patched-jsf.js > {code} > Other options: > * change all mappings in {{custom-mappings.properties}} at own > * copy all resources from {{richfaces-component-ui.jar}} to own location > ---- > For simplification, I suggest default resource mapping location root be > {code} > #{facesContext.externalContext.requestContextPath}/org.richfaces.resources/javax.faces.resource/#{resourceLocation} > {code} > so it would refer to JSF resources root ({{my.war/resources}} or {{some.jar/META-INF/resources}}) by default. > Then, we would force {{richfaces-components-ui.jar}} to define mappings which points from JSF resources root, e.g.: > {code} > jquery.js=org.richfaces.staticResource/4.1.0.Final/PackedCompressed/jquery.js > {code} > ---- > Additionally, Brian suggested support for multiple {{mapping.properties}} files, so their content will be merged. > It means user won't be forced to copy&paste RichFaces mapping configuration from {{richfaces-components-ui.jar}}. > ---- > Finally, the only thing user would need to define is: > {code:XML|title=web.xml} > > org.richfaces.resourceMapping.mappingFile > META-INF/custom-mapping.properties > > {code} > {code:title=META-INF/custom-mapping.properties} > javax.faces:jsf.js=patched-jsf.js > {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 Jan 23 12:06:19 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 23 Jan 2012 12:06:19 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11909) Custom resource mapping can't simply reuse pre-generated RichFaces resources In-Reply-To: <42430590.13417.1327071978848.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <225297503.17398.1327338379257.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated RF-11909: ---------------------------- Comment: was deleted (was: This will just need change of default values and pre-generated resource mapping files.) > Custom resource mapping can't simply reuse pre-generated RichFaces resources > ---------------------------------------------------------------------------- > > Key: RF-11909 > URL: https://issues.jboss.org/browse/RF-11909 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 4.1.0.Final > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 4.2.0.CR1 > > > Custom resource mapping can't simply reuse pre-generated RichFaces resources. > Use case: > * user wants to use resource mapping for several purposes > ** using RichFaces pre-generated resources in {{richfaces-components-ui.jar/META-INF/resources/org.richfaces.staticResources//...}} > ** using custom mappings like {{javax.faces:jsf.js=patched-jsf.js}} using e.g. {{my.war/resources/patched-jsf.js}} > ---- > With {{4.1.0.Final}}, configuration of {{org.richfaces.resourceMapping.location}} is by default referring to root of packed resources: > {code}#{facesContext.externalContext.requestContextPath}/org.richfaces.resources/javax.faces.resource/org.richfaces.staticResource/#{a4j.version.implementationVersion}/%Features%/#{resourceLocation} > {code} > and mapping file looks like: > {code} > jquery.js=jquery.js > {code} > When you want to reuse RichFaces mappings, you [need to copy mapping file from {{richfaces-component-ui.jar}}|http://docs.jboss.org/richfaces/latest_4_X/Developer_Guide/en-US/html/chap-Developer_Guide-Advanced_features.html#d0e1692] and extend it by custom properties. > and additionally you need to place custom resources to directory called specifically for RF, like: > {code} > my.war/resources/org.richfaces.staticResource/4.1.0.Final/PackedCompressed/patched-jsf.js > {code} > Other options: > * change all mappings in {{custom-mappings.properties}} at own > * copy all resources from {{richfaces-component-ui.jar}} to own location > ---- > For simplification, I suggest default resource mapping location root be > {code} > #{facesContext.externalContext.requestContextPath}/org.richfaces.resources/javax.faces.resource/#{resourceLocation} > {code} > so it would refer to JSF resources root ({{my.war/resources}} or {{some.jar/META-INF/resources}}) by default. > Then, we would force {{richfaces-components-ui.jar}} to define mappings which points from JSF resources root, e.g.: > {code} > jquery.js=org.richfaces.staticResource/4.1.0.Final/PackedCompressed/jquery.js > {code} > ---- > Additionally, Brian suggested support for multiple {{mapping.properties}} files, so their content will be merged. > It means user won't be forced to copy&paste RichFaces mapping configuration from {{richfaces-components-ui.jar}}. > ---- > Finally, the only thing user would need to define is: > {code:XML|title=web.xml} > > org.richfaces.resourceMapping.mappingFile > META-INF/custom-mapping.properties > > {code} > {code:title=META-INF/custom-mapping.properties} > javax.faces:jsf.js=patched-jsf.js > {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 Jan 23 12:08:20 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 23 Jan 2012 12:08:20 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11909) Custom resource mapping can't simply reuse pre-generated RichFaces resources In-Reply-To: <42430590.13417.1327071978848.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1431023089.17414.1327338500053.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12661221#comment-12661221 ] Luk?? Fry? commented on RF-11909: --------------------------------- The proposal is not changing backward compatibility. We can also create default for {{org.richfaces.resourceMapping.mappingFile}} and don't user force to define {{web.xml}} fragment. File presence detection would be necessary. > Custom resource mapping can't simply reuse pre-generated RichFaces resources > ---------------------------------------------------------------------------- > > Key: RF-11909 > URL: https://issues.jboss.org/browse/RF-11909 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 4.1.0.Final > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 4.2.0.CR1 > > > Custom resource mapping can't simply reuse pre-generated RichFaces resources. > Use case: > * user wants to use resource mapping for several purposes > ** using RichFaces pre-generated resources in {{richfaces-components-ui.jar/META-INF/resources/org.richfaces.staticResources//...}} > ** using custom mappings like {{javax.faces:jsf.js=patched-jsf.js}} using e.g. {{my.war/resources/patched-jsf.js}} > ---- > With {{4.1.0.Final}}, configuration of {{org.richfaces.resourceMapping.location}} is by default referring to root of packed resources: > {code}#{facesContext.externalContext.requestContextPath}/org.richfaces.resources/javax.faces.resource/org.richfaces.staticResource/#{a4j.version.implementationVersion}/%Features%/#{resourceLocation} > {code} > and mapping file looks like: > {code} > jquery.js=jquery.js > {code} > When you want to reuse RichFaces mappings, you [need to copy mapping file from {{richfaces-component-ui.jar}}|http://docs.jboss.org/richfaces/latest_4_X/Developer_Guide/en-US/html/chap-Developer_Guide-Advanced_features.html#d0e1692] and extend it by custom properties. > and additionally you need to place custom resources to directory called specifically for RF, like: > {code} > my.war/resources/org.richfaces.staticResource/4.1.0.Final/PackedCompressed/patched-jsf.js > {code} > Other options: > * change all mappings in {{custom-mappings.properties}} at own > * copy all resources from {{richfaces-component-ui.jar}} to own location > ---- > For simplification, I suggest default resource mapping location root be > {code} > #{facesContext.externalContext.requestContextPath}/org.richfaces.resources/javax.faces.resource/#{resourceLocation} > {code} > so it would refer to JSF resources root ({{my.war/resources}} or {{some.jar/META-INF/resources}}) by default. > Then, we would force {{richfaces-components-ui.jar}} to define mappings which points from JSF resources root, e.g.: > {code} > jquery.js=org.richfaces.staticResource/4.1.0.Final/PackedCompressed/jquery.js > {code} > ---- > Additionally, Brian suggested support for multiple {{mapping.properties}} files, so their content will be merged. > It means user won't be forced to copy&paste RichFaces mapping configuration from {{richfaces-components-ui.jar}}. > ---- > Finally, the only thing user would need to define is: > {code:XML|title=web.xml} > > org.richfaces.resourceMapping.mappingFile > META-INF/custom-mapping.properties > > {code} > {code:title=META-INF/custom-mapping.properties} > javax.faces:jsf.js=patched-jsf.js > {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 Jan 23 15:02:18 2012 From: jira-events at lists.jboss.org (Robert Gary (JIRA)) Date: Mon, 23 Jan 2012 15:02:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11914) Would like to see a dynamic subtable option for extendedDataTable Message-ID: <1890896963.17700.1327348938263.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Robert Gary created RF-11914: -------------------------------- Summary: Would like to see a dynamic subtable option for extendedDataTable Key: RF-11914 URL: https://issues.jboss.org/browse/RF-11914 Project: RichFaces Issue Type: Enhancement Security Level: Public (Everyone can see) Components: component-tables Affects Versions: 4.1.0.Final Reporter: Robert Gary Priority: Minor In RF 3.3.3 extendedDataTable offered the ability for the user to select any column and subgroup on it. This is no longer supported in RF 4.X. We do have the callapsibleSubTable tag but it requires each column to be pre-configured for subtable grouping. Could subtable grouping simply be an attribute on the column??? We would also want to allow the user to customize the expand/collapse subtable icon once the subtable grouping is enabled. -Robert -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 23 15:23:18 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 23 Jan 2012 15:23:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11814) a4j:commandLink in tabPanel disabled if switchtype = ajax In-Reply-To: <796306910.9115.1323859989475.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <957170782.17726.1327350198868.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-11814. -------------------------------- Assignee: Brian Leathem Resolution: Won't Fix Nesting ajax actions like this is not supported by JSF. When switchtype=ajax, this is effectively the same as nesting a commandButton within another commandButton - which one should take precedence? To avoid this ambiguity, you have two choices: # use switchType=client, and nest the button within the tab (as you already pointed out). # use switchType=ajax, and put your action in the tab itself, as in: {code} Logging out, please wait ! {code} > a4j:commandLink in tabPanel disabled if switchtype = ajax > --------------------------------------------------------- > > Key: RF-11814 > URL: https://issues.jboss.org/browse/RF-11814 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core, component-panels-layout-themes > Affects Versions: 4.1.0.CR2 > Environment: Win 7 64 Bit, Tomcat 7.0.23, Mojarra 2.1.3 > Reporter: Friedhelm Kuehn > Assignee: Brian Leathem > > In the following constellation (=extract from real page) the a4j:commandlink action method > is correctly triggered on clicking when tabPanels switchType = "client" but not when switchType = "ajax" > {code} > > > > > ..... > > > > > > > Logging out, please wait ! > > > {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 Jan 23 15:23:19 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 23 Jan 2012 15:23:19 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11838) Warning in Chrome console for pages with ajax In-Reply-To: <836209596.24520.1324389969366.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1494266881.17730.1327350199085.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-11838: ------------------------------- Fix Version/s: 4.2.0.CR1 A grep of the RichFaces codebase does not provide any immediate indication as to what is causing this. A web search indicates this can also be caused by installed chrome extensions - I disabled all my extensions, and still observed the method. Further investigation is required. > Warning in Chrome console for pages with ajax > --------------------------------------------- > > Key: RF-11838 > URL: https://issues.jboss.org/browse/RF-11838 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: compatibility > Affects Versions: 4.1.0.Final > Environment: Google Chrome 16.0.912.63 > Reporter: Pavol Pitonak > Fix For: 4.2.0.CR1 > > > # open Showcase in Chrome http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=ajax&skin=blueSky > # open browser console > # type "xxx" into input > result: > The following warning is displayed in browser console 6 times (twice for each Ajax request). Seems to be Chrome-specific and seems not to influence functionality of any component. > {quote} > event.layerX and event.layerY are broken and deprecated in WebKit. They will be removed from the engine in the near future. > {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 Mon Jan 23 15:27:18 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 23 Jan 2012 15:27:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11846) rich:validator ignores @NotEmpty In-Reply-To: <651588956.26878.1324469409370.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1669587073.17737.1327350438469.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-11846: ------------------------------- Fix Version/s: 4.3-Tracking I think you're right Jan, this probably has to do with validation being triggered by blur events. Further investigation is required. > rich:validator ignores @NotEmpty > -------------------------------- > > Key: RF-11846 > URL: https://issues.jboss.org/browse/RF-11846 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-validators > Affects Versions: 4.1.0.Final > Environment: Maven 3, Tomcat 6.0.x, Ubuntu 11.10 x64, Glassfish jsf 2.x implementation, Hibernate validator 4.1.0.Final > Reporter: Mercer Traieste > Fix For: 4.3-Tracking > > > I want to have [client-side validation|http://richfaces-showcase.appspot.com/richfaces/component-sample.jsf?demo=clientValidation&sample=jsr303&skin=blueSky] using rich:validator in Richfaces 4.1, but @NotEmpty is ignored. > {code:xml} > > > > > > {code} > {code:java} > import org.hibernate.validator.constraints.NotEmpty; > import javax.faces.bean.ManagedBean; > import javax.faces.bean.SessionScoped; > import java.io.Serializable; > @ManagedBean > @SessionScoped > public class RichBean implements Serializable { > private static final long serialVersionUID = -2403138958014741653L; > @NotEmpty > private String firstName; > public String getFirstName() { > return firstName; > } > public void setFirstName(String firstName) { > this.firstName = firstName; > } > } > {code} > @Email, another specific Hibernate validator 4.1 annotation works 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 Mon Jan 23 15:33:18 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 23 Jan 2012 15:33:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11871) Mobile Showcase and a4j:poll demo: stop button doesn't respond on the first click In-Reply-To: <1495571967.52108.1326200889891.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <838460537.17742.1327350798257.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem reassigned RF-11871: ---------------------------------- Assignee: Jan Papousek Jan, this works with me on a recent SNAPSHOT. It was possibly fixed with the recent Atmosphere upgrade that Lukas did. Can you please try this again to confirm it is no longer an issue? > Mobile Showcase and a4j:poll demo: stop button doesn't respond on the first click > --------------------------------------------------------------------------------- > > Key: RF-11871 > URL: https://issues.jboss.org/browse/RF-11871 > 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 > Reporter: Jan Papousek > Assignee: 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 Mon Jan 23 15:39:19 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 23 Jan 2012 15:39:19 -0500 (EST) 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: <170644102.17778.1327351159143.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. -------------------------------- Assignee: Brian Leathem Resolution: Cannot Reproduce Bug Unable to reproduce with a recent RichFaces SNAPSHOT, and Google chrome 16. If you continue to observe this behavior, please re-open the issue including details of your browser environment. > 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 > Reporter: Jan Papousek > 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 Mon Jan 23 15:41:18 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 23 Jan 2012 15:41:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11874) rich:extendedDataTable keyboard navigation fails in IE8 In-Reply-To: <1410319121.2645.1326369141473.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1768637260.17782.1327351278377.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem reassigned RF-11874: ---------------------------------- Assignee: Pavol Pitonak QE, please verify. > rich:extendedDataTable keyboard navigation fails in IE8 > ------------------------------------------------------- > > Key: RF-11874 > URL: https://issues.jboss.org/browse/RF-11874 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-ScrollableDataTable > Affects Versions: 4.1.0.Final > Environment: JSF-RI 2 > Internet Explorer version 8.0.7601.17514 > Reporter: Dmitry Volkov > Assignee: Pavol Pitonak > > Continous keyboard navigation fails in IE8 when ajax loading(clientRows="..") used. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 23 15:43:18 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 23 Jan 2012 15:43:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11875) rich:extendedDataTable in ajax loading mode, crashes when dataset length changes between requests In-Reply-To: <1944546618.3014.1326375801528.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <569591025.17786.1327351398497.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem reassigned RF-11875: ---------------------------------- Assignee: Pavol Pitonak QE, please confirm > rich:extendedDataTable in ajax loading mode, crashes when dataset length changes between requests > ------------------------------------------------------------------------------------------------- > > Key: RF-11875 > URL: https://issues.jboss.org/browse/RF-11875 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-ScrollableDataTable > Affects Versions: 4.1.0.Final > Environment: JSF-RI 2.0, Tomcat 6.0.29 > Reporter: Dmitry Volkov > Assignee: Pavol Pitonak > > rich:extendedDataTable in ajax loading mode(clientRows=".."), crashes when dataset length changes between requests. > It makes ajax loading mode unusable for database paging. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 23 15:45:18 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 23 Jan 2012 15:45:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11879) Add examle of usage of a4j:actionListener into RF showcase In-Reply-To: <43091471.3804.1326385042424.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1815466880.17791.1327351518553.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-11879: ------------------------------- Fix Version/s: 4.2.0.CR1 > Add examle of usage of a4j:actionListener into RF showcase > ---------------------------------------------------------- > > Key: RF-11879 > URL: https://issues.jboss.org/browse/RF-11879 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: showcase > Affects Versions: 4.1.0.Final > Reporter: Marek Novotny > Priority: Minor > Fix For: 4.2.0.CR1 > > > a4j:actionListener is not presented in showcase example -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 23 15:49:19 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 23 Jan 2012 15:49:19 -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: <1928371595.17799.1327351759210.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 updated RF-11882: ------------------------------- Description: 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 was: I get a FATAL: ...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" Which wasn't there in richfaces 3.3.3 The code snippet: 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;} } } 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 > 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 > Priority: Minor > > 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 Mon Jan 23 15:57:18 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 23 Jan 2012 15:57:18 -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: <1949789890.17816.1327352238233.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12661291#comment-12661291 ] Brian Leathem commented on RF-11882: ------------------------------------ Would you please frovide a complete, [self-contained example|http://sscce.org/] demonstrating this behavior? > 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 > 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 Mon Jan 23 15:59:18 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 23 Jan 2012 15:59:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11886) Style of the panelMenu changed from 4.1 In-Reply-To: <383594832.626.1326705438390.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1306649188.17820.1327352358420.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem reassigned RF-11886: ---------------------------------- Assignee: Brian Leathem > Style of the panelMenu changed from 4.1 > --------------------------------------- > > Key: RF-11886 > URL: https://issues.jboss.org/browse/RF-11886 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: showcase > Affects Versions: 4.1.0.Final > Environment: Showcase > Reporter: Luk?? Fry? > Assignee: Brian Leathem > Priority: Minor > Attachments: new.png, old.png > > > On the screenshots, there is visual change of panelMenu from 4.1 (http://showcase.richfaces.org/), > the border around the panelMenu has been 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 Jan 23 15:59:18 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 23 Jan 2012 15:59:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11886) Style of the panelMenu changed from 4.1 In-Reply-To: <383594832.626.1326705438390.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1786760464.17818.1327352358366.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-11886. -------------------------------- Resolution: Won't Fix The menupanel border was removed with the addition of round-corner support - when the menu items have round corners, the border doesn't look right. > Style of the panelMenu changed from 4.1 > --------------------------------------- > > Key: RF-11886 > URL: https://issues.jboss.org/browse/RF-11886 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: showcase > Affects Versions: 4.1.0.Final > Environment: Showcase > Reporter: Luk?? Fry? > Priority: Minor > Attachments: new.png, old.png > > > On the screenshots, there is visual change of panelMenu from 4.1 (http://showcase.richfaces.org/), > the border around the panelMenu has been 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 Jan 23 15:59:18 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 23 Jan 2012 15:59:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11887) Showcase: ajax transitions between demos/samples In-Reply-To: <410816163.1013.1326713298365.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1115992687.17822.1327352358477.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-11887: ------------------------------- Fix Version/s: 4.Future > Showcase: ajax transitions between demos/samples > ------------------------------------------------ > > Key: RF-11887 > URL: https://issues.jboss.org/browse/RF-11887 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: showcase > Reporter: Luk?? Fry? > Fix For: 4.Future > > > When navigating between demos/samples, whole page updates are necessary currently. > Navigation may be much more fluent when using Ajax transitions only. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 23 16:01:18 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 23 Jan 2012 16:01:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11888) Resource Servlet can't handle query string appended to resource url In-Reply-To: <787852126.1337.1326719298230.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <415629244.17838.1327352478587.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12661295#comment-12661295 ] Brian Leathem commented on RF-11888: ------------------------------------ Note: When you upgrade from version 4.1 to 4.2, the URL for packed.js will change: https://localhost:8181/MyApp/org.richfaces.resources/javax.faces.resource/org.richfaces.staticResource/4.1.0.Final/PackedCompressed/blueSky/packed/packed.css?v=23 Not the RichFaces version in the URL. > Resource Servlet can't handle query string appended to resource url > ------------------------------------------------------------------- > > Key: RF-11888 > URL: https://issues.jboss.org/browse/RF-11888 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: resource handling > Affects Versions: 4.1.0.Final > Environment: Glassfish 3.1.1 (NO Tomcat)/Mojarra 2.1.3 Chrome browser - > Reporter: Brendan Healey > Priority: Critical > > A custom resource handler (http://blogs.oracle.com/rlubke/entry/jsf_2_0_new_feature) > can be used to append a version string (i.e. ?v=23) to a resource url to force a > browser to refresh a resource rather than use any cached version. > At present any appending of a version string causes a 404 response status, for example: > Request URL: > https://localhost:8181/MyApp/org.richfaces.resources/javax.faces.resource/org.richfaces.staticResource/4.1.0.Final/PackedCompressed/blueSky/packed/packed.css?v=23 > Removing the url parameter makes it work ok. As you can see I have resourceMapping > enabled. > This is essential to cause a browser to issue a request to the server if a static > resource is held in a browser cache and is not expired, but you've upgraded the > richfaces version. You have to have a way to invalidate the cache, and I'm not > seeing how this can be done in a sensible way. You can set the Cache-Control > no-cache header, but I'd need to do this in a way that says "I've just upgraded > richfaces, so don't use the cache, issue a request to the server for the resource, > but cache the result and use this until the next time". -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 23 16:01:18 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 23 Jan 2012 16:01:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11888) Resource Servlet can't handle query string appended to resource url In-Reply-To: <787852126.1337.1326719298230.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <243073932.17842.1327352478809.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem reassigned RF-11888: ---------------------------------- Assignee: Luk?? Fry? Lukas, please assess and schedule accordingly. > Resource Servlet can't handle query string appended to resource url > ------------------------------------------------------------------- > > Key: RF-11888 > URL: https://issues.jboss.org/browse/RF-11888 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: resource handling > Affects Versions: 4.1.0.Final > Environment: Glassfish 3.1.1 (NO Tomcat)/Mojarra 2.1.3 Chrome browser - > Reporter: Brendan Healey > Assignee: Luk?? Fry? > Priority: Critical > > A custom resource handler (http://blogs.oracle.com/rlubke/entry/jsf_2_0_new_feature) > can be used to append a version string (i.e. ?v=23) to a resource url to force a > browser to refresh a resource rather than use any cached version. > At present any appending of a version string causes a 404 response status, for example: > Request URL: > https://localhost:8181/MyApp/org.richfaces.resources/javax.faces.resource/org.richfaces.staticResource/4.1.0.Final/PackedCompressed/blueSky/packed/packed.css?v=23 > Removing the url parameter makes it work ok. As you can see I have resourceMapping > enabled. > This is essential to cause a browser to issue a request to the server if a static > resource is held in a browser cache and is not expired, but you've upgraded the > richfaces version. You have to have a way to invalidate the cache, and I'm not > seeing how this can be done in a sensible way. You can set the Cache-Control > no-cache header, but I'd need to do this in a way that says "I've just upgraded > richfaces, so don't use the cache, issue a request to the server for the resource, > but cache the result and use this until the next time". -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 23 16:23:18 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 23 Jan 2012 16:23:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11891) Simple bug in org.richfaces.resource.Xcss2EcssConverter In-Reply-To: <815303006.6467.1326841279163.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <2079098074.17868.1327353798357.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-11891: ------------------------------- Fix Version/s: 4.2.0.CR1 Priority: Trivial (was: Major) Assignee: Luk?? Fry? > Simple bug in org.richfaces.resource.Xcss2EcssConverter > ------------------------------------------------------- > > Key: RF-11891 > URL: https://issues.jboss.org/browse/RF-11891 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 4.1.0.Final > Environment: Any > Reporter: Dmytro Batishchev > Assignee: Luk?? Fry? > Priority: Trivial > Fix For: 4.2.0.CR1 > > > Simple bug in org.richfaces.resource.Xcss2EcssConverter classfile in main class, please, comment out or delete next line: > {quote} > _String string = "E:/projs/richafces4/framework/trunk/impl/src/test/java/org/ajax4jsf/cache/extended.xcss"_ > {quote} > PS: Sorry for my English. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 23 16:23:18 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 23 Jan 2012 16:23:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11891) Simple bug in org.richfaces.resource.Xcss2EcssConverter In-Reply-To: <815303006.6467.1326841279163.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1758231896.17866.1327353798303.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12661300#comment-12661300 ] Brian Leathem commented on RF-11891: ------------------------------------ Simply commenting out this line would break the subsequent line: {code} String string = "E:/projs/richafces4/framework/trunk/impl/src/test/java/org/ajax4jsf/cache/extended.xcss"; parser.parse(string); {code} rather, given that this is a _public static void main_ method, I suspect the string should be set to _args\[0\]_. > Simple bug in org.richfaces.resource.Xcss2EcssConverter > ------------------------------------------------------- > > Key: RF-11891 > URL: https://issues.jboss.org/browse/RF-11891 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 4.1.0.Final > Environment: Any > Reporter: Dmytro Batishchev > Fix For: 4.2.0.CR1 > > > Simple bug in org.richfaces.resource.Xcss2EcssConverter classfile in main class, please, comment out or delete next line: > {quote} > _String string = "E:/projs/richafces4/framework/trunk/impl/src/test/java/org/ajax4jsf/cache/extended.xcss"_ > {quote} > PS: Sorry for my English. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 23 16:30:18 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 23 Jan 2012 16:30:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11910) Showcase: reduntant MANIFEST.MF, it is configured in pom.xml and also in resources In-Reply-To: <850752854.13850.1327076298214.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1293644671.17871.1327354218286.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-11910. -------------------------------- Assignee: Brian Leathem Resolution: Won't Fix The problem is, maven only generates the manifest.mf file during the package phase, not during the compile phase. This causes a problem when you run the showcase from the exploded directory, as the exploded directory does not have the MANIFEST.MF file present. The file is duplicated here as a workaround for this maven behavior. If you have an alternate solution/workaround for this problem, feel free to re-open this issue. > Showcase: reduntant MANIFEST.MF, it is configured in pom.xml and also in resources > ---------------------------------------------------------------------------------- > > Key: RF-11910 > URL: https://issues.jboss.org/browse/RF-11910 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: showcase > Affects Versions: 4.1.0.Final > Reporter: Luk?? Fry? > Assignee: Brian Leathem > > These files should be merged, and only {{pom.xml}} should be used preferably. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 23 16:43:19 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 23 Jan 2012 16:43:19 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11855) error@malformedXML on inputText files - Ajax Validation on event change - RichFaces 4.1 Final In-Reply-To: <26805713.30230.1324582930232.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <876353185.17908.1327354999249.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-11855. -------------------------------- Assignee: Brian Leathem Resolution: Won't Fix Without a [short, self-contained example|http://sscce.org/] demonstrating the error, it is impossible to isolate the problem causing the malformed XML response -- there are to many variables at play to proceed. Feel free to re-open with a simple example that demonstrates the problem. > error at malformedXML on inputText files - Ajax Validation on event change - RichFaces 4.1 Final > ---------------------------------------------------------------------------------------------- > > Key: RF-11855 > URL: https://issues.jboss.org/browse/RF-11855 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.1.0.Final > Environment: Websphere 8.0.0.1 - RAD 8.0.0.4 - JSF Mojorra 2.1.4 - Spring 3.0.6 Final - Hibernate Validator 4.2. - Java 6 > Reporter: Jean ANDRE > Assignee: Brian Leathem > Labels: INPUT, MALFORMED, UI, XML > Attachments: createClient1.xhtml, CreateClientController1.java, error at malformedXML-ScreenShot-1.jpg, error at malformedXML.debug.txt, error at malformedXML.viewSource.html, index.xhtml > > > We got a error at malformedXML message when we want to apply an ajax validation on imput text. > The field is include inside a tab in mode "server" - What ever the mode, we getting the error. Tab content is built by including some xhtml. See attachment. > {code} > > xmlns:h="http://java.sun.com/jsf/html" > xmlns:f="http://java.sun.com/jsf/core" > xmlns:rich="http://richfaces.org/rich" > xmlns:c="http://java.sun.com/jsp/jstl/core" > xmlns:a4j="http://richfaces.org/a4j"> > > > > > > > > > > > > > > > > {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 Jan 23 16:47:18 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 23 Jan 2012 16:47:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11867) showcase - rich:hotKey - pressing of home or end key causes moving of whole page instead of just selected/removing all cities on FF 3.6.x In-Reply-To: <1258943306.48046.1326104829526.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1813540518.17926.1327355238522.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem reassigned RF-11867: ---------------------------------- Assignee: Luk?? Fry? Lukas, please assess and schedule accordingly > showcase - rich:hotKey - pressing of home or end key causes moving of whole page instead of just selected/removing all cities on FF 3.6.x > ----------------------------------------------------------------------------------------------------------------------------------------- > > Key: RF-11867 > URL: https://issues.jboss.org/browse/RF-11867 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-misc, showcase > Affects Versions: 4.2.0.CR1 > Environment: container: Tomcat 7.0.20, JBoss AS 6.0.0.Final > browser: Firefox 3.6.24 > Reporter: Juraj Huska > Assignee: Luk?? Fry? > Priority: Minor > > The current binding for selecting/removing all cities in the demo for rich:hotKey are 'home' and 'end' buttons respectively. > It works as expected on Chrome and Firefox 8, however it is not working as expected on *Firefox 3.6.x*. > *Pressing of 'home' of 'end' button (city is selected, so the pickList has user focus) causes moving of the whole page, like the pickList has no focus. The cities are added/removed too, but with the side effect of the page moving, which indeed looks a little ugly.* > The workaround can be to use other keys. > What I would really appreciate is to bind some key to the switching between the two panels. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 23 16:47:18 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 23 Jan 2012 16:47:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11868) showcase - rich:hotKey - using bound hotKeys generates JS warning on FF 3.6.x In-Reply-To: <992167140.48074.1326105790453.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1326044153.17928.1327355238589.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem reassigned RF-11868: ---------------------------------- Assignee: Luk?? Fry? Lukas, please assess and schedule accordingly > showcase - rich:hotKey - using bound hotKeys generates JS warning on FF 3.6.x > ----------------------------------------------------------------------------- > > Key: RF-11868 > URL: https://issues.jboss.org/browse/RF-11868 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-misc, showcase > Affects Versions: 4.2.0.CR1 > Environment: container: all > browser: Firefox 3.6.x > Reporter: Juraj Huska > Assignee: Luk?? Fry? > Priority: Minor > > Using of bound hot keys in the demo for rich:hotKey generates on Firefox 3.6.x a warning: > {code} > The 'charCode' property of a keydown event should not be used. The value is meaningless. > {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 Jan 23 16:51:18 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 23 Jan 2012 16:51:18 -0500 (EST) 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: <138179345.17942.1327355478688.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 ] Brian Leathem reassigned RF-11905: ---------------------------------- Assignee: Juraj Huska When I shutdown AS 7 (7.0.2), I see: {code} 13:48:32,403 INFO [org.hibernate.tool.hbm2ddl.SchemaExport] HHH00227:Running hbm2ddl schema export 13:48:32,408 INFO [org.hibernate.tool.hbm2ddl.SchemaExport] HHH00230:Schema export complete {code} Can you provide details describing how to reproduce the error message you reported? > 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: Juraj Huska > Priority: Minor > > 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 Jan 23 16:53:18 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 23 Jan 2012 16:53:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11913) Simplify Documentation and Process of using Resource Packing with Custom Skins In-Reply-To: <130703154.17370.1327337778226.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <749974989.17948.1327355598258.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem reassigned RF-11913: ---------------------------------- Assignee: Luk?? Fry? Lukas, please assess and schedule accordingly. > Simplify Documentation and Process of using Resource Packing with Custom Skins > ------------------------------------------------------------------------------ > > Key: RF-11913 > URL: https://issues.jboss.org/browse/RF-11913 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Affects Versions: 4.1.0.Final > Reporter: Cody Lerum > Assignee: Luk?? Fry? > > Once a user creates their own skin the steps to enable resource packing are complex and not all documented in a easy to find manner. > At a minimum it would be nice to just pack the 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 Jan 23 17:17:18 2012 From: jira-events at lists.jboss.org (Brendan Healey (JIRA)) Date: Mon, 23 Jan 2012 17:17:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11888) Resource Servlet can't handle query string appended to resource url In-Reply-To: <787852126.1337.1326719298230.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1992657818.17957.1327357038289.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12661316#comment-12661316 ] Brendan Healey commented on RF-11888: ------------------------------------- >Note: When you upgrade from version 4.1 to 4.2, the URL for packed.js will change: Hello Brian, that's a very good point - that definitely takes the edge off my concerns, I should have realised this myself, too much coding. Thanks. > Resource Servlet can't handle query string appended to resource url > ------------------------------------------------------------------- > > Key: RF-11888 > URL: https://issues.jboss.org/browse/RF-11888 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: resource handling > Affects Versions: 4.1.0.Final > Environment: Glassfish 3.1.1 (NO Tomcat)/Mojarra 2.1.3 Chrome browser - > Reporter: Brendan Healey > Assignee: Luk?? Fry? > Priority: Critical > > A custom resource handler (http://blogs.oracle.com/rlubke/entry/jsf_2_0_new_feature) > can be used to append a version string (i.e. ?v=23) to a resource url to force a > browser to refresh a resource rather than use any cached version. > At present any appending of a version string causes a 404 response status, for example: > Request URL: > https://localhost:8181/MyApp/org.richfaces.resources/javax.faces.resource/org.richfaces.staticResource/4.1.0.Final/PackedCompressed/blueSky/packed/packed.css?v=23 > Removing the url parameter makes it work ok. As you can see I have resourceMapping > enabled. > This is essential to cause a browser to issue a request to the server if a static > resource is held in a browser cache and is not expired, but you've upgraded the > richfaces version. You have to have a way to invalidate the cache, and I'm not > seeing how this can be done in a sensible way. You can set the Cache-Control > no-cache header, but I'd need to do this in a way that says "I've just upgraded > richfaces, so don't use the cache, issue a request to the server for the resource, > but cache the result and use this until the next time". -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 23 17:19:18 2012 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 23 Jan 2012 17:19:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11914) Would like to see a dynamic subtable option for extendedDataTable In-Reply-To: <1890896963.17700.1327348938263.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1120039950.17960.1327357158397.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-11914: ------------------------------- Fix Version/s: 4.Future Scheduling to 4.Future for now, we'll re-visit when we look at all outstanding EDT feature requests. > Would like to see a dynamic subtable option for extendedDataTable > ----------------------------------------------------------------- > > Key: RF-11914 > URL: https://issues.jboss.org/browse/RF-11914 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.1.0.Final > Reporter: Robert Gary > Priority: Minor > Fix For: 4.Future > > > In RF 3.3.3 extendedDataTable offered the ability for the user to select any column and subgroup on it. This is no longer supported in RF 4.X. We do have the callapsibleSubTable tag but it requires each column to be pre-configured for subtable grouping. Could subtable grouping simply be an attribute on the column??? > > We would also want to allow the user to customize the expand/collapse subtable icon once the subtable grouping is enabled. > -Robert -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 23 17:35:18 2012 From: jira-events at lists.jboss.org (Robert Gary (JIRA)) Date: Mon, 23 Jan 2012 17:35:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11914) Would like to see a dynamic subtable option for extendedDataTable In-Reply-To: <1890896963.17700.1327348938263.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <761353395.17978.1327358118406.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12661321#comment-12661321 ] Robert Gary commented on RF-11914: ---------------------------------- Perhaps a better interface would be to add the option on the EDT tag... Where columntoSubgroupOn resolved to "name" This would prevent the uncomfortable situation that would arise if the user were able to request more than one column to be subgrouped on. > Would like to see a dynamic subtable option for extendedDataTable > ----------------------------------------------------------------- > > Key: RF-11914 > URL: https://issues.jboss.org/browse/RF-11914 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.1.0.Final > Reporter: Robert Gary > Priority: Minor > Fix For: 4.Future > > > In RF 3.3.3 extendedDataTable offered the ability for the user to select any column and subgroup on it. This is no longer supported in RF 4.X. We do have the callapsibleSubTable tag but it requires each column to be pre-configured for subtable grouping. Could subtable grouping simply be an attribute on the column??? > > We would also want to allow the user to customize the expand/collapse subtable icon once the subtable grouping is enabled. > -Robert -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 24 04:21:18 2012 From: jira-events at lists.jboss.org (Jan Papousek (JIRA)) Date: Tue, 24 Jan 2012 04:21:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11871) Mobile Showcase and a4j:poll demo: stop button doesn't respond on the first click In-Reply-To: <1495571967.52108.1326200889891.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1531747908.18566.1327396878418.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Papousek updated RF-11871: ------------------------------ Attachment: richfaces-showcase-4.2.0-20120123.231757-13-jbas7.war > Mobile Showcase and a4j:poll demo: stop button doesn't respond on the first click > --------------------------------------------------------------------------------- > > Key: RF-11871 > URL: https://issues.jboss.org/browse/RF-11871 > 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 > Reporter: Jan Papousek > Assignee: Jan Papousek > 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 Jan 24 04:25:18 2012 From: jira-events at lists.jboss.org (Jan Papousek (JIRA)) Date: Tue, 24 Jan 2012 04:25:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11871) Mobile Showcase and a4j:poll demo: stop button doesn't respond on the first click In-Reply-To: <1495571967.52108.1326200889891.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <268051908.18568.1327397118263.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Papousek updated RF-11871: ------------------------------ Steps to Reproduce: # download Showcase WAR file from attachments # start JBoss AS 7 # deploy the WAR file and open http://localhost:8080/showcase/phoneHome.jsf#poll:poll # click on the "Stop" button -> nothing happens (wrong) # click on the "Stop" button again -> polling is stopped (correct) 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 was:richfaces-showcase-4.1.1-20120106.230242-18 Workaround Description: (was: # deploy showcase and open http://localhost:8080/showcase/phoneHome.jsf#poll:poll (or open http://showcase-jpapouse.rhcloud.com/phoneHome.jsf#poll:poll without deploying) # click on the "Stop" button -> nothing happens (wrong) # click on the "Stop" button again -> polling is stopped (correct)) > Mobile Showcase and a4j:poll demo: stop button doesn't respond on the first click > --------------------------------------------------------------------------------- > > Key: RF-11871 > URL: https://issues.jboss.org/browse/RF-11871 > 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 > Reporter: Jan Papousek > Assignee: Jan Papousek > 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 Jan 24 04:29:18 2012 From: jira-events at lists.jboss.org (Jan Papousek (JIRA)) Date: Tue, 24 Jan 2012 04:29:18 -0500 (EST) 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: <768817335.18572.1327397358421.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 reopened RF-11872: ------------------------------- The issue isn't fixed,. so I'll update the description. > 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 > Reporter: Jan Papousek > Assignee: Brian Leathem > 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 Jan 24 04:29:18 2012 From: jira-events at lists.jboss.org (Jan Papousek (JIRA)) Date: Tue, 24 Jan 2012 04:29:18 -0500 (EST) 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: <1182468396.18575.1327397358524.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 updated RF-11872: ------------------------------ Attachment: richfaces-showcase-4.2.0-20120123.231757-13-jbas7.war > 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 > Reporter: Jan Papousek > Assignee: Brian Leathem > 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 Jan 24 04:31:18 2012 From: jira-events at lists.jboss.org (Jan Papousek (JIRA)) Date: Tue, 24 Jan 2012 04:31:18 -0500 (EST) 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: <273555640.18582.1327397478483.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 updated RF-11872: ------------------------------ Steps to Reproduce: # download Showcase WAR file from attachments # start JBoss AS 7 # deploy the WAR fileand open http://localhost:8080/showcase/phoneHome.jsf#region:region # type something into the name and e-mail input fields # click on the "Submit" button -> nothing happens (wrong) # click on the "Submit" button again -> the form is submitted (correct) was: # deploy showcase and open http://localhost:8080/showcase/phoneHome.jsf#region:region (or open http://showcase-jpapouse.rhcloud.com/phoneHome.jsf#region:region without deploying) # type something into the name and e-mail input fields # click on the "Submit" button -> nothing happens (wrong) # click on the "Submit" button again -> the form is submitted (correct) 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 was:richfaces-showcase-4.1.1-20120106.230242-18 > 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 > Reporter: Jan Papousek > Assignee: Brian Leathem > 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 Jan 24 04:31:18 2012 From: jira-events at lists.jboss.org (Jan Papousek (JIRA)) Date: Tue, 24 Jan 2012 04:31:18 -0500 (EST) 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: <385128133.18584.1327397478608.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=12661373#comment-12661373 ] Jan Papousek edited comment on RF-11872 at 1/24/12 4:29 AM: ------------------------------------------------------------ The issue isn't fixed, so I'll update the description. was (Author: jpapouse): The issue isn't fixed,. so I'll update the description. > 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 > Reporter: Jan Papousek > Assignee: Brian Leathem > 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 Jan 24 04:31:18 2012 From: jira-events at lists.jboss.org (Jan Papousek (JIRA)) Date: Tue, 24 Jan 2012 04:31:18 -0500 (EST) 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: <30219553.18588.1327397478876.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 updated RF-11872: ------------------------------ Steps to Reproduce: # download Showcase WAR file from attachments # start JBoss AS 7 # deploy the WAR file and open http://localhost:8080/showcase/phoneHome.jsf#region:region # type something into the name and e-mail input fields # click on the "Submit" button -> nothing happens (wrong) # click on the "Submit" button again -> the form is submitted (correct) was: # download Showcase WAR file from attachments # start JBoss AS 7 # deploy the WAR fileand open http://localhost:8080/showcase/phoneHome.jsf#region:region # type something into the name and e-mail input fields # click on the "Submit" button -> nothing happens (wrong) # click on the "Submit" button again -> the form is submitted (correct) > 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 > Reporter: Jan Papousek > Assignee: Brian Leathem > 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 Jan 24 04:37:19 2012 From: jira-events at lists.jboss.org (Jan Papousek (JIRA)) Date: Tue, 24 Jan 2012 04:37:19 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11871) Mobile Showcase and a4j:poll demo: stop button doesn't respond on the first click In-Reply-To: <1495571967.52108.1326200889891.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1407929753.18615.1327397839087.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12661378#comment-12661378 ] Jan Papousek commented on RF-11871: ----------------------------------- Brian: It's weird. The behaviour is still the same on my computer. Have you tried mobile version? It's important, because the button works correctly in the common version. > Mobile Showcase and a4j:poll demo: stop button doesn't respond on the first click > --------------------------------------------------------------------------------- > > Key: RF-11871 > URL: https://issues.jboss.org/browse/RF-11871 > 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 > Reporter: Jan Papousek > Assignee: Jan Papousek > 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 Jan 24 05:15:18 2012 From: jira-events at lists.jboss.org (Juraj Huska (JIRA)) Date: Tue, 24 Jan 2012 05:15:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11903) showcase - a4j:push - error on the server side, Unable to resume the suspended connection with latchId In-Reply-To: <1647203784.10826.1326982278758.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1373045697.18651.1327400118572.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12661380#comment-12661380 ] Juraj Huska commented on RF-11903: ---------------------------------- I could not reproduce any of above mentioned errors after building components and showcase snapshots. > showcase - a4j:push - error on the server side, Unable to resume the suspended connection with latchId > ------------------------------------------------------------------------------------------------------- > > Key: RF-11903 > URL: https://issues.jboss.org/browse/RF-11903 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll, showcase, third-party > Affects Versions: 4.1.0.Final > Environment: container: JBoss AS 6.0.0.Final, JBoss AS 7.0.2.Final, JBoss AS 7.1.0.CR1b > browsers: all > application: showcase 4.2.0-SNAPSHOT > Reporter: Juraj Huska > Assignee: Juraj Huska > Fix For: 4.2.0.CR1 > > > *All* demos for 14j:push are causing *error* on the server side when it is pushing something to them: > {code} > 15:03:42,962 ERROR [org.atmosphere.container.BlockingIOCometSupport] Unable to resume the suspended connection with latchId: 11597405 > {code} > Note that the latchId is for each push different. *The functionality* however remains *ok*, at least for Topics context usage and JMS push. > This particular error is thrown only on *JBoss AS 6*, *other containers* throws also some errors, please see the comments below. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 24 05:23:19 2012 From: jira-events at lists.jboss.org (Juraj Huska (JIRA)) Date: Tue, 24 Jan 2012 05:23:19 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11903) showcase - a4j:push - error on the server side, Unable to resume the suspended connection with latchId In-Reply-To: <1647203784.10826.1326982278758.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1877875573.18674.1327400599880.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12661380#comment-12661380 ] Juraj Huska edited comment on RF-11903 at 1/24/12 5:23 AM: ----------------------------------------------------------- I could not reproduce any of above mentioned errors after building components and showcase snapshots. So as you guess the upgrade of Atmosphere fixed it. was (Author: jhuska): I could not reproduce any of above mentioned errors after building components and showcase snapshots. > showcase - a4j:push - error on the server side, Unable to resume the suspended connection with latchId > ------------------------------------------------------------------------------------------------------- > > Key: RF-11903 > URL: https://issues.jboss.org/browse/RF-11903 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll, showcase, third-party > Affects Versions: 4.1.0.Final > Environment: container: JBoss AS 6.0.0.Final, JBoss AS 7.0.2.Final, JBoss AS 7.1.0.CR1b > browsers: all > application: showcase 4.2.0-SNAPSHOT > Reporter: Juraj Huska > Assignee: Juraj Huska > Fix For: 4.2.0.CR1 > > > *All* demos for 14j:push are causing *error* on the server side when it is pushing something to them: > {code} > 15:03:42,962 ERROR [org.atmosphere.container.BlockingIOCometSupport] Unable to resume the suspended connection with latchId: 11597405 > {code} > Note that the latchId is for each push different. *The functionality* however remains *ok*, at least for Topics context usage and JMS push. > This particular error is thrown only on *JBoss AS 6*, *other containers* throws also some errors, please see the comments below. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 24 05:25:19 2012 From: jira-events at lists.jboss.org (Juraj Huska (JIRA)) Date: Tue, 24 Jan 2012 05:25:19 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11903) showcase - a4j:push - error on the server side, Unable to resume the suspended connection with latchId In-Reply-To: <1647203784.10826.1326982278758.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <655101294.18688.1327400719085.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj Huska resolved RF-11903. ------------------------------ Resolution: Done Fixed with Atmosphere upgrade. > showcase - a4j:push - error on the server side, Unable to resume the suspended connection with latchId > ------------------------------------------------------------------------------------------------------- > > Key: RF-11903 > URL: https://issues.jboss.org/browse/RF-11903 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll, showcase, third-party > Affects Versions: 4.1.0.Final > Environment: container: JBoss AS 6.0.0.Final, JBoss AS 7.0.2.Final, JBoss AS 7.1.0.CR1b > browsers: all > application: showcase 4.2.0-SNAPSHOT > Reporter: Juraj Huska > Assignee: Juraj Huska > Fix For: 4.2.0.CR1 > > > *All* demos for 14j:push are causing *error* on the server side when it is pushing something to them: > {code} > 15:03:42,962 ERROR [org.atmosphere.container.BlockingIOCometSupport] Unable to resume the suspended connection with latchId: 11597405 > {code} > Note that the latchId is for each push different. *The functionality* however remains *ok*, at least for Topics context usage and JMS push. > This particular error is thrown only on *JBoss AS 6*, *other containers* throws also some errors, please see the comments below. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 24 05:25:19 2012 From: jira-events at lists.jboss.org (Juraj Huska (JIRA)) Date: Tue, 24 Jan 2012 05:25:19 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11903) showcase - a4j:push - error on the server side, Unable to resume the suspended connection with latchId In-Reply-To: <1647203784.10826.1326982278758.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <5261767.18696.1327400719501.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj Huska closed RF-11903. ---------------------------- > showcase - a4j:push - error on the server side, Unable to resume the suspended connection with latchId > ------------------------------------------------------------------------------------------------------- > > Key: RF-11903 > URL: https://issues.jboss.org/browse/RF-11903 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll, showcase, third-party > Affects Versions: 4.1.0.Final > Environment: container: JBoss AS 6.0.0.Final, JBoss AS 7.0.2.Final, JBoss AS 7.1.0.CR1b > browsers: all > application: showcase 4.2.0-SNAPSHOT > Reporter: Juraj Huska > Assignee: Juraj Huska > Fix For: 4.2.0.CR1 > > > *All* demos for 14j:push are causing *error* on the server side when it is pushing something to them: > {code} > 15:03:42,962 ERROR [org.atmosphere.container.BlockingIOCometSupport] Unable to resume the suspended connection with latchId: 11597405 > {code} > Note that the latchId is for each push different. *The functionality* however remains *ok*, at least for Topics context usage and JMS push. > This particular error is thrown only on *JBoss AS 6*, *other containers* throws also some errors, please see the comments below. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 24 05:32:18 2012 From: jira-events at lists.jboss.org (Jan Papousek (JIRA)) Date: Tue, 24 Jan 2012 05:32:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11871) Mobile Showcase and a4j:poll demo: stop button doesn't respond on the first click In-Reply-To: <1495571967.52108.1326200889891.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1854304381.18713.1327401138294.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Papousek updated RF-11871: ------------------------------ Assignee: Brian Leathem (was: Jan Papousek) > Mobile Showcase and a4j:poll demo: stop button doesn't respond on the first click > --------------------------------------------------------------------------------- > > Key: RF-11871 > URL: https://issues.jboss.org/browse/RF-11871 > 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 > Reporter: Jan Papousek > Assignee: Brian Leathem > 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 Jan 24 06:31:18 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?J=C3=A1n_Hala=C5=A1a_=28JIRA=29?=) Date: Tue, 24 Jan 2012 06:31:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11915) MenuGroup with all items disabled or no items causes JS error Message-ID: <2107920490.18850.1327404678300.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> J?n Hala?a created RF-11915: ------------------------------- Summary: MenuGroup with all items disabled or no items causes JS error Key: RF-11915 URL: https://issues.jboss.org/browse/RF-11915 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-menu Affects Versions: 4.1.0.Final Environment: Tomcat 6.0.26, MyFaces 2.1.13, RichFaces Reporter: J?n Hala?a Submenu (r:menuGroup) containing only disabled items or no items, causes a JavaScript error when it is supposed to get hidden (moving cursor to the next item in the parent menu). In Firefox 9: parentMenu is undefined menu-base.js, line 126 In MSIE 7: 'nodeType' is null or not an object richfaces.js, line 43 It's the same error only reported from the different level of the call stack. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 24 07:24:18 2012 From: jira-events at lists.jboss.org (Juraj Huska (JIRA)) Date: Tue, 24 Jan 2012 07:24:18 -0500 (EST) 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: <85845914.18920.1327407858366.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=12661409#comment-12661409 ] Juraj Huska commented on RF-11905: ---------------------------------- After first starting of JBoss it shuts down as you said. It is noticeable after several shut downing. I have also found AS7-2045, where they suffer the same problem. It seems therefore that it is AS problem, not showcase. I have tried also the workaround described in that JIRA, but I am not sure whether I have set it up correctly, since in showcase we are using dataSource to provide persistence connection. > 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: Juraj Huska > Priority: Minor > > 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 Tue Jan 24 07:24:18 2012 From: jira-events at lists.jboss.org (Juraj Huska (JIRA)) Date: Tue, 24 Jan 2012 07:24:18 -0500 (EST) 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: <1762263254.18922.1327407858527.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 reassigned RF-11905: -------------------------------- Assignee: (was: Juraj Huska) > 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 > Priority: Minor > > 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 Tue Jan 24 08:30:18 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 24 Jan 2012 08:30:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11903) showcase - a4j:push - error on the server side, Unable to resume the suspended connection with latchId In-Reply-To: <1647203784.10826.1326982278758.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1084332583.19025.1327411818419.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? reopened RF-11903: ----------------------------- > showcase - a4j:push - error on the server side, Unable to resume the suspended connection with latchId > ------------------------------------------------------------------------------------------------------- > > Key: RF-11903 > URL: https://issues.jboss.org/browse/RF-11903 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll, showcase, third-party > Affects Versions: 4.1.0.Final > Environment: container: JBoss AS 6.0.0.Final, JBoss AS 7.0.2.Final, JBoss AS 7.1.0.CR1b > browsers: all > application: showcase 4.2.0-SNAPSHOT > Reporter: Juraj Huska > Assignee: Juraj Huska > > *All* demos for 14j:push are causing *error* on the server side when it is pushing something to them: > {code} > 15:03:42,962 ERROR [org.atmosphere.container.BlockingIOCometSupport] Unable to resume the suspended connection with latchId: 11597405 > {code} > Note that the latchId is for each push different. *The functionality* however remains *ok*, at least for Topics context usage and JMS push. > This particular error is thrown only on *JBoss AS 6*, *other containers* throws also some errors, please see the comments below. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 24 08:30:18 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 24 Jan 2012 08:30:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11903) showcase - a4j:push - error on the server side, Unable to resume the suspended connection with latchId In-Reply-To: <1647203784.10826.1326982278758.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1268704222.19028.1327411818561.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved RF-11903. ----------------------------- Fix Version/s: (was: 4.2.0.CR1) Resolution: Duplicate Issue > showcase - a4j:push - error on the server side, Unable to resume the suspended connection with latchId > ------------------------------------------------------------------------------------------------------- > > Key: RF-11903 > URL: https://issues.jboss.org/browse/RF-11903 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll, showcase, third-party > Affects Versions: 4.1.0.Final > Environment: container: JBoss AS 6.0.0.Final, JBoss AS 7.0.2.Final, JBoss AS 7.1.0.CR1b > browsers: all > application: showcase 4.2.0-SNAPSHOT > Reporter: Juraj Huska > Assignee: Juraj Huska > > *All* demos for 14j:push are causing *error* on the server side when it is pushing something to them: > {code} > 15:03:42,962 ERROR [org.atmosphere.container.BlockingIOCometSupport] Unable to resume the suspended connection with latchId: 11597405 > {code} > Note that the latchId is for each push different. *The functionality* however remains *ok*, at least for Topics context usage and JMS push. > This particular error is thrown only on *JBoss AS 6*, *other containers* throws also some errors, please see the comments below. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 24 08:34:18 2012 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 24 Jan 2012 08:34:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11910) Showcase: reduntant MANIFEST.MF, it is configured in pom.xml and also in resources In-Reply-To: <850752854.13850.1327076298214.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <1201742167.19039.1327412058230.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? reopened RF-11910: ----------------------------- Assignee: Luk?? Fry? (was: Brian Leathem) Brian, we can re-schedule manifest generation to the another phase. I will investigate if it can help and come back with results. > Showcase: reduntant MANIFEST.MF, it is configured in pom.xml and also in resources > ---------------------------------------------------------------------------------- > > Key: RF-11910 > URL: https://issues.jboss.org/browse/RF-11910 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: showcase > Affects Versions: 4.1.0.Final > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > > These files should be merged, and only {{pom.xml}} should be used preferably. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.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 Jan 24 08:38:18 2012 From: jira-events at lists.jboss.org (Brendan Healey (JIRA)) Date: Tue, 24 Jan 2012 08:38:18 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11588) HeaderClass is ignored on ExtendedDataTable column In-Reply-To: <1427004328.27237.1319584545776.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> Message-ID: <777789222.19046.1327412298757.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> [ https://issues.jboss.org/browse/RF-11588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12661427#comment-12661427 ] Brendan Healey commented on RF-11588: ------------------------------------- just hit this one in 4.1.0.Final... for the record > HeaderClass is ignored on ExtendedDataTable column > -------------------------------------------------- > > Key: RF-11588 > URL: https://issues.jboss.org/browse/RF-11588 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.1.0.Milestone3 > Reporter: Cody Lerum > Priority: Minor > Fix For: 4.Future > > > When a header class is defined on a rich:column inside an rich:extendedDataTable it is ignored > Assume > {code} > > Foo > > > {code} > What is rendered is > {code} >
>
>
>
>
>
Foo
>
> 		>
>
>
>
>
Foo
>
> 		>
>
>
>
>
Foo
>
> 		>
>
>
>
>
Foo
>
>
_ elements, and _
_ elements. I suppressed the html scope attribute when the element is not th. Alternatively, we could look changing the _
_ elements. > Data table: The scope attribute on the td element is obsolete > ------------------------------------------------------------- > > Key: RF-11860 > URL: https://issues.jboss.org/browse/RF-11860 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: compatibility, component-tables > Affects Versions: 4.1.0.Final > Environment: RichFaces 4.1.1-SNAPSHOT > Metamer 4.1.1-SNAPSHOT r.23118 > Mojarra 2.1.5 > JBoss AS 7.1.0.CR1 > OpenJDK Runtime Environment 1.6.0_22-b22 @ Linux > Chrome 16.0.912.63 @ Linux i686 > Reporter: Pavol Pitonak > Assignee: Brian Leathem > Priority: Minor > Fix For: 4.2.0.CR1 > > > The column footer is rendered as in following code snippet (can be reproduced in Metamer http://localhost:8080/metamer/faces/components/richDataTable/facets.xhtml): > {code:xml} >
> State Footer > > Capital Footer >
> Footer >
>
>
>
>
>
Foo
>
>