Update documentation

- Correct the doc manual and java api links

- Add release notes

Author: rainboyan

src/docs/guide/gettingStarted.adoc

@@ -1,58 +1,26 @@
-=== Basic Setup
+== Basic Setup
 
 To get started with GORM for MongoDB within Grails you need configure it as a dependency in `build.gradle`:
 
 [source,groovy,subs="attributes"]
 ----
 dependencies {
-    compile 'org.grails.plugins:mongodb:{pluginVersion}'
+    implementation 'org.graceframework.plugins:mongodb:{version}'
 }
 ----
 
-=== Common Errors
-
-If you receive an error that indicates a failure to resolve the `grails-datastore-simple` dependency you may need to add the following to `build.gradle` directly above the `dependencies` block:
-
-[source,groovy]
-.build.gradle
-----
-configurations.all {
-    exclude module:'grails-datastore-simple'
-}
-----
-
-If you receive an error at runtime such as:
-
-[source,groovy]
-----
-Caused by: org.bson.codecs.configuration.CodecConfigurationException: Can't find a codec for class org.bson.BsonDecimal128.
-        at org.bson.codecs.configuration.CodecCache.getOrThrow(CodecCache.java:46)
-        at org.bson.codecs.configuration.ProvidersCodecRegistry.get(ProvidersCodecRegistry.java:63)
-        at org.bson.codecs.configuration.ChildCodecRegistry.get(ChildCodecRegistry.java:51)
-        at org.bson.codecs.BsonTypeCodecMap.<init>(BsonTypeCodecMap.java:44)
-        at org.bson.codecs.BsonDocumentCodec.<init>(BsonDocumentCodec.java:65)
-----
-
-It means you have an older version of the MongoDB Java driver on your classpath and you should add the following declaration to `build.gradle` to ensure the dependency is correct:
-
-[source,groovy,subs="attributes"]
-.build.gradle
-----
-compile "org.mongodb:mongodb-driver:{mongoDriverVersion}"
-----
-
-=== Configuring MongoDB
+== Configuring MongoDB
 
 With that done you need to set up a running MongoDB server. Refer to the https://docs.mongodb.com/getting-started/shell/[MongoDB Documentation] for an explanation on how to startup a MongoDB instance. Once installed, starting MongoDB is typically a matter of executing the following command:
 
-[source,groovy]
+[source,console]
 ----
 MONGO_HOME/bin/mongod
 ----
 
 With the above command executed in a terminal window you should see output like the following appear:
 
-[source,groovy]
+[source,console]
 ----
 2015-11-18T19:38:50.073+0100 I JOURNAL  <<initandlisten>> journal dir=/data/db/journal
 2015-11-18T19:38:50.073+0100 I JOURNAL  <<initandlisten>> recover : no journal files present, no recovery needed
@@ -71,9 +39,9 @@ With the above command executed in a terminal window you should see output like
 2015-11-18T19:38:50.176+0100 I NETWORK  <<initandlisten>> waiting for connections on port 27017
 ----
 
-As you can see the server is running on port 27017, but don't worry the MongoDB plugin for Grails will automatically configure itself to look for MongoDB on that port by default.
+As you can see the server is running on port 27017, but don't worry the MongoDB plugin for Grace framework will automatically configure itself to look for MongoDB on that port by default.
 
-If you want to configure how Grails connects to MongoDB then you can do so using the following settings in `grails-app/conf/application.yml`:
+If you want to configure how Grace framework connects to MongoDB then you can do so using the following settings in `app/conf/application.yml`:
 
 [source,groovy]
 ----

src/docs/guide/gettingStarted/advancedConfig.adoc

@@ -1,8 +1,6 @@
+=== Mongo Database Connection Configuration
 
-==== Mongo Database Connection Configuration
-
-
-As mentioned the GORM for MongoDB plugin will configure all the defaults for you, but if you wish to customize those defaults you can do so in the `grails-app/conf/application.groovy` file:
+As mentioned the GORM for MongoDB plugin will configure all the defaults for you, but if you wish to customize those defaults you can do so in the `app/conf/application.groovy` file:
 
 [source,groovy]
 ----
@@ -33,12 +31,11 @@ grails {
 }
 ----
 
-Available options and their descriptions are defined in the https://api.mongodb.org/java/current/com/mongodb/MongoClientOptions.html[MongoClientOptions] javadoc.
-
-==== MongoDB Connection Strings
+Available options and their descriptions are defined in the https://mongodb.github.io/mongo-java-driver/5.0/apidocs/mongodb-driver-legacy/com/mongodb/MongoClientOptions.html[MongoClientOptions] javadoc.
 
+=== MongoDB Connection Strings
 
-Since 2.0, you can also use MongoDB https://docs.mongodb.org/manual/reference/connection-string/[connection strings] to configure the connection:
+Since 2.0, you can also use MongoDB https://www.mongodb.com/docs/manual/reference/connection-string/[connection strings] to configure the connection:
 
 [source,groovy]
 ----
@@ -51,10 +48,7 @@ grails {
 
 Using MongoDB connection strings is currently the most flexible and recommended way to configure MongoDB connections.
 
-
-
-==== Configuration Options Guide
-
+=== Configuration Options Guide
 
 Below is a complete example showing all configuration options:
 
@@ -87,12 +81,9 @@ grails {
 }
 ----
 
+=== Global Mapping Configuration
 
-
-==== Global Mapping Configuration
-
-
-Using the `grails.mongodb.default.mapping` setting in `grails-app/conf/application.groovy` you can configure global mapping options across your domain classes. This is useful if, for example, you want to disable optimistic locking globally or you wish to use `DBRefs` in your association mappings. For example, the following configuration will disable optimistic locking globally and use `DBRefs` for all properties:
+Using the `grails.mongodb.default.mapping` setting in `app/conf/application.groovy` you can configure global mapping options across your domain classes. This is useful if, for example, you want to disable optimistic locking globally or you wish to use `DBRefs` in your association mappings. For example, the following configuration will disable optimistic locking globally and use `DBRefs` for all properties:
 
 [source,groovy]
 ----

src/docs/guide/gettingStarted/mongoOnly.adoc

@@ -2,14 +2,14 @@ If you plan to use MongoDB as your primary datastore then you need to remove the
 
 [source,groovy]
 ----
-compile 'org.grails.plugins:hibernate'
+implementation 'org.graceframework.plugins:hibernate'
 ----
 
-With this done all domain classes in grails-app/domain will be persisted via MongoDB and not Hibernate. You can create a domain class by running the regular `create-domain-class` command:
+With this done all domain classes in `app/domain` will be persisted via MongoDB and not Hibernate. You can create a domain class by running the regular `create-domain-class` command:
 
-[source,groovy]
+[source,console]
 ----
-grails create-domain-class Person
+$ grace create-domain-class Person
 ----
 
 The `Person` domain class will automatically be a persistent entity that can be stored in MongoDB.

src/docs/guide/gettingStarted/outsideGrails.adoc

@@ -1,8 +1,9 @@
-If you wish to use GORM for MongoDB outside of a Grails application you should declare the necessary dependencies, for example in Gradle:
+If you wish to use GORM for MongoDB outside of a Grace application you should declare the necessary dependencies, for example in Gradle:
 
 [source,groovy,subs="attributes"]
 ----
-compile "org.grails:grails-datastore-gorm-mongodb:{version}"
+implementation "org.graceframework:grace-boot:{version}"
+implementation "org.graceframework.plugins:mongodb:{version}"
 ----
 
 Then annotate your entities with the `grails.gorm.annotation.Entity` annotation:

src/docs/guide/gettingStarted/springBoot.adoc

@@ -2,29 +2,27 @@ To use GORM for MongoDB in Spring Boot add the necessary dependencies to your Bo
 
 [source,groovy,subs="attributes"]
 ----
-compile("org.grails:gorm-mongodb-spring-boot:{version}")
+implementation "org.graceframework:grace-boot:{version}"
+implementation "org.graceframework.plugins:mongodb:{version}"
 ----
 
-Ensure your Boot `Application` class is annotated with `ComponentScan`, example:
+Ensure your Boot `Application` class is annotated with `GrailsComponentScan`, example:
 
 [source,groovy]
 ----
 import org.springframework.boot.SpringApplication
-import org.springframework.boot.autoconfigure.EnableAutoConfiguration
-import org.springframework.context.annotation.*
+import org.springframework.boot.autoconfigure.SpringBootApplication
 
-@Configuration
-@EnableAutoConfiguration
-@ComponentScan
+@SpringBootApplication
 class Application {
     static void main(String[] args) {
         SpringApplication.run Application, args
     }
 }
 ----
 
-NOTE: Using `ComponentScan` without a value results in Boot scanning for classes in the same package or any package nested within the `Application` class package.
-If your GORM entities are in a different package specify the package name as the value of the `ComponentScan` annotation.
+NOTE: Using `GrailsComponentScan` without a value results in Boot scanning for classes in the same package or any package nested within the `Application` class package.
+If your GORM entities are in a different package specify the package name as the value of the `GrailsComponentScan` annotation.
 
 Finally create your GORM entities and ensure they are annotated with `grails.persistence.Entity`:
 

src/docs/guide/gettingStarted/withHibernate.adoc

@@ -1,8 +1,6 @@
-If you have both the Hibernate and Mongo plugins installed then by default all classes in the `grails-app/domain` directory will be persisted by Hibernate and not Mongo. If you want to persist a particular domain class with Mongo then you must use the `mapWith` property in the domain class:
+If you have both the Hibernate and Mongo plugins installed then by default all classes in the `app/domain` directory will be persisted by Hibernate and not Mongo. If you want to persist a particular domain class with Mongo then you must use the `mapWith` property in the domain class:
 
 [source,groovy]
 ----
 static mapWith = "mongo"
 ----
-
-

src/docs/guide/integrationTesting.adoc

@@ -1,3 +1 @@
 There is a plugin available that will execute an in memory Mongo database during your integration tests. Data will be cleared between test cases so they can work similarly to H2 with `@Rollback`.
-
-Visit the github page of the link:https://github.com/grails-plugins/grails-embedded-mongodb[Embedded MongoDB Grails Plugin] to learn more.

src/docs/guide/introduction/compatibility.adoc

@@ -1,4 +1,4 @@
-This implementation tries to be as compatible as possible with GORM for Hibernate. In general you can refer to the https://grails.org/doc/latest/guide/5.%20Object%20Relational%20Mapping%20(GORM).html[GORM documentation] and the "Domain Classes" section of the https://grails.org/doc/latest/[reference guide] (see the right nav) for usage information.
+This implementation tries to be as compatible as possible with GORM for Hibernate. In general you can refer to the https://graceframework.org/grace-data/2023.3.x/[GORM documentation] for usage information.
 
 The following key features are supported by GORM for Mongo:
 

src/docs/guide/introduction/upgradeNotes.adoc

@@ -1,14 +1,14 @@
 ==== Dependency Upgrades
 
-GORM 7.1 supports Apache Groovy 3, Java 14, MongoDB Driver 4.3 and Spring 5.3.x.
+GORM 2023.3 supports Apache Groovy 4.0, Java 17, MongoDB Driver 5.0 and Spring 6.1.x.
 
 Each of these underlying components may have changes that require altering your application. These changes are beyond the scope of this documentation.
 
 ==== Default Autowire By Type inside GORM Data Services
 
-A Grails Service (or a bean) inside GORM DataService will default to autowire by-type, For example:
+A GORM Service (or a bean) inside GORM DataService will default to autowire by-type, For example:
 
-_./grails-app/services/example/BookService.groovy_
+_./app/services/example/BookService.groovy_
 ```
 package example
 
@@ -27,5 +27,4 @@ abstract class BookService {
 }
 ```
 
-Please note that with autowire by-type as the default, when multiple beans for same type are found the application with throw Exception. Use the Spring `@Qualifier annotation for https://docs.spring.io/spring-framework/docs/5.3.10/reference/html/core.html#beans-autowired-annotation-qualifiers[Fine-tuning Annotation Based Autowiring with Qualifiers].
-
+Please note that with autowire by-type as the default, when multiple beans for same type are found the application with throw Exception. Use the Spring `@Qualifier annotation for link:{springrefdoc}/core/beans/annotation-config/autowired-qualifiers.html[Fine-tuning Annotation Based Autowiring with Qualifiers].

src/docs/guide/lowLevelApi.adoc

@@ -1,6 +1,6 @@
 A lower level API is provided by the plugin via the MongoDB driver
 
-NOTE: There is an excellent tutorial on how to use the MongoDB Java driver's API directly in the https://mongodb.github.io/mongo-java-driver/3.1/driver/getting-started/quick-tour/[MongoDB documentation]
+NOTE: There is an excellent tutorial on how to use the MongoDB Java driver's API directly in the https://mongodb.github.io/mongo-java-driver/5.0/driver/getting-started/quick-start/[MongoDB documentation]
 
 An example can be seen below: