What advide do you need. Everything you mention is possible with jBPM. The only thing is that in 3 the employee realy completes a task and the supervisor has to have another task (4) to 'complete' it. Nothing special here.
I am sorry. I forgot to write my question. Does jBPM add any considerable advantage for my project as its kind of simple?
If the 'jobs' are simple, jBPM probably does not offer a considerable amount of advantage. Probably JSF with a simple pageflow and a db is enough. This doesnt mean you *can* do it with jBPM :-)
I do see advantages even for simple processes. In the first place, you can easily adapt your software to eventual changes in the process. Second, and perhaps even more important, you get activity logs, which lets you do things like check which jobs are outstanding, evaluate performance and identify bottlenecks. Finally,
jBPM is lightweight enough to fit even this size of project.
If the logs are of no use to you, I'd adhere to Ronald's opinion.
You are right Alex, I forgot the logs, but that is probably because we (internally at the company I work for) are used to having components that do log, so we get that automagically.
The other 'advantages' you mention are eventually also true. There could be a slight disadvantage also. If you do not defined e.g. the process in your war file and deploy it in one go with the webapp) it could introduce an extra deployment difficulty. You have to deploy the war as well as the process. It would be nice if we could create an example of an all in one war (code + process) as an example