Products
In-IDE
IDE extension that lets you fix coding issues before they exist!
Discover SonarLint
SaaS
Setup is effortless and analysis is automatic for most languages
Discover SonarCloud
Self-Hosted
Fast, accurate analysis; enterprise scalability
Discover SonarQube

Java static code analysis

Unique rules to find Bugs, Vulnerabilities, Security Hotspots, and Code Smells in your JAVA code

Methods should not call same-class methods with incompatible "@Transactional" values

Bug

BlockerSonarSource default severity
click to learn more

When using Spring proxies, calling a method in the same class (e.g. this.aMethod()) with an incompatible @Transactional requirement will result in runtime exceptions because Spring only "sees" the caller and makes no provisions for properly invoking the callee.

Therefore, certain calls should never be made within the same class:

From	To
non-`@Transactional`	MANDATORY, NESTED, REQUIRED, REQUIRES_NEW
MANDATORY	NESTED, NEVER, NOT_SUPPORTED, REQUIRES_NEW
NESTED	NESTED, NEVER, NOT_SUPPORTED, REQUIRES_NEW
NEVER	MANDATORY, NESTED, REQUIRED, REQUIRES_NEW
NOT_SUPPORTED	MANDATORY, NESTED, REQUIRED, REQUIRES_NEW
REQUIRED or `@Transactional`	NESTED, NEVER, NOT_SUPPORTED, REQUIRES_NEW
REQUIRES_NEW	NESTED, NEVER, NOT_SUPPORTED, REQUIRES_NEW
SUPPORTS	MANDATORY, NESTED, NEVER, NOT_SUPPORTED, REQUIRED, REQUIRES_NEW

Noncompliant Code Example

@Override
public void doTheThing() {
  // ...
  actuallyDoTheThing();  // Noncompliant
}

@Override
@Transactional
public void actuallyDoTheThing() {
  // ...
}

Available In:

Catch issues on the fly,
in your IDE

Detect issues in your GitHub, Azure DevOps Services, Bitbucket Cloud, GitLab repositories

Analyze code in your
on-premise CI

In-IDE

SaaS

Self-Hosted