此文档是毕业设计外文翻译成品( 含英文原文+中文翻译)，无需调整复杂的格式！下载之后直接可用，方便快捷！本文价格不贵,也就几十块钱！一辈子也就一次的事！

外文标题：Data Access with Spring Boot

外文作者：Felipe Gutierrez

文献出处: Pro Spring Boot pp 121-147，2018 (如觉得年份太老，可改为近2年，毕竟很多毕业生都这样做)

英文4434单词，27307字符(字符就是印刷符)，中文7050汉字。

Data Access with Spring Boot

Data has become the most important part of the IT world, from trying to access, persist, and analyze it, to using a few bytes to petabytes of information. There have been many attempts to create frameworks and libraries to facilitate a way for developers to interact with the data, but sometimes this becomes too complicated. After version 3.0, the Spring Framework created different teams that specialized in the different technologies. The Spring Data project team was born. This particular project’s goal is to simplify uses of data access technologies, from relational and non- relational databases, to map-reduce frameworks and cloud-based data services. This Spring Data project is a collection of subprojects specific to a given database. This chapter covers data access with Spring Boot using the ToDo application from previous chapters. You are going to make the ToDo app work with SQL and NoSQL databases. Let’s get started.

SQL Databases

Do you remember those days when (in the Java world) you needed to deal with all the JDBC (Java Database Connectivity) tasks? You had to download the correct drivers and connection strings, open and close connections, SQL statements, result sets, and transactions, and convert from result sets to objects. In my opinion, these are all very manual tasks. Then a lot of ORM (object-relational mapping) frameworks started to emerge to manage these tasks—frameworks like Castor XML, ObjectStore, and Hibernate, to mention a few. They allowed you to identify the domain classes and create XML that was related to the database’s tables. At some point, you also needed to be an expert to manage those kinds of frameworks.

The Spring Framework helped a lot with those frameworks by following the

英文原文

Spring

contains

a

lot

of

functionality

and

features,

which

are

well-organized

in

seven

modules shown in the diagram below. This section discusses each the of modules in turn.

The

Core

package

is

the

most

fundamental

part

of

the

framework

and

provides

the

Dependency

Injection

features

allowing

you

to

manage

bean

container

functionality.

The

basic

concept

here

is

the

BeanFactory,

which

provides

a

factory

pattern

removing

the

need

for

programmatic

singletons

and

allowing

you

to

decouple

the

configuration

and

specification

of

dependencies from your actual program logic.

On top of the Core package sits the Context package, providing a way to access beans in a

framework-style manner, somewhat resembling a JNDI-registry. The context package inherits its

features from the beans package and adds support for text messaging using e.g. resource bundles,

event-propagation, resource-loading and transparent creation of contexts by, for example, a servlet

container.

The DAO

package

provides

a JDBC-abstraction

layer

that

removes

the

need

to

do

tedious

JDBC

coding

and

parsing

of

database-vendor

specific

error

codes.

Also,

the

JDBC

package

provides a way to do programmatic as well as declarative transaction management, not only for

classes implementing special interfaces, but for all your POJOs (plain old java objects).

The ORM

package provides

integration

layers

for

popular

object-relational

mapping

APIs,

including JDO, Hibernate and iBatis. Using the ORM package you can use all those O/R-mappers

in

combination

with

all

the

other

features

Spring

offers,

like

simple

declarative

transaction

management mentioned before.

Spring's

AOP

package

provides

an

AOP

Alliance

compliant

aspect-oriented

programming

implementation allowing you to define, for example, method-interceptors and pointcuts to cleanly

decouple

code

implementing

functionality

that

should

logically

speaking

be

separated.

Using

source-level

metadata functionality

you can incorporate all kinds of behavioral information into

your code, a little like .NET attributes.

Spring's

Web

package

provides

basic

web-oriented

integration

features,

such

as

multipart

functionality,

initialization

of

contexts

using

servlet

listeners

and

a

web-oriented

application

context. When using Spring together with WebWork or Struts, this is the package to integrate with.

Spring's

Web

MVC

package

provides

a

Model-View-Controller

implementation

for

web-applications.

Spring's

MVC

implementation

is

not

just

any

implementation,

it

provides

a

clean separation between domain model code and web forms and allows you to use all the other

features of the Spring Framework like validation.

Spring's

web

MVC

framework

is

designed

around

a

DispatcherServlet

that

dispatches

requests

to

handlers,

with

configurable

handler

mappings,

view

resolution,

locale

and

theme

resolution

as

well

as

support

for

upload

files.

The

default

handler

is

a

very

simple

Controller

interface,

just

offering

a

ModelAndView

handleRequest(request,response)

method.

This

can

already

be

used

for

application

controllers,

but

you

will

prefer

the

included

implementation

hierarchy,

consisting

of,

for

example

AbstractController,

AbstractCommandController

and

SimpleFormController. Application controllers will typically be subclasses of those. Note that you

CHAPTER 5

Data Access with

Spring Boot

Data has become the most important part of the IT world, from trying to access, persist,

and analyze it, to using a few bytes to petabytes of information. There have been many

attempts to create frameworks and libraries to facilitate a way for developers to interact

with the data, but sometimes this becomes too complicated.

After version 3.0, the Spring Framework created different teams that specialized

in the different technologies. The Spring Data project team was born. This particular

project’s goal is to simplify uses of data access technologies, from relational and non-

relational databases, to map-reduce frameworks and cloud-based data services. This

Spring Data project is a collection of subprojects specific to a given database.

This chapter covers data access with Spring Boot using the ToDo application from

previous chapters. You are going to make the ToDo app work with SQL and NoSQL

databases. Let’s get started.

SQL Databases

Do you remember those days when (in the Java world) you needed to deal with all the

JDBC (Java Database Connectivity) tasks? You had to download the correct drivers

and connection strings, open and close connections, SQL statements, result sets, and

transactions, and convert from result sets to objects. In my opinion, these are all very

manual tasks. Then a lot of ORM (object-relational mapping) frameworks started

to emerge to manage these tasks—frameworks like Castor XML, ObjectStore, and

Hibernate, to mention a few. They allowed you to identify the domain classes and create

XML that was related to the database’s tables. At some point, you also needed to be an

expert to manage those kinds of frameworks.

127

© Felipe Gutierrez 2019

F. Gutierrez, Pro Spring Boot 2, /10.1007/978-1-4842-3676-5_5

Chapter 5 Data aCCess with spring Boot

The Spring Framework helped a