March 2009 - richfaces-issues - Jboss List Archives

[JBoss JIRA] Created: (RF-5184) ExtendedDataTable produce a javascript error when the page is loaded in IE7

by Laura Romero Brox (JIRA)

ExtendedDataTable produce a javascript error when the page is loaded in IE7 --------------------------------------------------------------------------- Key: RF-5184 URL: https://jira.jboss.org/jira/browse/RF-5184 Project: RichFaces Issue Type: Bug Affects Versions: 3.2.2 Environment: Eclipse 3.4.0, jboss-4.2.2.GA, jboss-seam-2.0.2.SP1, IE7 Reporter: Laura Romero Brox Priority: Optional Fix For: 3.2.2 When the page have a ExtendedDataTable, throws a javascript error: 'this.table' is null or isn´t an object. -- 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, 6 months

3
4
0 / 0

[JBoss JIRA] Created: (RF-6659) ExtendedDataTable: grouping does not work or works incorrect in case sortBy is not defined for column.

by Alexander Dubovsky (JIRA)

ExtendedDataTable: grouping does not work or works incorrect in case sortBy is not defined for column. ------------------------------------------------------------------------------------------------------ Key: RF-6659 URL: https://jira.jboss.org/jira/browse/RF-6659 Project: RichFaces Issue Type: Bug Affects Versions: 3.3.1 Environment: 3.3.1.BETA2 Reporter: Alexander Dubovsky Assignee: Nick Belaevski Sources: <rich:extendedDataTable id="table" value="#{exDataTable.value}" var="items" width="400px" groupingColumn="make"> <rich:column id="make" label="Make" width="150px"> <f:facet name="header"> <h:outputText value="Make" /> </f:facet> <h:outputText value="#{items.make}" /> </rich:column> <rich:column id="model" label="Model" width="80px" sortBy="#{items.model}" selfSorted="true"> <f:facet name="header"> <h:outputText value="Model" /> </f:facet> <h:outputText value="#{items.model}" /> </rich:column> </rich:extendedDataTable> # Open page and check grouping of the first column Result: table is grouped complete by the first value # Check "Group by this column" menu item in header menu for this column Result: it is disabled. Seems like new attribute for column is necessary, e.g. "groupBy". -- 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, 6 months

3
2
0 / 0

[JBoss JIRA] Created: (RF-5086) extendedTable: Allow to turn of built-in menu

by Ilya Shaikovsky (JIRA)

extendedTable: Allow to turn of built-in menu --------------------------------------------- Key: RF-5086 URL: https://jira.jboss.org/jira/browse/RF-5086 Project: RichFaces Issue Type: Feature Request Affects Versions: 3.3.0 Reporter: Ilya Shaikovsky Assignee: Nick Belaevski http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4192406#4192406 -- 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, 6 months

12
15
0 / 0

[JBoss JIRA] Created: (RF-5962) Incorrect work of multiply selection with first row in Extended table

by Eugene Stherbin (JIRA)

Incorrect work of multiply selection with first row in Extended table ---------------------------------------------------------------------- Key: RF-5962 URL: https://jira.jboss.org/jira/browse/RF-5962 Project: RichFaces Issue Type: Bug Affects Versions: 3.3.0 Reporter: Eugene Stherbin Priority: Minor 1. RichFaces livedemo http://livedemo.exadel.com/richfaces-demo/richfaces/extendedDataTable.jsf 2. Select selection mode "Multi" (by default) 3. Press Shift button and click on the 1st then 2nd rows --> 1st and 2nd rows are selected 4. Click 3rd row (shift button is still pressed) ------------------------------------------------------------ !!! The first row isn't selected now -- 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, 6 months

3
2
0 / 0

[JBoss JIRA] Created: (RF-6654) ExtendedDataTable: frame/border attributes do not work in Safari

by Alexander Dubovsky (JIRA)

ExtendedDataTable: frame/border attributes do not work in Safari ---------------------------------------------------------------- Key: RF-6654 URL: https://jira.jboss.org/jira/browse/RF-6654 Project: RichFaces Issue Type: Bug Affects Versions: 3.3.1 Environment: 3.3.1.BETA2 Safari 3.2 Reporter: Alexander Dubovsky Assignee: Nick Belaevski Priority: Optional # Set frame="border" and border="10" for ExtendedDataTable # Open page with table under Safari and check frame width Result: frame does not present arrount the table. -- 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, 6 months

3
2
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, 6 months

4
9
0 / 0

[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, 6 months

4
10
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, 6 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, 6 months

3
4
0 / 0

[JBoss JIRA] Created: (RF-5598) a4j:push is not portlet session aware

by Dirk Pitt (JIRA)

a4j:push is not portlet session aware ------------------------------------- Key: RF-5598 URL: https://jira.jboss.org/jira/browse/RF-5598 Project: RichFaces Issue Type: Bug Components: portal Affects Versions: 3.3.0 Environment: Richfaces 3.3.0.CR2, JBoss Portletbridge 1.0.0.B5, JBoss Portal 2.6.4 Reporter: Dirk Pitt Hallo, I have funny problem with a4j:pushBean... We have a web application, which runs perfectly in test environment with single web client. But if for the same page in the web application another browser client is opened, second browser start receiving the events intended for the first browser... So my first impression is that push functionality make no distinction about from which session is called... So I surf little bit in the source code and here what I found.... In org.ajax4jsf.webapp.BaseFilter an instance of PushEventsCounter is obtained with the following call PushEventsCounter listener = eventsManager .getListener(ajaxPushHeader); which my debuging shows ajaxPushHeader contains no session specific information. At this point I have to say I am using the JBoss Portal and JBoss Portlet Bridge. I made some more debuging and I found this.... In org.ajax4jsf.component.UIPush in method getListenerId method only HttpSession case taking into count.... Object session = context.getExternalContext().getSession(false); StringBuffer id = new StringBuffer(); if(null != session && session instanceof HttpSession){ HttpSession httpSession = (HttpSession) session; id.append(httpSession.getId()); } id.append(context.getViewRoot().getViewId()); id.append(NamingContainer.SEPARATOR_CHAR); id.append(getClientId(context)); return id.toString(); But portal delivers PortletSession object so the SessionId is not there at that is causing the mentioned problem... Now this problem is quite critical for our project and I can actually deliver code solution to be commited jboss source tree also but the question is how to solve this without putting portal dependencies to Richfaces classes... Or can we solve this PortletBridge? -- 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, 6 months

4
8
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues March 2009