Please provide my brief description on Processing strategy in mule. That topic is not clear to me.
I'm assuming you mean Mule 3.
Here's the documentation: https://docs.mulesoft.com/mule-user-guide/v/3.9/flow-processing-strategies
Mule 4 (supposedly): https://forums.mulesoft.com/questions/96610/mule-4-processing-strategies.html
Related
How to use Spring Boot Autoconfiguration to enable exactly once delivery in Spring Kafka?
Would just setting spring.kafka.producer.transaction-id-prefix be enough? Or do I need anything else as well?
Also, do I also need to enable idempotence as suggested by a few blogs? Or would enabling transactions anyways make sure that my producer is idempotent?
You assumption is correct. As long as you use auto-configured KafkaTemplate in a listener thread, you got a proper Kafka transaction.
No, you don't need to configure idempotency in case of transactions.
See more info in respective Kafka docs: https://kafka.apache.org/documentation/#producerconfigs_transactional.id
I am working on a Stub of a microservice with which the Network Function under test communicates via a REST API. The stub is developed with Spring MVC (Spring Boot 2.5.0)
Under certain cirtumstances we need to provoke an absence of reply from the stub to the NF. And here is where the question comes: how to sneak into the Servlet to block the reply back to the client? If that is even possible.
I have been for a while googling but I haven't found anything being really of any use. Before digging more into the framework I am making the question in case someone has had to solve this problem before.
If it is, any hint that we can use to work on the solution would be appreciated.
Thanks!
I have already gone through the below link to mask/hide/encrypt sensitive data before logging but unable to do so using Mule4. Can someone please share if implemented or suggestions?
http://bushorn.com/encrypting-a-json-element/
The link is no longer available. I'll assume it is a method base on some log4j2 interception that will not work on Mule 4. What you can do is create a custom logging component with the Mule SDK and apply the same logic there, avoiding trying to intercept Mule 4 logging.
Is there anywhere a working (runnable) example of implementation of Camel servlet endpoint with "no-xml" approach? Working unit test with http-client wold also be great. To me, the set up seems too "complicated" being not familiar with servlet configurations. Examples I can find use mostly XML-only approach.
I'm using Camel on top of Spring Boot.
Its covered in the Camel in Action 2nd edition book, where there is a camel-servlet example in the microservices chapter 7.
https://www.manning.com/books/camel-in-action-second-edition
The example comes as part of a bigger use-case but its the rating service: https://github.com/camelinaction/camelinaction2/tree/master/chapter7/prototype/rating
I want to start using the framework Pact for JVM for contract testing. But does Pact JVM support REST and JMS?
I haven't found any information about this.
Yes, Pact JVM supports REST[1], its primary use case, and also supports JMS testing in the form of Messages [2].
Note that as of this moment, the other language implementations don't support this Message style test, but the work is in progress to make it happen.
[1] Assuming REST = JSON/HTTP
[2] https://github.com/DiUS/pact-jvm/tree/master/pact-jvm-consumer-junit#consumer-test-for-a-message-consumer
Pact is a restful consumer/provider testing tool only; It has to communicate over HTTP and the data contract can only be in JSON at the moment (this could change in the future). We have talked about supporting other protocols like messaging (websockets), but there isn't much need for it as of yet and we have other priorities to work on currently.