Short addition: The JbpmCallback doesn't work in the same way the other stuff does (BpmProcessor with command), this is also not consistent.
Sorry, but the To EPR is the correct one. It is the incoming information which was originally specified in the ReplyTo of the outgoing request. It is not a bug in JBpmCallback.
It's purpose is very different from BpmProcessor.
Can you point me to the right docs/sample or whatever to get the idea of the JbpmCallback? Thanks...
Okay, I walked through a lot more documentation, code and examples and got the idea now... Sorry for bothering you in the first place! And next time I will RTFM and use the user forum first... Hopefully I didn't gambled away credits!
But the second point is still an issue to me, better understandable code would be cool. Or should that be postponed for the integration of jBPM 4?
Just would be interested what you think about it...
You haven't gambled away any credits :)
As for BpmProcessor, I tend to agree with your observations. This was from the original integration of jBPM but had some serious issues. The integration was, therefore, redone (and simplified) but some of the original code is still present.
Tidying it up is certainly something that we need to do but we have had higher priority issues to deal with.
We will certainly be redoing this for ESB 5, regardless of which version of jBPM is included.