[JBoss JIRA] Created: (RF-11447) extendedDataTable re-rendering
by Brendan Healey (JIRA)
extendedDataTable re-rendering
-------------------------------
Key: RF-11447
URL: https://issues.jboss.org/browse/RF-11447
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 4.0.0.Final
Environment: Mojarra 2.1.3.
Reporter: Brendan Healey
I've got a h:selectOneMenu inside a column of an extendedDataTable which can
be used to modify a property of the current row. The changeInviteState
valueChangeListener persists the modification to the database. What I would
expect to happen in the below example is that the getEventTeamList() method
returns the current data, selectOneMenu is used to make a change and the
nested "<a4j:ajax render="teamTable"/>" causes the table to be re-rendered
(the table getter getEventTeamList should be called to refresh the data).
The problem is that this re-rendering of the table doesn't happen. I see the
value change listener firing but the table value getter is not executed after
the VCL.
The importance of being able to re-render the table after the data change is
that when using optimistic locking the table will contain a stale version
number and subsequent modification attempts will fail (unless you refresh the
data before making a modification, but that is an inferior approach).
Note that removing <a4j:ajax event="selectionchange" makes no difference.
<rich:extendedDataTable
id="teamTable"
binding="#{bean.teamTable}"
value="#{bean.eventTeamList}" var="var"
selectionMode="single"
selection="#{bean.selectedTeamRow}">
<a4j:ajax event="selectionchange"
listener="#{bean.teamRowSelect}"/>
<rich:column style="text-align: center">
<h:selectOneMenu value="#{var.inviteState}"
immediate="true"
valueChangeListener="#{bean.changeInviteState}"
rendered="#{bean.showStatusInput}">
<f:selectItems value="#{bean.teamStatusOptions}"
var="svar" itemLabel="#{svar.localName}" itemValue="#{svar}"/>
<a4j:ajax render="teamTable"/>
</h:selectOneMenu>
</rich:column>
</rich:extendedDataTable>
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] (RF-11487) Metamer: rich:calendar: @showApplyButton=false causes ConvertException
by Brian Leathem (Updated) (JIRA)
[ https://issues.jboss.org/browse/RF-11487?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-11487:
-------------------------------
Fix Version/s: 4.Future
> Metamer: rich:calendar: @showApplyButton=false causes ConvertException
> ----------------------------------------------------------------------
>
> Key: RF-11487
> URL: https://issues.jboss.org/browse/RF-11487
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-input
> Affects Versions: 4.1.0.Milestone2
> Environment: RichFaces 4.1.0.20110910-M2 r.
> Metamer 4.1.0.20110910-M2 r.22701
> Mojarra 2.0.4-b09-jbossorg-4
> JBoss Web 7.0.1.Final
> Java(TM) SE Runtime Environment 1.6.0_26-b03 @ Linux
> Mozilla/5.0 (X11; Linux i686; rv:7.0) Gecko/20100101 Firefox/7.0
> Reporter: Ján Jamrich
> Assignee: Ján Jamrich
> Priority: Minor
> Fix For: 4.Future
>
>
> set @showApplyButton = false raise following error:
> {quote}
> javax.faces.convert.ConverterException: form:calendar: 'Thu Sep 01 02:00:00 CEST 2011' could not be understood as a date.
> {quote}
> Even value was selected from calendar and submitted by button without validation errors (Sep 14, 2011 13:03, output: Sep 14, 2011 13:03)
> Another value set and submitted: Sep 2, 2011 10:09, and error the same as above (with Sep 1)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] (RF-11487) Metamer: rich:calendar: @showApplyButton=false causes ConvertException
by Jay Balunas (Commented) (JIRA)
[ https://issues.jboss.org/browse/RF-11487?page=com.atlassian.jira.plugin.s... ]
Jay Balunas commented on RF-11487:
----------------------------------
Can we get a step by step for steps to reproduce.
> Metamer: rich:calendar: @showApplyButton=false causes ConvertException
> ----------------------------------------------------------------------
>
> Key: RF-11487
> URL: https://issues.jboss.org/browse/RF-11487
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-input
> Affects Versions: 4.1.0.Milestone2
> Environment: RichFaces 4.1.0.20110910-M2 r.
> Metamer 4.1.0.20110910-M2 r.22701
> Mojarra 2.0.4-b09-jbossorg-4
> JBoss Web 7.0.1.Final
> Java(TM) SE Runtime Environment 1.6.0_26-b03 @ Linux
> Mozilla/5.0 (X11; Linux i686; rv:7.0) Gecko/20100101 Firefox/7.0
> Reporter: Ján Jamrich
> Assignee: Ján Jamrich
> Priority: Minor
>
> set @showApplyButton = false raise following error:
> {quote}
> javax.faces.convert.ConverterException: form:calendar: 'Thu Sep 01 02:00:00 CEST 2011' could not be understood as a date.
> {quote}
> Even value was selected from calendar and submitted by button without validation errors (Sep 14, 2011 13:03, output: Sep 14, 2011 13:03)
> Another value set and submitted: Sep 2, 2011 10:09, and error the same as above (with Sep 1)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] (RF-11507) Metamer: rich:extendedDataTable: reset sorting button causes exception in log
by Ján Jamrich (Created) (JIRA)
Metamer: rich:extendedDataTable: reset sorting button causes exception in log
-----------------------------------------------------------------------------
Key: RF-11507
URL: https://issues.jboss.org/browse/RF-11507
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: cdk
Affects Versions: 4.1.0.Milestone3
Environment: RichFaces 4.1.0.20111011-M3 r.
Metamer 4.1.0.20111011-M3 r.22776
Mojarra 2.0.4-b09-jbossorg-4
JBoss Web 7.0.1.Final
Java(TM) SE Runtime Environment 1.6.0_26-b03 @ Linux
Firefox 8.0 @ Linux i686
Reporter: Ján Jamrich
Press button "Reset Sorting" on page faces/components/richExtendedDataTable/sorting-using-component-control.xhtml causes exception in log.
It doesn't matter if some sorting was done before press this button.
There is stack trace:
SEVERE [org.richfaces.log.Context] (http--127.0.0.1-8080-6) null: java.lang.NullPointerException
at org.richfaces.renderkit.SortingFilteringRowsRenderer.updateSortOrder(SortingFilteringRowsRenderer.java:127) [richfaces-components-ui-4.1.0.20111011-M3.jar:]
at org.richfaces.renderkit.SortingFilteringRowsRenderer.decodeSorting(SortingFilteringRowsRenderer.java:109) [richfaces-components-ui-4.1.0.20111011-M3.jar:]
at org.richfaces.renderkit.SortingFilteringRowsRenderer.decodeSortingFiltering(SortingFilteringRowsRenderer.java:67) [richfaces-components-ui-4.1.0.20111011-M3.jar:]
at org.richfaces.renderkit.ExtendedDataTableRenderer.doDecode(ExtendedDataTableRenderer.java:822) [richfaces-components-ui-4.1.0.20111011-M3.jar:]
at org.richfaces.renderkit.RendererBase.decode(RendererBase.java:80) [richfaces-components-ui-4.1.0.20111011-M3.jar:]
at javax.faces.component.UIComponentBase.decode(UIComponentBase.java:795) [jboss-jsf-api_2.0_spec-1.0.0.Final.jar:1.0.0.Final]
at org.richfaces.component.UIDataAdaptor.processDecodes(UIDataAdaptor.java:823) [richfaces-components-ui-4.1.0.20111011-M3.jar:]
at org.richfaces.context.PartialViewExecuteVisitCallback.visit(PartialViewExecuteVisitCallback.java:53) [richfaces-core-impl-4.1.0.20111011-M3.jar:]
at org.richfaces.context.BaseExtendedVisitContext.invokeVisitCallback(BaseExtendedVisitContext.java:321) [richfaces-core-impl-4.1.0.20111011-M3.jar:]
at org.richfaces.component.UIDataAdaptor.visitTree(UIDataAdaptor.java:1323) [richfaces-components-ui-4.1.0.20111011-M3.jar:]
at javax.faces.component.UIComponent.visitTree(UIComponent.java:1496) [jboss-jsf-api_2.0_spec-1.0.0.Final.jar:1.0.0.Final]
at javax.faces.component.UIForm.visitTree(UIForm.java:335) [jboss-jsf-api_2.0_spec-1.0.0.Final.jar:1.0.0.Final]
at javax.faces.component.UIComponent.visitTree(UIComponent.java:1496) [jboss-jsf-api_2.0_spec-1.0.0.Final.jar:1.0.0.Final]
at javax.faces.component.UIComponent.visitTree(UIComponent.java:1496) [jboss-jsf-api_2.0_spec-1.0.0.Final.jar:1.0.0.Final]
at javax.faces.component.UIComponent.visitTree(UIComponent.java:1496) [jboss-jsf-api_2.0_spec-1.0.0.Final.jar:1.0.0.Final]
at org.richfaces.context.ExtendedPartialViewContextImpl.executeComponents(ExtendedPartialViewContextImpl.java:237) [richfaces-core-impl-4.1.0.20111011-M3.jar:]
at org.richfaces.context.ExtendedPartialViewContextImpl.processPartialExecutePhase(ExtendedPartialViewContextImpl.java:217) [richfaces-core-impl-4.1.0.20111011-M3.jar:]
at org.richfaces.context.ExtendedPartialViewContextImpl.processPartial(ExtendedPartialViewContextImpl.java:196) [richfaces-core-impl-4.1.0.20111011-M3.jar:]
at javax.faces.component.UIViewRoot.processDecodes(UIViewRoot.java:924) [jboss-jsf-api_2.0_spec-1.0.0.Final.jar:1.0.0.Final]
at com.sun.faces.lifecycle.ApplyRequestValuesPhase.execute(ApplyRequestValuesPhase.java:78) [jsf-impl-2.0.4-b09-jbossorg-4.jar:2.0.4-b09-jbossorg-4]
at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) [jsf-impl-2.0.4-b09-jbossorg-4.jar:2.0.4-b09-jbossorg-4]
at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118) [jsf-impl-2.0.4-b09-jbossorg-4.jar:2.0.4-b09-jbossorg-4]
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:312) [jboss-jsf-api_2.0_spec-1.0.0.Final.jar:1.0.0.Final]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
at org.richfaces.tests.metamer.TestIdentityFilter.doFilter(TestIdentityFilter.java:93) [classes:]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
at org.richfaces.webapp.PushFilter.doFilter(PushFilter.java:130) [richfaces-core-impl-4.1.0.20111011-M3.jar:]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:139) [jboss-as-web-7.0.1.Final.jar:7.0.1.Final]
at org.jboss.as.web.NamingValve.invoke(NamingValve.java:57) [jboss-as-web-7.0.1.Final.jar:7.0.1.Final]
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:154) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:667) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:952) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_26]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] Created: (RF-11403) showcase - a4j:queue - input in sample is wrongly generated, it is disabled on Tomcat
by Juraj Huska (JIRA)
showcase - a4j:queue - input in sample is wrongly generated, it is disabled on Tomcat
-------------------------------------------------------------------------------------
Key: RF-11403
URL: https://issues.jboss.org/browse/RF-11403
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: showcase
Affects Versions: 4.1.0.Milestone2
Environment: containers: Tomcat 6.0.32 and Tomcat 7.0.20
war: richfaces-showcase-4.1.0.20110910-tomcat6.war from maven staging repo
browsers: Chrome 13, FF 3.6
Reporter: Juraj Huska
Input for typing, which should fire events(first input), is has wrongly generated source code, since it is disabled by default. Its source code is:
{code:xml}
<input id="form:myinput" type="text" name="form:myinput" value="" onkeyup="addEvent();" disabled="disabled">
{code}
On JBoss 6 or 7 this input works fine and has source code:
{code:xml}
<input id="form:myinput" type="text" name="form:myinput" value="" onkeyup="jsf.util.chain(this,event,'addEvent();','RichFaces.ajax(this,event,{"parameters":{"javax.faces.behavior.event":"keyup","org.richfaces.ajax.component":"form:myinput"} ,"sourceId":this,"begin":"addRequest();"} )')">
{code}
This is noticed only on Tomcats. The page source code is the same on tomcat and jboss wars, they are different after deploying.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month