For example using http proxy to deliver events to customer service (https://github.com/eventuate-examples/eventuate-tram-reactive-examples-customers-and-orders):

Proxy does HTTP POST to Customer Service
Customer service successfully updates database etc.
Customer Service sends back an HTTP response
Proxy crashes before receiving the HTTP response and recording the duplicate.
Proxy recovers and redelivers what is now a duplicate.

This scenario shows that duplicate detection should be handled on application side and should be removed from proxy.

Is eventuate-tram-messaging-http-master responsible for sending messages to consumers via HTTP? Is there any relationship between eventuate-tram-messaging-http-master and CDC, or are they separate projects? When eventuate-tram-messaging-http-master sends messages, does it first persist the messages to the database like Tram, and then rely on CDC for distribution? If so, is there any documentation for this? I couldn't find any HTTP-related code in CDC. Is there another project that CDC needs to depend on? If eventuate-tram-messaging-http-master does not persist messages when sending, what are the main use cases for this project?Thank you very much.

The new build creates source and javadoc jars and so COPY fails because the filecard matches multiple JARs.

The solution is for the Dockerfile to COPY build/libs/eventuate-tram-messaging-proxy-service-.jar

There are several parts to the solution:

• Gradle Docker compose plugin already sets PROXY_SERVICE_VERSION env var
• docker-compose.yml passes the P_S_V to Dockerfile using https://docs.docker.com/compose/compose-file/compose-file-v3/#args
• Dockerfile uses the P_S_V arg to copy the right version.