January 2013 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-12736) rich:notifyMessages output is not escaped

by Ilia Vassilev (JIRA)

[ https://issues.jboss.org/browse/RF-12736?page=com.atlassian.jira.plugin.s... ] Ilia Vassilev updated RF-12736: ------------------------------- Assignee: Brian Leathem > rich:notifyMessages output is not escaped > ----------------------------------------- > > Key: RF-12736 > URL: https://issues.jboss.org/browse/RF-12736 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.2.3.Final > Reporter: Ilia Vassilev > Assignee: Brian Leathem > > rich:notifyMessages output is not escaped like rich:messages. rich:notifyMessages doesn't have 'escape' attribute, but the default value for rich:messages is escape=”true”. -- 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

11 years, 12 months

1
0
0 / 0

[JBoss JIRA] (RF-12689) Upgrade Atmosphere from 1.0.1 to 1.0.7 (or 1.1.0.beta2)

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12689?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated RF-12689: ---------------------------- Fix Version/s: 5-Tracking > Upgrade Atmosphere from 1.0.1 to 1.0.7 (or 1.1.0.beta2) > ------------------------------------------------------- > > Key: RF-12689 > URL: https://issues.jboss.org/browse/RF-12689 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build/distribution, component-push/poll > Affects Versions: 4.3.0.M3 > Reporter: Juergen Zimmermann > Fix For: 4.3-Tracking, 5-Tracking > > > 4.3.0.M3 still uses Atmosphere 1.0.1. However, there is 1.0.7 (or even 1.1.0.beta2) -- 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

11 years, 12 months

1
0
0 / 0

[JBoss JIRA] (RF-12735) Metamer: DnD: rich:dragSource: dropping causes Error status [myfaces]

by Ján Jamrich (JIRA)

Ján Jamrich created RF-12735: -------------------------------- Summary: Metamer: DnD: rich:dragSource: dropping causes Error status [myfaces] Key: RF-12735 URL: https://issues.jboss.org/browse/RF-12735 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-drag/drop Affects Versions: 4.3.0.CR1 Environment: RichFaces 4.3.0.CR1 Metamer 4.3.0.20130114-CR1 Weld Servlet (Uber Jar) 20120106-1159 Apache Tomcat 7.0.32 Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux Firefox 17.0 @ Linux i686 (browser doesn't influence it) Metamer: 2023898d4b163a889955c1d028149a31 metamer-4.3.0.20130114-CR1-tomcat7-myfaces.war Reporter: Ján Jamrich Dropping doesn't work for componsite component example (even simple example for dragSource works correctly). When drag from first draggable area and drop in first dropping area (indicator indicated Accepting), object is not "accepted" - doesn't appears in dropping area, and error status appears in Metamer header. When change type to drg2 then still doesn't for first dropping area. Only second droppiing area works correctly, even drg2 should be accepted by both dropping areas (and dragIndicator is indicating accepting over dropping1 area) Indicator type doesn't influence behavior. -- 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

11 years, 12 months

1
0
0 / 0

[JBoss JIRA] (RF-12412) Metamer: rich:dropDownMenu: missing menu icon [myfaces]

by Ján Jamrich (JIRA)

[ https://issues.jboss.org/browse/RF-12412?page=com.atlassian.jira.plugin.s... ] Ján Jamrich updated RF-12412: ----------------------------- Affects Version/s: 4.3.0.CR1 > Metamer: rich:dropDownMenu: missing menu icon [myfaces] > ------------------------------------------------------- > > Key: RF-12412 > URL: https://issues.jboss.org/browse/RF-12412 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.3.0.CR1 > Environment: RichFaces 4.3.0.20120802-M1 > Metamer 4.3.0.20120802-M1 > Apache MyFaces JSF-2.1 Core Impl 2.1.8 > Apache Tomcat 7.0.29 > OpenJDK Runtime Environment 1.7.0_05-icedtea-mockbuild_2012_07_09_19_42-b00 @ Linux > Chrome 20.0.1132.47 @ Linux i686 > Reporter: Ján Jamrich > Labels: myfaces > Fix For: 5-Tracking > > > DropDown menu is missing icon on the left from label. -- 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

11 years, 12 months

1
0
0 / 0

[JBoss JIRA] (RF-12415) Metamer: rich:toolBar, rich:toolBarGroup: missing icons in toolbar [myfaces]

by Ján Jamrich (JIRA)

[ https://issues.jboss.org/browse/RF-12415?page=com.atlassian.jira.plugin.s... ] Ján Jamrich updated RF-12415: ----------------------------- Affects Version/s: 4.3.0.CR1 > Metamer: rich:toolBar, rich:toolBarGroup: missing icons in toolbar [myfaces] > ---------------------------------------------------------------------------- > > Key: RF-12415 > URL: https://issues.jboss.org/browse/RF-12415 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.3.0.CR1 > Environment: RichFaces 4.3.0.20120802-M1 > Metamer 4.3.0.20120802-M1 > Apache MyFaces JSF-2.1 Core Impl 2.1.8 > Apache Tomcat 7.0.29 > OpenJDK Runtime Environment 1.7.0_05-icedtea-mockbuild_2012_07_09_19_42-b00 @ Linux > Chrome 20.0.1132.47 @ Linux i686 > Reporter: Ján Jamrich > Labels: myfaces > Fix For: 5-Tracking > > > All toolbars (rich:toolBar and rich:toolbarGroup) examples missing icons. > Image's src refers to "RES_NOT_FOUND" -- 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

11 years, 12 months

1
0
0 / 0

[JBoss JIRA] (RF-12734) Metamer: rich:tree: Tree Data Model: unable to expand tree, getting Error status [myfaces]

by Ján Jamrich (JIRA)

Ján Jamrich created RF-12734: -------------------------------- Summary: Metamer: rich:tree: Tree Data Model: unable to expand tree, getting Error status [myfaces] Key: RF-12734 URL: https://issues.jboss.org/browse/RF-12734 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-tree Affects Versions: 4.3.0.CR1 Environment: RichFaces 4.3.0.CR1 Metamer 4.3.0.20130114-CR1 Weld Servlet (Uber Jar) 20120106-1159 Apache Tomcat 7.0.32 Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux Firefox 17.0 @ Linux i686 (not browser related) Metamer: md5sum metamer-4.3.0.20130114-CR1-tomcat7-myfaces.war Reporter: Ján Jamrich Two tree related examples using Tree Data Model doesn't expand tree (on any level). Found in following examples: faces/components/richTree/rowKeyConverterRichFacesTreeDataModel.xhtml faces/components/richTree/simpleRichFacesTreeDataModel.xhtml -- 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

11 years, 12 months

1
0
0 / 0

[JBoss JIRA] (RF-12717) “Component ID <componentId> has already been found in the view” exception when using rich:dataTable with JSF 2.1.13 on EAP 6.0.1.

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/RF-12717?page=com.atlassian.jira.plugin.s... ] Juraj Húska edited comment on RF-12717 at 1/16/13 8:57 AM: ----------------------------------------------------------- Hey Brain, *I can just confirm the reported behavior.* * When deploying on {{EAP 6.0.1}} - exception is thrown. * When application is deployed on {{EAP 6.0.0}}, no exception is thrown when working with the table. Changing {{<rich:dataTable>}} for {{<h:dataTable>}} and {{<rich:column>}} for {{<h:column>}} make the code working as being said. Please, let me know if I can do more about this one. was (Author: jhuska): Hey Brain, *I can just confirm the reported behavior.* * When deploying on {{EAP 6.0.1}} - exception is thrown. * When application is deployed on {{EAP 6.0.0}}, no exception is thrown when working with the table. Changing {{<rich:dataTable>}} for {{<h:dataTable>}} and {{<rich:column>}} for {{<h:column>}} make the code working as being said. Please, let me know I can do more about this one. > “Component ID <componentId> has already been found in the view” exception when using rich:dataTable with JSF 2.1.13 on EAP 6.0.1. > --------------------------------------------------------------------------------------------------------------------------------- > > Key: RF-12717 > URL: https://issues.jboss.org/browse/RF-12717 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.2.3.Final > Reporter: Ilia Vassilev > Assignee: Brian Leathem > Attachments: sample.rar > > > This is a problem with <richataTable>. The component id for each row is reused. If you change the markup to use an ordinary <h:dataTable> and <h:column> then it works correctly. -- 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

11 years, 12 months

1
0
0 / 0

[JBoss JIRA] (RF-12717) “Component ID <componentId> has already been found in the view” exception when using rich:dataTable with JSF 2.1.13 on EAP 6.0.1.

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/RF-12717?page=com.atlassian.jira.plugin.s... ] Juraj Húska updated RF-12717: ----------------------------- Assignee: Brian Leathem (was: Juraj Húska) > “Component ID <componentId> has already been found in the view” exception when using rich:dataTable with JSF 2.1.13 on EAP 6.0.1. > --------------------------------------------------------------------------------------------------------------------------------- > > Key: RF-12717 > URL: https://issues.jboss.org/browse/RF-12717 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.2.3.Final > Reporter: Ilia Vassilev > Assignee: Brian Leathem > Attachments: sample.rar > > > This is a problem with <richataTable>. The component id for each row is reused. If you change the markup to use an ordinary <h:dataTable> and <h:column> then it works correctly. -- 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

11 years, 12 months

1
0
0 / 0

[JBoss JIRA] (RF-12717) “Component ID <componentId> has already been found in the view” exception when using rich:dataTable with JSF 2.1.13 on EAP 6.0.1.

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/RF-12717?page=com.atlassian.jira.plugin.s... ] Juraj Húska edited comment on RF-12717 at 1/16/13 8:57 AM: ----------------------------------------------------------- Hey Brain, *I can just confirm the reported behavior.* * When deploying on {{EAP 6.0.1}} - exception is thrown. * When application is deployed on {{EAP 6.0.0}}, no exception is thrown when working with the table. Changing {{<rich:dataTable>}} for {{<h:dataTable>}} and {{<rich:column>}} for {{<h:column>}} make the code working as being said. Please, let me know I can do more about this one. was (Author: jhuska): Hey Brain, I can just confirm the reported behavior, when deploying on {{EAP 6.0.1}} - exception is thrown. When application is deployed on {{EAP 6.0.0}}, no exception is thrown when working with the table. Changing {{<rich:dataTable>}} for {{h:dataTable}} and {{rich:column}} for {{h:column}} make the code working as being said. Please, let me know I can do more about this one. > “Component ID <componentId> has already been found in the view” exception when using rich:dataTable with JSF 2.1.13 on EAP 6.0.1. > --------------------------------------------------------------------------------------------------------------------------------- > > Key: RF-12717 > URL: https://issues.jboss.org/browse/RF-12717 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.2.3.Final > Reporter: Ilia Vassilev > Assignee: Juraj Húska > Attachments: sample.rar > > > This is a problem with <richataTable>. The component id for each row is reused. If you change the markup to use an ordinary <h:dataTable> and <h:column> then it works correctly. -- 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

11 years, 12 months

1
0
0 / 0

[JBoss JIRA] (RF-12717) “Component ID <componentId> has already been found in the view” exception when using rich:dataTable with JSF 2.1.13 on EAP 6.0.1.

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/RF-12717?page=com.atlassian.jira.plugin.s... ] Juraj Húska commented on RF-12717: ---------------------------------- Hey Brain, I can just confirm the reported behavior, when deploying on {{EAP 6.0.1}} - exception is thrown. When application is deployed on {{EAP 6.0.0}}, no exception is thrown when working with the table. Changing {{<rich:dataTable>}} for {{h:dataTable}} and {{rich:column}} for {{h:column}} make the code working as being said. Please, let me know I can do more about this one. > “Component ID <componentId> has already been found in the view” exception when using rich:dataTable with JSF 2.1.13 on EAP 6.0.1. > --------------------------------------------------------------------------------------------------------------------------------- > > Key: RF-12717 > URL: https://issues.jboss.org/browse/RF-12717 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.2.3.Final > Reporter: Ilia Vassilev > Assignee: Juraj Húska > Attachments: sample.rar > > > This is a problem with <richataTable>. The component id for each row is reused. If you change the markup to use an ordinary <h:dataTable> and <h:column> then it works correctly. -- 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

11 years, 12 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 January 2013