6.1: inject JMS AuditLogger into kieSession

[jboss-gpe]

inject JMS AuditLogger (from org.jbpm.process.audit.AuditLoggerFactory) into ksession for asynch messaging as transport for BAM events from process engine.

the other AuditLogger implementation is JPA based. for each deploymentUnit, selection of the AuditLogger type should be configurable.

BAM event consumer should be deployed separately from the process engine and persist BAM events to it's own dedicated database.

• it appears that VFSDeploymentService and KModuleDeploymentService are hard-coded to make use of the JPA based AuditLogger in both bpms6 ER3 and upstream community jbpm.
• • The alternative AuditLogger is JMS based.
• • I don't see an existing BZ that discusses a change to these DeploymentServices to make them both configurable to use either a JPA or JMS AuditLogger.

[jboss-gpe]

BZ for this found here: https://bugzilla.redhat.com/show_bug.cgi?id=1012939

[jboss-gpe]

pretty close to being done. two remaining issues:

1) the MDB audit log consumer has dependencies on jbpm libraries (obviously). will do so with JBoss modules dependencies

2) this error in the bpm-core-* jvm now that core and bam persistence has been split: Caused by: java.lang.IllegalArgumentException: Named query not found: getProcessInstancesByDeploymentId at org.hibernate.ejb.AbstractEntityManagerImpl.createNamedQuery(AbstractEntityManagerImpl.java:601) at org.jbpm.shared.services.impl.JbpmServicesPersistenceManagerImpl.queryWithParameters(JbpmServicesPersistenceManagerImpl.java:521) at org.jbpm.shared.services.impl.JbpmServicesPersistenceManagerImpl.queryWithParametersInTransaction(JbpmServicesPersistenceManagerImpl.java:446)

[fasharaf]

I am also facing same issue. Have you find any resolution of this?