Fix path variables (e.g. samples-dir) used in documentation and source files.
Remove trailing path separator (/).
This commit is contained in:
@@ -44,7 +44,7 @@ However in this case, we simply model the `TemperatureReading` as:
|
||||
.TemperatureReading class
|
||||
[source,java]
|
||||
----
|
||||
include::{samples-dir}boot/actuator/src/main/java/example/app/temp/model/TemperatureReading.java[tags=class]
|
||||
include::{samples-dir}/boot/actuator/src/main/java/example/app/temp/model/TemperatureReading.java[tags=class]
|
||||
----
|
||||
|
||||
The `TemperatureReading` class is annotated with SDG's `@Region` mapping annotation to declare the Apache Geode Region
|
||||
@@ -61,7 +61,7 @@ For that, we introduce the simple `TemperatureEvent` base class:
|
||||
.TemperatureEvent class
|
||||
[source,java]
|
||||
----
|
||||
include::{samples-dir}boot/actuator/src/main/java/example/app/temp/event/TemperatureEvent.java[tags=class]
|
||||
include::{samples-dir}/boot/actuator/src/main/java/example/app/temp/event/TemperatureEvent.java[tags=class]
|
||||
----
|
||||
|
||||
`TemperatureEvent` is a Spring `ApplicationEvent` capable of being published to to Spring `@EventListeners` registered
|
||||
@@ -79,7 +79,7 @@ a Spring Data _Repository_:
|
||||
.TemperatureReadingRepository interface
|
||||
[source,java]
|
||||
----
|
||||
include::{samples-dir}boot/actuator/src/main/java/example/app/temp/repo/TemperatureReadingRepository.java[tags=class]
|
||||
include::{samples-dir}/boot/actuator/src/main/java/example/app/temp/repo/TemperatureReadingRepository.java[tags=class]
|
||||
----
|
||||
|
||||
The _Repository_ showcases a an example, derived query methods, `findByTimestampGreaterThanAndTimestampLessThan(..)`
|
||||
@@ -101,7 +101,7 @@ or drops below freezing (32 °F):
|
||||
.TemperatureMonitor class
|
||||
[source,java]
|
||||
----
|
||||
include::{samples-dir}boot/actuator/src/main/java/example/app/temp/service/TemperatureMonitor.java[tags=class]
|
||||
include::{samples-dir}/boot/actuator/src/main/java/example/app/temp/service/TemperatureMonitor.java[tags=class]
|
||||
----
|
||||
|
||||
When the temperature changes, triggering our queries, we receive an event and publish an appropriate `TemperatureEvent`
|
||||
@@ -120,7 +120,7 @@ For that we have the `TemperatureSensor` class:
|
||||
.TemperatureSensor class
|
||||
[source,java]
|
||||
----
|
||||
include::{samples-dir}boot/actuator/src/main/java/example/app/temp/service/TemperatureSensor.java[tags=class]
|
||||
include::{samples-dir}/boot/actuator/src/main/java/example/app/temp/service/TemperatureSensor.java[tags=class]
|
||||
----
|
||||
|
||||
To generate a stream of temperatures, we use Spring's {spring-framework-docs}/integration.html#scheduling[Scheduling Service]
|
||||
@@ -150,7 +150,7 @@ using the `TemperatureSensor` class:
|
||||
.BootGeodeServerApplication main class
|
||||
[source,java]
|
||||
----
|
||||
include::{samples-dir}boot/actuator/src/main/java/example/app/temp/geode/server/BootGeodeServerApplication.java[tags=class]
|
||||
include::{samples-dir}/boot/actuator/src/main/java/example/app/temp/geode/server/BootGeodeServerApplication.java[tags=class]
|
||||
----
|
||||
|
||||
This class is annotated with `@SpringBootApplication` making it a proper Spring Boot application. It uses Spring Boot's
|
||||
@@ -186,7 +186,7 @@ Next, we need a client functioning as the "monitor" in our Temperature Service a
|
||||
.BootGeodeClientApplication main class
|
||||
[source,java]
|
||||
----
|
||||
include::{samples-dir}boot/actuator/src/main/java/example/app/temp/geode/client/BootGeodeClientApplication.java[tags=class]
|
||||
include::{samples-dir}/boot/actuator/src/main/java/example/app/temp/geode/client/BootGeodeClientApplication.java[tags=class]
|
||||
----
|
||||
|
||||
Again, this class is also annotated with `@SpringBootApplication` making it a proper Spring Boot application. It too
|
||||
|
||||
@@ -37,7 +37,7 @@ namely a `Customer`. For this example, the `Customer` class is implemented as f
|
||||
.Customer class
|
||||
[source,java]
|
||||
----
|
||||
include::{samples-dir}boot/configuration/src/main/java/example/app/crm/model/Customer.java[tags=class]
|
||||
include::{samples-dir}/boot/configuration/src/main/java/example/app/crm/model/Customer.java[tags=class]
|
||||
----
|
||||
|
||||
The `Customer` class uses https://projectlombok.org/[Project Lombok] to simplify the implementation so we can focus on
|
||||
@@ -63,7 +63,7 @@ using Spring Data's _Repository_ abstraction:
|
||||
.CustomerRepository inteface
|
||||
[source,java]
|
||||
----
|
||||
include::{samples-dir}boot/configuration/src/main/java/example/app/crm/repo/CustomerRepository.java[tags=class]
|
||||
include::{samples-dir}/boot/configuration/src/main/java/example/app/crm/repo/CustomerRepository.java[tags=class]
|
||||
----
|
||||
|
||||
`CustomerRepository` is a Spring Data `CrudRepository`. `CrudRepository` provides basic CRUD (Create, Read, Update,
|
||||
@@ -90,7 +90,7 @@ to drive the interactions with Customers:
|
||||
.CustomerServiceApplication class
|
||||
[source,java]
|
||||
----
|
||||
include::{samples-dir}boot/configuration/src/main/java/example/app/crm/CustomerServiceApplication.java[tags=class]
|
||||
include::{samples-dir}/boot/configuration/src/main/java/example/app/crm/CustomerServiceApplication.java[tags=class]
|
||||
----
|
||||
|
||||
The `CustomerServiceApplication` class is annotated with `@SpringBootApplication`. Therefore, the main class is
|
||||
|
||||
Reference in New Issue
Block a user