[JBoss JIRA] Created: (HIBERNATE-62) Default value of hibernate.transaction.factory_class is not used
by Takaaki Igarashi (JIRA)
Default value of hibernate.transaction.factory_class is not used
----------------------------------------------------------------
Key: HIBERNATE-62
URL: http://jira.jboss.com/jira/browse/HIBERNATE-62
Project: Hibernate
Issue Type: Bug
Environment: JBoss 4.0.5.AS
Hibernate 3.2.3
Java 1.5
Reporter: Takaaki Igarashi
Assigned To: Steve Ebersole
Priority: Minor
I tried to use container-managed transaction in JBoss with Hibernate.
So, I put the followings in the hibernate configure file:
<property name="hibernate.transaction.factory_class" value="org.hibernate.transaction.JTATransactionFactory"/>
<property name="hibernate.transaction.manager_lookup_class" value="org.hibernate.transaction.JBossTransactionManagerLookup"/>
When I run the app, Hibernate complains that "Cannot join transaction, not a JoinableCMTTransaction"
I also tried with org.hibernate.transaction.CMTTransactionFactory and org.hibernate.transaction.JDBCTransactionFactory.
Both of them didn't work either.
When I delete the parameter, it works.
So, I think the default value is not used.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 3 months
[JBoss JIRA] Commented: (JBPM-165) process instance versioning
by Bernd Ruecker (JIRA)
[ http://jira.jboss.com/jira/browse/JBPM-165?page=comments#action_12359530 ]
Bernd Ruecker commented on JBPM-165:
------------------------------------
By the way: I have a issue to improve the command on my Todo-List for next week: add support for change states in task-nodes and vice-verca.
> process instance versioning
> ---------------------------
>
> Key: JBPM-165
> URL: http://jira.jboss.com/jira/browse/JBPM-165
> Project: JBoss jBPM
> Issue Type: Feature Request
> Components: Core Engine
> Reporter: Tom Baeyens
> Assigned To: Tom Baeyens
> Fix For: jBPM jPDL 3.2.1
>
>
> i think jbpm could offer some degree of assistence in process instance versioning.
> when a new version of a process is deployed, jbpm could do the following conversion for a process instance :
> * input required: mapping of the nodes from the old to the new definition.
> * cancel the old process instance
> * create a new process instance and copy the runtime (exe) information such as tokens and process variables from the old process instance.
> * then establish a special link between the 2 process instances to indicate that the new process instance is the continuation of the old process instance.
> this way we can avoid the problematic conversion of logs, while still keeping them in the system.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 3 months
[JBoss JIRA] Commented: (JBPM-165) process instance versioning
by Bernd Ruecker (JIRA)
[ http://jira.jboss.com/jira/browse/JBPM-165?page=comments#action_12359501 ]
Bernd Ruecker commented on JBPM-165:
------------------------------------
org.jbpm.command.ChangeProcessInstanceVersionCommand
> process instance versioning
> ---------------------------
>
> Key: JBPM-165
> URL: http://jira.jboss.com/jira/browse/JBPM-165
> Project: JBoss jBPM
> Issue Type: Feature Request
> Components: Core Engine
> Reporter: Tom Baeyens
> Assigned To: Tom Baeyens
> Fix For: jBPM jPDL 3.2.1
>
>
> i think jbpm could offer some degree of assistence in process instance versioning.
> when a new version of a process is deployed, jbpm could do the following conversion for a process instance :
> * input required: mapping of the nodes from the old to the new definition.
> * cancel the old process instance
> * create a new process instance and copy the runtime (exe) information such as tokens and process variables from the old process instance.
> * then establish a special link between the 2 process instances to indicate that the new process instance is the continuation of the old process instance.
> this way we can avoid the problematic conversion of logs, while still keeping them in the system.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 3 months
[JBoss JIRA] Commented: (JBPM-165) process instance versioning
by Bernd Ruecker (JIRA)
[ http://jira.jboss.com/jira/browse/JBPM-165?page=comments#action_12359500 ]
Bernd Ruecker commented on JBPM-165:
------------------------------------
Hi Tom,
the Command is already commited, but I have updated it right now to our latest version (which works for us)
> process instance versioning
> ---------------------------
>
> Key: JBPM-165
> URL: http://jira.jboss.com/jira/browse/JBPM-165
> Project: JBoss jBPM
> Issue Type: Feature Request
> Components: Core Engine
> Reporter: Tom Baeyens
> Assigned To: Tom Baeyens
> Fix For: jBPM jPDL 3.2.1
>
>
> i think jbpm could offer some degree of assistence in process instance versioning.
> when a new version of a process is deployed, jbpm could do the following conversion for a process instance :
> * input required: mapping of the nodes from the old to the new definition.
> * cancel the old process instance
> * create a new process instance and copy the runtime (exe) information such as tokens and process variables from the old process instance.
> * then establish a special link between the 2 process instances to indicate that the new process instance is the continuation of the old process instance.
> this way we can avoid the problematic conversion of logs, while still keeping them in the system.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 3 months