jbpm4.1 task duedate does not persist

[rujimethut]

I have duedate attribute set in a task like this:








When process arrive Step1, task was created notification and reminder fired correctly but I check the table JBPM4_TASK the DUEDATE_ is null,


Is this normal behavior? Is there any way I can get the task duedate through the api ?


Thanks

[rujimethut]

sorry this is the xml:

 <task name="Step1" duedate="3 minutes" >
 <notification/>
 <reminder duedate="3 minutes"/>
 <transition name="deny" to="end"/>
 <transition ame="approve" to="Step2"/>
 </task>

[rujimethut]

I was working around and solve this problem by

1. get the task

2. query its reminder's Job

3. get remider's duedate


Thanks for looking.

[kukeltje]

But the reminder duedate can be something totally different than the task duedate. If you can make a unittest where you can demonstrate the duedate not being persisted, please make one and file a jira issue for it.

[bixby]

I'd like to contribute some code to fix this. Is there a guide or doc somewhere about submission of code for the project?

I guess first thing is to file a JIRA issue.

To clarify the problem, the task definition's due date is not persisted and obviously therefore not referenced when the task activity is created so no due date can (currently) be set on a task based on the definition.

[sebastian.s]

The first thing would indeed be to file a JIRA issue but only if you can supply a unit test or example code to demonstrate the problem. For information about how to contribute read the sticked post in the developper forum:

http://www.jboss.org/index.html?module=bb&op=viewforum&f=219

[bixby]

created https://jira.jboss.org/jira/browse/JBPM-2560 and supplied test case and patches