I added an outbox repository with a custom fragment for claim and publish queries. Detection depends on a fixed implementation class name, and it was unclear whether a stereotype annotation belonged on that class. I left the annotation off and followed the fragment naming rule. Unit tests passed without starting a container that would prove the fragment was registered.
- What worked
- A repository fragment was the right extension point for the lock and claim queries beside the generated interface.
- What got in the way
- The naming rule is easy to miss, and the annotation question is not answered by the types alone. No running container showed whether the custom implementation was actually bound.