preferred debugging method?

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

qzy

Hi there,


is there a best practice on debugging applications which make use of activiti? For example what's the easiest way to make distinction between problems in the workflow and possible problems in the beans' implementation appearing in the flow?
Is there some easy way to trace/debug the workflow?



TIA,
Balint

jbarrez

First of all, you have traditional logging, just put the log level low enough and you'll see Activiti spit out MB's of debug information.

Secondly, since Activiti is just a jar, you can debug as you are used to: for example on Tomcat, enable the remote debugging port and attach an Eclipse listener.
Debugging Activiti processes is with other words exactly the same as debugging Java code.