June 2009 - richfaces-issues - Jboss List Archives

[JBoss JIRA] Created: (RF-6138) calendar and german translation of button labels

by chris s (JIRA)

calendar and german translation of button labels ------------------------------------------------ Key: RF-6138 URL: https://jira.jboss.org/jira/browse/RF-6138 Project: RichFaces Issue Type: Bug Affects Versions: 3.3.0 Reporter: chris s Priority: Trivial Fix For: 3.3.1 Several button labels in calendar component are not translated to German: I try to give you the best possible translation even if it's not always the literal one: 'Apply' = 'Übernehmen' 'Today' = 'Heute' 'Clean' = 'Löschen' 'Ok' = 'OK' 'Cancel'= 'Abbrechen' I hope you are familiar with German 'Umlaute' (öäüß, ÖÄÜ). It's properly displayed with UTF-8 or ISO-8859-1 or -15. If your EMail-client can't display it, here are the codes: 'Ü' in 'Übernehmen' = U+00DC or ANSI \uDC 'ö' in 'Löschen' = U+00F6 \uF6 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 7 months

3
3
0 / 0

[JBoss JIRA] Created: (RF-7173) extendedDataTable: bottom of the table is too wide under IE8

by Alexander Dubovsky (JIRA)

extendedDataTable: bottom of the table is too wide under IE8 ------------------------------------------------------------ Key: RF-7173 URL: https://jira.jboss.org/jira/browse/RF-7173 Project: RichFaces Issue Type: Bug Components: browser compatibility Affects Versions: 3.3.1 Environment: IE8 Reporter: Alexander Dubovsky Assignee: Nick Belaevski Priority: Minor # Open richfaces-demo on extendedDataTable page (or any application with extendedDataTable) # Check table bottom Result: it is too wide. See attached screen shot. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 7 months

5
11
0 / 0

[JBoss JIRA] Created: (RF-5608) Tree : ajaxSingle doesn not keep its state if was defined via el-expression.

by Alexander Dubovsky (JIRA)

Tree : ajaxSingle doesn not keep its state if was defined via el-expression. ---------------------------------------------------------------------------- Key: RF-5608 URL: https://jira.jboss.org/jira/browse/RF-5608 Project: RichFaces Issue Type: Bug Affects Versions: 3.2.2, 3.3.0 Environment: 3.2.2.GA, 3.3.0.CR2 Reporter: Alexander Dubovsky Assignee: Nick Belaevski Fix For: Future Code: <rich:tree value="#{custom.data}" var="item"> <rich:treeNode ajaxSingle="true" dragListener="#{item.processDrag}" dropListener="#{item.processDrop}" dragType="all" acceptedTypes="all"> <h:outputText value="#{item.value}" /> </rich:treeNode> </rich:tree> # In this case drag/drop is possible normally any node on any node => listeners are triggered OK # Change ajaxSingle="#{true}" and try drag/srop Result: drag/ drop operation is possible only on itself, i.e. listeners are triggered only in case drag node1 and drop it on node1 (itself). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 8 months

3
5
0 / 0

[JBoss JIRA] Created: (RF-7192) Ajax component processing outside of region/form

by Thomas W (JIRA)

Ajax component processing outside of region/form ------------------------------------------------ Key: RF-7192 URL: https://jira.jboss.org/jira/browse/RF-7192 Project: RichFaces Issue Type: Bug Components: component-a4j-core Affects Versions: 3.3.0 Reporter: Thomas W RF 3.3.0 GA Issue with server side processing of AJAX enabled components that are outside of any region that is requested to be rendered as well as any a:outputPanel with ajaxRendered="true". This happens with tree and table components, for example. I could track this down to behavior in UIDataAdapter. With the following change the unwanted processing is turned off: public void encodeAjaxChild(FacesContext context, String path, final Set<String> ids, final Set<String> renderedAreas) throws IOException { boolean isRenderedPath = false; for (String id : ids) { if (id.startsWith(path)) { isRenderedPath = true; } } if (!isRenderedPath) { return; } With this addition, any component that falls outside the list of requested ids (reRender) will be skipped. This has muted the excessive component processing (processing that would never result in DOM rendering). A real fix would need to allow for processing of outputPanels with ajaxRendered="true". What is the correct fix for this problem? <a:outputPanel id="searchResults" ajaxRendered="false" styleClass="noBorder"> <a:region> <h:form id="searchForm" styleClass="noBorder"> <rich:scrollableDataTable .... <a:support event="onselectionchange" action="#{someAction.process}" reRender="region1,region2" limitToList="true" status="globalStatus"/> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 8 months

3
3
0 / 0

[JBoss JIRA] Created: (RF-7141) richfaces-demo: broken header on Calendar and Tree pages when Tag Information tab is opened

by Alexander Dubovsky (JIRA)

richfaces-demo: broken header on Calendar and Tree pages when Tag Information tab is opened ------------------------------------------------------------------------------------------- Key: RF-7141 URL: https://jira.jboss.org/jira/browse/RF-7141 Project: RichFaces Issue Type: Bug Affects Versions: 3.3.1 Reporter: Alexander Dubovsky Assignee: Ilya Shaikovsky Priority: Optional Attachments: 64.png # Open richfaces-demo on Calendar or Tree page # Move to Tag Information tab # Scroll to the right Result: See attached screen shot. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 8 months

3
8
0 / 0

[JBoss JIRA] Created: (RF-6471) Drap and drop should scroll tree up or down when scrollbars are displayed

by Wouter van Reeven (JIRA)

Drap and drop should scroll tree up or down when scrollbars are displayed ------------------------------------------------------------------------- Key: RF-6471 URL: https://jira.jboss.org/jira/browse/RF-6471 Project: RichFaces Issue Type: Feature Request Affects Versions: 3.3.0 Reporter: Wouter van Reeven We have a rich:panel with a rich:tree inside of it. The rich:panel has "overflow: auto;" in its style. Whenever the tree gets higher than a certain height, the rich:panel displays scrollbars. For maintenance of the tree we have implemented dragging and dropping of tree nodes to either move them to a certain location, or to copy them to that location. When the tree is very high and the scrollbars are visible, the panel doesn't automatically scroll up or down whenever a tree node is dragged to the upper or lower boundary of the panel. When using a mouse with a wheel, it is possible to scroll the panel with the mouse wheel while dragging a tree node. However, many of our users use laptops with no wheelmouse so they cannot do this. Please extend the rich:panel (and other components that may have a tree component inside of them) with a setting that enables (or disables) scrolling of the panel during drag actions. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 8 months

3
2
0 / 0

[JBoss JIRA] Created: (RF-5465) Tree: node is expanded and then automatically collapsed.

by Alexander Dubovsky (JIRA)

Tree: node is expanded and then automatically collapsed. -------------------------------------------------------- Key: RF-5465 URL: https://jira.jboss.org/jira/browse/RF-5465 Project: RichFaces Issue Type: Bug Affects Versions: 3.3.0 Environment: 3.3.0.BETA5 Reporter: Alexander Dubovsky Assignee: Nick Belaevski Define tree with following attributes: toggleOnClick="true", switchType="client", ajaxSubmitSelection="true" # Open page with defined tree # Click on any node without leaves Result: node is expanded and then automatically collapsed -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 8 months

2
4
0 / 0

[JBoss JIRA] Created: (RF-4521) Duplicated tags in rich.taglib.xml and richfaces.taglib.xml

by Juergen Zimmermann (JIRA)

Duplicated tags in rich.taglib.xml and richfaces.taglib.xml ----------------------------------------------------------- Key: RF-4521 URL: https://jira.jboss.org/jira/browse/RF-4521 Project: RichFaces Issue Type: Bug Affects Versions: 3.2.2 Environment: RichFaces 3.2.2, Mojarra 2.0 nightly as of Sep. 17 Reporter: Juergen Zimmermann META-INF/rich.taglib.xml and META-INF/richfaces.taglib.xml are containing twice the tag definitions "dragListener" and "dropListener". The new Facelets compiler being part of Mojarra 2.0 is complaining about such duplicates. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 8 months

3
4
0 / 0

[JBoss JIRA] Created: (RF-4522) Incompatibility with Mojarra 2.0: package names changed

by Juergen Zimmermann (JIRA)

Incompatibility with Mojarra 2.0: package names changed ------------------------------------------------------- Key: RF-4522 URL: https://jira.jboss.org/jira/browse/RF-4522 Project: RichFaces Issue Type: Bug Affects Versions: 3.2.2 Reporter: Juergen Zimmermann RichFaces 3.2.2 are incompatible with Mojarra 2.0 because the package names changed: * old: com.sun.facelets * new: com.sun.faces.facelets -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 8 months

3
4
0 / 0

[JBoss JIRA] Created: (RF-7226) AjaxValidator - Could not build a default Bean Validator factory

by Lukas Fryc (JIRA)

AjaxValidator - Could not build a default Bean Validator factory ---------------------------------------------------------------- Key: RF-7226 URL: https://jira.jboss.org/jira/browse/RF-7226 Project: RichFaces Issue Type: Bug Components: component Affects Versions: 3.3.1 Environment: JBoss AS 5.0.1.GA, JDK 1.5 or just http://livedemo.exadel.com/richfaces-demo/ Reporter: Lukas Fryc When I tried to put something in inputs using <rich:ajaxValidator event="onblur"/> on AjaxValidator's page and next I let it validate (blur input), it resulted to HTTP Status 500: javax.servlet.ServletException: javax.faces.FacesException: Could not build a default Bean Validator factory javax.faces.webapp.FacesServlet.service(FacesServlet.java:277) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83) org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:38) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:90) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) ... javax.validation.ValidationException: Unable to find a default provider javax.validation.Validation$GenericBootstrapImpl.configure(Validation.java:248) javax.validation.Validation.buildDefaultValidatorFactory(Validation.java:115) org.richfaces.validator.BeanValidator.getValidator(BeanValidator.java:105) org.richfaces.validator.BeanValidator.validate(BeanValidator.java:41) org.richfaces.validator.ObjectValidator$ValidationResolver.setValue(ObjectValidator.java:411) org.jboss.el.parser.AstPropertySuffix.setValue(AstPropertySuffix.java:73) org.jboss.el.parser.AstValue.setValue(AstValue.java:84) org.jboss.el.ValueExpressionImpl.setValue(ValueExpressionImpl.java:249) ... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 8 months

4
12
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues June 2009