Allow access to all incomplete event publications

[zikozee]

I am looking at a scenario where I can dynamically batch the incomplete events which can also give room to do some extra work before or after.

[patrzalektom]

@odrotbohm - the thing mentioned here is that CompletedEventPublications interface exposes a method findAll() which would return all completed event publications, but IncompleteEventPublications does not provide such a method and there's a need to inject EventPublicationRegistry (e.g. in tests) to assert anything related to incomplete publications.

This difference might be misleading in my opinion.

I could try handling this and opening a pull request with that, what do you think about that?

[patrzalektom]

Mentioned pull request: #616

[kalwinskidawid]

@odrotbohm Will it be implemented in the near future? Additionally, once it's possible to use findAll and obtain the UUID, it would be great to also have the ability to call resubmitIncompletePublication(UUID)

[odrotbohm]

@kalwinskidawid — Can you elaborate on the use case you have in mind?

[kalwinskidawid]

@odrotbohm Ideally, no event should go unprocessed, but we don't live in a perfect world. Therefore, in my case, I think it would be useful to have a list of events that didn’t complete successfully available at the service level. That way, we could directly attempt to process them again using their UUIDs.

[odrotbohm]

What I wonder is: what would you want to do with the publication beyond resubmitting it? If there's nothing else, isn't the general resubmission mechanism already present, sufficient?