afaik, the due date is calculated the moment the timer is created. So the behaviour you see is the 'correct' behaviour. Well, at least as implemented (on purpose or as a result of adding 'suspend/resume' later) without thinking about this issue.
So the duedate is not something that does a countdown, not a 'delta' or whatever. If you want the behaviour you describe, that is an enhancement.
I actually just wanted to start some discussion and get jBPM-familiar people talking about it, hopefully spurring off some good design talk :)
It's already something we know we're going to have to code up ourselves, as we need it.
At the least, I'll probably create a JIRA Feature Request, and add any notes/code/etc if we build it ourselves.
cpob, I tried to PM and email you without luck. Did you ever find a way to get this to work? Being able to do this is critical to meet our business requirements and we're stumped and could use a pointer.