Skip to content

Commit a1df7e7

Browse files
code include:: fixes
1 parent fb446d8 commit a1df7e7

File tree

1 file changed

+12
-12
lines changed

1 file changed

+12
-12
lines changed

modules/howtos/pages/managing-connections.adoc

Lines changed: 12 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ Multiple addresses may be specified in a connection string by delimiting them wi
3030

3131
[source,java]
3232
----
33-
include::example$ManagingConnections.java[tag=multinodeconnect,indent=0]
33+
include::devguide:example$java/ManagingConnections.java[tag=multinodeconnect,indent=0]
3434
----
3535

3636
TIP: You don't need to include the address of every node in the cluster.
@@ -46,7 +46,7 @@ You can customize the client's behavior by providing a callback that modifies a
4646

4747
[source,java]
4848
----
49-
include::example$ManagingConnections.java[tag=customenv,indent=0]
49+
include::devguide:example$java/ManagingConnections.java[tag=customenv,indent=0]
5050
----
5151

5252
TIP: When you customize the environment using a callback like in the above example, the client creates an environment that is managed completely by the Java SDK.
@@ -99,7 +99,7 @@ If a single application needs to connect to multiple Couchbase Server clusters,
9999

100100
[source,java]
101101
----
102-
include::example$ManagingConnections.java[tag=shareclusterenvironment,indent=0]
102+
include::devguide:example$java/ManagingConnections.java[tag=shareclusterenvironment,indent=0]
103103
----
104104

105105
[WARNING]
@@ -131,15 +131,15 @@ If the external ports are not the default, you can specify custom ports in the c
131131

132132
[source,java]
133133
----
134-
include::example$managing_connections.java[tag=managing_connections_5,indent=0]
134+
include::devguide:example$java/managing_connections.java[tag=managing_connections_5,indent=0]
135135
----
136136

137137
For nodes that do not have the KV service, you can connect using a custom manager port instead.
138138
Notice how `=manager` appears after the port number, identifying it as a manager port:
139139

140140
[source,java]
141141
----
142-
include::example$managing_connections.java[tag=managing_connections_6,indent=0]
142+
include::devguide:example$java/managing_connections.java[tag=managing_connections_6,indent=0]
143143
----
144144

145145
TIP: In a deployment that uses multi-dimensional scaling, a custom KV port is only applicable for nodes running the KV service.
@@ -216,7 +216,7 @@ The next step is to enable encryption and pass it the path to the certificate fi
216216
217217
[source,java]
218218
----
219-
include::example$ManagingConnections.java[tag=tls,indent=0]
219+
include::devguide:example$java/ManagingConnections.java[tag=tls,indent=0]
220220
----
221221
222222
If you want to verify it's actually working, you can use a tool like [.cmd]`tcpdump`.
@@ -299,7 +299,7 @@ In order to make the SDK use the SRV records, you need to pass in the hostname f
299299

300300
[source,java]
301301
----
302-
include::example$ManagingConnections.java[tag=dnssrv,indent=0]
302+
include::devguide:example$java/ManagingConnections.java[tag=dnssrv,indent=0]
303303
----
304304

305305
If the DNS SRV records could not be loaded properly you'll get the exception logged and the given host name will be used as a A record lookup.
@@ -329,14 +329,14 @@ If you are working at the _Cluster_ level, then add to the `cluster()` in the xr
329329

330330
[source,java]
331331
----
332-
include::example$managing_connections.java[tag=managing_connections_8,indent=0]
332+
include::devguide:example$java/managing_connections.java[tag=managing_connections_8,indent=0]
333333
----
334334

335335
Or more fully:
336336

337337
[source,java]
338338
----
339-
include::example$ClusterExample.java[tag=managing_connections_9,indent=0]
339+
include::devguide:example$java/ClusterExample.java[tag=managing_connections_9,indent=0]
340340
----
341341

342342
If you are working at the _Bucket_ level, then the https://docs.couchbase.com/sdk-api/couchbase-java-client/com/couchbase/client/java/Bucket.html#waitUntilReady-java.time.Duration-[Bucket-level `waitUntilReady`] does the same as the Cluster-level version,
@@ -370,21 +370,21 @@ So if you are connecting to the bucket synchronously but then want to switch ove
370370

371371
[source,java]
372372
----
373-
include::example$ManagingConnections.java[tag=blockingtoasync,indent=0]
373+
include::devguide:example$java/ManagingConnections.java[tag=blockingtoasync,indent=0]
374374
----
375375

376376
On the other hand, you can use the Async API right from the beginning:
377377
// todo use tabs here?
378378
[source,java]
379379
----
380-
include::example$ManagingConnections.java[tag=asynccluster,indent=0]
380+
include::devguide:example$java/ManagingConnections.java[tag=asynccluster,indent=0]
381381
----
382382

383383
Here's the same example, but using the Reactive API instead of the Async API:
384384

385385
[source,java]
386386
----
387-
include::example$ManagingConnections.java[tag=reactivecluster,indent=0]
387+
include::devguide:example$java/ManagingConnections.java[tag=reactivecluster,indent=0]
388388
----
389389

390390

0 commit comments

Comments
 (0)