November 2013 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-13352) Introduce @Category(FailingOnFirefox.class) to pom.xml

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-13352?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč moved RFPL-3055 to RF-13352: --------------------------------------- Project: RichFaces (was: RichFaces Planning) Key: RF-13352 (was: RFPL-3055) Issue Type: Enhancement (was: Feature Request) Component/s: tests - functional (was: build) (was: jsf-test) > Introduce @Category(FailingOnFirefox.class) to pom.xml > ------------------------------------------------------ > > Key: RF-13352 > URL: https://issues.jboss.org/browse/RF-13352 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: tests - functional > Reporter: Lukáš Macko > Assignee: Lukáš Fryč > > Creating test for the chart component, I came across an issues that one test is running in Chrome and PhantomJS and it is failing on Firefox. As [~lfryc] suggested in the [comment | https://issues.jboss.org/browse/RF-13331?focusedCommentId=12923949&page=c...], I've annotated it with FailingOnFirefox. ATM it has no effect concerning tests. > It might be useful to add this category to rf/pom.xml configuration to exclude FailingOnFirefox test when tests run on firefox. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-13323) FileUploadEvent listener reset the list value with Viewscope

by Jiří Štefek (JIRA)

[ https://issues.jboss.org/browse/RF-13323?page=com.atlassian.jira.plugin.s... ] Jiří Štefek commented on RF-13323: ---------------------------------- [~wish79], tried this: - vanilla JBoss AS 7.1.1.Final: impl: _jsf-impl-2.1.7-jbossorg-2_ and apis: _jboss-jsf-api_2.1_spec-2.0.1.Final_ , works. - JBoss AS 7.1.1.Final with updated impl to: _jsf-impl-2.1.9-jbossorg-1_ , works. - JBoss AS 7.1.1.Final with updated impl to: _jsf-impl-2.1.9-jbossorg-1_ + updated apis to: _jboss-jsf-api_2.1_spec-2.0.9.Final_ , works. What apis/impls are you using? Do you replace them as in this [comment|http://stackoverflow.com/a/11495699]? Or are you using the Oracle ones? System? JDK? 64bit? > FileUploadEvent listener reset the list value with Viewscope > ------------------------------------------------------------ > > Key: RF-13323 > URL: https://issues.jboss.org/browse/RF-13323 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.4 > Environment: Jboss 7.1 > Richfaces 4.3.4 > JSF 2.1.9 > > Reporter: Mohammad Weshah > Assignee: Jiří Štefek > Labels: rich:fileUpload > Attachments: RF-13323-2.zip, RF-13323-SessionScoped.png, RF-13323-ViewScoped.png, RF-13323.zip, TestRichFacesWebProject.rar, TestRichFacesWebProject.war > > > Hello All, > i make an example of upload file from richfaces showcase it is working successfully , but i notice if i changed the backing bean to viewscope the files list inside the FileUploadEvent listener will be rest every time that i upload new file , the code as follow : > > {code} > protected List<UploadedImage> files = new ArrayList<UploadedImage>(); > > public void FileUploadlistener(FileUploadEvent event) throws Exception { > UploadedFile item = event.getUploadedFile(); > UploadedImage file = new UploadedImage(); > file.setLength(item.getData().length); > file.setName(item.getName()); > file.setData(item.getData()); > > files.add(file); > } > {code} > > but when i changed the scope to session the files still contain the old files, is it mandatory to the backing be session or there is something wrong ? > > Regards > Wish79 -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-13341) Charts: implement AjaxProps

by Lukáš Macko (JIRA)

[ https://issues.jboss.org/browse/RF-13341?page=com.atlassian.jira.plugin.s... ] Lukáš Macko commented on RF-13341: ---------------------------------- I think the advantage of the custom chart server-side listener/event is that event.data can be propagated to the server. It will not be the most common use case probably, however it might be useful e.g to show some additional information related to a value clicked in a chart, in my opinion. > Charts: implement AjaxProps > --------------------------- > > Key: RF-13341 > URL: https://issues.jboss.org/browse/RF-13341 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-output > Reporter: Lukáš Macko > Priority: Minor > > I think AbstractChart should implements AjaxProps since it uses server-side listeners. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-13340) orderingList - setting of some attributes does not have any effect on the component

by Jiří Štefek (JIRA)

[ https://issues.jboss.org/browse/RF-13340?page=com.atlassian.jira.plugin.s... ] Jiří Štefek reassigned RF-13340: -------------------------------- Assignee: Brian Leathem (was: Jiří Štefek) Yes, [~bleathem], it is out of date now . > orderingList - setting of some attributes does not have any effect on the component > ----------------------------------------------------------------------------------- > > Key: RF-13340 > URL: https://issues.jboss.org/browse/RF-13340 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 5.0.0.Alpha2 > Reporter: Jiří Štefek > Assignee: Brian Leathem > Fix For: 5.0.0.Alpha2 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > Setting of these attributes on a {{orderingList}} has no effect on the rendered component > * style > * valueChangeListener -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-13351) orderingList: styleClass attribute is rendered wrongly as styleclass instead of class attribute

by Jiří Štefek (JIRA)

[ https://issues.jboss.org/browse/RF-13351?page=com.atlassian.jira.plugin.s... ] Jiří Štefek reassigned RF-13351: -------------------------------- Assignee: Jiří Štefek (was: Brian Leathem) > orderingList: styleClass attribute is rendered wrongly as styleclass instead of class attribute > ----------------------------------------------------------------------------------------------- > > Key: RF-13351 > URL: https://issues.jboss.org/browse/RF-13351 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 5.0.0.Alpha2 > Reporter: Jiří Štefek > Assignee: Jiří Štefek > Fix For: 5.0.0.Alpha2 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > Setting of {{styleClass}} attribute to the {{orderingList}} component makes generated markup to contain {{styleclass}} attribute - instead of just adjusted {{class}} attribute. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-13351) orderingList: styleClass attribute is rendered wrongly as styleclass instead of class attribute

by Jiří Štefek (JIRA)

[ https://issues.jboss.org/browse/RF-13351?page=com.atlassian.jira.plugin.s... ] Jiří Štefek commented on RF-13351: ---------------------------------- I'll send a PR. > orderingList: styleClass attribute is rendered wrongly as styleclass instead of class attribute > ----------------------------------------------------------------------------------------------- > > Key: RF-13351 > URL: https://issues.jboss.org/browse/RF-13351 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 5.0.0.Alpha2 > Reporter: Jiří Štefek > Assignee: Brian Leathem > Fix For: 5.0.0.Alpha2 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > Setting of {{styleClass}} attribute to the {{orderingList}} component makes generated markup to contain {{styleclass}} attribute - instead of just adjusted {{class}} attribute. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-13351) orderingList: styleClass attribute is rendered wrongly as styleclass instead of class attribute

by Jiří Štefek (JIRA)

[ https://issues.jboss.org/browse/RF-13351?page=com.atlassian.jira.plugin.s... ] Jiří Štefek updated RF-13351: ----------------------------- Description: Setting of {{styleClass}} attribute to the {{orderingList}} component makes generated markup to contain {{styleclass}} attribute - instead of just adjusted {{class}} attribute. (was: Setting of {{styleClass}} attribute to the {{pickList}} component makes generated markup to contain {{styleclass}} attribute - instead of just adjusted {{class}} attribute. The {{styleClass}} is included just in {{passThrough}} attributes - [here|https://github.com/richfaces/richfaces/blob/master/framework/src/mai...]. Should not be it done as it is for example [here|https://github.com/richfaces/richfaces/blob/master/framework/src/mai...] in autocomplate render base ?) > orderingList: styleClass attribute is rendered wrongly as styleclass instead of class attribute > ----------------------------------------------------------------------------------------------- > > Key: RF-13351 > URL: https://issues.jboss.org/browse/RF-13351 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 5.0.0.Alpha2 > Reporter: Jiří Štefek > Assignee: Brian Leathem > Fix For: 5.0.0.Alpha2 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > Setting of {{styleClass}} attribute to the {{orderingList}} component makes generated markup to contain {{styleclass}} attribute - instead of just adjusted {{class}} attribute. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-13351) orderingList: styleClass attribute is rendered wrongly as styleclass instead of class attribute

by Jiří Štefek (JIRA)

Jiří Štefek created RF-13351: -------------------------------- Summary: orderingList: styleClass attribute is rendered wrongly as styleclass instead of class attribute Key: RF-13351 URL: https://issues.jboss.org/browse/RF-13351 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-selects Affects Versions: 5.0.0.Alpha2 Reporter: Jiří Štefek Assignee: Brian Leathem Fix For: 5.0.0.Alpha2 Setting of {{styleClass}} attribute to the {{pickList}} component makes generated markup to contain {{styleclass}} attribute - instead of just adjusted {{class}} attribute. The {{styleClass}} is included just in {{passThrough}} attributes - [here|https://github.com/richfaces/richfaces/blob/master/framework/src/mai...]. Should not be it done as it is for example [here|https://github.com/richfaces/richfaces/blob/master/framework/src/mai...] in autocomplate render base ? -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-13339) orderingList: ordered values are reset after submit

by Jiří Štefek (JIRA)

[ https://issues.jboss.org/browse/RF-13339?page=com.atlassian.jira.plugin.s... ] Jiří Štefek commented on RF-13339: ---------------------------------- Verified, it works. > orderingList: ordered values are reset after submit > --------------------------------------------------- > > Key: RF-13339 > URL: https://issues.jboss.org/browse/RF-13339 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 5.0.0.Alpha2 > Reporter: Jiří Štefek > Assignee: Brian Leathem > Priority: Blocker > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > -- 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, 11 months

1
0
0 / 0

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

by Pavel Slegr (JIRA)

[ https://issues.jboss.org/browse/RF-13317?page=com.atlassian.jira.plugin.s... ] Pavel Slegr reassigned RF-13317: -------------------------------- Assignee: Pavel Slegr > 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: Pavel Slegr > Priority: Critical > Labels: jsf22 > Fix For: 4.3.5 > > > 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 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, 11 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 November 2013