topic Re: jar deployment for human tasks in Alfresco Archive

jar deployment for human tasks

shizanu — Mon, 04 Mar 2013 10:14:08 GMT

Hello,I am using the camunda fox community edition, which is activiti readily deployed on a jboss AS7.1When trying to use expressions in human tasks I get the following problem:The human task form generator in the activiti explorer doesn´t find my java classes deployed to the web-inf/lib directory,

Re: jar deployment for human tasks

frederikherema1 — Mon, 04 Mar 2013 15:23:35 GMT

The best practice is to place your custom classes right next to the activiti-classes (activiti-engine.jar) so they're loaded with the same class loader. I'm not aware of how the fox-platform handles class-deployment and resolving, so I'm not much of a help for that matter…

Re: jar deployment for human tasks

shizanu — Thu, 07 Mar 2013 10:14:10 GMT

I am doing that (with fox-engine.jar). It works perfectly fine for service task delegates and on process level.

However the human task form generator of the activiti explorer seems to be getting his classes from a different place.

I am faced with the same problem while creating custom task forms via cdi now. I could write code to bind a object from my web application to a process variable. However I wont be able to use it in the process, because the process doesn´t have access to the class definition, which is in the lib folder of my web application.

I would very much like to do that though, because it would enable me to use a consistent object based datamodel in my processes, that would be far easier to maintain then a huge number of process variables, that are never defined in a central place.
Some kind of mapping between task form variables and process variables would do the job too (though being rather inconvenient), however task forms seem to always access process variables directly. While this has a lot of advantages, it really hurts the ability to easily exchange one delegate for another without having to know everything about the process. Also it forces me to bind all my input paramters in forms directly to process variables, because of above problem. Exactly this last thing is what I want to get away from somehow.