Files
spring-pulsar/spring-pulsar-sample-apps
Chris Bono ae05982286 Update to Pulsar 3.3.2 (#875)
This commit updates the version of Pulsar to 3.3.2.

Also, in Pulsar 3.3.2 the schema validation of an outgoing message value
happens later than it did previously. This requires the PulsarTemplate
to widen the try/catch net so that when this happens the producer is
closed properly. The backing change in Pulsar 3.3.2 can be seen here
f3c177e224 (diff-095bc2359e03726e031d8c2f210560c6a3218f48a969b0f75a2482e25cd54744R69)
2024-10-16 10:24:01 -05:00
..
2023-12-01 13:06:10 -06:00

= Spring Pulsar Sample Applications

Sample applications that can be used to demonstrate and manually verify Spring Pulsar functionality.


[[build-apps]]
== Building
To build the applications simply execute the following command from the `spring-pulsar-sample-apps` directory:
[source,bash]
----
../gradlew clean build
----

[[run-apps]]
== Running

=== Pre-requisites
****
* The components have all been built by following the <<build-apps>> steps.
* Apache Pulsar standalone cluster  available at `pulsar://localhost:6650`

TIP: Some samples (those w/ a `compose.yaml` file) include Docker Compose support and will automatically start the Pulsar cluster. For the other sample apps the included link:../tools/pulsar/docker/README.adoc#_start_pulsar[Pulsar tools] can be used to easily start a standalone cluster locally on the required coordinates.
****

=== Steps

Make sure the above pre-requisites are satisfied.

===== IDE
To run the app in your IDE just choose `Run/Debug` on the desired sample application class.

===== Command Line
To run the app on the command line open a terminal and navigate to the desired sample application directory (underneath `spring-pulsar-sample-apps`) and execute the following command:

[source,bash]
----
../../gradlew bootRun
----

TIP: When running on the command line the `add-opens` JVM args are automatically configured which prevents annoying exceptions at runtime.