January 2010 - richfaces-issues - Jboss List Archives

[JBoss JIRA] Updated: (RF-8327) Update BaseModifiableHibernateDataModel according to forum suggestions

by Jay Balunas (JIRA)

[ https://jira.jboss.org/jira/browse/RF-8327?page=com.atlassian.jira.plugin... ] Jay Balunas updated RF-8327: ---------------------------- Component/s: component-tables > Update BaseModifiableHibernateDataModel according to forum suggestions > ---------------------------------------------------------------------- > > Key: RF-8327 > URL: https://jira.jboss.org/jira/browse/RF-8327 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 3.3.3.CR1 > Reporter: Nick Belaevski > Assignee: Andrey Markhel > Fix For: 3.3.3.CR1 > > > See forum link. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Moved: (RF-8327) Update BaseModifiableHibernateDataModel according to forum suggestions

by Nick Belaevski (JIRA)

[ https://jira.jboss.org/jira/browse/RF-8327?page=com.atlassian.jira.plugin... ] Nick Belaevski moved RFPL-367 to RF-8327: ----------------------------------------- Project: RichFaces (was: RichFaces Planning) Key: RF-8327 (was: RFPL-367) Fix Version/s: 3.3.3.CR1 (was: 3.3.3.CR1) Affects Version/s: 3.3.3.CR1 (was: 3.3.3.CR1) > Update BaseModifiableHibernateDataModel according to forum suggestions > ---------------------------------------------------------------------- > > Key: RF-8327 > URL: https://jira.jboss.org/jira/browse/RF-8327 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: 3.3.3.CR1 > Reporter: Nick Belaevski > Assignee: Andrey Markhel > Fix For: 3.3.3.CR1 > > > See forum link. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (RF-8222) wrong information about scripts strategies and compression.

by Ilya Shaikovsky (JIRA)

wrong information about scripts strategies and compression. ----------------------------------------------------------- Key: RF-8222 URL: https://jira.jboss.org/jira/browse/RF-8222 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: doc Affects Versions: 3.3.2.SR1 Reporter: Ilya Shaikovsky Assignee: Nick Belaevski Priority: Critical Fix For: 3.3.3.CR1 Nick, not sure why this issue originally was risen https://jira.jboss.org/jira/browse/RF-2117 but if fix is even worse than previous state was :) Currently NOTE looks like: If you use ALLvalue of Scripts Load Strategy, the JavaScript files compression turns off! -- 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, 10 months

3
9
0 / 0

[JBoss JIRA] Created: (RF-8215) <f:actionParam> is invoked on INVOKE_APPLICATION phase rather than UPDATE_MODEL_VALUES phase when used inside a jsFunction

by George Gastaldi (JIRA)

<f:actionParam> is invoked on INVOKE_APPLICATION phase rather than UPDATE_MODEL_VALUES phase when used inside a jsFunction -------------------------------------------------------------------------------------------------------------------------- Key: RF-8215 URL: https://jira.jboss.org/jira/browse/RF-8215 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-a4j-core Affects Versions: 3.3.2.SR1 Reporter: George Gastaldi The documentation in http://livedemo.exadel.com/richfaces-demo/richfaces/actionparam.jsf?c=act... and http://docs.jboss.org/richfaces/latest_3_3_X/en/devguide/html/a4j_actionp... states that the property assigned in the "assignTo" attribute is set in the UPDATE_MODEL_VALUES phase. By using a jsFunction with an actionParam, it is possible to see that the assignment is done on the INVOKE_APPLICATION phase, thus calling the actionListener defined in the jsFunction Example: <a4j:jsFunction name="myJsFunction" actionListener="#{myBean.myActionListener}" > <a4j:actionparam name="param1"assignTo="#{myBean.paramName}" /> </a4j:jsFunction> Calling: myJsFunction('Any Value') does the trick. The ActionListener will be called AFTER the assignment of the actionParam -- 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, 10 months

4
4
0 / 0

[JBoss JIRA] Created: (RF-8040) Add Maven configuration section to Migration Guide

by Sean Rogers (JIRA)

Add Maven configuration section to Migration Guide -------------------------------------------------- Key: RF-8040 URL: https://jira.jboss.org/jira/browse/RF-8040 Project: RichFaces Issue Type: Task Affects Versions: 4.0.0.ALPHA2 Reporter: Sean Rogers Assignee: Sean Rogers Refer to http://www.jboss.org/community/wiki/HowToConfigureMavenForRichFaces -- 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, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (RF-8199) calendar documentation contains wrong example

by Ilya Shaikovsky (JIRA)

calendar documentation contains wrong example --------------------------------------------- Key: RF-8199 URL: https://jira.jboss.org/jira/browse/RF-8199 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: doc Affects Versions: 3.3.2.SR1 Reporter: Ilya Shaikovsky Assignee: Sean Rogers I the text from the buide highlighted below we getting example which not works since 3.3.0 and then making a not that it not works :) I prefer to just write actually working sample with "onchanged" event. And dateselected could be mentioned but not too wide as it not usefull in common use-cases after its functionality change =============================== "ondateselect" attribute is used to define an event that is triggered before date selection. The "ondateselected" attribute is used to define an event that is triggered after date selection. For example, to fire some event after date selection you should use <a4j:support> . And it should be bound to "ondateselected" event as it's shown in the example below: ... <rich:calendar id="date" value="#{bean.dateTest}"> <a4j:support event="ondateselected" reRender="mainTable"/> </rich:calendar> ... Note: When a timePicker was fulfilled, the "ondateselected" attribute does not allow you to submit a selected date. It happens because this event rose when the date is selected but the input hasn't been updated with new value yet. ================================== -- 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, 10 months

3
2
0 / 0

[JBoss JIRA] Created: (RF-8244) dataTable built-in filter cause form values to be submitted to different rows.

by Hugh Nguyen (JIRA)

dataTable built-in filter cause form values to be submitted to different rows. ------------------------------------------------------------------------------ Key: RF-8244 URL: https://jira.jboss.org/jira/browse/RF-8244 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-tables Affects Versions: 3.3.3.BETA1, 3.3.2.SR1, 3.3.2.GA, 3.3.2.CR1, 3.3.1 Reporter: Hugh Nguyen This is regarding rich:dataTable built-in filtering. The filter requests submit and process the entire form that enclosed the table, including all the form fields inside the table. Besides the issue of inefficiency, this submission cause an obscure bug: The form data of the first row before filtering SOMETIMES get submitted into the first row that appear after the the filtering request is completed. For example, I have an Invoice table like this Invoice No Invoice Amt (filter input) [ ] ------------------------------------------------------------------------------------------------ INV1 [100.00] INV2 [200.00] INV3 [300.00] The filterEvent is set to 'onkeyup' Now, if I type quickly type INV3 to the filter input, the table will show only invoice INV3, which is expected, but the Invoice Amt for INV3 would become 100.00, which is the value for INV1. The value is not just the screen value, but it's also set into the backing bean for INV1. If I leave filterEvent value as default 'onblur', the bug is less likely to occur, but still can happen if I manage to cause the Ajax requests to be sent fast enough. For Richfaces configuration, I enabled the global queue in web.xml. With a bit of tracing, I found that all the input field values present in the table before the filtering happen is sent along with the Filter input during the enclosing form submission, and there is no ajaxSingle attribute for the Filter input. I guess that there is some mix up of processing the multiple filter requests that come before the filtered result is returned, and this cause the submission value to go into the wrong row(s). My suggestion is that there should be some way to cause the form to only process the Filter input, all other inputs should be ignored, in a manner similar to ajaxSingle attribute for the components that support it. -- 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, 10 months

2
12
0 / 0

[JBoss JIRA] Created: (RF-8273) calendar: day cell content has the same id for all the days

by Ilya Shaikovsky (JIRA)

calendar: day cell content has the same id for all the days ----------------------------------------------------------- Key: RF-8273 URL: https://jira.jboss.org/jira/browse/RF-8273 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 3.3.3.BETA1 Reporter: Ilya Shaikovsky Assignee: Nick Belaevski Proposed to fix in 3.3.3 in order to avid possible cross-browsers problems. <a4j:outputPanel layout="block" id="cell" onclick="#{rich:component('organizer')}.resetSelectedDate()" style="height: 100%;"> <h:panelGrid columns="1" width="100%"> <h:outputText value="{day}" style="align:center"/> <h:outputText value="{data.shortDescription.escapeHTML()}"/> <h:outputText value="{data.description.escapeHTML()}"/> </h:panelGrid> </a4j:outputPanel> inside the rich calendar defines markup for the day. So this components encoded once as template for the day. And all the day cells in the result constructed from the tamplate are div's with the same id. Proposed to add month and day to id in order it to became like form:cell:month_day -- 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, 10 months

2
1
0 / 0

[JBoss JIRA] Created: (RF-8274) Creating an HttpSession with Ajax Request and then redirecting the response causes an HTTPSession to leak

by yagish sharma (JIRA)

Creating an HttpSession with Ajax Request and then redirecting the response causes an HTTPSession to leak --------------------------------------------------------------------------------------------------------- Key: RF-8274 URL: https://jira.jboss.org/jira/browse/RF-8274 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-a4j-core Affects Versions: 3.3.2.GA Environment: j2sdk1.5.0_06/1.6.0_14, Windows/Linux, JSF1.2, JBoss 5.1.0GA, Weblogic 9.2 Reporter: yagish sharma While running the load test on our environment, we found a HTTPSession object getting created in response to an AjaxRequest, but in the "redirected" response, the Set-Cookie - JSessionID was missing causing the server to leak an HttpSession. Further digging down the issue, we found the BaseXMLFilter.resetResponse method "resets" the original (server) response object, and then copies the cookies over from a response wrapper, thus missing to reset the JSessionID cookie into the response object. This issue is closely related to how the JSessionID is set in the response object by the AppServer. JBoss (Tomcat), on creation of an HTTPSession object, creates a JSessionID cookie and appends it directly to the response object's cookies arrayList (without calling the ServletResponse.addCookie() method). Similar behavior was found in load testing on Weblogic 9.2 app server as well. -- 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, 10 months

2
1
0 / 0

[JBoss JIRA] Resolved: (RF-8284) RESTful partial page submit with Ajax4JSF

by Jay Balunas (JIRA)

[ https://jira.jboss.org/jira/browse/RF-8284?page=com.atlassian.jira.plugin... ] Jay Balunas resolved RF-8284. ----------------------------- Resolution: Out of Date JSF 2, and JAX-RS handle some of this already, and we are not planning on changing anything list this. Support like this can come from core frameworks I think. Which is what happened :-) > RESTful partial page submit with Ajax4JSF > ----------------------------------------- > > Key: RF-8284 > URL: https://jira.jboss.org/jira/browse/RF-8284 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Gavin King > Assignee: Alexander Smirnov > Priority: Critical > > If Ajax4JSF could put page parameters after the # in the URL after a partial submit, then we could make the page bookmarkable. Requires changes to Ajax4JSF, possibly also to Seam. -- 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, 10 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 2010