Activiti
  1. Activiti
  2. ACT-45

Add Spring support in a JTA and appserver environment

    Details

    • Type: Improvement Improvement
    • Status: Resolved Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: Sooner
    • Component/s: Engine
    • Labels:
      None
    • Number of attachments :
      0

      Description

      Potentially this involves: Finishing transaction manager integration for Spring so that ACtiviti TX interceptors are respected properly and REQUIRES_NEW is respected / enforced where necessary.

        Activity

        Hide
        Tom Baeyens added a comment -

        I believe these were intended for future releases. I assigned them to beta 1 release so that we can discuss them in context of the next release

        Show
        Tom Baeyens added a comment - I believe these were intended for future releases. I assigned them to beta 1 release so that we can discuss them in context of the next release
        Hide
        Tom Baeyens added a comment -

        this will require that we split the command executor in 2 versions, a required and a requiresNew.
        the requiresNew will have to be used in DecrementJobRetriesListener and in the DbIdGenerator.

        Show
        Tom Baeyens added a comment - this will require that we split the command executor in 2 versions, a required and a requiresNew. the requiresNew will have to be used in DecrementJobRetriesListener and in the DbIdGenerator.
        Hide
        Bernd Ruecker (camunda) added a comment -

        There is one related bug in the DbIdGenerator (see TODO in the getNewBlock()), I hope that will be fixed within this isse? That would be perfect, since this is a show stopper for going live in big installations.

        Show
        Bernd Ruecker (camunda) added a comment - There is one related bug in the DbIdGenerator (see TODO in the getNewBlock()), I hope that will be fixed within this isse? That would be perfect, since this is a show stopper for going live in big installations.
        Hide
        Tom Baeyens added a comment -

        Bernd, that should already be covered.
        dbIdGenerator.setCommandExecutor(commandExecutorTxRequiresNew);

        The only thing we don't yet have is a configuration file that shows how to configure the JTA transaction context. And QA runs that show we operate well in spring tx context and in jta tx context.

        We should see progress in the qa this week. Almost there.

        Show
        Tom Baeyens added a comment - Bernd, that should already be covered. dbIdGenerator.setCommandExecutor(commandExecutorTxRequiresNew); The only thing we don't yet have is a configuration file that shows how to configure the JTA transaction context. And QA runs that show we operate well in spring tx context and in jta tx context. We should see progress in the qa this week. Almost there.
        Hide
        Tom Baeyens added a comment -

        The strategy is going to be the following:

        We plan to add a test suite to Alfresco test suite that reads all the tests to include from a resource file.
        We'll create a profile so that the activiti engine test module will include as a resource the lists all the tests. That way, the activiti engine test classes library can just be included in the Alfresco test classpath. This should then happen each time when the activiti jar is updated in the alfresco codebase.

        Frederik is going to ask the Gavin and Nick where we can include extra test dependencies. I'll investigate how we can move the generation of that resource that lists all the tests from activiti-spring module to the activiti-engine module.

        Show
        Tom Baeyens added a comment - The strategy is going to be the following: We plan to add a test suite to Alfresco test suite that reads all the tests to include from a resource file. We'll create a profile so that the activiti engine test module will include as a resource the lists all the tests. That way, the activiti engine test classes library can just be included in the Alfresco test classpath. This should then happen each time when the activiti jar is updated in the alfresco codebase. Frederik is going to ask the Gavin and Nick where we can include extra test dependencies. I'll investigate how we can move the generation of that resource that lists all the tests from activiti-spring module to the activiti-engine module.
        Hide
        Bernd Ruecker (camunda) added a comment -

        Outdated, please re-open if still relevant (I hope not )

        Show
        Bernd Ruecker (camunda) added a comment - Outdated, please re-open if still relevant (I hope not )

          People

          • Assignee:
            Tom Baeyens
            Reporter:
            Dave Syer
          • Votes:
            3 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: