[tejjbpm]

Thanks Swati for all your contribution..

Thanks Ronald for your reply. The flip side of changing the jbpm code is you cant upgrade to the latest version whenever you want..If we can fix it in our code(if only it is possible) we always have the flexibility to upgrade...i hope you agree with me..

[kukeltje]

Sigh... That is why I said make a unit test and remember my first reply in this topic:

What I would do is 'fix' it in the task-assign handler in jBPM where you e.g. try to find a template with that name -assign and use that if it does exist. If it does not, use the normal template. This way you get per task templates without changes to the jPDL or database. If you 'fix' it this way and include a testcase, I might try to get it incorporated in jBPM.

Then you will not have the problem you describe...... not at all, never again.... Your processdefinitions stay cleaner etc...etc...etc... it is not that hard to contribute in return for getting lots of my free time ;-)

[tejjbpm]

that is very true Ronald..Cant imagine this forum live without your contributions..no doubt..:)..thanks again..

[kukeltje]

So? that means you are going to fix it IN jBPM and contribute that? ;-)

[tejjbpm]

why not..definitely..that is exactly what i meant..

[kukeltje]

Cool... then I make sure it gets into the source