什么是推荐的项目结构为弹簧启动休息项目?

我是弹簧靴的初学者。我参与了一个项目的开始,在这个项目中,我们将使用 spring boot 构建 rest 服务。在构建仅公开其他服务的项目时,您能否建议遵循推荐的目录结构?

190525 次浏览

Please use Spring Tool Suite (Eclipse-based development environment that is customized for developing Spring applications).
Create a Spring Starter Project, it will create the directory structure for you with the spring boot maven dependencies.

Use Link-1 to generate a project. this a basic project for learning. you can understand the folder structure. Use Link-2 for creating a basic Spring boot project. 1: http://start.spring.io/ 2: https://projects.spring.io/spring-boot/

Create a gradle/maven project Automatically src/main/java and src/main/test will be created. create controller/service/Repository package and start writing the code.

-src/main/java(source folder) ---com.package.service(package) ---ServiceClass(Class) ---com.package.controller(package) ---ControllerClass(Class)

You do not need to do anything special to start. Start with a normal java project, either maven or gradle or IDE project layout with starter dependency.

You need just one main class, as per guide here and rest...

There is no constrained package structure. Actual structure will be driven by your requirement/whim and the directory structure is laid by build-tool / IDE

You can follow same structure that you might be following for a Spring MVC application.

You can follow either way

  • A project is divided into layers:

    for example: DDD style

    • Service layer : service package contains service classes
    • DAO/REPO layer : dao package containing dao classes
    • Entity layers


    or

    any layer structure suitable to your problem for which you are writing problem.

  • A project divided into modules or functionalities or features and A module is divided into layers like above

I prefer the second, because it follows Business context. Think in terms of concepts.

What you do is dependent upon how you see the project. It is your code organization skills.

config - class which will read from property files

cache - caching mechanism class files

constants - constant defined class

controller - controller class

exception - exception class

model - pojos classes will be present

security - security classes

service - Impl classes

util - utility classes

validation - validators classes

bootloader - main class

Though this question has an accepted answer, still I would like to share my project structure for RESTful services.

src/main/java
+- com
+- example
+- Application.java
+- ApplicationConstants.java
+- configuration
|   +- ApplicationConfiguration.java
+- controller
|   +- ApplicationController.java
+- dao
|   +- impl
|   |   +- ApplicationDaoImpl.java
|   +- ApplicationDao.java
+- dto
|   +- ApplicationDto.java
+- service
|   +- impl
|   |   +- ApplicationServiceImpl.java
|   +- ApplicationService.java
+- util
|   +- ApplicationUtils.java
+- validation
|   +- impl
|   |   +- ApplicationValidationImpl.java
|   +- ApplicationValidation.java

DAO = Data Access Object.
DTO = Data Transfer Object.

From the docs:, this is the recommended way

The following listing shows a typical layout:

com
+- example
+- myapplication
+- Application.java
+- customer
+- Customer.java
+- CustomerController.java
+- CustomerService.java
+- CustomerRepository.java
+- order
+- order.java
+- OrderController.java
+- OrderService.java
+- OrderRepository. java
                

The Application. java file would declare the main method, along with the basic SpringBootApplication as follows:

package com.example.myapplication;
import org. springframework.boot.springApplication;
import org.springframework.boot.autoconfigure.SpringBootApplication;


@SpringBootApplication public class Application {
public static void main(string[] args)
{
springApplication.run(Application. class, args);
}
}