March 2008 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Resolved: (JBPM-1059) Minor patch to avoid possible integer overflow in DayPart.add() in case of crazy Calendar values

by Alejandro Guizar (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-1059?page=all ] Alejandro Guizar resolved JBPM-1059. ------------------------------------ Resolution: Done Resolving, as the enclosing issue has been resolved as well. > Minor patch to avoid possible integer overflow in DayPart.add() in case of crazy Calendar values > ------------------------------------------------------------------------------------------------ > > Key: JBPM-1059 > URL: http://jira.jboss.com/jira/browse/JBPM-1059 > Project: JBoss jBPM > Issue Type: Patch > Affects Versions: jBPM 3.1.4, jBPM jPDL 3.2.2 > Reporter: Johan Parent > Assigned To: Alejandro Guizar > Fix For: jBPM 3.1.5, jBPM jPDL 3.2.3, jBPM 3.2.2 SOA 1 > > > In > public Date add(Date date, Duration duration) { > Date end = null; > > Calendar calendar = BusinessCalendar.getCalendar(); > calendar.setTime(date); > int hour = calendar.get(Calendar.HOUR_OF_DAY); > int minute = calendar.get(Calendar.MINUTE); > long dateMilliseconds = ((hour*60)+minute)*60*1000; > long dayPartEndMilleseconds = ((toHour*60)+toMinute)*60*1000; > change last two lines into: > long dateMilliseconds = ((hour*60L)+minute)*60*1000; > long dayPartEndMilleseconds = ((toHour*60L)+toMinute)*60*1000; -- 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

16 years, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBPM-1059) Minor patch to avoid possible integer overflow in DayPart.add() in case of crazy Calendar values

by Alejandro Guizar (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-1059?page=all ] Alejandro Guizar updated JBPM-1059: ----------------------------------- Fix Version/s: jBPM 3.2.2 SOA 1 > Minor patch to avoid possible integer overflow in DayPart.add() in case of crazy Calendar values > ------------------------------------------------------------------------------------------------ > > Key: JBPM-1059 > URL: http://jira.jboss.com/jira/browse/JBPM-1059 > Project: JBoss jBPM > Issue Type: Patch > Affects Versions: jBPM 3.1.4, jBPM jPDL 3.2.2 > Reporter: Johan Parent > Assigned To: Alejandro Guizar > Fix For: jBPM 3.1.5, jBPM jPDL 3.2.3, jBPM 3.2.2 SOA 1 > > > In > public Date add(Date date, Duration duration) { > Date end = null; > > Calendar calendar = BusinessCalendar.getCalendar(); > calendar.setTime(date); > int hour = calendar.get(Calendar.HOUR_OF_DAY); > int minute = calendar.get(Calendar.MINUTE); > long dateMilliseconds = ((hour*60)+minute)*60*1000; > long dayPartEndMilleseconds = ((toHour*60)+toMinute)*60*1000; > change last two lines into: > long dateMilliseconds = ((hour*60L)+minute)*60*1000; > long dayPartEndMilleseconds = ((toHour*60L)+toMinute)*60*1000; -- 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

16 years, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBPM-1059) Minor patch to avoid possible integer overflow in DayPart.add() in case of crazy Calendar values

by Alejandro Guizar (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-1059?page=all ] Alejandro Guizar updated JBPM-1059: ----------------------------------- Fix Version/s: jBPM 3.1.5 jBPM jPDL 3.2.3 (was: jBPM 3.1.4) Affects Version/s: jBPM jPDL 3.2.2 Assignee: Alejandro Guizar (was: Tom Baeyens) This fix will be incorporated in the resolution of JBPM-1098. > Minor patch to avoid possible integer overflow in DayPart.add() in case of crazy Calendar values > ------------------------------------------------------------------------------------------------ > > Key: JBPM-1059 > URL: http://jira.jboss.com/jira/browse/JBPM-1059 > Project: JBoss jBPM > Issue Type: Patch > Affects Versions: jBPM 3.1.4, jBPM jPDL 3.2.2 > Reporter: Johan Parent > Assigned To: Alejandro Guizar > Fix For: jBPM 3.1.5, jBPM jPDL 3.2.3 > > > In > public Date add(Date date, Duration duration) { > Date end = null; > > Calendar calendar = BusinessCalendar.getCalendar(); > calendar.setTime(date); > int hour = calendar.get(Calendar.HOUR_OF_DAY); > int minute = calendar.get(Calendar.MINUTE); > long dateMilliseconds = ((hour*60)+minute)*60*1000; > long dayPartEndMilleseconds = ((toHour*60)+toMinute)*60*1000; > change last two lines into: > long dateMilliseconds = ((hour*60L)+minute)*60*1000; > long dayPartEndMilleseconds = ((toHour*60L)+toMinute)*60*1000; -- 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

16 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPM-1144) Calculate dates fpr timers

by thilker (JIRA)

Calculate dates fpr timers -------------------------- Key: JBPM-1144 URL: http://jira.jboss.com/jira/browse/JBPM-1144 Project: JBoss jBPM Issue Type: Feature Request Components: Core Engine Affects Versions: jBPM jPDL 3.2.2 Reporter: thilker Assigned To: Tom Baeyens I was facing the problem, that I'm not able to schedule calculated dates in a workflow. So I modified the class I send you a little bit. Now I've two new possibilties. 1. I'm able to enter a absolute date in the workflow. (yyyy.MM.dd HH:mm:ss) Ok, that's poor, I must confess. :) 2. But here is the power feature: I'm calculating a certain date. And store it in the Workflowcontext. An example: ================================================================ public class InitProjektBeginnTimerHandler implements ActionHandler { /** * App Logger */ public final static Logger logger = Logger.getLogger(InitProjektBeginnTimerHandler.class); public void execute(ExecutionContext executionContext) throws Exception { Projekt projekt = (Projekt) executionContext.getContextInstance() .getVariable(WorkflowDAO.doKey); int offset = projekt.getTraeger().getMandant().getEinstellungen().getOffsetMonatsbericht(); Calendar dateForNextReport = new GregorianCalendar(); dateForNextReport.setTime(projekt.getBeginn()); dateForNextReport.set(Calendar.DAY_OF_MONTH, 1); dateForNextReport.add(Calendar.MONTH, 1); dateForNextReport.set(Calendar.DAY_OF_MONTH, offset); executionContext.setVariable(MbEnum.Variable.DateForNextReport.name(), dateForNextReport.getTime()); logger.info("Leaving node."); executionContext.leaveNode(); } } =========================================================================== With my modifications in the class CreateTimerAction I'm able to assign the variable to a timer by its name. I choose the following pattern (variable name: "DateForNextReport") : #{DateForNextReport} I think this is a very powerful feature and will be appreciated by many other users. What do you think? Regards, Thorsten -- 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

16 years, 2 months

2
8
0 / 0

[JBoss JIRA] Resolved: (JBPM-1022) 3.2.1 Admin Console: Any user sees all users tasks

by Ronald van Kuijk (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-1022?page=all ] Ronald van Kuijk resolved JBPM-1022. ------------------------------------ Resolution: Done Some changes checked in. It was more work since there also should be a 'managers' tasklist. Duplicated tasks.xhtml to tasks_all.xhtml and changed the former. The template (t_task.xhtml) still has to be changed so the personal tasklist does not have (all) the filter options > 3.2.1 Admin Console: Any user sees all users tasks > --------------------------------------------------- > > Key: JBPM-1022 > URL: http://jira.jboss.com/jira/browse/JBPM-1022 > Project: JBoss jBPM > Issue Type: Bug > Components: Web Interface > Affects Versions: jBPM jPDL 3.2.1, jBPM jPDL 3.2.2 > Reporter: Burr Sutter > Assigned To: Ronald van Kuijk > Priority: Blocker > Fix For: jBPM jPDL 3.2.3 > > Original Estimate: 2 days > Remaining Estimate: 2 days > > In the current Admin Console, any given user will see all other users tasks. Plus a user can "take" another person's assigned tasks even when they are not an "administrator". -- 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

16 years, 2 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBPM-1022) 3.2.1 Admin Console: Any user sees all users tasks

by David Ling (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-1022?page=comments#action_12401062 ] David Ling commented on JBPM-1022: ---------------------------------- Hi all, I tried the solution that Sebastien suggested by changing the listTasks to request.remoteUser, but it doesn't seem to work for me. Is that the only change I need to make? Just to be sure, we are talking about the tasks.xhtml in jbpm-console.war\sa of C:\jbpm-jpdl-3.2.2\server\server\jbpm\deploy\ right? Any help would be much appreciated. Also, can I ask if 3.2.3 is coming soon? Thanks David > 3.2.1 Admin Console: Any user sees all users tasks > --------------------------------------------------- > > Key: JBPM-1022 > URL: http://jira.jboss.com/jira/browse/JBPM-1022 > Project: JBoss jBPM > Issue Type: Bug > Components: Web Interface > Affects Versions: jBPM jPDL 3.2.1, jBPM jPDL 3.2.2 > Reporter: Burr Sutter > Assigned To: Ronald van Kuijk > Priority: Blocker > Fix For: jBPM jPDL 3.2.3 > > Original Estimate: 2 days > Remaining Estimate: 2 days > > In the current Admin Console, any given user will see all other users tasks. Plus a user can "take" another person's assigned tasks even when they are not an "administrator". -- 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

16 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues March 2008