I noticed this same issue when I was working with Seam and jBPM several months ago. The
way tasks are implemented at a start node, they are not created automatically, but must be
explicitly created. Seam did not know this, so it would not create startTaskInstances. The
web console always did it, assuming that there were always startTasks. Which is true for
the web sale process but not true in general.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3997659#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...