SpringBoot solves cross-domain\multi-environment configuration; java obtains the IP of the requester; @Transactional explanation; VSCode cannot open the terminal window solution

5 ways SpringBoot solves cross-domain issues

springboot multi-environment configuration reference 1
springboot switching dev environment


java gets the ip of the requester


@Transactional(rollbackFor = Exception) in Spring


The solution to the problem that the Terminal window cannot be opened in VS Code.
Although it is said online that adding this setting will do the trick.

"terminal.integrated.shell.windows": "C:\\Windows\\system32\\cmd.exe"

But I still can't open it, mainly because I can't find the correct path. I need to change system32 to sysnative,
such as: sysnative origin reference
sysnative
. As for why I need to do this, it is mainly because:
32-bit applications running on WOW64 will Placed under file system redirection. Therefore, if your application is 32-bit, the path "C:\Windows\System32\fodhelper.exe" will be redirected to C:\Windows\SysWOW64\fodhelper.exe, but it does not exist. You have some solutions:
use SysNative to access the real system32 folder, which means you need to explicitly turn off filesystem redirection using something like system("C:\Windows\SysNative\fodhelper.exe"); (which should generally be avoided ) or better yet compile your exe into a 64-bit application. --—— Translated from
vscode, the solution to the problem of being unable to open the terminal

Guess you like

Origin blog.csdn.net/qq_45699990/article/details/122456571