From 1f82019fdfdd7320f425c379f9818fd6833e115d Mon Sep 17 00:00:00 2001 From: Patrik Nordwall Date: Wed, 20 Nov 2024 14:36:56 +0100 Subject: [PATCH] chore: Some broken links --- docs/src/main/paradox/durable-state.md | 4 ++-- docs/src/main/paradox/eventsourced.md | 2 +- docs/src/main/paradox/grpc-producer-push.md | 2 +- .../main/paradox/grpc-replicated-event-sourcing-transport.md | 4 ++-- docs/src/main/paradox/r2dbc.md | 2 +- docs/src/main/paradox/snapshots.md | 2 +- 6 files changed, 8 insertions(+), 8 deletions(-) diff --git a/docs/src/main/paradox/durable-state.md b/docs/src/main/paradox/durable-state.md index a49090a74..41fa4f026 100644 --- a/docs/src/main/paradox/durable-state.md +++ b/docs/src/main/paradox/durable-state.md @@ -43,7 +43,7 @@ The table below shows the `akka-projection-durable-state` direct dependencies.Th ## SourceProvider for changesByTag A @apidoc[SourceProvider] defines the source of the envelopes that the `Projection` will process. A `SourceProvider` -for the `changes` query can be defined with the @apidoc[DurableStateStoreProvider$] like this: +for the `changes` query can be defined with the @apidoc[DurableStateStoreProvider] like this: Scala : @@snip [DurableStateStoreDocExample.scala](/examples/src/test/scala/docs/state/DurableStateStoreDocExample.scala) { #changesByTagSourceProvider } @@ -63,7 +63,7 @@ by the `Projection`. See @apidoc[akka.persistence.query.DurableStateChange] for ## SourceProvider for changesBySlices A @apidoc[SourceProvider] defines the source of the envelopes that the `Projection` will process. A `SourceProvider` -for the `changesBySlices` query can be defined with the @apidoc[DurableStateStoreProvider$] like this: +for the `changesBySlices` query can be defined with the @apidoc[DurableStateStoreProvider] like this: Scala : @@snip [DurableStateStoreDocExample.scala](/examples/src/test/scala/docs/state/DurableStateStoreDocExample.scala) { #changesBySlicesSourceProvider } diff --git a/docs/src/main/paradox/eventsourced.md b/docs/src/main/paradox/eventsourced.md index c2d3dae01..4c5dae391 100644 --- a/docs/src/main/paradox/eventsourced.md +++ b/docs/src/main/paradox/eventsourced.md @@ -97,4 +97,4 @@ and loading of events from the database. `EventsBySliceFirehoseQuery` is used in place of `EventsBySliceQuery` with the `EventSourcedProvider`. -It is typically used together with @extref:[Sharded Daemon Process with colocated processes](akka:typed/cluster-sharded-daemon-process.md#colocate-processes). +It is typically used together with @extref:[Sharded Daemon Process with colocated processes](akka:typed/cluster-sharded-daemon-process.html#colocate-processes). diff --git a/docs/src/main/paradox/grpc-producer-push.md b/docs/src/main/paradox/grpc-producer-push.md index f826ac2d4..3538c9cad 100644 --- a/docs/src/main/paradox/grpc-producer-push.md +++ b/docs/src/main/paradox/grpc-producer-push.md @@ -91,7 +91,7 @@ This can be used together with the additional producer metadata to add authentic ## Producer set up The producer is essentially a special projection handler for a projection running on the producer. It could be a single actor system -running one projection handling all slices, or it could be @extref:[Sharded Daemon Process](akka:typed/cluster-sharded-daemon-process.md) +running one projection handling all slices, or it could be @extref:[Sharded Daemon Process](akka:typed/cluster-sharded-daemon-process.html) pushing events for partitioned slices of the entities. The producer is created through @apidoc[EventProducerPush], which has a method `handler()` which returns a handler to be plugged into diff --git a/docs/src/main/paradox/grpc-replicated-event-sourcing-transport.md b/docs/src/main/paradox/grpc-replicated-event-sourcing-transport.md index d44eb17df..273aa318d 100644 --- a/docs/src/main/paradox/grpc-replicated-event-sourcing-transport.md +++ b/docs/src/main/paradox/grpc-replicated-event-sourcing-transport.md @@ -6,8 +6,8 @@ such as active-active and hot standby. Originally, Akka Replicated Event Sourcing has required cross-replica access to the underlying replica database, which can be hard to open up for security and infrastructure reasons. It was also easiest to use in an -[Akka Multi DC Cluster](https://doc.akka.io/libraries/akka-core/current/typed/cluster-dc.html) setup -where a single cluster spans multiple datacenters or regions, another thing that can be complicated to allow. +Akka Multi DC Cluster setup where a single cluster spans multiple datacenters or regions, another +thing that can be complicated to allow. Akka Replicated Event Sourcing over gRPC builds on @ref:[Akka Projection gRPC](grpc.md) and @extref:[Akka gRPC](akka-grpc:index.html) to instead use gRPC as the cross-replica transport for events. diff --git a/docs/src/main/paradox/r2dbc.md b/docs/src/main/paradox/r2dbc.md index df40d80f2..d4bce0c18 100644 --- a/docs/src/main/paradox/r2dbc.md +++ b/docs/src/main/paradox/r2dbc.md @@ -248,7 +248,7 @@ Same type of handlers can be used with `R2dbcProjection` instead of `CassandraPr ### Actor handler A good alternative for advanced state management is to implement the handler as an -@extref:[actor](akka:typed/typed/actors.html) which is described in +@extref:[actor](akka:typed/actors.html) which is described in @ref:[Processing with Actor](actor.md). ### Flow handler diff --git a/docs/src/main/paradox/snapshots.md b/docs/src/main/paradox/snapshots.md index 434121da3..849074c1c 100644 --- a/docs/src/main/paradox/snapshots.md +++ b/docs/src/main/paradox/snapshots.md @@ -3,7 +3,7 @@ project.description: Snapshot builds of Akka Projection. --- # Snapshots -Snapshots are published to https://repo.akka.io/snapshots repository after every successful build on main. +Snapshots are published to https://repo.akka.io/snapshots/ repository after every successful build on main. Add the following to your project build definition to resolve Akka Projection's snapshots: ## Configure repository