Updatduring theg Spring Study Others was not effortless, but that had nothing regarding Springtime Data Others alone

That being said, it might not sound right to even do this. I cannot inquire the builders as to the reasons it absolutely was done so way, they aren’t here any more. Which project’s facts can only find out with their Git records.

Training read upgrading Spring season Investigation Other people

We suspect the audience is playing with Spring Research People wrong, wrongly blend WebMVC principles. Whenever we had not done so right from the start, one thing might have run far simpler.

We’re now through with the Spring season Studies Other people migration. It is time to move onto all of our 2nd Spring component, Spring season Kafka.

Springtime Kafka

Spring season Kafka, or rather Spring to possess Apache Kafka , is a great answer to have fun with Kafka on the Spring season tactics. It offers simple-to-fool around with layouts to possess sending messages and normal Spring season annotations to have taking texts.

Configuring the fresh customers

1 [ERROR] coffee.lang.IllegalStateException: Didn't stream ApplicationContext 2 step 3 Caused by: org.springframework.beans.facility.BeanCreationException: Error creating bean that have identity 'consumerFactory' discussed in group street resource [ de / application / config / KafkaConsumerConfig . class ]: 4 5 Caused by: java . lang . NullPointerException six at java . feet / java . util . concurrent . ConcurrentHashMap . putVal ( ConcurrentHashMap . java: 1011 ) eight at java . base / java . util . concurrent . ConcurrentHashMap . init >( ConcurrentHashMap . java: 852 ) 8 at org . springframework . kafka . center . DefaultKafkaConsumerFactory . init >( DefaultKafkaConsumerFactory . java: 125 ) nine at org . springframework . kafka . core . DefaultKafkaConsumerFactory . init >( DefaultKafkaConsumerFactory . java: 98 ) 10 at de . app . config . KafkaConsumerConfig . consumerFactory ( AbstractKafkaConsumerConfig . java: 120 ) 

It turns out, we had been configuring the consumerConfigs bean and setting null values in its properties. The following change from HashMap to ConcurrentHashMap means we can no longer configure null values. We refactored our code and now tests are green. Easy-peasy.

Kafka messages having JsonFilter

1 [ERROR] org .apache .kafka mon .errors .SerializationException : Can also be 't serialize research [Enjoy [payload=MyClass(Id=201000000041600097, . ] having material [my-topic] 2 3 Considering: com.fasterxml.jackson.databind.exc.InvalidDefinitionException: Dont look after PropertyFilter that have id ‘myclassFilter' ; no FilterProvider configured (as a result of site chain: de- .sample .Experience [ "payload" ] ) 4 in the com .fasterxml .jackson .databind .exc .InvalidDefinitionException .away from (InvalidDefinitionException .coffees : 77 ) 

Some of our Java Beans use ato manipulate the serialization and deserialization. This requires a propertyFilter to be configured on the ObjectMapper.

Spring for Apache Kafka made a change to the JsonSerializer , introducing an ObjectWriter . When the ObjectWriter instance is created, the ObjectMapper configuration is copied, not referenced. Our test case was re-configuring the ObjectMapper with the appropriate propertyFilter after the ObjectWriter instance was created. Hence, the ObjectWriter didn't know anything about the propertyFilter (since the configuration was already copied). After some refactoring, changing how we create mujeres solteras petite cerca de ti and configure the JsonSerializer , our test cases were green.

Running our build $ mvn clean verify finally resulted in a green build. Everything is working as it should. We pushed our changes to Bitbucket and everything built like a charm.

Courses discovered updating Spring season Kafka

Lessons discovered during Spring Boot inform

Spring and Spring Boot do a great job documenting their releases, their release notes are well maintained. That being said, upgrading was challenging, it took quite a while before everything was working again. A big part of that is on us, for not following best practices, guidelines, etc. A lot of this code was written when the team was just starting out with Spring and Spring Boot. Code evolves over time, without refactoring and applying those latest practices. Eventually that catches up with you, but we use this as a learning experience and improved things. Our test cases are now significantly better, and we'll keep a closer eye on them moving forward.