I maintain a library of jBPM processes (about 30 or so at this point in time), and I'm having a a tough time finding a list of best practices to help reduce my maintenance overhead and improve the (unit) testability of my code and processes. Do you discuss anything along those lines in Chapter 15 of Seam In Action? Could you mention a few suggestions for jBPM best practices here?
Would you have any suggestions on how to inject Spring beans into jBPM Action Handlers and Decision Handlers? I was thinking I could use AOP and inject beans from a given XML file (e.g. beanconfig.xml) that sits next to each processdefinition.xml and would be picked up by the AOP before advice code, and the beans listed in the XML file could be configured via Spring Annotations to minimize the need for file reading from the database. This is a question I believe I'm seeing often enough in Google searches, and definitely welcome any suggestions you might have.
Thanks so much,
[ August 05, 2008: Message edited by: Jim Bethancourt ]