July 2010 - richfaces-issues - Jboss List Archives

[JBoss JIRA] Created: (RF-6156) FileUpload: status indicator isn't stopped

by Nick Belaevski (JIRA)

FileUpload: status indicator isn't stopped ------------------------------------------ Key: RF-6156 URL: https://jira.jboss.org/jira/browse/RF-6156 Project: RichFaces Issue Type: Bug Affects Versions: 3.3.1 Reporter: Nick Belaevski Priority: Minor Fix For: Future -- 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

15 years, 3 months

3
4
0 / 0

[JBoss JIRA] Created: (RF-8984) No mime type could be found for file *.ecss

by Pavol Pitonak (JIRA)

No mime type could be found for file *.ecss ------------------------------------------- Key: RF-8984 URL: https://jira.jboss.org/browse/RF-8984 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component Affects Versions: 4.0.0.Milestone1 Environment: v.4.0.0-SNAPSHOT SVN r.18238, Mojarra 2.0.2 (FCS b10) Reporter: Pavol Pitonak 1. build and deploy showcase 2. open http://localhost:8080/richfaces-showcase/richfaces/component-sample.jsf?d... 3. the following appears in server log: WARNING: JSF1091: No mime type could be found for file skinning.ecss. To resolve this, add a mime-type mapping to the applications web.xml. WARNING: JSF1091: No mime type could be found for file list.ecss. To resolve this, add a mime-type mapping to the applications web.xml. WARNING: JSF1091: No mime type could be found for file rich/css/page.ecss. To resolve this, add a mime-type mapping to the applications web.xml. WARNING: JSF1091: No mime type could be found for file rich/css/panel.ecss. To resolve this, add a mime-type mapping to the applications web.xml. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

3
7
0 / 0

[JBoss JIRA] Created: (RF-8860) Design: Requirements gathering.

by Ilya Shaikovsky (JIRA)

Design: Requirements gathering. ------------------------------- Key: RF-8860 URL: https://jira.jboss.org/browse/RF-8860 Project: RichFaces Issue Type: Sub-task Security Level: Public (Everyone can see) Components: component-input Affects Versions: 4.0.0.Alpha2 Reporter: Ilya Shaikovsky Assignee: Pavel Yaschenko Fix For: 4.0.0.Milestone1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

3
3
0 / 0

[JBoss JIRA] Created: (RF-8785) design: components skinning

by Ilya Shaikovsky (JIRA)

design: components skinning --------------------------- Key: RF-8785 URL: https://jira.jboss.org/browse/RF-8785 Project: RichFaces Issue Type: Sub-task Security Level: Public (Everyone can see) Components: component-panels-layout-themes Affects Versions: 4.0.0.Alpha2 Reporter: Ilya Shaikovsky Assignee: Lex Dmitriev Fix For: 4.0.0.Milestone1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

3
5
0 / 0

[JBoss JIRA] Created: (RF-8135) FileUpload: transaction timeout happens for lon-running uploads

by Nick Belaevski (JIRA)

FileUpload: transaction timeout happens for lon-running uploads --------------------------------------------------------------- Key: RF-8135 URL: https://jira.jboss.org/jira/browse/RF-8135 Project: RichFaces Issue Type: Bug Components: component-input, performance, regression Affects Versions: 3.3.2.SR1 Reporter: Nick Belaevski Assignee: Nick Belaevski Priority: Critical Details are at forum thread, basically this happens: Nov-11 18:12:50,808 DEBUG [ajp-jbossdev5.namerica.idexxi.com%2F172.31.29.160-8309-9] [org.ajax4jsf.event.AjaxPhaseListener] Process after phase UPDATE_MODEL_VALUES 4 Nov-11 18:12:50,808 DEBUG [ajp-jbossdev5.namerica.idexxi.com%2F172.31.29.160-8309-9] [javax.enterprise.resource.webcontainer.jsf.timing] [TIMING] - [47ms] : Execution time for phase (including any PhaseListeners) -> UPDATE_MODEL_VALUES 4 Nov-11 18:12:50,808 DEBUG [ajp-jbossdev5.namerica.idexxi.com%2F172.31.29.160-8309-9] [org.ajax4jsf.event.AjaxPhaseListener] Process before phase INVOKE_APPLICATION 5 Nov-11 18:12:50,808 DEBUG [ajp-jbossdev5.namerica.idexxi.com%2F172.31.29.160-8309-9] [javax.enterprise.resource.webcontainer.jsf.lifecycle] Entering InvokeApplicationsPhase Nov-11 18:12:50,808 DEBUG [ajp-jbossdev5.namerica.idexxi.com%2F172.31.29.160-8309-9] [javax.enterprise.resource.webcontainer.jsf.lifecycle] Exiting InvokeApplicationsPhase Nov-11 18:12:50,808 DEBUG [ajp-jbossdev5.namerica.idexxi.com%2F172.31.29.160-8309-9] [org.ajax4jsf.event.AjaxPhaseListener] Process after phase INVOKE_APPLICATION 5 Nov-11 18:12:50,810 WARN [ajp-jbossdev5.namerica.idexxi.com%2F172.31.29.160-8309-9] [com.arjuna.ats.arjuna.logging.arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.BasicAction_40] - Abort called on already aborted atomic action -53e0e260:84df:4afb2c53:26cc Nov-11 18:12:50,810 WARN [ajp-jbossdev5.namerica.idexxi.com%2F172.31.29.160-8309-9] [org.jboss.seam.jsf.SeamPhaseListener] uncaught exception, passing to exception handler java.lang.IllegalStateException: Could not commit transaction at org.jboss.seam.jsf.SeamPhaseListener.commitOrRollback(SeamPhaseListener.java:626) at org.jboss.seam.jsf.SeamPhaseListener.commitOrRollback(SeamPhaseListener.java:605) at org.jboss.seam.jsf.SeamPhaseListener.handleTransactionsAfterPhase(SeamPhaseListener.java:343) at org.jboss.seam.jsf.SeamPhaseListener.afterServletPhase(SeamPhaseListener.java:243) at org.jboss.seam.jsf.SeamPhaseListener.afterPhase(SeamPhaseListener.java:194) at com.sun.faces.lifecycle.Phase.handleAfterPhase(Phase.java:175) at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:114) at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:265) -- 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

15 years, 4 months

4
11
0 / 0

[JBoss JIRA] Created: (RF-8136) Richfaces.Calendar.parseDate using pattern "yyMMdd" is incompatible with java.text.SimpleDateFormat

by Francisco Jose Peredo Noguez (JIRA)

Richfaces.Calendar.parseDate using pattern "yyMMdd" is incompatible with java.text.SimpleDateFormat --------------------------------------------------------------------------------------------------- Key: RF-8136 URL: https://jira.jboss.org/jira/browse/RF-8136 Project: RichFaces Issue Type: Bug Affects Versions: 3.3.1 Reporter: Francisco Jose Peredo Noguez I have a rich calendar configured with the pattern "yyMMdd" If the user writes 600210 and the user clicks the little calendar button to show the popup, he can see that the date has been translated to "February 10 of 2060" but if he writes 700210 it is translated in to "February 10 of 1970". That is not consistent the behavior of java.text.SimpleDateFormat. The problem is at the file 3.3.1.GA\ui\calendar\src\main\resources\org\richfaces\renderkit\html\scripts\calendar.js (line 394 of the file): At the function Richfaces.Calendar.parseDate = function(dateString, pattern, monthNames, monthNamesShort) method: var yy = parseInt(match[y],10); if (isNaN(yy)) return null; else if (yy<70) yy+=2000; else if (yy<100) yy+=1900; That code translates the year in 600210 to 2060 when it should translate it to 1960 (to be consistent with java.text.SimpleDateFormat behavior. -- 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

15 years, 4 months

4
6
0 / 0

[JBoss JIRA] Created: (RF-7547) FileUpload: add temp files location configuration parameter

by Nick Belaevski (JIRA)

FileUpload: add temp files location configuration parameter ----------------------------------------------------------- Key: RF-7547 URL: https://jira.jboss.org/jira/browse/RF-7547 Project: RichFaces Issue Type: Feature Request Components: component-input Reporter: Nick Belaevski -- 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

15 years, 4 months

3
4
0 / 0

[JBoss JIRA] Created: (RF-7490) TreeNode API doesn't allow for multiple types of nodes

by Nick Belaevski (JIRA)

TreeNode API doesn't allow for multiple types of nodes ------------------------------------------------------ Key: RF-7490 URL: https://jira.jboss.org/jira/browse/RF-7490 Project: RichFaces Issue Type: Bug Components: component-tree Reporter: Nick Belaevski Assignee: Nick Belaevski Priority: Minor Fix For: 4.0.0.BETA1 -- 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

15 years, 4 months

2
5
0 / 0

[JBoss JIRA] Created: (RF-7979) FileUpload: Can't use addFileUploadListener to register listener while creating component with java code

by Ilya Shaikovsky (JIRA)

FileUpload: Can't use addFileUploadListener to register listener while creating component with java code -------------------------------------------------------------------------------------------------------- Key: RF-7979 URL: https://jira.jboss.org/jira/browse/RF-7979 Project: RichFaces Issue Type: Bug Components: component-input Affects Versions: 3.3.2.GA, 3.3.2.SP1 Reporter: Ilya Shaikovsky Assignee: Nick Belaevski Fix For: Future Attachments: FU_UploadEvent.patch description at forum. verified at fileUploadDemo. Investigated and patch attached. -- 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

15 years, 4 months

2
4
0 / 0

[JBoss JIRA] Created: (RF-5297) FileUpload: required should works with form submission(using submitForm and beforeSubmit)

by Ilya Shaikovsky (JIRA)

FileUpload: required should works with form submission(using submitForm and beforeSubmit) ----------------------------------------------------------------------------------------- Key: RF-5297 URL: https://jira.jboss.org/jira/browse/RF-5297 Project: RichFaces Issue Type: Bug Affects Versions: 3.3.0 Reporter: Ilya Shaikovsky -- 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

15 years, 4 months

4
11
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues July 2010