February 2013 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-12750) extendedDataTable make facet header clickable using default sortHandle

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12750?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12750: ------------------------------- Sprint: 4.3.1 Sprint - Fixes > extendedDataTable make facet header clickable using default sortHandle > ---------------------------------------------------------------------- > > Key: RF-12750 > URL: https://issues.jboss.org/browse/RF-12750 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.3.0.M3 > Reporter: Marc A. Harnos > Priority: Minor > Labels: datatable, extendedDataTable, extended_datatable, extendeddatatable > Fix For: 4.3.1 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > It would be nice, if the default sort handler on an extendedDataTable would also make the facet header clickable (like the sorting arrows span). -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-12523) a4j:commandButton generates duplicated context path using a resource value expression within image attribute

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12523?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12523: ------------------------------- Sprint: 4.3.1 Sprint - Fixes > a4j:commandButton generates duplicated context path using a resource value expression within image attribute > ------------------------------------------------------------------------------------------------------------ > > Key: RF-12523 > URL: https://issues.jboss.org/browse/RF-12523 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: resource handling > Affects Versions: 4.2.2.Final, 4.3.0.M1 > Environment: Windows 7 Professional, JBoss AS 6.1.0.Final, Mojarra 2.1.7 > Reporter: Andreas Owczarek > Priority: Minor > Labels: testcase_provided > Fix For: 4.3.1 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > a4j:commandButton produces an extra context path prefix for the image resource path, when it is used with the value expression {code}#{resource['library:file']}{code} for the image attribute. > {code:xml|title=Example code} > <a4j:commandButton image="#{resource['icons:icon.gif']}" value="#{resource['icons:icon.gif']}"/> > {code} > {code:xml|title=Generated Result code} > <input type="image" alt="/com.example.my.context.path/faces/javax.faces.resource/icon.gif?ln=icons" src="/com.example.my.context.path/com.example.my.context.path/faces/javax.faces.resource/icon.gif?ln=icons" value="/com.example.my.context.path/faces/javax.faces.resource/icon.gif?ln=icons" onclick="RichFaces.ajax("j_idt76",event,{"incId":"1"} );return false;" name="j_idt76" id="j_idt76"> > {code} > The generated code show the correct value for the expression within the generated button label, but the image could not be located correctly because of the wrong generated image resource path. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-12768) Metamer: rich:tabPanel: Tabs are not clickable and can't be removed in Firefox 18/19

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12768?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on RF-12768: --------------------------------- No worries, I have put a fix together: https://github.com/richfaces/qa/pull/9 > Metamer: rich:tabPanel: Tabs are not clickable and can't be removed in Firefox 18/19 > ------------------------------------------------------------------------------------ > > Key: RF-12768 > URL: https://issues.jboss.org/browse/RF-12768 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.2.3.Final > Environment: Ubuntu 12.04 LTS, JBoss AS 7.1, Firefox 18.0.1 > Reporter: Petr Mensik > Assignee: Petr Mensik > Attachments: RF-12768.png > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > Adding new tabs to to rich:tabPanel works fine but you can't remove panels created this way and you also can't click on them so their content is never displayed. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-12754) rich:validator message cannot be customized when using bean validation (via javax.faces.validator.BeanValidator.MESSAGE property)

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12754?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12754: ------------------------------- Sprint: 4.3.1 Sprint - Fixes > rich:validator message cannot be customized when using bean validation (via javax.faces.validator.BeanValidator.MESSAGE property) > --------------------------------------------------------------------------------------------------------------------------------- > > Key: RF-12754 > URL: https://issues.jboss.org/browse/RF-12754 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-validators > Affects Versions: 4.3.0.CR1 > Environment: Glassfish 3.1.2.2, jdk7u9 > Reporter: Nejc G > Assignee: Brian Leathem > Labels: testcase_provided > Fix For: 4.3.1 > > Attachments: sample.rar > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > rich:validator clientside validation is ignoring javax.faces.validator.BeanValidator.MESSAGE property for messages. Standard validation without rich:validator works fine. Problem is there is no way to customize error (show label) hence making bean validation using this path nearly useless. > I have the aforementioned property in a property file, configured to be used through locale-config line in faces-config.xml. The line reads: > javax.faces.validator.BeanValidator.MESSAGE={1}: {0} > and as mentioned rich:validator only outputs {0} (that is msg from bean validation). Seems to me it doesn't behave as configured. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-12786) Showcase - rewrite readme to markdown

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12786?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12786: ------------------------------- Sprint: 4.3.1 Sprint - Fixes > Showcase - rewrite readme to markdown > ------------------------------------- > > Key: RF-12786 > URL: https://issues.jboss.org/browse/RF-12786 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: doc, showcase > Affects Versions: 4.3.0.Final > Reporter: Juraj Húska > Assignee: Juraj Húska > Priority: Minor > Fix For: 4.3.1 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > Please consider rewriting of showcase readme.txt to mark down syntax to be nicely parsed by GitHub. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-12784) Showcase readme - update deployment from eclipse part

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12784?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12784: ------------------------------- Sprint: 4.3.1 Sprint - Fixes > Showcase readme - update deployment from eclipse part > ----------------------------------------------------- > > Key: RF-12784 > URL: https://issues.jboss.org/browse/RF-12784 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: doc, showcase > Affects Versions: 4.3.0.Final, 5-Tracking > Reporter: Juraj Húska > Assignee: Juraj Húska > Priority: Trivial > Fix For: 4.3.1 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > The deployment of the showcase from eclipse needs to be written down in in more details, because it is not trivial: > An user needs to be aware of: > * select correct maven profile > * alter the deployment assembly > * be aware of wrong context root load in the eclipse browser > I will send pull request for this one. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-12791) Update the quickstart pom files to match changes made in the jboss-jdf repository

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12791?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12791: ------------------------------- Sprint: 4.3.1 Sprint - Fixes > Update the quickstart pom files to match changes made in the jboss-jdf repository > --------------------------------------------------------------------------------- > > Key: RF-12791 > URL: https://issues.jboss.org/browse/RF-12791 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: examples > Reporter: Sande Gilda > Fix For: 4.3.1 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > There were numerous changes to the quickstart pom files: > - property names were shortened and standardized > - property versions were updated > - comments were standardized around product/community version numbers > It may be easiest just to copy and paste the corresponding jboss-jdf quickstart pom.xml files into your repository, however, these are the commits: > https://github.com/sgilda/quickstart/commit/ca2a7bea84262a7aa28b082760746... > https://github.com/sgilda/quickstart/commit/d951d07c1a2e980b0550ff62145cf... -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-12781) The kitchensink-rf quickstart uses obsolete property names and values

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12781?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12781: ------------------------------- Sprint: 4.3.1 Sprint - Fixes > The kitchensink-rf quickstart uses obsolete property names and values > ---------------------------------------------------------------------- > > Key: RF-12781 > URL: https://issues.jboss.org/browse/RF-12781 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: examples > Reporter: Sande Gilda > Fix For: 4.3.1 > > Original Estimate: 45 minutes > Remaining Estimate: 45 minutes > > The POM file currently contains: > {code} > <jboss.as.plugin.version>7.1.1.Final</jboss.as.plugin.version> > {code} > The correct name/value is: > {code} > <version.org.jboss.as.plugins.maven.plugin>7.3.Final</version.org.jboss.as.plugins.maven.plugin> > {code} > It also defines: > {code} >  > <jboss.bom.version>1.0.0.Final</jboss.bom.version> >  >  > {code} > That section should be defined as follows: > {code} >  > <version.org.jboss.bom>1.0.4.Final</version.org.jboss.bom> >  >  > {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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-12765) Rich:tabPanel not possible to switch tabs when only dynamic tabs are present

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12765?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12765: ------------------------------- Fix Version/s: (was: 4.3.1) > Rich:tabPanel not possible to switch tabs when only dynamic tabs are present > ---------------------------------------------------------------------------- > > Key: RF-12765 > URL: https://issues.jboss.org/browse/RF-12765 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.3.0.M3, 4.3.0.CR2 > Environment: Linux, windows any browser Chrom, Mozilla > Reporter: Tali Han > Assignee: Lukáš Fryč > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > Rih:Tab panel functionality is broken. > If you have dynamically generated tabs, you'll be able to switch from first to last, and then to first, but you'll not be able to switch to any other tab again. > Remove from example that comes with richfaces distribution first static tab for dynamic tabs and you'll be able to reproduce this behaviour. > richfaces/tabPanel/samples/dynamic-sample.xhtml > {code} > <rich:tabPanel activeItem="#{dynamicPanelBean.activeTab}"> > <ui:remove> > <rich:tab header="Static"> > This tab is static one. > > All of the following tabs are dynamically generated using a4j:repeat. > </rich:tab> > </ui:remove> > <a4j:repeat value="#{skinBean.skins}" var="skinName"> > > <rich:tab header="#{skinName}" name="#{skinName}"> > <f:facet name="header">#{skinName}</f:facet> > All the controls below are just standard JSF components skinned with RichFaces: > <hr /> > <h:form> > {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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-12768) Metamer: rich:tabPanel: Tabs are not clickable and can't be removed in Firefox 18/19

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12768?page=com.atlassian.jira.plugin.s... ] Brian Leathem resolved RF-12768. -------------------------------- Fix Version/s: (was: 4.3.1) Resolution: Rejected > Metamer: rich:tabPanel: Tabs are not clickable and can't be removed in Firefox 18/19 > ------------------------------------------------------------------------------------ > > Key: RF-12768 > URL: https://issues.jboss.org/browse/RF-12768 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.2.3.Final > Environment: Ubuntu 12.04 LTS, JBoss AS 7.1, Firefox 18.0.1 > Reporter: Petr Mensik > Assignee: Petr Mensik > Attachments: RF-12768.png > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > Adding new tabs to to rich:tabPanel works fine but you can't remove panels created this way and you also can't click on them so their content is never displayed. -- 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, 9 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 February 2013