January 2013 - richfaces-issues - Jboss List Archives

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

by Nejc G (JIRA)

[ https://issues.jboss.org/browse/RF-12754?page=com.atlassian.jira.plugin.s... ] Nejc G updated RF-12754: ------------------------ Attachment: sample.rar Hm I made sample and now I noticed you probably don't need it anymore... attaching it anyway since I've also noticed a4j:ajax works correctly for keyup event until blur happens (and msg gets replaced), so this is probably f:ajax thing. > 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 > Attachments: sample.rar > > > 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, 2 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 Pavol Pitonak (JIRA)

[ https://issues.jboss.org/browse/RF-12754?page=com.atlassian.jira.plugin.s... ] Pavol Pitonak reassigned RF-12754: ---------------------------------- Assignee: Brian Leathem (was: Pavol Pitonak) I reproduced the issue and created tests for it https://github.com/richfaces/richfaces5/pull/6 > 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 > > 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, 2 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: ----------------------------- Workaround Description: Set the _context-param_ _javax.faces.PARTIAL_STATE_SAVING_ to _false_. (was: Set the _context-param_ _javax.faces.PARTIAL_STATE_SAVING_ set to _false_.) > “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 > Fix For: 4.3.0.Final > > Attachments: sample.rar > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > 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, 2 months

1
0
0 / 0

[JBoss JIRA] (RF-12710) rich:calendar - currentDate attribute has confusing name and documentation

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12710?page=com.atlassian.jira.plugin.s... ] Brian Leathem resolved RF-12710. -------------------------------- Resolution: Done Thanks [~jpapouse]! > rich:calendar - currentDate attribute has confusing name and documentation > -------------------------------------------------------------------------- > > Key: RF-12710 > URL: https://issues.jboss.org/browse/RF-12710 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: doc > Affects Versions: 4.3.0.CR1 > Reporter: Jan Papousek > Assignee: Brian Leathem > Fix For: 4.3.0.Final > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > Rich:calendar@currentDate sets a default month which will be displayed in its popup. The VDL doc says {quote}Defines the current date{quote} > I think the attribute name should be more explanatory and its documentation should be updated. -- 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, 2 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 Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12717?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12717: ------------------------------- Workaround Description: Set the _context-param_ _javax.faces.PARTIAL_STATE_SAVING_ set to _false_. Thanks for taking the time to narrow down the cause [~jhuska]! > “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 > Fix For: 4.3.0.Final > > Attachments: sample.rar > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > 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, 2 months

1
0
0 / 0

[JBoss JIRA] (RF-12728) rich:fileUpload doesn't accept valid file after its unsuccessful multiple upload

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12728?page=com.atlassian.jira.plugin.s... ] Brian Leathem reassigned RF-12728: ---------------------------------- Assignee: Jan Papousek (was: Brian Leathem) Jan, I made a fix to the component, undoing the change introduced in RF-12693. PLease verify by running through your steps to reproduce. > rich:fileUpload doesn't accept valid file after its unsuccessful multiple upload > -------------------------------------------------------------------------------- > > Key: RF-12728 > URL: https://issues.jboss.org/browse/RF-12728 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > 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.34 > Java(TM) SE Runtime Environment 1.7.0_10-b18 @ Linux > Firefox 16.0 @ Linux x86_64 > RichFaces 4.3.0.CR1 > Metamer 4.3.0.20130114-CR1 > JBoss Application Server: Weld Integration 7.1.1.Final > JBoss AS 7.1.1.Final > Java(TM) SE Runtime Environment 1.7.0_10-b18 @ Linux > Firefox 16.0 @ Linux x86_64 > Reporter: Jan Papousek > Assignee: Jan Papousek > Labels: needs-qe, regression > Fix For: 4.3.0.Final > > Attachments: to_upload.png > > Original Estimate: 3 hours > Remaining Estimate: 3 hours > > Using 4.3.0.M3 I've successfuly uploaded 3 files from the attachment in one time. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (RF-12636) rich:calendar: @preloadDateRangeBegin and @preloadDateRangeEnd are not working

by Jiří Štefek (JIRA)

[ https://issues.jboss.org/browse/RF-12636?page=com.atlassian.jira.plugin.s... ] Jiří Štefek resolved RF-12636. ------------------------------ Assignee: Jiří Štefek Fix Version/s: (was: 5-Tracking) Resolution: Rejected A @dataModel bound with calendar was necessary to get it working. > rich:calendar: @preloadDateRangeBegin and @preloadDateRangeEnd are not working > ------------------------------------------------------------------------------ > > Key: RF-12636 > URL: https://issues.jboss.org/browse/RF-12636 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input, doc > Environment: RichFaces 4.3.0-SNAPSHOT > Metamer 4.3.0-SNAPSHOT > Apache Tomcat 7.0.32/ JBoss AS 7.1 > Java(TM) SE Runtime Environment 1.7.0_09-b05 @ Linux > Firefox 16.0 @ Linux x86_64 > Reporter: Jiří Štefek > Assignee: Jiří Štefek > > These attributes should work with dateModel and calendar in client mode, but they do not. > Should an ajax request be made when navigating calendar to not preloaded date? Or should calendar forbid such action? > Or else? > Please, also update a VDL-doc for these two. -- 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, 2 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 Pavol Pitonak (JIRA)

[ https://issues.jboss.org/browse/RF-12754?page=com.atlassian.jira.plugin.s... ] Pavol Pitonak commented on RF-12754: ------------------------------------ Hi [~neikius], could you please provide a sample? > 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: Pavol Pitonak > > 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, 2 months

1
0
0 / 0

[JBoss JIRA] (RF-12038) IE8 - Object does not support this property or method - a4j:jsFunction

by Jean ANDRE (JIRA)

[ https://issues.jboss.org/browse/RF-12038?page=com.atlassian.jira.plugin.s... ] Jean ANDRE commented on RF-12038: --------------------------------- Well, probably not necessary - What I'm expecting from the richFaces team because is not really an issue from RF code is that you update the documentation of this tag. The documentation should warn the user that using the same name for id and name for this tag triggers an error with IE. The doc, should explain the message and the workaround for the error. As IE implementation is going to stay like this for a while, it is no a temporary advise but a constraint, a limitation and then having a clearly explanation to the developer community will be help us to not losing our time. Probably, you can have a special section like "Compatibility issues and limitations". Best regards. > IE8 - Object does not support this property or method - a4j:jsFunction > ---------------------------------------------------------------------- > > Key: RF-12038 > URL: https://issues.jboss.org/browse/RF-12038 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.2.0.Final > Environment: cssparser-0.9.6- guava-11.0.1 - hibernate-validator-4.2.0.Final - JSF/Mojarra 2.1.6 - springframework-3.0.6.RELEASE - sac-1.3 - Windows 7 - IE 8.0.1.7601.17514 > Reporter: Jean ANDRE > Assignee: Brian Leathem > Labels: waiting_on_user > Attachments: index.xhtml, NestedWeb.zip, NestedWeb_RF-12038.zip, ScreenShot_RF-12038.png > > > Under IE8, IE reports the following error message due to a javascript error. However, the page are well displayed and the application is running ok. > Object doesn't support this property or method line 177 caracter 1 > Object doesn't support this property or method line 177 caracter 99 > Under IE Debugger, the line is: > {code} > closeTab=function(tabId){RichFaces.ajax("closeTab",null,{"incId":"1","parameters":{"tabId":tabId} } )};< > The caracter 99, is..............................................................................| (here) > {code} > This is a code generated by a4j:jsFunction from the XHTML > {code} >  >  >  > <a4j:jsFunction id="closeTab" name="closeTab" action="#{desktopTabController.doCloseTab}" render="menu-opened-tabs,desktopTabPanel"> > <a4j:param name="tabId" assignTo="#{desktopTabController.closeTabId}" /> > </a4j:jsFunction> > {code} > The rendered code is : > {code} >  >  > <span id="closeTab" style="display: none;"><script type="text/javascript">closeTab=function(tabId){RichFaces.ajax("closeTab",null,{"incId":"1","parameters":{"tabId":tabId} } )};</script></span> > {code} > See also this link as we got almost a similar: https://bugzilla.redhat.com/show_bug.cgi?id=601360. -- 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, 2 months

1
0
0 / 0

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

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/RF-12523?page=com.atlassian.jira.plugin.s... ] Juraj Húska updated RF-12523: ----------------------------- Assignee: (was: Juraj Húska) > 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 > Labels: testcase_provided > Fix For: 5-Tracking > > > 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, 2 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