However, it may not seem sensible to do this. I can not inquire the latest builders as to why it absolutely was done this way, they aren’t right here anymore. That it project’s tale can simply find out with their Git record.

Lessons learned upgrading Spring season Research People

We suspect we’re playing with Springtime Analysis Rest completely wrong, incorrectly blend WebMVC rules. Whenever we ВїCuГЎnto cuesta casarse con una mujer mexicana had not done this right from the start, something would have work with far easier.

We’re today done with this new Spring season Data Other individuals migration. It is time to disperse to all of our 2nd Springtime module, Spring season Kafka.

Spring Kafka

Spring Kafka, or in other words Springtime for Apache Kafka , is a superb way to explore Kafka on your Springtime tactics. It provides effortless-to-explore templates to have sending texts and normal Spring annotations getting sipping texts.

Configuring this new people

step step one [ERROR] coffee.lang.IllegalStateException: Did not load ApplicationContext 2 step 3 For the reason that: org.springframework.beans.factory.BeanCreationException: Error creating bean which have term 'consumerFactory' defined in group highway financing [ de / software / config / KafkaConsumerConfig . class ]: cuatro 5 Caused by: java . lang . NullPointerException 6 at java . legs / java . util . concurrent . ConcurrentHashMap . putVal ( ConcurrentHashMap . java: ten11 ) 7 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 texts that have JsonFilter

1 [ERROR] org .apache .kafka mon .mistakes .SerializationException : Can 't serialize data [Knowledge [payload=MyClass(Id=201000000041600097, . ] having question [my-topic] 2 3 Considering: com.fasterxml.jackson.databind.exc.InvalidDefinitionException: Never manage PropertyFilter that have id ‘myclassFilter' ; no FilterProvider configured (through resource strings: de .sample .Knowledge [ "payload" ] ) 4 within com .fasterxml .jackson .databind .exc .InvalidDefinitionException .out of (InvalidDefinitionException .coffee : 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 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.

Lessons discovered upgrading Spring season Kafka

Training learned throughout the Springtime Boot change

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.