good catch! do you mind creating jira for it and if you would be so kind pull request with updated content?
I have done as you requested. I had trouble with a puzzling issue where your new producer would not be recognized by WELD, can you please review the JIRA? (https://issues.jboss.org/browse/JBPM-4235) I had to apply a patch locally to overcome this issue and hence I have submitted a code pull request as well as a documentation pull request.
The version of weld in the JBPM BOM is 1.1.3, but JBoss 7.1.1 comes with 1.1.5. I don't think so, but that also might be a factor.
just quickly looked at the pull request and I see you added @Selectable in the for the producer methods which actually should not be there as only the producer itself is marked as @Selectable due to the way weld/cdi sees alternatives - it will scope the alternatives to given bean archive only and thus this workaround to allow injecting the one defined in beans.xml and provide additional producer method within the upper bean archive (like war) to provide the actual impls. See here for example.
When it comes to version of weld it is 1.1.13 which is aligned with version used by EAP 6.1.1. Might be worth switching to EAP instead of JBoss 7.1.1 as it has much more fixes that users of JBoss 7.1.1 are suffering. EAP is now available on community downloads as well.
Yes, as I mentioned in the JIRA I raised, I was forced to push the @Selectable down to the method, as I was getting WELD unresolved errors unless I did so. Via the debugger I confirmed the alternative was loaded in into the WELD bean manager, but the producer methods were not considered as matching until I marked them individually as @Selectable.
do you use the UserGroupCallback in your code? As all the parts in jBPM do not use @Selectable for injection of the actual UserGroupCallback instance any more. Make sure you use default qualifier (meaning no qualifiers) on the UserGroupCallback and that should work.