[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
13 years, 12 months
[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
13 years, 12 months
[JBoss JIRA] Created: (RF-5177) fileUpload: validator attribute doesn't work.
by Mikhail Vitenkov (JIRA)
fileUpload: validator attribute doesn't work.
---------------------------------------------
Key: RF-5177
URL: https://jira.jboss.org/jira/browse/RF-5177
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.3.0
Environment: IE6, IE7, FF 3.1.3, Safari 3.1, Opera 9.62(3.3.0.BETA1)
Reporter: Mikhail Vitenkov
Assignee: Nick Belaevski
#1. Create class that implements Validator class.
#2. Override validate method, like this:
public void validate(FacesContext context, UIComponent component,
Object value) throws ValidatorException {
File f = (File)value;
if(f.getName().toString().contains("emo")){
throw new ValidatorException(new FacesMessage("Test validator: no 'emo' should present in file name!"));
}
}
#3. Pass method from previous step to "validator" component's attribute: validator="#{fileUpload.validate}".
#4. Navigate to page.
#5. Add & upload any file with 'emo' substring.
Actual behavior:
validate method wasn't called.
--
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