You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+2-22Lines changed: 2 additions & 22 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -85,17 +85,16 @@ The library uses flyway migrations to set up its own database schema `nakadi_eve
85
85
86
86
### Nakadi communication configuration
87
87
88
-
By default, Nakadi-producer-spring-boot starter uses the Fahrschein library to submit its events. It needs some configuration to know how to do this – we describe three ways here (basically in order of ease of use):
88
+
By default, Nakadi-producer-spring-boot starter uses the Fahrschein library to submit its events. It needs some configuration to know how to do this – we support two ways:
89
89
90
90
* Using existing Fahrschein setup
91
91
* Letting this library set things up
92
-
* Implement Nakadi communication yourself
93
92
94
93
#### Using existing Fahrschein setup
95
94
96
95
If you are already using the [Fahrschein library](https://github.com/zalando-nakadi/fahrschein) directly (e.g. for event consumption) and have already a configured `org.zalando.fahrschein.NakadiClient` object, just make sure it is available as a Spring bean. Nakadi-Producer-Spring-Boot-Starter will pick it up and use it directly.
97
96
98
-
The configurations in the next section are then not needed at all.
97
+
The configuration in the next section is then not needed at all.
99
98
100
99
#### Letting this library set things up
101
100
@@ -137,25 +136,6 @@ nakadi-producer:
137
136
138
137
If you do not use the STUPS Tokens library, you can implement token retrieval yourself by defining a Spring bean of type `org.zalando.nakadiproducer.AccessTokenProvider`. The starter will detect it and call it once for each request to retrieve the token.
139
138
140
-
#### Implement Nakadi communication yourself
141
-
142
-
If you don't like Fahrschein, you can implement the communication with Nakadi yourself. Just provide an implementation of the `NakadiPublishingClient` interface as a Spring bean. Nakadi-producer-spring-boot-starter will just use that bean. (This is used in the [test support](#test-support) described below.)
143
-
144
-
You can then also exclude the Fahrschein dependency:
0 commit comments