Currently the default strategy is Singleton and that's why automatic deployment (during build and deploy) will use that strategy. If that is not what you would like to use you would need to undeply it and then deploy it again with selected strategy using Deployments -> New Deployment Unit.
There is already an enhancement registered to provide sort of deployment descriptor on kjar level allow fine grained configuration of how it should be deployed. That is scheduled for 6.1 though.
Hi, I'm using 6.1.0 RC, but I see no way to change the runtime strategy.
Also, If I do what you suggest, it does not works:
"Deployment of unit com.example:DummyProcess:1.0 failed: Cannot find kbase, either it does not exist or there are multiple default kbases in kmodule.xml"
doing Deployments -> New Deployment is not working in jBpm 6.1.Final