January 2013 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-12733) Metamer: rich:treeToggleListener: unable expand tree in second level [myFaces]

by Ján Jamrich (JIRA)

[ https://issues.jboss.org/browse/RF-12733?page=com.atlassian.jira.plugin.s... ] Ján Jamrich updated RF-12733: ----------------------------- Summary: Metamer: rich:treeToggleListener: unable expand tree in second level [myFaces] (was: Metamer: rich:treeToggleListener: cannot expand tree in second level [myFaces]) > Metamer: rich:treeToggleListener: unable expand tree in second level [myFaces] > ------------------------------------------------------------------------------ > > Key: RF-12733 > URL: https://issues.jboss.org/browse/RF-12733 > 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 > Metamer: > 2023898d4b163a889955c1d028149a31 metamer-4.3.0.20130114-CR1-tomcat7-myfaces.war > Reporter: Ján Jamrich > Labels: myfaces > Attachments: metamer-treeToggleListener-expand-2nd-level-tree-problem.png > > > Cannot expand second level in tree in rich:treeToggleListener demo. > Getting Error status instead. > See screenshot for more info. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12733) Metamer: rich:treeToggleListener: cannot expand tree in second level [myFaces]

by Ján Jamrich (JIRA)

[ https://issues.jboss.org/browse/RF-12733?page=com.atlassian.jira.plugin.s... ] Ján Jamrich updated RF-12733: ----------------------------- Attachment: metamer-treeToggleListener-expand-2nd-level-tree-problem.png Add screenshot with state I get when attempt expand tree on second level. > Metamer: rich:treeToggleListener: cannot expand tree in second level [myFaces] > ------------------------------------------------------------------------------ > > Key: RF-12733 > URL: https://issues.jboss.org/browse/RF-12733 > 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 > Metamer: > 2023898d4b163a889955c1d028149a31 metamer-4.3.0.20130114-CR1-tomcat7-myfaces.war > Reporter: Ján Jamrich > Labels: myfaces > Attachments: metamer-treeToggleListener-expand-2nd-level-tree-problem.png > > > Cannot expand second level in tree in rich:treeToggleListener demo. > Getting Error status instead. > See screenshot for more info. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12733) Metamer: rich:treeToggleListener: cannot expand tree in second level [myFaces]

by Ján Jamrich (JIRA)

Ján Jamrich created RF-12733: -------------------------------- Summary: Metamer: rich:treeToggleListener: cannot expand tree in second level [myFaces] Key: RF-12733 URL: https://issues.jboss.org/browse/RF-12733 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 Metamer: 2023898d4b163a889955c1d028149a31 metamer-4.3.0.20130114-CR1-tomcat7-myfaces.war Reporter: Ján Jamrich Cannot expand second level in tree in rich:treeToggleListener demo. Getting Error status instead. See screenshot for more info. -- 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, 11 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č edited comment on RF-12689 at 1/16/13 8:07 AM: ---------------------------------------------------------- According to Atmosphere release notes, there are many stability improvements, so I would suggest to upgrade latest stable in point releases. was (Author: lfryc): According to Atmosphere release notes, there are many stability improvements, so I would suggest to release latest stable in point releases. > 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 > Assignee: Lukáš Fryč > Fix For: 4.3-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, 11 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č edited comment on RF-12689 at 1/16/13 8:07 AM: ---------------------------------------------------------- According to Atmosphere release notes, there are many stability improvements, so I would suggest to upgrade to latest stable in point releases. was (Author: lfryc): According to Atmosphere release notes, there are many stability improvements, so I would suggest to upgrade latest stable in point releases. > 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 > Assignee: Lukáš Fryč > Fix For: 4.3-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, 11 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: ---------------------------- Assignee: (was: Lukáš Fryč) > 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 > > > 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, 11 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: 4.3-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 > Assignee: Lukáš Fryč > Fix For: 4.3-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, 11 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č commented on RF-12689: --------------------------------- According to Atmosphere release notes, there are many stability improvements, so I would suggest to release latest stable in point releases. > 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 > Assignee: Lukáš Fryč > > 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, 11 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 Pavol Pitonak (JIRA)

[ https://issues.jboss.org/browse/RF-12717?page=com.atlassian.jira.plugin.s... ] Pavol Pitonak reassigned RF-12717: ---------------------------------- Assignee: Juraj Húska (was: Pavol Pitonak) > “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, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12732) tabindex on rich:tabPanel

by Alexander Kunkel (JIRA)

Alexander Kunkel created RF-12732: ------------------------------------- Summary: tabindex on rich:tabPanel Key: RF-12732 URL: https://issues.jboss.org/browse/RF-12732 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Alexander Kunkel >From the last element inside richfaces tabpanel we would like to tab to the next tab flap. From there either: - press tab again or use the arrow keys to navigate the flaps - press enter to navigate to the contend of the tab that whoose flap tab focus Moreover that last element might be a rich:autocomplete instead of h:input -- 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, 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 January 2013