hibernate-validator | Hibernate Validator - Jakarta Bean Validation Reference | Validation library

Spring 3.2.0.RELEASE uses asm 4.0, which does not support Java 8 or higher.

Since Java 7 is not supported any more, you should upgrade Spring to the latest patch release:

I managed to get the error to go away. All I needed to do it all the dependency config for the related tasks (in build.gradle):

I've tried your example:

I cannot reproduce the problem because IDEA does not find the Lombok setters. Even when delegating build actions before run to Maven, I get NoSuchMethodError: '...TestEntity.setCode(java.lang.String)'. Next, I am going to try without Lombok. Please note that Lombok and AspectJ do not play nice with each other, see my answer here. Alternatively, you could also make sure that Maven does either of these:

1. First build with Javac + Lombok, then apply AspectJ binary weaving in a second step, all in one module.
2. Similar to above, but do the first build step in module A and the second one in a separate module B. Then you have an unwoven and a woven artifact, which you can both use according to your preferences. For example, you could also use the unwoven one and apply transaction aspects via load-time weaving (LTW) while starting the application. See my other answer here for both approaches #1 and #2.
3. Delombok the source code build the generated sources with the AspectJ compiler in a second build step.

I generated constructors, getters and setters in the IDE instead of using Lombok. Now the project compiles in both IDE and Maven. It behaves exactly as it should. With @Transactional, 0 entities are created, without it 2.

I am not sure if Lombok vs. AspectJ really is the problem due to non-compileability when using Lombok annotations, but it should be easy enough to try without Lombok for you. If it works in your context, too, we found the culprit and can think about implementing one of the 3 approaches mentioned above. Then you can tell me if you have any difficulty in doing so.

Update: I created the two-module version - Javac + Lombok, then Aspect weaving - for you in my fork and also issued pull request #1. I also improved testability a bit. See if that works for you.

Caveat: You cannot simply run DemoApplication from the application-lombok module, because that module is still unwoven and will not show transactional behaviour. But you can simply change the classpath for the run config to the application-aspectj module:

Update: As we found out in the comment section of the other answer, in addition to the problematic Lombok vs. AspectJ compiler configuration, the OP also simply had a problem with his IDE: Using IntelliJ IDEA Community Edition, he was first unaware of, then unable to install the AspectJ plugin, which means that IDEA does not know antyhing about the AspectJ compiler and simply overwrites anything which might have been compiled by AspectJ Maven before with plain Java classes. Therefore, transactional aspects do not work either, unless

• either pre-run compilation is disabled and mvn compile started as an additional pre-build step for the corresponding run configuration,
• or all build actions for the project are being delegated to Maven via configuration,
• the OP buys a licence of IDEA Ultimate and installs the AspectJ plugin.

It was an Intelli-J issue!

So, cleaning the Intelli-J dependency spaghetti up solved it!

1. File > Invalidate cache ... and restart. Helped a bit.
2. Closing the Intelli-J project. Then removed manually the ".idea" folder and any *.iml file.

Yes, I did option 1 previously. Especially doing action 2 solved it within a minute.

I just solved the problem... It was the order of dependecies. I switched quarkus-resteasy-reactive to the top and it is working now.

Your CurrencyExchange_Logic class has two constructors: the required args constructor, which has parameters corresponding to the 3 final fields, and the all args constructor, with parameters corresponding to those 3 fields as well as start and end.

When you only have one constructor defined, Spring knows how to implicitly choose it for injection. However, when you have more than one, you have to tell it which one you want it to use, using the @Autowired or @Inject annotation.

I would guess you want Spring to use the required args constructor, as I doubt Spring has any way of knowing how to resolve the start or end fields. This can be done in lombok (@RequiredArgsConstructor(onConstructor_ = @Autowired)), or by just explicitly writing the constructor yourself and annotating it. Note you could also get rid of the all args constructor, if you don't need it, and Spring's implicit constructor injection should "just work."

HttpFilter is a class introduced in Servlet 4.0, therefore you need to upgrade to Tomcat 9.0.

Regarding Tomcat 10 (Servlet 5.0), it is incompatible with previous releases and will be the target of Spring Framework 6.x (Spring Boot 3.x).

Since Spring Framework 5.x and Spring Boot 2.x have a baseline of Servlet 3.1 (cf. documentation) this might be actually a bug, but it is impossible to tell without a full stack trace.

Edit: Apparently the only reference to HttpFilter in Spring Boot is:

The problem was the AWS time zone configuration, for some strange reason it interfered with how Quarkus validates the IAT and EXP claims of the token. I removed the AWS time zone settings and set the zone using a system property at the JVM level and the problem was completely fixed.