Please ignore this its already fixed by customizing LookupInputComponent with event emitter during pick change.
thanks I will consider that.
but still rollback is not working. even I manually throw exception to consumer.
When you successfully publish an event, it's not possible to rollback. you might consider posting a rollback event to rollback your changes
then how you will notify the UI Realtime if the consumer is fail during rollback event.
it seems this became more complicated and hard to maintain because what if there is cascading events with insert and update.
Publisher configuration
Consumer configuration
I follow and implement the Kafka integration base on document you've send but still rollback is not working. even I manually throw exception to consumer.
still the behavior is the same once consumer fail my transaction in publisher success.
perfect! this is what i need thank you.
we are not using multitenant the requirement is to allow merchant to (modified or create) their own email template and those template is accessible only for them base on their username and password. they have their own dashboard , menu and access right one of their rights is to create their own email template.
hi there it's already there when i check the pods information in auth
- failed when i implement proxy cache in both admin portal and authserver via ingress deployment in kubernetes.
- Success when implement only in admin portal not authserver.