My Plan: JBPM 2 Wiki Bridge

[gf_public]

Hello

I have a plan: I want to write something like a "jbpm-Plugin", that updates a wiki whenever new workflow-instances are created and finished. I don't want to implement that into the design of the workflow process. It should be something that you can plug into "any" jbpm installation, and then it starts writing to a wiki. I am writing a little Servlet for the snipsnap wiki software (www.snipsnap.org), that shall update the pages.
My question is now: What is the best practice to have this servlet called by the jbpm.

My first idea is JMS+MDBs. Is it possible to configure jbpm, so that it sends messages to a topic as a publisher?
Then I would try to write my first MDB, which then calls the wiki-servlet.

Let me tell you the versions i am using.. I don't want to change these anymore as time is passing by ...

JBoss 4.0.2 (from the starters-kis)
jbpm 3.1.2 (from the starters-kis)

Thanks for any comments on my idea,
Gregor

[gf_public]

I found the JBoss jBPM Developers Forums. Maybe this Post is better discissed there. Please reply here:
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3965327#3965327
Gregor Fellenz

[kukeltje]

Wrong, this forum is the better place. It is about usage of jBPM, not development of the core of jBPM.

If you read the docs about actionhandlers, you will see they are normal pojo's so you can do anything from them, including calling jms, or whatever

[gf_public]

Hi Ronald

But isn't it, that using actionhandlers, the process designer has to take care of calling them? I wanted something that is transparent to the jBPM workflow designer.

Gregor

[cpob]

It can be. You have have your product programmatically add your action handlers to the process definition before you deploy a provided process to your database.

You have full control over the process definition with the api.

[kukeltje]

What you could also do is implement your own log mechanism by extending the jbpm one. On certain events you could do things yourself, on other events not. For the rest of the logging, pass the call on to the base logging