4 Replies Latest reply on Dec 14, 2005 4:31 PM by Eduardo Jimenez

    Issue JBPM-462

    Eduardo Jimenez Newbie

      Hey guys,

      Respectfully, I think issue 462 (hence 468) can be fixed in jBPM 3.0.x. jBPM 3.1.x seems to be a pretty major upgrade, not everyone might be ready to upgrade immediately, including us as would have completed almost all work on our project when 3.1 is released for production use. Also we probably won't use many of its features as we've implemented them in our own ways and 3.1 would not replace those implementations.

      The aforementioned bugs are trivial to fix in 3.0.2 (for release in 3.0.3) without any need of schema changes. In fact, I'm not sure schema changes solve the problem at all, as a schema change would mean that tokens would have a subprocess LIST. This is not exactly the bug. The bug is that there is no way for the subprocess-end event to know which subprocess ended.

      The schema change fix would solve the problem of SAVING subprocess instances, but not the subprocess-end event issue.

      The no-schema-change fix can be found in the issue comments:


      Please comment on this. I would really like to use an unchanged jBPM in our environment to make minor version upgrades easy.

      If you guys disagree, that's fine..we'll just have to maintain a list of things we have fixed to backport them to 3.0.3 and so on until we go to 3.1 (again, if that even happens)