[JBoss JIRA] Created: (JBPM-2958) Timer should refer to the business calendar used at the time of creation
11:31 p.m.
Timer should refer to the business calendar used at the time of creation
------------------------------------------------------------------------
Key: JBPM-2958
URL: https://jira.jboss.org/browse/JBPM-2958
Project: jBPM
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 3.2.9
Reporter: Toshiya Kobayashi
Assignee: Alejandro Guizar
Fix For: jBPM 3.2.10
Assuming you want to use different business calendars by loading different jbpm.cfg.xmls;
When you use a Timer, a scheduler service thread will set repeatDate to the timer using
BusinessCalendar which is associated with given jbpmContext. The jbpmContext comes from
default jbpm.cfg.xml (jbpm.esb/jbpm.cfg.xml). Also the BusinessCalendar field is static.
So you cannot switch business calendars for each Timer in the scheduler service thread.
The timer should be able to acquire the business calendar which was used at the time of
Timer creation.
--
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
3:21 a.m.
New subject: [JBoss JIRA] Resolved: (JBPM-2958) Timer should refer to the business calendar used at the time of creation
[
https://jira.jboss.org/browse/JBPM-2958?page=com.atlassian.jira.plugin.sy...
]
Alejandro Guizar resolved JBPM-2958.
------------------------------------
Resolution: Done
Timer should refer to the business calendar used at the time of
creation
------------------------------------------------------------------------
Key: JBPM-2958
URL: https://jira.jboss.org/browse/JBPM-2958
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 3.2.9
Reporter: Toshiya Kobayashi
Assignee: Alejandro Guizar
Fix For: jBPM 3.2.10
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
Assuming you want to use different business calendars by loading different
jbpm.cfg.xmls;
When you use a Timer, a scheduler service thread will set repeatDate to the timer using
BusinessCalendar which is associated with given jbpmContext. The jbpmContext comes from
default jbpm.cfg.xml (jbpm.esb/jbpm.cfg.xml). Also the BusinessCalendar field is static.
So you cannot switch business calendars for each Timer in the scheduler service thread.
The timer should be able to acquire the business calendar which was used at the time of
Timer creation.
--
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
3:21 a.m.
New subject: [JBoss JIRA] Commented: (JBPM-2958) Timer should refer to the business calendar used at the time of creation
[
https://jira.jboss.org/browse/JBPM-2958?page=com.atlassian.jira.plugin.sy...
]
Alejandro Guizar commented on JBPM-2958:
----------------------------------------
The business calendar resource used to create each timer is now saved in the database.
To facilitate acceptance testing, I have deployed a binary artifact containing this update
to the JBoss snapshots repository. Be sure to pick the snapshot dated Oct 17, 2010.
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbp...
The Hibernate configuration file needs to be modified as well. Replace
"Timer.hbm.xml" with "Timer.calendar.hbm.xml". Apart from that, add a
varchar column named "CALENDARRESOURCE_" to the JBPM_JOB table. The new column
stores the business calendar resource used to create the timer.
TimerCalendarTest is an example of this update. It provides two jBPM configurations, one
of them points to a custom business calendar where Saturday is a work day. The test starts
a process instance under the Saturday configuration, which creates a timer that references
the Saturday calendar. The timer is executed in the normal configuration. The test asserts
that the timer repeat date is a Saturday.
JUnit test case:
http://anonsvn.jboss.org/repos/jbpm/jbpm3/branches/jbpm-3.2-soa/core/src/...
Process and configuration files:
http://anonsvn.jboss.org/repos/jbpm/jbpm3/branches/jbpm-3.2-soa/core/src/...
Timer should refer to the business calendar used at the time of
creation
------------------------------------------------------------------------
Key: JBPM-2958
URL: https://jira.jboss.org/browse/JBPM-2958
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 3.2.9
Reporter: Toshiya Kobayashi
Assignee: Alejandro Guizar
Fix For: jBPM 3.2.10
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
Assuming you want to use different business calendars by loading different
jbpm.cfg.xmls;
When you use a Timer, a scheduler service thread will set repeatDate to the timer using
BusinessCalendar which is associated with given jbpmContext. The jbpmContext comes from
default jbpm.cfg.xml (jbpm.esb/jbpm.cfg.xml). Also the BusinessCalendar field is static.
So you cannot switch business calendars for each Timer in the scheduler service thread.
The timer should be able to acquire the business calendar which was used at the time of
Timer creation.
--
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
3:21 a.m.
New subject: [JBoss JIRA] Updated: (JBPM-2958) Timer should refer to the business calendar used at the time of creation
[
https://jira.jboss.org/browse/JBPM-2958?page=com.atlassian.jira.plugin.sy...
]
Alejandro Guizar updated JBPM-2958:
-----------------------------------
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
Timer should refer to the business calendar used at the time of
creation
------------------------------------------------------------------------
Key: JBPM-2958
URL: https://jira.jboss.org/browse/JBPM-2958
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 3.2.9
Reporter: Toshiya Kobayashi
Assignee: Alejandro Guizar
Fix For: jBPM 3.2.10
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
Assuming you want to use different business calendars by loading different
jbpm.cfg.xmls;
When you use a Timer, a scheduler service thread will set repeatDate to the timer using
BusinessCalendar which is associated with given jbpmContext. The jbpmContext comes from
default jbpm.cfg.xml (jbpm.esb/jbpm.cfg.xml). Also the BusinessCalendar field is static.
So you cannot switch business calendars for each Timer in the scheduler service thread.
The timer should be able to acquire the business calendar which was used at the time of
Timer creation.
--
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
11:28 p.m.
New subject: [JBoss JIRA] Reopened: (JBPM-2958) Timer should refer to the business calendar used at the time of creation
[
https://issues.jboss.org/browse/JBPM-2958?page=com.atlassian.jira.plugin....
]
David Le Sage reopened JBPM-2958:
---------------------------------
Temporarily reopening to update release note info.
Timer should refer to the business calendar used at the time of
creation
------------------------------------------------------------------------
Key: JBPM-2958
URL: https://issues.jboss.org/browse/JBPM-2958
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 3.2.9
Reporter: Toshiya Kobayashi
Assignee: Alejandro Guizar
Fix For: jBPM 3.2.10
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
Assuming you want to use different business calendars by loading different
jbpm.cfg.xmls;
When you use a Timer, a scheduler service thread will set repeatDate to the timer using
BusinessCalendar which is associated with given jbpmContext. The jbpmContext comes from
default jbpm.cfg.xml (jbpm.esb/jbpm.cfg.xml). Also the BusinessCalendar field is static.
So you cannot switch business calendars for each Timer in the scheduler service thread.
The timer should be able to acquire the business calendar which was used at the time of
Timer creation.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:58 p.m.
New subject: [JBoss JIRA] Resolved: (JBPM-2958) Timer should refer to the business calendar used at the time of creation
[
https://issues.jboss.org/browse/JBPM-2958?page=com.atlassian.jira.plugin....
]
Alejandro Guizar resolved JBPM-2958.
------------------------------------
Resolution: Done
Resolving in order to mark v3.2.10 as released.
Timer should refer to the business calendar used at the time of
creation
------------------------------------------------------------------------
Key: JBPM-2958
URL: https://issues.jboss.org/browse/JBPM-2958
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 3.2.9
Reporter: Toshiya Kobayashi
Assignee: Alejandro Guizar
Fix For: jBPM 3.2.10
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
Assuming you want to use different business calendars by loading different
jbpm.cfg.xmls;
When you use a Timer, a scheduler service thread will set repeatDate to the timer using
BusinessCalendar which is associated with given jbpmContext. The jbpmContext comes from
default jbpm.cfg.xml (jbpm.esb/jbpm.cfg.xml). Also the BusinessCalendar field is static.
So you cannot switch business calendars for each Timer in the scheduler service thread.
The timer should be able to acquire the business calendar which was used at the time of
Timer creation.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
5042
days inactive
5187
days old
5 comments
3 participants
participants (3)
-
Alejandro Guizar (JIRA) -
David Le Sage (JIRA)
-
Toshiya Kobayashi (JIRA)