it has nothing to do with the jBPM console. The jBPM console is just a front-end to jBPM.
Your bean classes should be somewhere on the classpath where Drools can 'see' them. If you read a little about jBPM, you could know that jBPM 3 deploys processdefinitions to the database (process repository) and that jBPM can read 'versioned actionhandlers' from that repository as well. Other libraries otoh can't. So depending on other configurations of your war/ear/... you can e.g. deploy them in the war, in a jar that is in an ear or whatever... Of-course also depending on how you packaged drools View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4254325#4254325 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4254325 _______________________________________________ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
