Extending HistorySession

[tcr]

Hi,

some time ago I asked in the user forum about experiences extending the history-session.

http://www.jboss.org/index.html?module=bb&op=viewtopic&t=161482

To me it seems that there are some public getters missing so that you can actually extend the historysession. In addition the binding for the HistorySessionChain is missing.

Is there a way that you could add public getters for the members of the history events in the next release?
Otherwise it is really hard and ugly to implement a custom history (e.g. to send customer specific audit-data to a backend system)

What I mean are getters like....

Event: ActivityEnd, DecisionEnd
Public getter for: transitionName

Event: TaskActivityStart, TaskAssign, TaskCreated, TaskDelete, TaskUpdated
Public getter for: task

Event: TaskAssign
Public getter for: assignee

Event: TaskComplete
Public getter for: outcome

Event: TaskDelete
Public getter for: reason

Event: VariableCreate, VariableUpdate
Public getter for: variable

etc...


That would be really great because we could use jBPM poperly :-)

Regards
Torsten

[sebastian.s]

Take a look at this issue:

https://jira.jboss.org/jira/browse/JBPM-2398

According to JIRA it's coding in process and it's scheduled for 4.2. Maybe you should comment the JIRA issue if you have propositions or if you want to report problems.

[tcr]

Hi Sebastian,

thank you for the response. The JIRA does not cover what I meant.

I don't want to query history data but be able to capture the Event/History-Data myself. We have a quite specific requirement to deliver status and event information live to another system. All these information are available as events in JBPM (e.g. closing a task).

We would like to add a history listener (adding historySessionChain). But right now the information are locked in (the actual Event-Objects) because all the Event-classes do not have getters (e.g. for the task that is the originator of the event).

Sorry it is not that easy to explain. I hope you understand what I mean.

Regards
Torsten

[sebastian.s]

Okay, now I got it. Thanks for the explanation. With my limited knowledge your proposition sounds raisonable and interesting to me. But we should wait to heart what the developers say. However my advice would be to create a jira issue (feature suggestion) and gather votes on it.

Regards
Sebastian

[kukeltje]

Yep... Sebastian is right. Would be a nice way of integrating jBPM with e.g. SeeWhy (that is also why it should be extendible)

[tcr]

Thx!

https://jira.jboss.org/jira/browse/JBPM-2576