if only I could do a @Transactional(propagation=ignoresubtransactions) or either something like @EnableTransactional(exclude=third-party.class)
and that is assuming that the current and expected behavior is that upon propagation=REQUIRED, transaction does support parent transaction but not parent's transactionmanager which I don't see it obvious at all
What the aspect does is determine what transaction manager to call around the method. It doesn't do any tracking of transactions or managers itself.
A third option is a custom aspect that looks at the method's class/package to decide which transaction manager to use, but IMO that's more messy.
none of which has anything to do with propagation
Are we sure theres no mechanism for marking a bean as not qualifiable to support transactions? I mean something like @EnableTransactions(exclude=thirdparty.class). I need the bean to be managed, but I want the @Transactional to be ignored
Anyway, thanks for your help james
perhaps you could do something really hacky with
Bean(Definition)PostProcessors but the other solutions are all easier
when I want to do A.allofB.size where allofB is the manytomany field that link A to B (through a join table)
I get in infinite recursion
I've dealt with infinite recursion when serializing my data (Json), but in that case I am not serializing anything…
(and the two manytomany sides are LAZY)
If I remove the manytomany field on the class B, then I can run that (but I cannot find all the A linked to an object B from an object of type B)
I can't find a way to have the both sides of that manytomany relation
(and I am NOT using serialization here)
I am wondering if it could be an issue with kotlin data classes that may want to hash the objects anyway
(as I am using sets)
The 2.2.2 -> 2.2.3 update appears to have broken properties loading via
@ActiveProfiles("test"). Maybe #19556 but there are no commas involved...
Ah yes: #19788
Just to double check: https://github.com/spring-projects/spring-boot/wiki/Spring-Boot-2.1-Release-Notes#third-party-library-upgrades
Tomcat 9 is the baseline. Spring boot no longer guarantees to work with older version, right?
Tomcat 9 is the baseline. Spring boot no longer guarantees to work with older version, right?
System requirements are documented here: https://docs.spring.io/spring-boot/docs/current/reference/html/getting-started.html#getting-started-system-requirements
That’s for the embedded container though
i think it has got something to do with java hibernate pipleline, because when i try to insert the data from datagrip it works fine
which is like the DB is configured fine, i think
Hi! how can I force one of my app's @Configuration @Beans to be loaded before an @AutoConfiguration one? My local bean instantiation actions a side-effect that is relevant to the @AutConfiguration bean runtime instantiation logic. The thing is both have as a dependency a previosusly autoconfigured bean
Hey! Am I the only one having problem fetching 2.1.12.RELEASE from mvn central? I see it here https://search.maven.org/artifact/org.springframework.boot/spring-boot-dependencies/2.1.12.RELEASE/pom but not here https://mvnrepository.com/artifact/org.springframework.boot/spring-boot-dependencies and I get release not found when trying to build it in my project. Any sync issue going on?