[Design of JBoss jBPM] - Re: Register EventListener on JbppmContext
by camunda
@Thomas: I also the events I want to listen for are more inside of the engine (so implementation detail ;-)). But the Listeners you propose also make sense, even if I don't understand the API at this part yet...
@Tom: I expected you to say that ;-) And I agree with you, but for me the situation is not putting effort in jbpm 3 or 4, but to solve the problem in the customer project either by some workarounds around jbpm (in "our" code) or to implement it correctly in the jbpm 3 core. Effort could be maybe the same. So I think it makes more sense to contribute it to jbpm and maybe even gather experiences for jbpm 4. And even jbpm 3 will be around for quite a while I think...
So if you don't vote explicitly against it I would maybe contribute it if it comes to that point in the current project (concept isn't yet fixed), ok?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4190987#4190987
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4190987
16 years, 3 months
[Design of JBoss jBPM] - Re: Register EventListener on JbppmContext
by tom.baeyens@jboss.com
"camunda" wrote : Hi.
|
| Yesterday I was at customer and they did an extension to jbpm where they added the possibility to add EventListener to the JbpmContext (configured via jbpm.cfg.xml).
|
| Today I face a similar problem, it would be interesting to get notified if each event fired inside the engine (basically to catch them and maybe throw the aggregated to some BAM engine).
|
| What do you guys think, include such a feature in jbpm core? I think it is an interesting one without bit complexity. Also the guys from yesterday could provide some code for it (Tom, I heard there is a pending committer status request from them), so maybe it wouldn't be that hard...
|
| Opinions?
|
| Cheers
| Bernd
all our jbpm 3 efforts are now focussed on increasing the stability and test coverage (mainly dbs).
this feature should be discussed in terms of jbpm4. in that context, it might be an option to leverage the environment for that. after a event propagated all the way up to the environment, it could be propagated further on the environment contexts. good idea, but needs some more reflection. performance might become an issue so it should be possible somehow to configure which events are propagated to the environment like that.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4190971#4190971
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4190971
16 years, 3 months
limited connectivity tomorrow
by Tom Baeyens
Tomorrow, me and Koen will be travelling on the train to talk to the JWT people. So
we will not be a lot on-line, if at all.
--
regards, tom.
16 years, 3 months