December 2012 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-12673) Collapsible sub table: filtering doesn't work inside switchable panels

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12673?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-12673: ------------------------------------ This problem was introduced with the commit: https://github.com/richfaces/components/commit/d65e614ef03adf87c0b6df2288... Since that commit, the ExtendedDataModel is instantiated in the RESTORE_VIEW phase, and is not re-instantiated again throughout the lifecycle. As such the ArrangeableModel filter method is not invoked after the filter input value is updated in the UPDATE_MODEL_VALUES phase. A possible solution involves clearing the ExtendedDataModel at the beginning of the encode method, to force a re-evaluation of the ArrangeableModel. > Collapsible sub table: filtering doesn't work inside switchable panels > ---------------------------------------------------------------------- > > Key: RF-12673 > URL: https://issues.jboss.org/browse/RF-12673 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables, regression > Affects Versions: 4.3.0.M3 > Environment: RichFaces 4.3.0.20121214-M3 > Metamer 4.3.0.20121214-M3 > Mojarra 2.1.7 (bundled in AS) > JBoss AS 7.1.2.Final-redhat-1 > Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux > Chrome 23.0.1271.97 @ Linux x86_64 > Reporter: Pavol Pitonak > Assignee: Brian Leathem > Priority: Critical > Fix For: 4.3.0.CR1 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > # deploy Metamer and open http://localhost:8080/metamer/faces/components/richCollapsibleSubTable/fi... > # set attribute rows to 0 > # type "Alexander" into input in first column ("Name") > result: > * table shows 159 result but only 10 should be visible (those containing "Alexander") > * worked fine in 4.3.0.M2 > * doesn't work in all switchable panels - _rich:accordion_, _rich:tabPanel_, _rich:togglePanel_ and _rich:collapsiblePanel_ -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (RF-12678) Rich:editor - unterminated string literal JS error when submitting editor value

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/RF-12678?page=com.atlassian.jira.plugin.s... ] Juraj Húska updated RF-12678: ----------------------------- Description: When submitting value from {{rich:editor}} JS error are thrown. Please see the attachment. I have not found any broken functionality though, just those JS errors. Is it caused by update of CKEditor or JQuery libraries ? was: When submitting value from {{rich:editor}} JS error are thrown. Please see the attachment. Is it caused by update of CKEditor or JQuery libraries ? > Rich:editor - unterminated string literal JS error when submitting editor value > -------------------------------------------------------------------------------- > > Key: RF-12678 > URL: https://issues.jboss.org/browse/RF-12678 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.0.M3 > Environment: RichFaces 4.3.0.20121214-M3 > Metamer 4.3.0.20121218-M3 > JBoss Application Server: Weld Integration 7.1.1.Final > JBoss AS 7.1.1.Final > Java(TM) SE Runtime Environment 1.7.0_05-b06 @ Linux > Firefox 17.0 @ Linux x86_64, Chrome > Reporter: Juraj Húska > Labels: regression > Attachments: editorJSerror1.png, editorJSerror2.png > > > When submitting value from {{rich:editor}} JS error are thrown. Please see the attachment. > I have not found any broken functionality though, just those JS errors. > Is it caused by update of CKEditor or JQuery libraries ? -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (RF-12678) Rich:editor - unterminated string literal JS error when submitting editor value

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/RF-12678?page=com.atlassian.jira.plugin.s... ] Juraj Húska updated RF-12678: ----------------------------- Priority: Minor (was: Major) > Rich:editor - unterminated string literal JS error when submitting editor value > -------------------------------------------------------------------------------- > > Key: RF-12678 > URL: https://issues.jboss.org/browse/RF-12678 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.0.M3 > Environment: RichFaces 4.3.0.20121214-M3 > Metamer 4.3.0.20121218-M3 > JBoss Application Server: Weld Integration 7.1.1.Final > JBoss AS 7.1.1.Final > Java(TM) SE Runtime Environment 1.7.0_05-b06 @ Linux > Firefox 17.0 @ Linux x86_64, Chrome > Reporter: Juraj Húska > Priority: Minor > Labels: regression > Attachments: editorJSerror1.png, editorJSerror2.png > > > When submitting value from {{rich:editor}} JS error are thrown. Please see the attachment. > I have not found any broken functionality though, just those JS errors. > Is it caused by update of CKEditor or JQuery libraries ? -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (RF-12250) kitchensink quickstart - re-rendering list of members causes push to stop work

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/RF-12250?page=com.atlassian.jira.plugin.s... ] Juraj Húska commented on RF-12250: ---------------------------------- Verified. > kitchensink quickstart - re-rendering list of members causes push to stop work > ------------------------------------------------------------------------------ > > Key: RF-12250 > URL: https://issues.jboss.org/browse/RF-12250 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: archetype, component-push/poll, mobile > Affects Versions: 4.2.2.Final > Environment: iPhone, Motorola Xoom > application container: JBoss AS 7.1.1.Final. > Reporter: Juraj Húska > Assignee: Lukáš Fryč > Fix For: 4.2.5, 4.3.0.M3 > > > Creating a new member from iPhone device causes that update on mobile devices does not work properly. The list of new members is not updated anymore, even when creating a new members from desktop browsers. > No error is thrown either on server or client side. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (RF-12076) Kitchensink archetype - back button does not back to the correct page state

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/RF-12076?page=com.atlassian.jira.plugin.s... ] Juraj Húska closed RF-12076. ---------------------------- > Kitchensink archetype - back button does not back to the correct page state > --------------------------------------------------------------------------- > > Key: RF-12076 > URL: https://issues.jboss.org/browse/RF-12076 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: archetype > Affects Versions: 4.2.0.Final > Environment: AS: JBoss AS 7.1.1.Final, EAP 6.0.0.ER3 > Reporter: Juraj Húska > Assignee: Brian Leathem > Priority: Minor > Fix For: 4.2.4, 4.3.0.M3 > > > When clicking on the url of the freshly created new member (like /rest/members/0) and backing back from the xml viewing, results in removed freshly added member. > After refresh, or AJAX update (clicking on collapsiblePanel), the table is with all members again. > This happens only for freshly added members. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (RF-12255) kitchensink archetype - error message from server side validation not rendered correctly

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/RF-12255?page=com.atlassian.jira.plugin.s... ] Juraj Húska closed RF-12255. ---------------------------- > kitchensink archetype - error message from server side validation not rendered correctly > ---------------------------------------------------------------------------------------- > > Key: RF-12255 > URL: https://issues.jboss.org/browse/RF-12255 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: archetype, component-validators > Affects Versions: 4.2.2.Final > Environment: project generated from kitchensink archetype > Reporter: Juraj Húska > Assignee: Brian Leathem > Priority: Minor > Fix For: 4.2.4, 4.3.0.M3 > > Attachments: errorAfterServerSideValidation.png > > > Validation error from server side validation is not rendered correctly, the image with red cross is overlapped with the text part. Please take a look at the attached 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (RF-12254) kitchensink archetype - accessing wrong facelet is held in session and consequently accessing a correct one causes HTTP Status 500

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/RF-12254?page=com.atlassian.jira.plugin.s... ] Juraj Húska closed RF-12254. ---------------------------- > kitchensink archetype - accessing wrong facelet is held in session and consequently accessing a correct one causes HTTP Status 500 > ----------------------------------------------------------------------------------------------------------------------------------- > > Key: RF-12254 > URL: https://issues.jboss.org/browse/RF-12254 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: archetype, mobile > Affects Versions: 4.2.2.Final > Environment: project generated from kitchensink archetype > Reporter: Juraj Húska > Priority: Minor > Fix For: 4.2.4, 4.3.0.M3 > > > When accessing wrong facelet on mobile device and consequently the right application context, then the HTTP Status 500 is returned with error message, which can be viewed in the attached screenshot. > It is caused because the {{PageBean}} hold the wrong part of the URL in the session, > {code} > public void setLocation(String location) { > this.location = location; > this.page = String.format("/mobile/%s.xhtml", location); > } > {code} > Note that I have tried to change the scope of the PageBean to RequestScoped, but then the list with members what not updated with the new created ones. It is noticeable only on mobile devices, as on desktop there is only one view. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (RF-12160) rich:validator does not validate on the client side the @Pattern constraint

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/RF-12160?page=com.atlassian.jira.plugin.s... ] Juraj Húska closed RF-12160. ---------------------------- > rich:validator does not validate on the client side the @Pattern constraint > --------------------------------------------------------------------------- > > Key: RF-12160 > URL: https://issues.jboss.org/browse/RF-12160 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-validators, examples > Affects Versions: 4.2.1.Final > Environment: application: generated project from richfaces-kitchensink-archetype 4.2.1-SNAPSHOT > browser: Chrome, Firefox > Reporter: Juraj Húska > Assignee: Brian Leathem > Fix For: 4.2.4, 4.3.0.M3 > > > When trying to validate input which has annotation based constraint @Pattern, validation for this constraint is triggered only after the submitting of the form. The other constraints (@NotNull, @Size) are triggered as expected, after the BLUR event fired on that input. > The issue is noticeable on the project generated by the kitchensink archetype with RichFaces 4.2.1-SNAPSHOT libraries. > The facelet for the input validation with pattern annotation-based constraints looks like: > {code:xml} > <h:panelGrid columns="3" columnClasses="titleCell"> > <h:outputLabel for="name" value="Name:"/> > <h:inputText id="name" value="#{cc.attrs.member.name}"> > <rich:validator/> > </h:inputText> > <rich:message for="name" errorClass="invalid"/> > </h:panelGrid> > {code} > The model entity field which is validated in the above mentioned input: > {code} > @NotNull > @Size(min = 1, max = 25) > @Pattern(regexp = "[A-Za-z ]*", message = "must contain only letters and spaces") > private String name; > {code} > Note that I have tried to reproduce this issue on metamer and I was not successful. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (RF-12229) Ajax partial response extension tag is not written when render="@all"

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/RF-12229?page=com.atlassian.jira.plugin.s... ] Juraj Húska closed RF-12229. ---------------------------- Verified on metamer. > Ajax partial response extension tag is not written when render="@all" > --------------------------------------------------------------------- > > Key: RF-12229 > URL: https://issues.jboss.org/browse/RF-12229 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 4.2.1.Final > Environment: RichFaces 4.3.0-SNAPSHOT > Reporter: Luca Nardelli > Assignee: Lukáš Fryč > Fix For: 4.3.0.M3 > > Original Estimate: 2 days > Remaining Estimate: 2 days > > * --Partial response extension is not written in f:ajax is one of the causes of RF-12031-- > * Partial response extension is not written if render="@all" (see steps to Reproduce) > Render all seems a wanted behaviour: ExtendedPartialViewContextImpl.visitActivatorAtRender method > {code:java} > if (!isRenderAll()) { > ... > if (!Boolean.TRUE.equals(renderAll) && !ids.contains(ALL)) { > addImplicitRenderIds(ids, limitRender); > appendOnbeforedomupdate(onbeforedomupdate); > appendOncomplete(oncomplete); > setResponseData(responseData); > } > } > {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, 2 months

1
0
0 / 0

[JBoss JIRA] (RF-12298) DropDownMenu: overlay problem in IE 9 (compatibility mode)

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/RF-12298?page=com.atlassian.jira.plugin.s... ] Juraj Húska closed RF-12298. ---------------------------- > DropDownMenu: overlay problem in IE 9 (compatibility mode) > ---------------------------------------------------------- > > Key: RF-12298 > URL: https://issues.jboss.org/browse/RF-12298 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-menu > Affects Versions: 4.2.2.Final > Environment: Windows 7 64bit, Tomcat 7.0.26, Internet Explorer, Rich Faces 4.2.2, Mojara 2.1.7 / 2.1.5 > Reporter: Michael Abele > Assignee: Brian Leathem > Labels: ie9 > Attachments: RF-12298-Menu-item-with-tab.png, richfaces-sanbox.zip > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > Menu item of a drop down menu is not displayed if it overlaps a panel/tab panel header in Internet Explorer 9 (compatibility mode). It works in Firefox and Internet Explorer 8 and 9 (strict mode). > This issue might be related to RF-9097 of RichFaces 3.3.3. -- 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, 2 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues December 2012