As a user, I can launch the activation workflow so that I can do the review process
(MGNLWORKFLOW-43)
|
|
| Status: | Closed |
| Project: | Magnolia Workflow Module |
| Component/s: | jBPM |
| Affects Version/s: | None |
| Fix Version/s: | 5.0 |
| Type: | Sub-task | Priority: | Neutral |
| Reporter: | Jozef Chocholacek | Assignee: | Unassigned |
| Resolution: | Not an issue | Votes: | 0 |
| Labels: | jBPM, persistence, tomcat, transactions | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Sprint: | Alpha 3, Iteration 2013-12, Iteration 2013-13, Iteration 2013-14, Iteration 2013-15, Iteration 2013-16 |
| Description |
|
Currently, the only way to have persistence working properly is to have a context.xml file in the webapp's META-INF directory. The file content is following: <Context>
<Transaction factory="bitronix.tm.BitronixUserTransactionObjectFactory" />
</Context>
|
| Comments |
| Comment by Jozef Chocholacek [ 16/Aug/12 ] |
|
Just a note about where this comes from: |
| Comment by Jozef Chocholacek [ 23/Apr/13 ] |
|
Does not make sense - the file would not apply without another restart. A check for a user transaction availability has been added to the jbpm module start() instead. |