nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

How transactions work in Activiti

birju

looking at someone legacy code.

If transaction is configured into a config file

      <bean id="transactionManager" class="org.springframework.jdbc.datasource.DataSourceTransactionManager">
        <property name="dataSource" ref="dataSource" />
      </bean>

And one of the APIs has following code

def insertUser(user:User) = {
  val user = identityService.newUser(user.id.toString)
  identityService.saveUser(user)

} ‍‍‍‍‍

identityService.newUser and identityService.saveUser both will run into separate transactions right? This is a code bug if that's true. If so what's the best way to combine multiple acticiti calls into a single transaction?

Find more posts tagged with

Comments

martin_grofcik

Hi,

it depends on transaction propagation level set in CommandConfig. e.g. for spring

<br>&nbsp; @Override<br>&nbsp; protected void initDefaultCommandConfig() {<br>&nbsp;&nbsp;&nbsp; if (defaultCommandConfig == null) {<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; defaultCommandConfig = new CommandConfig().setContextReusePossible(true);<br>&nbsp;&nbsp;&nbsp; }<br>&nbsp; }<br>

By default TransactionPropagation.REQUIRED

More info:
http://www.activiti.org/userguide/#N1094F

Regards
Martin

birju

Since it's using default which like you said is TransactionPropogation.REQUIRED still don't following two calls run into separate transactions?

<code>
def insertUser(user:User) = {
val user = identityService.newUser(user.id.toString)
identityService.saveUser(user)

}
</code>
The way I understand Propogation.REQUIRED is that if let's say identityService.newUser was calling another transactional method within itself, then it'll use the same transaction.

particular usage of calling two separate methods in above code has no knowledge about combining the two into one transaction given they are distinct calls? Isn't that right?

martin_grofcik

Hi,

<br>&nbsp;&nbsp;&nbsp; try {<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; User secondUser = identityService.newUser("testuser2");<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; if (true)<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; throw new RuntimeException();<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; identityService.saveUser(secondUser);<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; fail("Exception should have been thrown");<br>&nbsp;&nbsp;&nbsp; } catch (RuntimeException re) {<br>&nbsp;&nbsp;&nbsp; } <br><br>&nbsp;&nbsp;&nbsp; assertEquals(0, identityService.createUserQuery().userId("testuser2").count());<br>

identityService.newUser("testuser2"); creates user object with Id set.
identityService.saveUser(secondUser); persists object into the DB.

Regards
Martin