Spring 整合 MongoDB 开发指南

3星 · 超过75%的资源需积分: 9 196 浏览量更新于2024-07-27 收藏 275KB PDF 举报

Spring-MongoDB整合文档本文档旨在介绍Spring与MongoDB的整合技术，旨在帮助开发者快速了解Spring Data MongoDB的使用方法和实现原理。 Spring Data MongoDB简介 Spring Data MongoDB是Spring Framework的一部分，提供了对MongoDB的支持，允许开发者使用Spring的方式来操作MongoDB数据库。Spring Data MongoDB提供了一个丰富的API，允许开发者使用Java语言来操作MongoDB数据库。为什么选择Spring Data MongoDB？选择Spring Data MongoDB的原因有很多，以下是一些主要的原因： * Spring Data MongoDB提供了一个简洁的API，允许开发者快速了解和使用MongoDB数据库。 * Spring Data MongoDB提供了丰富的功能，包括数据访问、数据映射、数据查询等。 * Spring Data MongoDB支持Spring Framework的所有特性，包括依赖注入、AOP等。 Spring Data MongoDB的主要特性 Spring Data MongoDB的主要特性包括： * 简洁的API：Spring Data MongoDB提供了一个简洁的API，允许开发者快速了解和使用MongoDB数据库。 * 丰富的功能：Spring Data MongoDB提供了丰富的功能，包括数据访问、数据映射、数据查询等。 * 高度灵活性：Spring Data MongoDB支持Spring Framework的所有特性，包括依赖注入、AOP等。 Spring Data MongoDB的应用场景 Spring Data MongoDB的应用场景包括： * 数据存储：Spring Data MongoDB可以用于存储大量的数据，例如日志、监控数据等。 * 数据分析：Spring Data MongoDB可以用于数据分析，例如数据挖掘、数据报表等。 * 实时数据处理：Spring Data MongoDB可以用于实时数据处理，例如实时监控、实时报表等。 Repositories 在Spring Data MongoDB中，Repositories是核心组件之一。Repositories提供了一个抽象层，允许开发者使用Java语言来操作MongoDB数据库。Repositories提供了多种方法来操作MongoDB数据库，包括数据访问、数据映射、数据查询等。 Query Methods 在Spring Data MongoDB中，Query Methods是Repositories的一部分。Query Methods提供了多种方法来查询MongoDB数据库，包括简单查询、复杂查询等。Query Methods支持多种查询语言，包括MongoDB的原生查询语言等。 Custom Implementations 在Spring Data MongoDB中，Custom Implementations是允许开发者自定义Repositories的实现。Custom Implementations提供了多种方法来自定义Repositories，包括添加自定义行为、添加自定义查询方法等。 Extensions 在Spring Data MongoDB中，Extensions是Repositories的一部分。Extensions提供了多种方法来扩展Repositories的功能，包括添加自定义行为、添加自定义查询方法等。Extensions支持多种扩展方式，包括使用Spring Framework的AOP等。 MongoDB支持在Spring Data MongoDB中，MongoDB支持是核心组件之一。MongoDB支持提供了多种方法来操作MongoDB数据库，包括数据访问、数据映射、数据查询等。MongoDB支持支持多种MongoDB版本，包括最新的MongoDB 4.x版本等。

dynamically.

Example 4.5. Using Pageable and Sort in query methods

Page<User> findByLastname(String lastname, Pageable pageable);

List<User> findByLastname(String lastname, Sort sort);

List<User> findByLastname(String lastname, Pageable pageable);

The first method allows you to pass a org.springframework.data.domain.Pageable instance to the query

method to dynamically add paging to your statically defined query. Sorting options are handed via the

Pageable instance too. If you only need sorting, simply add an org.springframework.data.domain.Sort

parameter to your method. As you also can see, simply returning a List is possible as well. We will then not

retrieve the additional metadata required to build the actual Page instance but rather simply restrict the query to

lookup only the given range of entities.

Note

To find out how many pages you get for a query entirely we have to trigger an additional count

query. This will be derived from the query you actually trigger by default.

4.3.3. Creating repository instances

So now the question is how to create instances and bean definitions for the repository interfaces defined.

4.3.3.1. XML Configuration

The easiest way to do so is by using the Spring namespace that is shipped with each Spring Data module that

supports the repository mechanism. Each of those includes a repositories element that allows you to simply

define a base package that Spring will scan for you.

<?xml version="1.0" encoding="UTF-8"?>

<beans:beans xmlns:beans="http://www.springframework.org/schema/beans"

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

xmlns="http://www.springframework.org/schema/data/jpa"

xsi:schemaLocation="http://www.springframework.org/schema/beans

http://www.springframework.org/schema/beans/spring-beans.xsd

http://www.springframework.org/schema/data/jpa

http://www.springframework.org/schema/data/jpa/spring-jpa.xsd">

</beans:beans>

In this case we instruct Spring to scan com.acme.repositories and all its sub packages for interfaces extending

Repository or one of its sub-interfaces. For each interface found it will register the persistence technology

specific FactoryBean to create the according proxies that handle invocations of the query methods. Each of

these beans will be registered under a bean name that is derived from the interface name, so an interface of

UserRepository would be registered under userRepository. The base-package attribute allows the use of

wildcards, so that you can have a pattern of scanned packages.

Using filters

Repositories

Spring Data Document () 10

JavaConfig in the Spring reference documentation -

http://static.springsource.org/spring/docs/3.1.x/spring-framework-reference/html/beans.html#beans-java

By default we will pick up every interface extending the persistence technology specific Repository

sub-interface located underneath the configured base package and create a bean instance for it. However, you

might want finer grained control over which interfaces bean instances get created for. To do this we support the

use of <include-filter /> and <exclude-filter /> elements inside <repositories />. The semantics are

exactly equivalent to the elements in Spring's context namespace. For details see Spring reference

documentation on these elements.

E.g. to exclude certain interfaces from instantiation as repository, you could use the following configuration:

Example 4.6. Using exclude-filter element

<context:exclude-filter type="regex" expression=".*SomeRepository" />

</repositories>

This would exclude all interfaces ending in SomeRepository from being instantiated.

4.3.3.2. JavaConfig

The repository infrastructure can also be triggered using a store-specific @Enable${store}Repositories

annotation on a JavaConfig class. For an introduction into Java based configuration of the Spring container

please have a look at the reference documentation.

A sample configuration to enable Spring Data repositories would look something like this.

Example 4.7. Sample annotation based repository configuration

@Configuration

@EnableJpaRepositories("com.acme.repositories")

class ApplicationConfiguration {

@Bean

public EntityManagerFactory entityManagerFactory() {

// …

}

Note that the sample uses the JPA specific annotation which would have to be exchanged dependingon which

store module you actually use. The same applies to the definition of the EntityManagerFactory bean. Please

consult the sections covering the store-specific configuration.

4.3.3.3. Standalone usage

You can also use the repository infrastructure outside of a Spring container usage. You will still need to have

some of the Spring libraries on your classpath but you can generally setup repositories programmatically as

well. The Spring Data modules providing repository support ship a persistence technology specific

RepositoryFactory that can be used as follows:

Example 4.8. Standalone usage of repository factory

Repositories

Spring Data Document () 11

剩余80页未读，继续阅读

于瓜瓜

粉丝: 29
资源: 16

Spring 整合 MongoDB 开发指南

Spring-Data-MongoDB3.2

spring-springMVC-mongodb整合例子

Error creating bean with name 'mongo'

springboot整合mangodb

SpringBoot 整合 mongodb 实现 持久化存储

springboot整合mongodb

如何用springboot整合mongodb?

springboot 整合mongodb

springboot整合mongodb事务

springboot整合mongodb的demo

最新资源

SpringBoot 整合 mongodb 实现持久化存储