April 2010 - richfaces-issues - Jboss List Archives

[JBoss JIRA] Created: (RF-1164) Font and hyphenation pattern in PDF

by Svetlana mukhina (JIRA)

Font and hyphenation pattern in PDF ----------------------------------- Key: RF-1164 URL: http://jira.jboss.com/jira/browse/RF-1164 Project: RichFaces Issue Type: Task Components: doc Affects Versions: Future Versions Reporter: Svetlana mukhina Assigned To: Nick Belaevski Fix For: 3.1.0 It's necessary to add more readable font and hyphenation possibility in PDF -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

4
10
0 / 0

[JBoss JIRA] Created: (RF-3911) Speed up documentation building process

by Svetlana mukhina (JIRA)

Speed up documentation building process ---------------------------------------- Key: RF-3911 URL: http://jira.jboss.com/jira/browse/RF-3911 Project: RichFaces Issue Type: Feature Request Components: doc Affects Versions: 3.2.1 Reporter: Svetlana mukhina Assigned To: Nick Belaevski Priority: Optional Fix For: 3.2.2 It's necessary to speed up documentation building process -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

4
9
0 / 0

[JBoss JIRA] Created: (RF-8232) Tags support

by Nick Belaevski (JIRA)

Tags support ------------ Key: RF-8232 URL: https://jira.jboss.org/jira/browse/RF-8232 Project: RichFaces Issue Type: Sub-task Security Level: Public (Everyone can see) Components: CDK Affects Versions: 4.0.0.ALPHA2 Reporter: Nick Belaevski Assignee: Alex Kolonitsky Fix For: 4.0.0.ALPHA2 Implement support for Facelets tags/TagHandler classes. @Tag should be supported for: - Component - Renderer - Behavior - Converter - Validator - Listener -- 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

14 years, 7 months

2
3
0 / 0

[JBoss JIRA] Created: (RF-7839) Support for metadata-complete

by Nick Belaevski (JIRA)

Support for metadata-complete ----------------------------- Key: RF-7839 URL: https://jira.jboss.org/jira/browse/RF-7839 Project: RichFaces Issue Type: Sub-task Components: CDK Affects Versions: 4.0.0.ALPHA2 Reporter: Nick Belaevski Assignee: Alexander Smirnov Fix For: 4.0.0.ALPHA2 -- 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

14 years, 7 months

2
3
0 / 0

[JBoss JIRA] Created: (RF-7770) Waste space between 2 columns in rich:layout

by Andreas Höhmann (JIRA)

Waste space between 2 columns in rich:layout --------------------------------------------- Key: RF-7770 URL: https://jira.jboss.org/jira/browse/RF-7770 Project: RichFaces Issue Type: Bug Components: component Affects Versions: 3.3.2.GA Environment: 3.3.2-SNAPSHOT FF 3 IE 6 Reporter: Andreas Höhmann Priority: Minor in the current 3.3.2-SNAPSHOT the layout-render component calculate the width of layout-panels a little bit "wrong" i have a 2 column layout "left:30%, right:70%" (i guess "left center" || "center right" produce the same problem) ... here is my template: <ui:composition xmlns="http://www.w3.org/1999/xhtml" xmlns:ui="http://java.sun.com/jsf/facelets" xmlns:h="http://java.sun.com/jsf/html" xmlns:f="http://java.sun.com/jsf/core" xmlns:a4j="http://richfaces.org/a4j" xmlns:rich="http://richfaces.org/rich" xmlns:c="http://java.sun.com/jstl/core" xmlns:fn="http://java.sun.com/jsp/jstl/functions" template="#{initParam.mainTemplate}"> <ui:define name="site-title"> <h:outputText value="#{bundle['components.header']}" /> </ui:define> <ui:define name="site-content"> <rich:layout style="width: 100%; height: 100%; background-color: red;"> <rich:layoutPanel id="leftColumn" position="left" width="30%"> <rich:layout id="leftLayout"> <rich:layoutPanel id="leftHeader" position="top" width="100%"> <h:panelGrid cellpadding="5" cellspacing="1" width="100%" headerClass="secondaryNavigation"> <f:facet name="header"> <ui:insert name="left-header"/> </f:facet> </h:panelGrid> </rich:layoutPanel> <rich:layoutPanel id="leftContent" position="bottom" width="100%"> <a4j:outputPanel id="leftContentContainer" layout="block" styleClass="verticalScrollerContainer" style="height: 500px; overflow: auto;"> <div class="verticalScrollerContainerFix"> <ui:insert name="left-content"/> </div> </a4j:outputPanel> </rich:layoutPanel> </rich:layout> </rich:layoutPanel> <rich:layoutPanel id="contentColumn" position="right" width="70%"> <rich:layout id="contentLayout"> <rich:layoutPanel id="contentHeader" position="top" width="100%"> <h:panelGrid cellpadding="5" cellspacing="1" width="100%" headerClass="secondaryNavigation"> <f:facet name="header"> <ui:insert name="content-header"/> </f:facet> </h:panelGrid> </rich:layoutPanel> <rich:layoutPanel id="contentContent" position="bottom" width="100%"> <a4j:outputPanel id="contentContentContainer" layout="block" styleClass="verticalScrollerContainer" style="height: 500px; overflow: auto;"> <div class="verticalScrollerContainerFix"> <ui:insert name="content-content"/> </div> </a4j:outputPanel> </rich:layoutPanel> </rich:layout> </rich:layoutPanel> </rich:layout> </ui:define> </ui:composition> The rendered html contains the following widths for the columns: <div id="leftColumn" style="float: left; width: 29.4%;" width="30%"> <div id="contentColumn" style="float: right; width: 68.6%;" width="70%"> The width-calculation in org.richfaces.renderkit.html.LayoutPanelRenderer should be changed. If i define only "%" widths i expect that the renderer don't change/calculate this widths. -- 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

14 years, 7 months

3
8
0 / 0

[JBoss JIRA] Created: (RF-3517) Entered values in rich:subTable are lost upon validation errors

by Jonck van der Kogel (JIRA)

Entered values in rich:subTable are lost upon validation errors --------------------------------------------------------------- Key: RF-3517 URL: http://jira.jboss.com/jira/browse/RF-3517 Project: RichFaces Issue Type: Bug Affects Versions: 3.1.4 Environment: Windows Vista, JBoss 4.0.5, JSF 1.2 Reporter: Jonck van der Kogel Given the following sample code: <rich:dataTable value="#{backingBean.holders}" var="holder"> <f:facet name="header"> <rich:columnGroup> <rich:column> <h:outputText value="Test"> </rich:column> </rich:columnGroup> </f:facet> <rich:column> <h:inputText value="#{holder.requiredTest}" required="true" /> </rich:column> <rich:subTable value="#{holder}" var="holderSubTable"> <rich:column colspan="1"> <h:inputText value="#{holderSubTable.test}" /> </rich:column> </rich:subTable> </rich:dataTable> When the surrounding form is submitted, the "test" field in the rich:subTable is cleared when a validation error occurs. This is not the expected behavior, normally in JSF when a validation error occurs the entered values remain. To illustrate this, I rebuilt the above scenario but now placed all fields within the same rich:dataTable like so: <rich:dataTable value="#{backingBean.holders}" var="holder"> <f:facet name="header"> <rich:columnGroup> <rich:column> <h:outputText value="Test"> </rich:column> <rich:column> <h:outputText value="Test2"> </rich:column> </rich:columnGroup> </f:facet> <rich:column> <h:inputText value="#{holder.requiredTest}" required="true" /> </rich:column> <rich:column> <h:inputText value="#{holder.test}" /> </rich:column> </rich:dataTable> In this case when the form is submitted and a validation error occurs the "test" field is not cleared, as expected. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

3
4
0 / 0

[JBoss JIRA] Created: (RF-1205) GWT4JSF UIPage tage does not implement GwtSource

by Curt (JIRA)

GWT4JSF UIPage tage does not implement GwtSource ------------------------------------------------ Key: RF-1205 URL: http://jira.jboss.com/jira/browse/RF-1205 Project: RichFaces Issue Type: Bug Environment: WinXP JBoss 4.1CR1, GWT4JSF-1.1.2-SNAPSHOT Reporter: Curt Attachments: UIPage.java.patch Using the page tag from the https://ajax4jsf.dev.java.net/gwt namespace generates an error when it contains a listener child tag. The error is in GwtListenerHandler: com.sun.facelets.tag.TagException: /pages/Login.jsp @14,57 <gwt:gwtListener> Parent is not of type GwtSource, type is: org.ajax4jsf.gwt.jsf.UIPage@99c4cc at org.ajax4jsf.gwt.jsf.GwtListenerHandler.apply(GwtListenerHandler.java:163 The JSF page was structured: <f:view xmlns:f="http://java.sun.com/jsf/core" xmlns:h="http://java.sun.com/jsf/html" xmlns:gwt="https://ajax4jsf.dev.java.net/gwt" xmlns:dri="https://ajax4jsf.dev.java.net/gwt/DRI" contentType="text/html"> <gwt:page title="DRI"> <f:facet name="head"> <h:panelGroup> </h:panelGroup> </f:facet>  <dri:component id="main"> <gwt:gwtListener serviceBean="#{userAuth}"/> </dri:component> </gwt:page> </f:view> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

3
8
0 / 0

[JBoss JIRA] Created: (RF-8568) Improve FreeMarker generator.

by Alexander Smirnov (JIRA)

Improve FreeMarker generator. ----------------------------- Key: RF-8568 URL: https://jira.jboss.org/jira/browse/RF-8568 Project: RichFaces Issue Type: Task Security Level: Public (Everyone can see) Components: CDK Reporter: Alexander Smirnov Assignee: Alexander Smirnov Fix For: 4.0.0.ALPHA2 1) Remove unnecessary wrappers, models and properties. 2) Cleanup FreMarkerRenderer code -- 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

14 years, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (RF-7549) rich:page component does not allow users to overwrite theme classes.

by Alexander Smirnov (JIRA)

rich:page component does not allow users to overwrite theme classes. -------------------------------------------------------------------- Key: RF-7549 URL: https://jira.jboss.org/jira/browse/RF-7549 Project: RichFaces Issue Type: Feature Request Components: component-output Affects Versions: 3.3.1 Reporter: Alexander Smirnov Assignee: Alexander Smirnov Theme CSS loaded after any user styles defined by the loadStyle component hence it has a higest precedence and user classes are ignored. -- 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

14 years, 7 months

2
3
0 / 0

[JBoss JIRA] Created: (RF-6958) RichFaces and Trinidad compatibility issue on Weblogic 10.1 (and Higher)

by Maxim Pavlov (JIRA)

RichFaces and Trinidad compatibility issue on Weblogic 10.1 (and Higher) ------------------------------------------------------------------------ Key: RF-6958 URL: https://jira.jboss.org/jira/browse/RF-6958 Project: RichFaces Issue Type: Bug Components: core Affects Versions: 3.3.0 Environment: Weblogic 10.1 (Same on 10.3), JSF 1.2 (RI), RichFaces 3.3.0, Trinidad 1.2.11 Reporter: Maxim Pavlov Trinidad PPR response can not be parsed in browser if a4j filter is enabled. Ajax4jsf builds in response and modyfies the html content. As a result trinidad can not parse the response on the client side. This code below in org.ajax4jsf.webapp.BaseFilter.handleRequest solved the issue but I'm more than sure that it is not the best solution anyway. protected void handleRequest(HttpServletRequest request, HttpServletResponse response, FilterChain chain) throws IOException, ServletException { final String TRININDAD_PPR_FLAG_PARTIAL = "partial"; final String AJAXREQUEST_FLAG = "AJAXREQUEST"; boolean isTrinidadRequest = request.getParameterMap().containsKey(TRININDAD_PPR_FLAG_PARTIAL) && !request.getParameterMap().containsKey(AJAXREQUEST_FLAG); if (!isTrinidadRequest) { if (log.isDebugEnabled()) { log.debug(Messages .getMessage(Messages.FILTER_XML_OUTPUT)); } // Execute the rest of the filter chain, including the // JSP xmlFilter.doXmlFilter(chain, request, response); } else { // normal request, execute chain ... if (log.isDebugEnabled()) { log.debug(Messages .getMessage(Messages.FILTER_NO_XML_CHAIN)); } chain.doFilter(request, response); } } -- 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

14 years, 7 months

3
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues April 2010