What are the correct maven artifact and group Ids?
by Simon Gibbs
Hi there,
I'm new to the list so apologies in advance for stumbling in, but I'm
seriously confused and could do with a little help here. I'm doing a
proof on concept involving Seam and jBPM 3.2, and we're at least a few
months from anything happening so don't mind an answer that is subject
to change. I should disclose that I am very new to half of the Seam
technology stack and Maven as well.
What are the correct maven artifact and group Ids for my scenario? In
particular, for the 3.2 heritage jbpm-identity.jar?
I have had the following details in the pom.xml:
<dependency>
<groupId>org.jbpm</groupId>
<artifactId>jbpm-jpdl</artifactId>
<version>3.2.2</version>
</dependency>
But I've been unable to find an equivalent set of details for the
identity jar which is essential since I need to use
org.jbpm.identity.assignment.ExpressionAssignmentHandler
I noticed in SVN the pom is referencing seam 2.0. I'm using Seam 2.1 for
the POC and was concerned about compatibility in the event of a change?
If I'm going to get into a pickle with Maven and conflicting
dependencies I'd appreciate a heads up :-) Is anyone using 3.3 and
seam 2.1 successfully already or will I be the first to try it?
from a nearby pom:
<groupId>org.jboss.seam</groupId>
<artifactId>jboss-seam</artifactId>
<version>2.1.0.GA</version>
Thanks in advance.
Simon Gibbs
17 years, 4 months
[JBoss jBPM] - JBPM and Managed Container Transactions
by trouby
Hey,
I am trying to make JBPM to work smoothly through EJB3 components with no success,
After invoking very simple methods through a stateless EJB3 such as:
| ProcessInstance pi = jbpmContext.loadProcessInstance(spmlTask.getWorkflowProcessId());
|
I'm getting errors such as:
| 23:13:38,858 ERROR [TimerImpl] Error invoking ejbTimeout: javax.ejb.EJBException: javax.persistence.TransactionRequiredException: Entity
| Manager must be access within a transaction
|
I assumed this is due to the fact that somewhere JBPM commits the transaction so invocations after that causes the exception,
I have followed section "7.1.3. Managed transactions" in the manual:
anonymous wrote :
| A stateless session facade in front of jBPM is a good practice. The easiest way on how to bind the jbpm transaction to the container transaction is to make sure that the hibernate configuration used by jbpm refers to an xa-datasource. So jbpm will have its own hibernate session, there will only be 1 jdbc connection and 1 transaction.
|
But setting it up is not clear enough, I tried to configure JBPM as follows:
hibernate.cfg.xml
| ...
|
| <property name="connection.datasource">java:/veloDatasource</property>
| <property name="transaction.factory_class">org.hibernate.transaction.JTATransactionFactory</property>
| <property name="transaction.manager_lookup_class">org.hibernate.transaction.JBossTransactionManagerLookup</property>
|
| ...
|
jbpm.cfg.xml
| <jbpm-context>
| <service name="persistence">
| <factory>
| <bean class="org.jbpm.persistence.db.DbPersistenceServiceFactory">
| <field name="isTransactionEnabled"><false/></field>
| </bean>
| </factory>
| </service>
| <service name="tx" factory="org.jbpm.tx.TxServiceFactory" />
|
| ...
|
where veloDataSource is defined in persistence.xml as follows
| <local-tx-datasource>
| <jndi-name>veloDatasource</jndi-name>
| <connection-url>jdbc:mysql://localhost:3306/velo</connection-url>
| <driver-class>com.mysql.jdbc.Driver</driver-class>
| <user-name>root</user-name>
| <password>password</password>
| </local-tx-datasource>
|
Seems like JBPM is not using the MC transaction and if I understand correctly, JBPM commits the transaction and that what causes the persistence unit to fail later on.,
Can anyone give me a hand how to proceed from here?
Man thanks,
Asaf.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4191905#4191905
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4191905
17 years, 4 months