Seam uses a number of different variable resolvers. I thought there already was a jBPM resolver. Could be though that it only works in the scope of a task. If you are on a task list, you are not in the scope of an individual task.
- I would not display all taskvariables on that task list. Will become very slow (to many queries to the db)
- put as little variables as possible in the task or even the process. Put as many as possible in your domain model
- just show someprocess-level info in the tasklist e.g. the businesskey (key on the processlevel
In this case you do not need the resolver you are talking about
thanks for your quick reply.
If I understand correctly your suggestion: an idea could be to remove variables from the Process and persist them in a table. Then back the table with an Entity Bean which could be easily referenced by Seam resolvers.
So I would use the Process Id to reference data in a table and keep the process light.
Your suggestions are always valuable, thanks !