Announcement Announcement Module

Spring Modules forum decommissioned in favor of Spring Extensions

As the Spring Modules project has been replaced by the Spring Extensions ( project, this forum has been decommissioned in favour of Spring Extensions one at:

Please see the Spring Extensions home page for a complete list of current projects in Java, .NET and ActionScript. You can also propose one if you want.

Costin Leau
SpringSource - Spring Training, Consulting, and Support - "From the Source"
See more
See less
Jbpm31 Module and Deploy Process Page Title Module
Move Remove Collapse
Conversation Detail Module
  • Filter
  • Time
  • Show
Clear All
new posts

  • Jbpm31 Module and Deploy Process

    I just downloaded last version of jbpm31 module and migrated our web-application from approach got from jbpm (initialization of configuration with jbpm's org.jbpm.web.JbpmContextFilter) to use jbpmConfiguration via spring beanFactory.

    I'm using default settings I've got from spring-jbpm31 test for dataSource (only difference i'm using Postgres), transactionManager and jbpmConfiguration...

    Everything works fine.... but only for reading...

    Then I try to save something - it seems done well - but not really saved.
    It seems for me that we problem in transaction management... but I'm not very familiar with transactions in Spring... before migration to the Spring jbpm works fine without any transactions...

    So, how it is possible to make working correctly? For example this code I'm using for deploying new process definition:
    ZipInputStream zis = new ZipInputStream(fileItem.getInputStream());
    JbpmContext jbpmContext = JbpmContext.getCurrentJbpmContext();
    processDefinition = ProcessDefinition.parseParZipInputStream(zis);
    What I should add or change to see my process definition on the next web-page? (I cannot find it by id I had in deploy)

    Thank you for your advice

  • #2
    I found the source of problem

    OK, I found the source of problem - JbpmContextFilter called jbpmContext.close() after processing the pages - this method commited hibernate transaction user in JBPM Context.

    So, I added this method into my code and everything started to work


    • #3
      So is there something missing from the jbpm support or the problem was in your code?