[andreasarf]

Summary

First of three event/messaging PRs: in-app Spring events, then outbox notifications to RabbitMQ, then durable sync jobs on RabbitMQ.

Events. ProjectService publishes Spring application events (new package events) inside the transaction that changes a project:

• ProjectCreated: the project's id, SDLC system, external id and name.
• ProjectUpdated: the new state plus which fields changed (NAME, EXTERNAL_ID, SDLC_SYSTEM).
  • Not published when an update changes nothing, or when it is rejected (validation or conflict).
  • Renames made by a sync are published too.
• occurredAt on both, so a listener (or, after Project notifications to RabbitMQ through an outbox (Spring Modulith) #20, another system) that receives events about one project out of order can drop stale ones. Added in the review round.

SyncOnProjectChange. A @TransactionalEventListener, so it only reacts to committed changes. It starts a background sync, the same as POST …/sync, when a project is:

• created, so a project created without a name gets it from the SDLC system;
• re-keyed (pointed at another SDLC project), so its name follows.

Other details:

• Failures. A sync that can't start is logged and skipped, and the create or update itself still succeeds. Spring runs after-commit listeners in afterCompletion, so even an unexpected exception there can't fail the request (checked in Spring's source).
• No loop. A sync only renames, so its own ProjectUpdated doesn't start another sync.
• Switch. resourceapi.sync.on-change (default true). The test config turns it off, so tests that create projects don't call SDLC systems unexpectedly.
• Transaction. createProject is now @Transactional, so its event belongs to the creating transaction.

Known cost. The listener runs on the request thread after commit. With Redis unreachable, the lock attempt adds about a second to a create or re-key, as it already does for POST …/sync. This is documented in the README.

Tests

• ProjectEventsTest (@RecordApplicationEvents):
  • create publishes ProjectCreated with occurredAt;
  • rename publishes ProjectUpdated{NAME}, later than the create;
  • re-key reports EXTERNAL_ID + SDLC_SYSTEM;
  • a no-op update and a rejected update publish nothing.
• SyncOnProjectChangeTest (WireMock SDLC system, real Redis):
  • a project created without a name gets it from the SDLC system;
  • re-keying fetches the new project's name;
  • renaming locally doesn't call the SDLC system.
• Mutation check: without the re-key condition, the last test fails.

Full suite: 120 tests pass.

🤖 Generated with Claude Code

https://claude.ai/code/session_012MLyPXGHeCc1fvTeB8JnT2