From ce156c1344fbe35d93c51d2d013d20977253235b Mon Sep 17 00:00:00 2001 From: Oliver Gierke Date: Sat, 4 Jul 2015 19:07:09 +0200 Subject: [PATCH] DATAMONGO-1250 - Fixed inline code formatting in reference docs. --- src/main/asciidoc/reference/mongodb.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/main/asciidoc/reference/mongodb.adoc b/src/main/asciidoc/reference/mongodb.adoc index 4685f7f89..a7a8c3c89 100644 --- a/src/main/asciidoc/reference/mongodb.adoc +++ b/src/main/asciidoc/reference/mongodb.adoc @@ -2013,7 +2013,7 @@ class MyConverter implements Converter { … } class MyConverter implements Converter { … } ---- -In case you write a `Converter` whose source and target type are native Mongo types there's no way for us to determine whether we should consider it as reading or writing converter. Registering the converter instance as both might lead to unwanted results then. E.g. a `Converter` is ambiguous although it probably does not make sense to try to convert all `String`s into `Long`s when writing. To be generally able to force the infrastructure to register a converter for one way only we provide `@ReadingConverter` as well as `@WritingConverter` to be used at the converter implementation. +In case you write a `Converter` whose source and target type are native Mongo types there's no way for us to determine whether we should consider it as reading or writing converter. Registering the converter instance as both might lead to unwanted results then. E.g. a `Converter` is ambiguous although it probably does not make sense to try to convert all `String` instances into `Long` instances when writing. To be generally able to force the infrastructure to register a converter for one way only we provide `@ReadingConverter` as well as `@WritingConverter` to be used at the converter implementation. [[mongo-template.index-and-collections]] == Index and Collection management