Spring Data MongoDB - Spring Web Services - Parent - SpringSource
Spring Data MongoDB - Spring Web Services - Parent - SpringSource Spring Data MongoDB - Spring Web Services - Parent - SpringSource
please define productname in your docbook file!• CommandResult executeCommand (String jsonCommand) Execute the a MongoDBcommand expressed as a JSON string.5.13 Lifecycle EventsBuilt into the MongoDB mapping framework are severalorg.springframework.context.ApplicationEvent events that your application can respondto by registering special beans in the ApplicationContext. By being based off Spring'sApplicationContext event infastructure this enables other products, such as Spring Integration, to easilyreceive these events as they are a well known eventing mechanism in Spring based applications.To intercept an object before it goes through the conversion process (which turns your domain objectinto a com.mongodb.DBObject), you'd register a subclass of AbstractMongoEventListener thatoverrides the onBeforeConvert method. When the event is dispatched, your listener will be calledand passed the domain object before it goes into the converter.public class BeforeConvertListener extends AbstractMongoEventListener {@Overridepublic void onBeforeConvert(Person p) {... does some auditing manipulation, set timestamps, whatever ...}}Example 5.25To intercept an object before it goes into the database, you'd register a subclass oforg.springframework.data.mongodb.core.mapping.event.AbstractMongoEventListenerthat overrides the onBeforeSave method. When the event is dispatched, your listener will be calledand passed the domain object and the converted com.mongodb.DBObject.public class BeforeSaveListener extends AbstractMongoEventListener {@Overridepublic void onBeforeSave(Person p, DBObject dbo) {… change values, delete them, whatever …}}Example 5.26Simply declaring these beans in your Spring ApplicationContext will cause them to be invoked wheneverthe event is dispatched.The list of callback methods that are present in AbstractMappingEventListener are• onBeforeConvert - called in MongoTemplate insert, insertList and save operations before theobject is converted to a DBObject using a MongoConveter.• onBeforeSave - called in MongoTemplate insert, insertList and save operations before inserting/saving the DBObject in the database.• onAfterSave - called in MongoTemplate insert, insertList and save operations after inserting/savingthe DBObject in the database.• onAfterLoad - called in MongoTempnlate find, findAndRemove, findOne and getCollection methodsafter the DBObject is retrieved from the database.1.4.0.BUILD-SNAPSHOTSpring Data MongoDB -Reference Documentation 65
please define productname in your docbook file!• onAfterConvert - called in MongoTempnlate find, findAndRemove, findOne and getCollectionmethods after the DBObject retrieved from the database was converted to a POJO.5.14 Exception TranslationThe Spring framework provides exception translation for a wide variety of database andmapping technologies. This has traditionally been for JDBC and JPA. The Spring support forMongoDB extends this feature to the MongoDB Database by providing an implementation of theorg.springframework.dao.support.PersistenceExceptionTranslator interface.The motivation behind mapping to Spring's consistent data access exception hierarchy is that youare then able to write portable and descriptive exception handling code without resorting to codingagainst MongoDB error codes. All of Spring's data access exceptions are inherited from the rootDataAccessException class so you can be sure that you will be able to catch all database relatedexception within a single try-catch block. Note, that not all exceptions thrown by the MongoDB driverinherit from the MongoException class. The inner exception and message are preserved so noinformation is lost.Some of the mappings performed by the MongoExceptionTranslator are: com.mongodb.Networkto DataAccessResourceFailureException and MongoException error codes 1003, 12001, 12010,12011, 12012 to InvalidDataAccessApiUsageException. Look into the implementation for moredetails on the mapping.5.15 Execution callbacksOne common design feature of all Spring template classes is that all functionality is routed into one of thetemplates execute callback methods. This helps ensure that exceptions and any resource managementthat maybe required are performed consistency. While this was of much greater need in the case ofJDBC and JMS than with MongoDB, it still offers a single spot for exception translation and logging tooccur. As such, using thexe execute callback is the preferred way to access the MongoDB driver's DBand DBCollection objects to perform uncommon operations that were not exposed as methods onMongoTemplate.Here is a list of execute callback methods.• T execute (Class entityClass, CollectionCallback action) Executesthe given CollectionCallback for the entity collection of the specified class.• T execute (String collectionName, CollectionCallback action) Executesthe given CollectionCallback on the collection of the given name.• T execute (DbCallback action) Spring Data MongoDB provides supportfor the Aggregation Framework introduced to MongoDB in version 2.2. Executesa DbCallback translating any exceptions as necessary.• T execute (String collectionName, DbCallback action) Executes aDbCallback on the collection of the given name translating any exceptions as necessary.• T executeInSession (DbCallback action) Executes the given DbCallback within thesame connection to the database so as to ensure consistency in a write heavy environment whereyou may read the data that you wrote.1.4.0.BUILD-SNAPSHOTSpring Data MongoDB -Reference Documentation 66
- Page 20 and 21: please define productname in your d
- Page 22 and 23: please define productname in your d
- Page 24 and 25: please define productname in your d
- Page 26 and 27: please define productname in your d
- Page 28 and 29: please define productname in your d
- Page 30 and 31: please define productname in your d
- Page 32 and 33: please define productname in your d
- Page 34 and 35: please define productname in your d
- Page 36 and 37: please define productname in your d
- Page 38 and 39: please define productname in your d
- Page 40 and 41: please define productname in your d
- Page 42 and 43: please define productname in your d
- Page 44 and 45: please define productname in your d
- Page 46 and 47: please define productname in your d
- Page 48 and 49: please define productname in your d
- Page 50 and 51: please define productname in your d
- Page 52 and 53: please define productname in your d
- Page 54 and 55: please define productname in your d
- Page 56 and 57: please define productname in your d
- Page 58 and 59: please define productname in your d
- Page 60 and 61: please define productname in your d
- Page 62 and 63: please define productname in your d
- Page 64 and 65: please define productname in your d
- Page 66 and 67: please define productname in your d
- Page 68 and 69: please define productname in your d
- Page 72 and 73: please define productname in your d
- Page 74 and 75: please define productname in your d
- Page 76 and 77: please define productname in your d
- Page 78 and 79: please define productname in your d
- Page 80 and 81: please define productname in your d
- Page 82 and 83: please define productname in your d
- Page 84 and 85: please define productname in your d
- Page 86 and 87: please define productname in your d
- Page 88 and 89: please define productname in your d
- Page 90 and 91: please define productname in your d
- Page 92 and 93: please define productname in your d
- Page 94 and 95: please define productname in your d
- Page 96 and 97: please define productname in your d
- Page 98 and 99: please define productname in your d
- Page 100 and 101: please define productname in your d
- Page 102 and 103: please define productname in your d
- Page 104: please define productname in your d
please define productname in your docbook file!• onAfterConvert - called in MongoTempnlate find, findAndRemove, findOne and getCollectionmethods after the DBObject retrieved from the database was converted to a POJO.5.14 Exception TranslationThe <strong>Spring</strong> framework provides exception translation for a wide variety of database andmapping technologies. This has traditionally been for JDBC and JPA. The <strong>Spring</strong> support for<strong>MongoDB</strong> extends this feature to the <strong>MongoDB</strong> <strong>Data</strong>base by providing an implementation of theorg.springframework.dao.support.PersistenceExceptionTranslator interface.The motivation behind mapping to <strong>Spring</strong>'s consistent data access exception hierarchy is that youare then able to write portable and descriptive exception handling code without resorting to codingagainst <strong>MongoDB</strong> error codes. All of <strong>Spring</strong>'s data access exceptions are inherited from the root<strong>Data</strong>AccessException class so you can be sure that you will be able to catch all database relatedexception within a single try-catch block. Note, that not all exceptions thrown by the <strong>MongoDB</strong> driverinherit from the MongoException class. The inner exception and message are preserved so noinformation is lost.Some of the mappings performed by the MongoExceptionTranslator are: com.mongodb.Networkto <strong>Data</strong>AccessResourceFailureException and MongoException error codes 1003, 12001, 12010,12011, 12012 to Invalid<strong>Data</strong>AccessApiUsageException. Look into the implementation for moredetails on the mapping.5.15 Execution callbacksOne common design feature of all <strong>Spring</strong> template classes is that all functionality is routed into one of thetemplates execute callback methods. This helps ensure that exceptions and any resource managementthat maybe required are performed consistency. While this was of much greater need in the case ofJDBC and JMS than with <strong>MongoDB</strong>, it still offers a single spot for exception translation and logging tooccur. As such, using thexe execute callback is the preferred way to access the <strong>MongoDB</strong> driver's DBand DBCollection objects to perform uncommon operations that were not exposed as methods onMongoTemplate.Here is a list of execute callback methods.• T execute (Class entityClass, CollectionCallback action) Executesthe given CollectionCallback for the entity collection of the specified class.• T execute (String collectionName, CollectionCallback action) Executesthe given CollectionCallback on the collection of the given name.• T execute (DbCallback action) <strong>Spring</strong> <strong>Data</strong> <strong>MongoDB</strong> provides supportfor the Aggregation Framework introduced to <strong>MongoDB</strong> in version 2.2. Executesa DbCallback translating any exceptions as necessary.• T execute (String collectionName, DbCallback action) Executes aDbCallback on the collection of the given name translating any exceptions as necessary.• T executeInSession (DbCallback action) Executes the given DbCallback within thesame connection to the database so as to ensure consistency in a write heavy environment whereyou may read the data that you wrote.1.4.0.BUILD-SNAPSHOT<strong>Spring</strong> <strong>Data</strong> <strong>MongoDB</strong> -Reference Documentation 66
Change language