Pablo Curiel

For instance, a case where I think reusing existing implementation can be helpful is customizing the DB schema. ```java class CustomMongoDbEventPublicationRepository extends MongoDbEventPublicationRepository { /* * Note: in this case,...

Interested in this as well. I think `invokeTargetListener` may make sense to be exposed as part of IncompleteEventPublications interface. Maybe `resubmitIncompletePublication(TargetEventPublication)`?

Very interested in this as well. In this case, due to a Keycloak custom Authenticator returning additional non-standard fields for some error cases, which there is no way to access...

Interested in this as well. We are trying to use AppAuth to interact with a custom Keycloak Authenticator, which adds new fields to the error response. Without, either direct access...

Hi @lbroudoux It makes sense to have the option to just not use the exchange.name, in order to prevent collisions. However, I think that it should: - At least use...

Hi! This is not a bug, but a feature that's being implemented: https://github.com/j-easy/easy-random/issues/397 This project is in maintaince mode, so sadly I think there is no estimation of when the...

I think it makes sense regarding event traceability. I will try to explain why with an example. Given this scenario: - `Service A` receives a request with Trace ID `ABC`...

Interested in this as well. Regarding Spring Event Publication, even though it is not fully integrated in the reactive stack (see [this Open issue](https://github.com/spring-projects/spring-framework/issues/21025)), at least some support for non-blocking...

It would be a very welcome change. And it makes a lot of sense to replicate it for the Spring generator if it is already done for Java clients. In...

As I detailed [in this issue](https://github.com/moby/buildkit/issues/5703), the problem is with the documentation. GIT_AUTH_HEADER can actually be used with a GitLab CI Token. Here is how you need to compute it...