The jbpm webconsole of version 3.2 has never been tested with 3.1.x in any way. There has never been any guarantee that it would/should work. So if that is your issue, unfortunately you are on your own. All the errors you get have most likely never been seen by others, and the jBPM core team has currently no intentions to try to backport the webconsole.
Deploying the webconsole on a different jboss instance is no different from deploying the full jbpm engine since the console needs the core.
The actionhandlers do not need to be deployed in each process, they can be deployed separately but if you do it on a packaging level there is not much overhead, at least for us there isn't.
If I were you, I'd focus on/pushing for seam to be compatible with jbpm 3.2
You are not asking to much of jbpm/seam, but what you are trying to do is put a ferrari engine on a lamborgini chassis and use a porsche bodywork.
thanks, I've solved most of the issues, but one that's not connected to jbpm, but the UCL :(
I'm seeking help/guidance on the AS forum, even call-by-value is not helping me so far.
BTW: Would you know why the MBean was discontinued on 3.2? I've created my own and we intend to use that way (one single remote jbpmConfiguration). I'm adding few methods like un-deploy process, list the number of process, number of instances per process, some metrics we need for a very few/raw/simple KPIs.