SpringBootDemo | SpringBootSSM框架整合，最简单的实例！ | Application Framework library

This happens when in your source code doesn't have any API listened, it means there aren't any classes marked with @RestController or @Controller anonation in your source code, SpringBoot at this time just simply build source code run and exit without returning any error messages

I am not sure what Deserializer are you using, but with the Jackson ObjectMapper I solved it changing the method names of the getter and setter for the developers properties: they should be called setDevelopers and getDevelopers. In your code they are called setDeveloper and getDeveloper, without the final S.

To avoid problem like these, I just add Lombok as a dependency and it takes care of creating setters and getters.

With Lombok your Team class would look like this:

Change hibernate configuration

Error message is explicit , this is not correct

I cannot run your code because you only provide a few little snippets, but what I noticed is:

• As for the difference between @target() and @within() in Spring AOP and also in AspectJ, see my answer here.
• Your annotation has @Target({ElementType.TYPE, ElementType.METHOD}), but both your pointcuts only target annotated types, not annotated methods. For that you would need to use @annotation. I.e. your annotated method will never be matched by this pointcut and consequently the advice will never fire.
• Your exception must come from another pointcut/advice pair, not the ones you have shown in your question - probably something global like execution(* *(..)) or within(*) or target(*) which will try to weave into all kinds of Spring components, both your own and internal ones. So you need to limit that other pointcut to something like execution(* my.base.package..*(..)) or within(my.base.package..*) or target(my.base.package..*) or at least exclude internal Spring packages you don't wish to intercept via !within(org.springframework..*).

Edit

Ensure that you update the tags before you save note. Also make sure that the service method saveNote in NoteServiceImpl is also annotated with @Transactional so that rollback will be initiated in case the query gets interrupted for some reason. I was able to reproduce the issue that you faced and guardian is right about how Hibernate handles such situations. You cannot save data to multiple tables in a single SQL command (this is related to Atomicity) but you achieve that using transactions. Here is a fantastic answer related to this.

In your code, you need to change saveNote method in NoteDaoImpl if you still want to save tags while saving data into T_NOTE.

The exception comes from the constructur of the Kernel32 class which is a class of the Maven coordinate net.java.dev.jna:jna-platform which itself depends on net.java.dev.jna:jna. It seems to me like you have to incompatible versions of those dependencies on the class path.

I assume that you use version 4 of JNA core and version 5 of JNA platform. Upgrade the first or downgrade the latter and the error should disappear.

In the provided piece of code the program and its arguments are being passed as the single string value as the ProcessBuilder ProcessBuilder.command(String... command) method parameter.

But that should not be the case: instead, the program and its arguments should be passed separately.

Let's use the ProcessBuilder ProcessBuilder.command(List command) method.

We will prepare the string list appropriately: it will contain the program and its arguments.

The draft solution:

Firstly, that's not JSON - it's an ordinary array. Secondly, you can use reduce like so: