标签：imp into article arc mongod dbn objectid pom one
This article will be a quick and practical introduction to Spring Data MongoDB.
We’ll go over the basics using both the MongoTemplate as well as MongoRepository using practical tests to illustrate each operation.
The MongoTemplate follows the standard template pattern in Spring and provides a ready to go, basic API to the underlying persistence engine.
The repository follows the Spring Data-centric approach and comes with more flexible and complex API operations, based on the well-known access patterns in all Spring Data projects.
For both, we need to start by defining the dependency – for example, in the pom.xml, with Maven:
|
1
2
3
4
5
|
<dependency> <groupId>org.springframework.data</groupId> <artifactId>spring-data-mongodb</artifactId> <version>1.10.4.RELEASE</version></dependency> |
To check if any new version of the library has been released – track the releases here.
Let’s start with the simple XML configuration for the Mongo template:
|
1
2
|
<mongo:mongo id="mongo" host="localhost" /> <mongo:db-factory id="mongoDbFactory" dbname="test" mongo-ref="mongo" /> |
First, we need to define the factory bean responsible for creating Mongo instances.
Next – we need to actually define (and configure) the template bean:
|
1
2
3
|
<bean id="mongoTemplate" class="org.springframework.data.mongodb.core.MongoTemplate"> <constructor-arg ref="mongoDbFactory"/> </bean> |
And finally we need to define a post processor to translate any MongoExceptionsthrown in @Repository annotated classes:
|
1
2
|
<bean class= "org.springframework.dao.annotation.PersistenceExceptionTranslationPostProcessor"/> |
Let’s now create a similar configuration using Java config by extending the base class for MongoDB configuration AbstractMongoConfiguration:
|
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
|
@Configurationpublic class MongoConfig extends AbstractMongoConfiguration { @Override protected String getDatabaseName() { return "test"; } @Override public Mongo mongo() throws Exception { return new MongoClient("127.0.0.1", 27017); } @Override protected String getMappingBasePackage() { return "org.baeldung"; }} |
Note: We didn’t need to define MongoTemplate bean in the previous configuration as it’s already defined in AbstractMongoConfiguration
We can also use our configuration from scratch without extending AbstractMongoConfiguration – as follows:
|
1
2
3
4
5
6
7
8
9
10
11
12
13
|
@Configurationpublic class SimpleMongoConfig { @Bean public Mongo mongo() throws Exception { return new MongoClient("localhost"); } @Bean public MongoTemplate mongoTemplate() throws Exception { return new MongoTemplate(mongo(), "test"); }} |
To make use of custom repositories (extending the MongoRepository) – we need to continue the configuration from section 3.1 and set up the repositories:
|
1
2
|
<mongo:repositories base-package="org.baeldung.repository" mongo-template-ref="mongoTemplate"/> |
Similarly, we’ll build on the configuration we already created in section 3.2 and add a new annotation into the mix:
|
1
|
@EnableMongoRepositories(basePackages = "org.baeldung.repository") |
Now, after the configuration, we need to create a repository – extending the existing MongoRepository interface:
|
1
2
3
|
public interface UserRepository extends MongoRepository<User, String> { // } |
Now we can auto-wire this UserRepository and use operations from MongoRepository or add custom operations.
Let’s start with the insert operation; let’s also start with a empty database:
|
1
2
|
{} |
Now if we insert a new user:
|
1
2
3
|
User user = new User();user.setName("Jon");mongoTemplate.insert(user, "user"); |
The database will look like this:
|
1
2
3
4
5
|
{ "_id" : ObjectId("55b4fda5830b550a8c2ca25a"), "_class" : "org.baeldung.model.User", "name" : "Jon"} |
The save operation has save-or-update semantics: if an id is present, it performs an update, if not – it does an insert.
Let’s look at the first semantic – the insert; here’s the initial state of the database:
|
1
2
|
{} |
When we now save a new user:
|
1
2
3
|
User user = new User();user.setName("Albert"); mongoTemplate.save(user, "user"); |
The entity will be inserted in the database:
|
1
2
3
4
5
|
{ "_id" : ObjectId("55b52bb7830b8c9b544b6ad5"), "_class" : "org.baeldung.model.User", "name" : "Albert"} |
Next, we’ll look at the same operation – save – with update semantics.
Let’s now look at save with update semantics, operating on an existing entity:
|
1
2
3
4
5
|
{ "_id" : ObjectId("55b52bb7830b8c9b544b6ad5"), "_class" : "org.baeldung.model.User", "name" : "Jack"} |
Now, when we save the existing user – we will update it:
|
1
2
3
4
|
user = mongoTemplate.findOne( Query.query(Criteria.where("name").is("Jack")), User.class);user.setName("Jim");mongoTemplate.save(user, "user"); |
The database will look like this:
|
1
2
3
4
5
|
{ "_id" : ObjectId("55b52bb7830b8c9b544b6ad5"), "_class" : "org.baeldung.model.User", "name" : "Jim"} |
As you can see, in this particular example, save uses the semantics of update, because we use an object with given _id.
updateFirst updates the very first document that matches the query.
Let’s start with the initial state of the database:
|
1
2
3
4
5
6
7
8
9
10
11
12
|
[ { "_id" : ObjectId("55b5ffa5511fee0e45ed614b"), "_class" : "org.baeldung.model.User", "name" : "Alex" }, { "_id" : ObjectId("55b5ffa5511fee0e45ed614c"), "_class" : "org.baeldung.model.User", "name" : "Alex" }] |
When we now run the updateFirst:
|
1
2
3
4
5
|
Query query = new Query();query.addCriteria(Criteria.where("name").is("Alex"));Update update = new Update();update.set("name", "James");mongoTemplate.updateFirst(query, update, User.class); |
Only the first entry will be updated:
|
1
2
3
4
5
6
7
8
9
10
11
12
|
[ { "_id" : ObjectId("55b5ffa5511fee0e45ed614b"), "_class" : "org.baeldung.model.User", "name" : "James" }, { "_id" : ObjectId("55b5ffa5511fee0e45ed614c"), "_class" : "org.baeldung.model.User", "name" : "Alex" }] |
UpdateMulti updates all document that matches the given query.
First – here’s the state of the database before doing the updateMulti:
|
1
2
3
4
5
6
7
8
9
10
11
12
|
[ { "_id" : ObjectId("55b5ffa5511fee0e45ed614b"), "_class" : "org.baeldung.model.User", "name" : "Eugen" }, { "_id" : ObjectId("55b5ffa5511fee0e45ed614c"), "_class" : "org.baeldung.model.User", "name" : "Eugen" }] |
Now, let’s now run the updateMulti operation:
|
1
2
3
4
5
|
Query query = new Query();query.addCriteria(Criteria.where("name").is("Eugen"));Update update = new Update();update.set("name", "Victor");mongoTemplate.updateMulti(query, update, User.class); |
Both existing objects will be updated in the database:
|
1
2
3
4
5
6
7
8
9
10
11
12
|
[ { "_id" : ObjectId("55b5ffa5511fee0e45ed614b"), "_class" : "org.baeldung.model.User", "name" : "Victor" }, { "_id" : ObjectId("55b5ffa5511fee0e45ed614c"), "_class" : "org.baeldung.model.User", "name" : "Victor" }] |
This operation works like updateMulti, but it returns the object before it was modified.
First – the state of the database before calling findAndModify:
|
1
2
3
4
5
|
{ "_id" : ObjectId("55b5ffa5511fee0e45ed614b"), "_class" : "org.baeldung.model.User", "name" : "Markus"} |
Let’s look at actual operation code:
|
1
2
3
4
5
|
Query query = new Query();query.addCriteria(Criteria.where("name").is("Markus"));Update update = new Update();update.set("name", "Nick");User user = mongoTemplate.findAndModify(query, update, User.class); |
The returned user object has the same values as the initial state in the database.
However, the new state in the database is:
|
1
2
3
4
5
|
{ "_id" : ObjectId("55b5ffa5511fee0e45ed614b"), "_class" : "org.baeldung.model.User", "name" : "Nick"} |
The upsert works operate on the find and modify else create semantics: if the document is matched, update it, else create a new document by combining the query and update object.
Let’s start with the initial state of the database:
|
1
2
3
4
5
|
{ "_id" : ObjectId("55b5ffa5511fee0e45ed614b"), "_class" : "org.baeldung.model.User", "name" : "Markus"} |
Now – let’s run the upsert:
|
1
2
3
4
5
|
Query query = new Query();query.addCriteria(Criteria.where("name").is("Markus"));Update update = new Update();update.set("name", "Nick");mongoTemplate.upsert(query, update, User.class); |
Here’s the state of the database after the operation:
|
1
2
3
4
5
|
{ "_id" : ObjectId("55b5ffa5511fee0e45ed614b"), "_class" : "org.baeldung.model.User", "name" : "Nick"} |
The state of the database before calling remove:
|
1
2
3
4
5
|
{ "_id" : ObjectId("55b5ffa5511fee0e45ed614b"), "_class" : "org.baeldung.model.User", "name" : "Benn"} |
Let’s now run remove:
|
1
|
mongoTemplate.remove(user, "user"); |
The result will be as expected:
|
1
2
|
{} |
First – the state of the database before running the insert:
|
1
2
|
{} |
Now, when we insert a new user:
|
1
2
3
|
User user = new User();user.setName("Jon");userRepository.insert(user); |
Here’s the end state of the database:
|
1
2
3
4
5
|
{ "_id" : ObjectId("55b4fda5830b550a8c2ca25a"), "_class" : "org.baeldung.model.User", "name" : "Jon"} |
Note how the operation works the same as the insert in the MongoTemplate API.
Similarly – save works the same as the save operation in the MongoTemplate API.
Let’s start by looking at the insert semantics of the operation; here’s the initial state of the database:
|
1
2
|
{} |
Now – we execute the save operation:
|
1
2
3
|
User user = new User();user.setName("Aaron");userRepository.save(user); |
This results in the user being added to the database:
|
1
2
3
4
5
|
{ "_id" : ObjectId("55b52bb7830b8c9b544b6ad5"), "_class" : "org.baeldung.model.User", "name" : "Aaron"} |
Note again how, in this example, save works with insert semantics, because we are inserting a new object.
Let’s now look at the same operation but with update semantics.
First – here’s the state of the database before running the new save:
|
1
2
3
4
5
|
{ "_id" : ObjectId("55b52bb7830b8c9b544b6ad5"), "_class" : "org.baeldung.model.User", "name" : "Jack"81*6} |
Now – we execute the operation:
|
1
2
3
4
|
user = mongoTemplate.findOne( Query.query(Criteria.where("name").is("Jack")), User.class);user.setName("Jim");userRepository.save(user); |
Finally, here is the state of the database:
|
1
2
3
4
5
|
{ "_id" : ObjectId("55b52bb7830b8c9b544b6ad5"), "_class" : "org.baeldung.model.User", "name" : "Jim"} |
Note again how, in this example, save works with update semantics, because we are using an existing object.
The state of the database before calling delete:
|
1
2
3
4
5
|
{ "_id" : ObjectId("55b5ffa5511fee0e45ed614b"), "_class" : "org.baeldung.model.User", "name" : "Benn"} |
Let’s run delete:
|
1
|
userRepository.delete(user); |
The result will simply be:
|
1
2
|
{} |
The state of the database when findOne is called:
|
1
2
3
4
5
|
{ "_id" : ObjectId("55b5ffa5511fee0e45ed614b"), "_class" : "org.baeldung.model.User", "name" : "Chris"} |
Let’s now execute the findOne:
|
1
|
userRepository.findOne(user.getId()) |
The result which will return the existing data:
|
1
2
3
4
5
|
{ "_id" : ObjectId("55b5ffa5511fee0e45ed614b"), "_class" : "org.baeldung.model.User", "name" : "Chris"} |
The state of the database before calling exists:
|
1
2
3
4
5
|
{ "_id" : ObjectId("55b5ffa5511fee0e45ed614b"), "_class" : "org.baeldung.model.User", "name" : "Harris"} |
Now, let’s run exists:
|
1
|
boolean isExists = userRepository.exists(user.getId()); |
Which of course will return true.
The state of the database before calling findAll:
|
1
2
3
4
5
6
7
8
9
10
11
12
|
[ { "_id" : ObjectId("55b5ffa5511fee0e45ed614b"), "_class" : "org.baeldung.model.User", "name" : "Brendan" }, { "_id" : ObjectId("67b5ffa5511fee0e45ed614b"), "_class" : "org.baeldung.model.User", "name" : "Adam" }] |
Let’s now run findAll with Sort:
|
1
|
List<User> users = userRepository.findAll(new Sort(Sort.Direction.ASC, "name")); |
The result will be sorted by name in ascending order:
|
1
2
3
4
5
6
7
8
9
10
11
12
|
[ { "_id" : ObjectId("67b5ffa5511fee0e45ed614b"), "_class" : "org.baeldung.model.User", "name" : "Adam" }, { "_id" : ObjectId("55b5ffa5511fee0e45ed614b"), "_class" : "org.baeldung.model.User", "name" : "Brendan" }] |
The state of the database before calling findAll:
|
1
2
3
4
5
6
7
8
9
10
11
12
|
[ { "_id" : ObjectId("55b5ffa5511fee0e45ed614b"), "_class" : "org.baeldung.model.User", "name" : "Brendan" }, { "_id" : ObjectId("67b5ffa5511fee0e45ed614b"), "_class" : "org.baeldung.model.User", "name" : "Adam" }] |
Let’s now execute findAll with a pagination request:
|
1
2
3
|
Pageable pageableRequest = new PageRequest(0, 1);Page<User> page = userRepository.findAll(pageableRequest);List<User> users = pages.getContent(); |
The result in users list will be only one user:
|
1
2
3
4
5
|
{ "_id" : ObjectId("55b5ffa5511fee0e45ed614b"), "_class" : "org.baeldung.model.User", "name" : "Brendan"} |
Finally, let’s also go over the simple annotations that Spring Data uses to drive these API operations.
|
1
2
|
@Idprivate String id; |
The field level @Id annotation can decorate any type, including long and string.
If the value of the @Id field is not null, it’s stored in the database as-is; otherwise, the converter will assume you want to store an ObjectId in the database (eitherObjectId, String or BigInteger work).
Next – @Document:
|
1
2
3
4
|
@Documentpublic class User { //} |
This annotation simply marks a class as being a domain object that needs to be persisted to the database, along with allowing us to choose the name of the collection to be used.
This article was a quick but comprehensive introduction to using MongoDB with Spring Data, both via the MongoTemplate API as well as making use of MongoRepository.
The implementation of all these examples and code snippets can be found over on Github – this is a Maven-based project, so it should be easy to import and run as it is.
Introduction to Spring Data MongoDB
标签：imp into article arc mongod dbn objectid pom one
原文地址：https://www.cnblogs.com/pejsidney/p/8989867.html
