December 2013 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-13182) Autocomplete: attributes style and styleClass missing

by Jiří Štefek (JIRA)

[ https://issues.jboss.org/browse/RF-13182?page=com.atlassian.jira.plugin.s... ] Jiří Štefek closed RF-13182. ---------------------------- verified, closing. > Autocomplete: attributes style and styleClass missing > ----------------------------------------------------- > > Key: RF-13182 > URL: https://issues.jboss.org/browse/RF-13182 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input, regression > Affects Versions: 5.0.0.Alpha2 > Environment: RichFaces 5.0.0-SNAPSHOT > Metamer 5.0.0-SNAPSHOT > Mojarra 2.1.19 > JBoss AS 7.2.0.Final-redhat-8 > Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux > Chrome 29.0.1547.65 @ Linux x86_64 > Reporter: Pavol Pitonak > Assignee: Lukáš Fryč > Fix For: 5.0.0.Alpha2 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > Component autocomplete is missing two attributes - style and styleClass. There attributes were present in 5.0.0.Alpha1. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (RF-13180) Autocomplete: ajax doesn't work with change event

by Jiří Štefek (JIRA)

[ https://issues.jboss.org/browse/RF-13180?page=com.atlassian.jira.plugin.s... ] Jiří Štefek closed RF-13180. ---------------------------- closing > Autocomplete: ajax doesn't work with change event > ------------------------------------------------- > > Key: RF-13180 > URL: https://issues.jboss.org/browse/RF-13180 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input, regression > Affects Versions: 5.0.0.Alpha2 > Environment: RichFaces 5.0.0-SNAPSHOT > Metamer 5.0.0-SNAPSHOT > Mojarra 2.1.19 > JBoss AS 7.2.0.Final-redhat-8 > Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux > Chrome 29.0.1547.65 @ Linux x86_64 > Reporter: Pavol Pitonak > Assignee: Lukáš Fryč > Priority: Blocker > Fix For: 5.0.0.Alpha2 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > # deploy Metamer and open http://localhost:8080/metamer/faces/components/richAutocomplete/autocompl... > # type "a" into input > # select Alabama > result: > * ajax request is not fired > * output is not updated > * when "change" event in r:ajax is changed to "blur", the use-case works -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 5 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: --------------------------------- I have tried to apply a naive fix leveraging {{Util#getViewStateId()}} and it fixed few more framework tests. > 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

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (RF-13237) Showcase: enable debugging tools (ui:debug, r:log) when in development mode

by Pavol Pitonak (JIRA)

[ https://issues.jboss.org/browse/RF-13237?page=com.atlassian.jira.plugin.s... ] Pavol Pitonak closed RF-13237. ------------------------------ > Showcase: enable debugging tools (ui:debug, r:log) when in development mode > --------------------------------------------------------------------------- > > Key: RF-13237 > URL: https://issues.jboss.org/browse/RF-13237 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: showcase > Affects Versions: 5.0.0.Alpha1 > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Fix For: 5.0.0.Alpha2 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (RF-13235) Tree - Row key conversion fails (UITree should not have generated @rowKeyConverter, since it is fully implemented in AbstractTree)

by Jiří Štefek (JIRA)

[ https://issues.jboss.org/browse/RF-13235?page=com.atlassian.jira.plugin.s... ] Jiří Štefek closed RF-13235. ---------------------------- Verified, closing. > Tree - Row key conversion fails (UITree should not have generated @rowKeyConverter, since it is fully implemented in AbstractTree) > ---------------------------------------------------------------------------------------------------------------------------------- > > Key: RF-13235 > URL: https://issues.jboss.org/browse/RF-13235 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tree > Affects Versions: 5.0.0.Alpha2 > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Priority: Critical > Fix For: 5.0.0.Alpha2 > > > The row key generation for Tree stopped to work: > *got:* <div id="j_idt106:tree:org.richfaces.model.SequenceRowKey[0, 0, 0]:j_idt111" class="rf-tr-nd rf-tr-nd-lf"> > *expected:* <div id="j_idt106:tree:0.0.0:j_idt111" class="rf-tr-nd rf-tr-nd-lf"> > ---- > The cause was that rowKeyConverter resolves to null, so plain toString on rowKey is used. > I was wondering why rowKeyConverter isn't resolved for Tree in Showcase - the problem is that CDK generates this attribute and thus its implementation in AbstractTree (which is the correct way of rowKeyResolution) isn't used at all. > I'm pretty sure this is caused by refactoring from tree-model-props.xml to use Java interfaces TreeProps and TreeCommonProps: > https://github.com/richfaces/richfaces/commit/62ab0fe3f00b44a166b522ecb71... > However it's not clear why the rowKeyConverter wasn't generated in RF 4.3 when it wasn't marked as generate=false: > https://github.com/richfaces4/components/blob/master/iteration/ui/src/mai... > Note that in RF 5 it is generated because UIAdaptor has @Attribute which defaults to generate=true: > https://github.com/richfaces/richfaces/blob/master/framework/src/main/jav... > Workaround is marking rowKeyConverter as generate=false in AbstracTree (or maybe RowKeyConverter), but we should rather investigate why this issue happens. > ---- > This issue has bigger potential since during refactoring of properties, [~bleathem] could work with the same assumption as I did ^. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (RF-13193) Rename the resource library to account for RF 4/5 resource overlap

by Jiří Štefek (JIRA)

[ https://issues.jboss.org/browse/RF-13193?page=com.atlassian.jira.plugin.s... ] Jiří Štefek closed RF-13193. ---------------------------- verified, closing. > Rename the resource library to account for RF 4/5 resource overlap > ------------------------------------------------------------------ > > Key: RF-13193 > URL: https://issues.jboss.org/browse/RF-13193 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: resource handling > Reporter: Brian Leathem > Assignee: Michal Petrov > Priority: Critical > Fix For: 5.0.0.Alpha2 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > Rename the RichFaces resource library name to something like: _org.richfaces.ui_, or _org.richfaces.widgets_. This will allow RF 4 and RF 5 components to co-exist when resource names overlap. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (RF-13402) JavaScript error thrown for the orderingList in the showcase

by Pavol Pitonak (JIRA)

[ https://issues.jboss.org/browse/RF-13402?page=com.atlassian.jira.plugin.s... ] Pavol Pitonak closed RF-13402. ------------------------------ > JavaScript error thrown for the orderingList in the showcase > ------------------------------------------------------------ > > Key: RF-13402 > URL: https://issues.jboss.org/browse/RF-13402 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 5.0.0.Alpha2 > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 5.0.0.Alpha2 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > Viewing the orderingLIst in the showcase yields the JavaScript error: > {code} > Uncaught TypeError: Object [object Object] has no method 'detach' > {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

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (RF-13035) Simpleapp Archetype: mobile version shows modal dialog

by Jiří Štefek (JIRA)

[ https://issues.jboss.org/browse/RF-13035?page=com.atlassian.jira.plugin.s... ] Jiří Štefek closed RF-13035. ---------------------------- Verified with RF 5, closing. > Simpleapp Archetype: mobile version shows modal dialog > ------------------------------------------------------- > > Key: RF-13035 > URL: https://issues.jboss.org/browse/RF-13035 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: archetype > Affects Versions: 4.1.0.Final, 5.0.0.Alpha1 > Reporter: Jan Papousek > Assignee: Brian Leathem > Fix For: 4.3.4, 5.0.0.Alpha2 > > Attachments: modal-iphone.png, richfaces-simpleapp-jee6.war, simpleapp-modal.png > > Original Estimate: 45 minutes > Remaining Estimate: 45 minutes > > When the simpleapp archetype is built with "-Dmobile-optimized=true", the welcome page shows modal dialog (see screenshot). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (RF-13434) archetypes: change the namespace of richfaces components

by Jiří Štefek (JIRA)

[ https://issues.jboss.org/browse/RF-13434?page=com.atlassian.jira.plugin.s... ] Jiří Štefek updated RF-13434: ----------------------------- Priority: Critical (was: Major) > archetypes: change the namespace of richfaces components > -------------------------------------------------------- > > Key: RF-13434 > URL: https://issues.jboss.org/browse/RF-13434 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: archetype > Affects Versions: 5.0.0.Alpha2 > Reporter: Jiří Štefek > Priority: Critical > > After RF-13143 the namespace of RF 5 components has changed to {{http://richfaces.org}} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (RF-13434) archetypes: change the namespace of richfaces components

by Jiří Štefek (JIRA)

Jiří Štefek created RF-13434: -------------------------------- Summary: archetypes: change the namespace of richfaces components Key: RF-13434 URL: https://issues.jboss.org/browse/RF-13434 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: archetype Affects Versions: 5.0.0.Alpha2 Reporter: Jiří Štefek After RF-13143 the namespace of RF 5 components has changed to {{http://richfaces.org}} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues December 2013