swagger-ui | 汉化了swagger-ui，修改了部分样式 | User Interface library

A 400 is a pretty unusual response code for a preflight response. That suggests the endpoint might be configured to expect a certain request body/payload or headers in the request regardless of what the HTTP method is for the request. But since for the preflight OPTIONS request, the browser sends no request body and no additional header, the server code is not receiving what it expects.

For such cases, the fix is to ensure you have a specific, separate handler for OPTIONS requests configured for that route/endpoint.

I got the solution

I created this Custom DocumentFiler thats sorts the Tags

This problem's caused by a bug in Springfox. It's making an assumption about how Spring MVC is set up that doesn't always hold true. Specifically, it's assuming that MVC's path matching will use the Ant-based path matcher and not the PathPattern-based matcher. PathPattern-based matching has been an option for some time now and is the default as of Spring Boot 2.6.

As described in Spring Boot 2.6's release notes, you can restore the configuration that Springfox assumes will be used by setting spring.mvc.pathmatch.matching-strategy to ant-path-matcher in your application.properties file. Note that this will only work if you are not using Spring Boot's Actuator. The Actuator always uses PathPattern-based parsing, irrespective of the configured matching-strategy. A change to Springfox will be required if you want to use it with the Actuator in Spring Boot 2.6 and later.

It looks like you have a service named database_ignite in your docker-compose.yml file. Docker by default creates a host using the name of your service. Try changing your host from database inside your index.ts file to database_ignite:

Spring Boot 3.0 is built for Java17 and JakartaEE, not JavaEE. Spring Boot 3 is still under development and hasn't seen a final release yet. There has been no official release date yet, but expect nothing sooner than Q4 of 2022. Until then I wouldn't consider Spring Boot 3 for production (or maybe when they start releasing Release Candidates).

That being said, there is currently no SpringFox release that supports JakartaEE and therefore isn't usable with Spring Boot 3 (see this). So until that has been resolved the combination of SpringFox and Spring Boot 3 won't work.

Use 2.6.x (which at this moment is the latest release version of Spring Boot).

You should enable the ShowPII flag first to get an actual error message.

How this is done is answered here.

In my case the URL used to fetch the discovery document was wrong but it could be really anything. The actual error message will give you a glue.

Swagger2's usage seems to require (or at least often includes) the concept of a Docket api via an instantiation such as new Docket() or new Docket(DocumentationType.SWAGGER_2). I don't see that in your code snippets, so wonder if that may be one issue.

Per the swagger docs, Docket is Springfox’s primary api configuration mechanism.

Specifically, this section regarding configuration may be helpful. Note the Docket instantiation:

I'm not sure this could be done with vanilla DRF. The best schema generator for Django being supported now, as far as I know, is drf-spectacular. So if you are using drf-spectacular, you have to document it this way:

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.