December 2013 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-13168) 3rd party JSF component disappears on RichFaces ajax refresh

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-13168?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč reassigned RF-13168: ------------------------------- Assignee: (was: Lukáš Fryč) > 3rd party JSF component disappears on RichFaces ajax refresh > ------------------------------------------------------------ > > Key: RF-13168 > URL: https://issues.jboss.org/browse/RF-13168 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: compatibility, component-a4j-core > Reporter: Frank Langelage > Labels: interop, jsf22 > Fix For: 5.0.0.Alpha3 > > Attachments: install-mojarra-2.1.19.cli, Jira-WFLY-UT.tar, xaa, xab, xac > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > On some of my pages I'm using richfaces a4j:poll to refresh components regularly. The components refreshed is an openfaces datatable. > This does not work with WildFly build from current sources. > Same code works with JBoss AS 7.20. So problem is not related to richfaces or openfaces for me. Probably related to replacement of jboss-web with undertow. > I'll attach a small project showing the problem. > The mojarra datatable works fine, is refreshed every 10 seconds. > The openfaces datatable below disappears on first refresh. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (RF-13317) ExtendedPartialViewContextImpl should specify correct javax.faces.ViewState id in startUpdate()

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-13317?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on RF-13317: --------------------------------- We are not able to simply fix this issue as the the straight-forward fix involves JSF-implementation-specific detail: the viewStateId is computed by [{{com.sun.faces.util.Util#getViewStateId(FacesContext)}}|https://github.com/jboss/mojarra/blob/2.2.4-jbossorg-1/jsf-ri/src/main/java/com/sun/faces/context/PartialViewContextImpl.java#L451]. ---- The right fix I have in mind could be leveraging the fact RichFaces doesn't need to re-implement PartialViewContextImpl, instead, it could just use DeferredEndingPartialResponseWriter which will add RichFaces {{<extension>}} and {{JavaScriptService}} scripts at the end of the partial response. This would guard us against possible future changes, however it's not certain whether we won't perceive regressions. > ExtendedPartialViewContextImpl should specify correct javax.faces.ViewState id in startUpdate() > ----------------------------------------------------------------------------------------------- > > Key: RF-13317 > URL: https://issues.jboss.org/browse/RF-13317 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.4 > Environment: Wildfly-8.0.0.Beta1, jsf-impl-2.2.3-jbossorg-1 > Reporter: Matti Bickel > Assignee: Lukáš Fryč > Priority: Critical > Labels: jsf22 > Fix For: 4.3.5, 5.0.0.Alpha3 > > > I'm using several {{<rich:autocomplete>}} fields in a {{<h:form>}}, but have noticed the issue with several other AJAX requests: > When the response comes back, the data is fine but I get a JSF error saying > bq. During update: javax.faces.ViewState not found > Following that, no componentData is available to the Autocomplete component and no suggestions get displayed. > For reference the [javadoc for ResponseStateManager.VIEW_STATE_PARAM|https://javaserverfaces.java.net/no...] says: > {quote} > Implementations must use this constant field value as the name of the client parameter in which to save the state between requests. The id attribute must be a concatenation of the return from UIComponent.getContainerClientId(javax.faces.context.FacesContext), the return from UINamingContainer.getSeparatorChar(javax.faces.context.FacesContext), this constant field value, the separator char, and a number that is guaranteed to be unique with respect to all the other instances of this kind of client parameter in the view. > {quote} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (RF-13213) RichFaces 4.5 CSV should share logic with RichFaces 5

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/RF-13213?page=com.atlassian.jira.plugin.s... ] Juraj Húska closed RF-13213. ---------------------------- Verified. Closing. > RichFaces 4.5 CSV should share logic with RichFaces 5 > ----------------------------------------------------- > > Key: RF-13213 > URL: https://issues.jboss.org/browse/RF-13213 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Fix For: 4.5.0.Alpha1 > > > The Client-Side Validation is a service on client which should share logic between RichFaces 5 and RichFaces 4.5 otherwise component validation won't be coordinated. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (RF-13186) Showcase 4.5.x fails

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/RF-13186?page=com.atlassian.jira.plugin.s... ] Juraj Húska closed RF-13186. ---------------------------- Verified. Closing. > Showcase 4.5.x fails > -------------------- > > Key: RF-13186 > URL: https://issues.jboss.org/browse/RF-13186 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.5.0.Alpha1 > Reporter: Michal Petrov > Assignee: Lukáš Fryč > Fix For: 4.5.0.Alpha1 > > > [https://github.com/michpetrov/richfaces/tree/showcase-4.5.x/examples/show...] - showcase 4.5 > [https://github.com/richfaces4/components/tree/4.5.x] - 4.5.x components > [https://github.com/richfaces4/dev-examples/tree/4.5.x] - 4.5 dev-examples > Builds and deploys fine. > Examples that do not work: > * -several examples (e.g. actionListener) produce "The form component needs to have a UIForm in its ancestry. Suggestion: enclose the necessary components within <h:form>"- > * validation - fails because rf.rf4.ui.Message is not defined, the resource is not being included due to resource optimization > * trees/rich:tree - missing …/javax.faces.resource/node_icon.gif.jsf?ln=org.richfaces > * menus/rich:contextMenu and rich:dropDownMenu - not working, probably for the same reason as validators (missing proper javascript resource) > * inputs/rich:inplaceInput - ditto > * selects/rich:inplaceSelect - ditto > * output/rich:tooltip - ditto > When resource optimization some components (dataTables) are missing background image causing a badly generated CSS. {{background-image: url()}} > h5. resource optimization turned off > h6. Issue with Validator > - org.richfaces.validator.FacesObjectDescriptor.getMessage() > - collision between RF4.5 and RF5 > the interface is the same in both versions but the Message class is in different packages in the two > h6. Issue with menus > - org.richfaces.renderkit.html.MenuItemRendererBase.getUtils() > - probably the same problem -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (RF-13147) Rename all occurences JavaScript closures which references to RichFaces object to rf

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/RF-13147?page=com.atlassian.jira.plugin.s... ] Juraj Húska reopened RF-13147: ------------------------------ I am reopening the issue because it was not changed for these two files in RF5: * ordering-list-bridge.js * pick-list-bridge.js > Rename all occurences JavaScript closures which references to RichFaces object to rf > ------------------------------------------------------------------------------------ > > Key: RF-13147 > URL: https://issues.jboss.org/browse/RF-13147 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Fix For: 4.5.0.Alpha1, 5.0.0.Alpha2 > > > It will unify sources and make easier to scan through files: > {code} > (function ($, rf) { > rf.ui = rf.ui || {}; > .... > })(RichFaces.jQuery, RichFaces); > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (RF-13147) Rename all occurences JavaScript closures which references to RichFaces object to rf

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/RF-13147?page=com.atlassian.jira.plugin.s... ] Juraj Húska edited comment on RF-13147 at 12/10/13 11:04 AM: ------------------------------------------------------------- I am verifying the issue. I have encounter following fact: some of the *.js files contains closure as described above, but some other contains a very slightly different one: {code:none} (function ($, rf) { rf.ui = rf.ui || {}; .... })(RichFaces.jQuery, window.RichFaces); {code} I guess it is only a cosmetic difference. Am I right ? It is by default searched in window object ? If yes, I would close this issue. was (Author: jhuska): I am verifying the issue. I have encounter following fact: some of the *.js files contains closure as described above, but some other contains a very slightly different one: {code:none} (function ($, rf) { rf.ui = rf.ui || {}; .... })(RichFaces.jQuery, window.RichFaces); {code} I guess it is only a cosmetic difference. Am I right ? It is by default searched in window object ? If yest I would close this issue. > Rename all occurences JavaScript closures which references to RichFaces object to rf > ------------------------------------------------------------------------------------ > > Key: RF-13147 > URL: https://issues.jboss.org/browse/RF-13147 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Fix For: 4.5.0.Alpha1, 5.0.0.Alpha2 > > > It will unify sources and make easier to scan through files: > {code} > (function ($, rf) { > rf.ui = rf.ui || {}; > .... > })(RichFaces.jQuery, RichFaces); > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (RF-13147) Rename all occurences JavaScript closures which references to RichFaces object to rf

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/RF-13147?page=com.atlassian.jira.plugin.s... ] Juraj Húska edited comment on RF-13147 at 12/10/13 11:04 AM: ------------------------------------------------------------- I am verifying the issue for *RF 4.5*. I have encounter following fact: some of the *.js files contains closure as described above, but some other contains a very slightly different one: {code:none} (function ($, rf) { rf.ui = rf.ui || {}; .... })(RichFaces.jQuery, window.RichFaces); {code} I guess it is only a cosmetic difference. Am I right ? It is by default searched in window object ? If yes, I would close this issue. was (Author: jhuska): I am verifying the issue. I have encounter following fact: some of the *.js files contains closure as described above, but some other contains a very slightly different one: {code:none} (function ($, rf) { rf.ui = rf.ui || {}; .... })(RichFaces.jQuery, window.RichFaces); {code} I guess it is only a cosmetic difference. Am I right ? It is by default searched in window object ? If yes, I would close this issue. > Rename all occurences JavaScript closures which references to RichFaces object to rf > ------------------------------------------------------------------------------------ > > Key: RF-13147 > URL: https://issues.jboss.org/browse/RF-13147 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Fix For: 4.5.0.Alpha1, 5.0.0.Alpha2 > > > It will unify sources and make easier to scan through files: > {code} > (function ($, rf) { > rf.ui = rf.ui || {}; > .... > })(RichFaces.jQuery, RichFaces); > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (RF-13147) Rename all occurences JavaScript closures which references to RichFaces object to rf

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/RF-13147?page=com.atlassian.jira.plugin.s... ] Juraj Húska commented on RF-13147: ---------------------------------- I am verifying the issue. I have encounter following fact: some of the *.js files contains closure as described above, but some other contains a very slightly different one: {code:none} (function ($, rf) { rf.ui = rf.ui || {}; .... })(RichFaces.jQuery, window.RichFaces); {code} I guess it is only a cosmetic difference. Am I right ? It is by default searched in window object ? If yest I would close this issue. > Rename all occurences JavaScript closures which references to RichFaces object to rf > ------------------------------------------------------------------------------------ > > Key: RF-13147 > URL: https://issues.jboss.org/browse/RF-13147 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Fix For: 4.5.0.Alpha1, 5.0.0.Alpha2 > > > It will unify sources and make easier to scan through files: > {code} > (function ($, rf) { > rf.ui = rf.ui || {}; > .... > })(RichFaces.jQuery, RichFaces); > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (RF-13134) Tie RichFaces 4.5 Components to CDK 4.5

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/RF-13134?page=com.atlassian.jira.plugin.s... ] Juraj Húska closed RF-13134. ---------------------------- Verified. Closing. > Tie RichFaces 4.5 Components to CDK 4.5 > --------------------------------------- > > Key: RF-13134 > URL: https://issues.jboss.org/browse/RF-13134 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: component > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Fix For: 4.5.0.Alpha1 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > This will allow: > * build Compoents on windows (RF-13022) > * have RF5 and RF4.5 Componets build with same CDK -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (RF-13300) Page Fragments: refine module dependencies

by Matej Novotny (JIRA)

[ https://issues.jboss.org/browse/RF-13300?page=com.atlassian.jira.plugin.s... ] Matej Novotny closed RF-13300. ------------------------------ Verified, closing issue. > Page Fragments: refine module dependencies > ------------------------------------------ > > Key: RF-13300 > URL: https://issues.jboss.org/browse/RF-13300 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: page-fragments > Affects Versions: 5.0.0.Alpha2 > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Fix For: 5.0.0.Alpha2 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > During the review, I have found out we may need to fine module dependencies: > https://github.com/richfaces/richfaces/pull/55#issuecomment-27339441 > ---- > {code} > joda-time:2.3 > - DateTime > commons-lang:2.6 > - Validate.isTrue > - StringEscapeUtils.unescapeJava > json-simple:1.1.1 > - JSONParser > org.jodah:typetools:0.3.0 > - TypeResolver.resolveRawArguments > {code} > I'm fine with {{DateTime}}, since it's going to be standardized - even though we may consider making it optional dependency and provide alternative in form of {{java.util.Date}}. > I didn't found reason to leave {{Validate.isTrue}} - this should be replaced by more verbose but dependency free code. > I did some googling for alternatives to {{StringEscapeUtils.unescapeJava}} and found out few [suggestions for dependency free Java-unescaping|http://stackoverflow.com/questions/3537706/howto-unescape...]. > {{JSONParser}} seems to be necessary (even though we don;t use it extensively yet), but I would favor standard APIs in form of [JSR-353|https://jsonp.java.net/index.html]. > I believe {{TypeResolver}} can be re-written from scratch, but since it's one-class ASL dependency, we might consider [shading it|http://maven.apache.org/plugins/maven-shade-plugin/]. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues December 2013