Open baumeister25 opened 2 years ago
@baumeister25, thanks for your issue. Are you planning to implement this? Filing issues with title "Adapt documentation" (I changed it to be slightly more precise) tend to never be closed. We need some kind of acceptance criteria to make clear what is to do and when the issue is done. Otherwise we will be drowning in issues that can never be closed as there is always something to improve...
Awaiting review.
Awaiting review.
Is there a Pull-Request available to review? I still do not get what is going on here...
I assumed that the Solution Draft Pull-Request is expected to be reviewed (as mentioned in further to dos above). To review the PR: https://github.com/devonfw/solutions/pull/132
As for adapting Kafka integration, it is implemented in our new devon4j-kafka-ship-sample repo: https://github.com/devonfw-forge/devon4j-kafka-ship-sample
Please kindly review these and we're looking forward to any feedback.
Adapt the documentation of the kafka integration
See also the guide to messaging containing information about Kafka https://devonfw.com/website/pages/docs/asciidoc_devonfw-guide_devon4j.wiki_devon4j.asciidoc_guides.html#devonfw-guide_devon4j.wiki_guide-kafka.asciidoc
A own messaging chapter under Java -> General should be created containing the information about messaging kafka and JMS and how they're connected.
9.6
Further to dos https://github.com/devonfw/solutions/issues/113:
[x] Define Context and Scope more clearly
[x] Solution Strategy
[x] Tracing, Retry, and Kafka Health Monitoring
[x] Limits (Constraints)
[x] shorten tool description