What are the commonly used directories for springBoot projects?
Common directories for springBoot projects
servicex // 项目名
|- admin-ui // 管理服务前端代码(一般将UI和SERVICE放到一个工程中,便于管理)
|- servicex-auth // 模块1
|- servicex-common // 模块2
|- servicex-gateway // 模块3
|- servicex-system // 模块4
|- src
|- main // 业务逻辑
|- assembly // 基于maven assembly插件的服务化打包方案
|- bin // 模块脚本(启动、停止、重启)
|- sbin // 管理员角色使用的脚本(环境检查、系统检测等等)
|- assembly.xml // 配置文件
|- java // 源码
|- com
|- hadoopx
|- servicex
|- system
|- annotation // 注解
|- aspect // 面向切面编程
|- config // 配置文件POJO
|- filter // 过滤器
|- constant // 存放常量
|- utils // 工具
|- exception // 异常
|- controller // 控制层(将请求通过URL匹配,分配到不同的接收器/方法进行处理,然后返回结果)
|- service // 服务层接口
|- impl // 服务层实现
|- mapper/repository // 数据访问层,与数据库交互为service提供接口
|- entity/domain // 实体对象
|- dto // 持久层需要的实体对象(用于服务层与持久层之间的数据传输对象)
|- vo // 视图层需要的实体对象(用于服务层与视图层之间的数据传输对象)
|- *Application.java // 入口启动类
|- resources // 资源
|- static // 静态资源(html、css、js、图片等)
|- templates // 视图模板(jsp、thymeleaf等)
|- mapper // 存放数据访问层对应的XML配置
|- *Mapper.xml
|- ...
|- application.yml // 公共配置
|- application-dev.yml // 开发环境配置
|- application-prod.yml // 生产环境配置
|- banner.txt
|- logback.xml // 日志配置
|- test // 测试源码
|- java
|- com
|- hadoopx
|- servicex
|- system
|- 根据具体情况按源码目录结构存放编写的测试用例
|- target // 编译打包输出目录(自动生成,不需要创建)
|- pom.xml // 该模块的POM文件
|- sql // 项目需要的SQL脚本
|- doc // 精简版的开发、运维手册
|- .gitignore // 哪些文件不用传到版本管控工具中
|- pom.xml // 工程总POM文件
|- README.md // 注意事项
External Libraries // 相关JAR包依赖
Copy after login
Notes(1). mapper/repository, data access layer, interacts with the database to provide an interface for the service (add, delete, and modify a certain table Check, a ’*Mapper.java’ and a ’*Mapper.xml’ correspond to a table (if there is a related query); Mybatis uses mapper, and JPA uses repository)( 2). Entity/domain, data entity class (Mybatis uses entity, JPA uses domain)(3). The meaning of POJO, VO, DTO, DO, PO, BO: servicex // 项目名 |- admin-ui // 管理服务前端代码(一般将UI和SERVICE放到一个工程中,便于管理) |- servicex-auth // 模块1 |- servicex-common // 模块2 |- servicex-gateway // 模块3 |- servicex-system // 模块4 |- src |- main // 业务逻辑 |- assembly // 基于maven assembly插件的服务化打包方案 |- bin // 模块脚本(启动、停止、重启) |- sbin // 管理员角色使用的脚本(环境检查、系统检测等等) |- assembly.xml // 配置文件 |- java // 源码 |- com |- hadoopx |- servicex |- system |- annotation // 注解 |- aspect // 面向切面编程 |- config // 配置文件POJO |- filter // 过滤器 |- constant // 存放常量 |- utils // 工具 |- exception // 异常 |- controller // 控制层(将请求通过URL匹配,分配到不同的接收器/方法进行处理,然后返回结果) |- service // 服务层接口 |- impl // 服务层实现 |- mapper/repository // 数据访问层,与数据库交互为service提供接口 |- entity/domain // 实体对象 |- dto // 持久层需要的实体对象(用于服务层与持久层之间的数据传输对象) |- vo // 视图层需要的实体对象(用于服务层与视图层之间的数据传输对象) |- *Application.java // 入口启动类 |- resources // 资源 |- static // 静态资源(html、css、js、图片等) |- templates // 视图模板(jsp、thymeleaf等) |- mapper // 存放数据访问层对应的XML配置 |- *Mapper.xml |- ... |- application.yml // 公共配置 |- application-dev.yml // 开发环境配置 |- application-prod.yml // 生产环境配置 |- banner.txt |- logback.xml // 日志配置 |- test // 测试源码 |- java |- com |- hadoopx |- servicex |- system |- 根据具体情况按源码目录结构存放编写的测试用例 |- target // 编译打包输出目录(自动生成,不需要创建) |- pom.xml // 该模块的POM文件 |- sql // 项目需要的SQL脚本 |- doc // 精简版的开发、运维手册 |- .gitignore // 哪些文件不用传到版本管控工具中 |- pom.xml // 工程总POM文件 |- README.md // 注意事项 External Libraries // 相关JAR包依赖
POJO
: It is a simple, ordinary JAVA object, which contains business logic processing or persistence logic, etc. But it is not JavaBean, EntityBean, etc., does not have any special role, does not inherit or implement any other JAVA framework classes or interfaces. Can contain objects similar to JavaBean properties and setter and getter methods for property access.
VO(View Object)
: View object, used for display layer display, representing the data that needs to be displayed in the display layer. Its function is to encapsulate all the data required by a specific page/component.
DTO(Data Transfer Object)
: Data transfer object, used for data transfer objects between the service layer and the persistence layer, representing the service layer that needs to receive/return The data.
DO(Domain Object)
: Domain object is a tangible or intangible entity object abstracted from the real world.
PO (Persistent Object)
: Persistence object, which forms a one-to-one mapping relationship with the data structure of the persistence layer (usually a relational database). Each field (or several) in the data table corresponds to one (or several) attributes of PO.
BO(Business Object)
: Business object is used to encapsulate business logic into an object, which can include one or more other objects.
- ##POJO
After persistence-> PO; During POJO transmission-> DTO; POJO is used as the presentation layer-> VO
The above is the detailed content of What are the commonly used directories for springBoot projects?. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics



Introduction to Jasypt Jasypt is a java library that allows a developer to add basic encryption functionality to his/her project with minimal effort and does not require a deep understanding of how encryption works. High security for one-way and two-way encryption. , standards-based encryption technology. Encrypt passwords, text, numbers, binaries... Suitable for integration into Spring-based applications, open API, for use with any JCE provider... Add the following dependency: com.github.ulisesbocchiojasypt-spring-boot-starter2. 1.1Jasypt benefits protect our system security. Even if the code is leaked, the data source can be guaranteed.

Usage scenario 1. The order was placed successfully but the payment was not made within 30 minutes. The payment timed out and the order was automatically canceled. 2. The order was signed and no evaluation was conducted for 7 days after signing. If the order times out and is not evaluated, the system defaults to a positive rating. 3. The order is placed successfully. If the merchant does not receive the order for 5 minutes, the order is cancelled. 4. The delivery times out, and push SMS reminder... For scenarios with long delays and low real-time performance, we can Use task scheduling to perform regular polling processing. For example: xxl-job Today we will pick

1. Redis implements distributed lock principle and why distributed locks are needed. Before talking about distributed locks, it is necessary to explain why distributed locks are needed. The opposite of distributed locks is stand-alone locks. When we write multi-threaded programs, we avoid data problems caused by operating a shared variable at the same time. We usually use a lock to mutually exclude the shared variables to ensure the correctness of the shared variables. Its scope of use is in the same process. If there are multiple processes that need to operate a shared resource at the same time, how can they be mutually exclusive? Today's business applications are usually microservice architecture, which also means that one application will deploy multiple processes. If multiple processes need to modify the same row of records in MySQL, in order to avoid dirty data caused by out-of-order operations, distribution needs to be introduced at this time. The style is locked. Want to achieve points

Springboot reads the file, but cannot access the latest development after packaging it into a jar package. There is a situation where springboot cannot read the file after packaging it into a jar package. The reason is that after packaging, the virtual path of the file is invalid and can only be accessed through the stream. Read. The file is under resources publicvoidtest(){Listnames=newArrayList();InputStreamReaderread=null;try{ClassPathResourceresource=newClassPathResource("name.txt");Input

When Springboot+Mybatis-plus does not use SQL statements to perform multi-table adding operations, the problems I encountered are decomposed by simulating thinking in the test environment: Create a BrandDTO object with parameters to simulate passing parameters to the background. We all know that it is extremely difficult to perform multi-table operations in Mybatis-plus. If you do not use tools such as Mybatis-plus-join, you can only configure the corresponding Mapper.xml file and configure The smelly and long ResultMap, and then write the corresponding sql statement. Although this method seems cumbersome, it is highly flexible and allows us to

SpringBoot and SpringMVC are both commonly used frameworks in Java development, but there are some obvious differences between them. This article will explore the features and uses of these two frameworks and compare their differences. First, let's learn about SpringBoot. SpringBoot was developed by the Pivotal team to simplify the creation and deployment of applications based on the Spring framework. It provides a fast, lightweight way to build stand-alone, executable

1. Customize RedisTemplate1.1, RedisAPI default serialization mechanism. The API-based Redis cache implementation uses the RedisTemplate template for data caching operations. Here, open the RedisTemplate class and view the source code information of the class. publicclassRedisTemplateextendsRedisAccessorimplementsRedisOperations, BeanClassLoaderAware{//Declare key, Various serialization methods of value, the initial value is empty @NullableprivateRedisSe

In projects, some configuration information is often needed. This information may have different configurations in the test environment and the production environment, and may need to be modified later based on actual business conditions. We cannot hard-code these configurations in the code. It is best to write them in the configuration file. For example, you can write this information in the application.yml file. So, how to get or use this address in the code? There are 2 methods. Method 1: We can get the value corresponding to the key in the configuration file (application.yml) through the ${key} annotated with @Value. This method is suitable for situations where there are relatively few microservices. Method 2: In actual projects, When business is complicated, logic
