That said, may possibly not add up to do this. I can not inquire the newest builders why it was done this means, they aren’t here anymore. That it project’s facts is only able to find out with the Git records.
Lessons read upgrading Spring Analysis Rest
We believe the audience is having fun with Spring season Study Other individuals wrong, wrongly blend WebMVC basics. Whenever we hadn’t done this right from the start, one thing will have work with much much easier.
We have been today through with the Spring Investigation People migration. It is time to move to our very own next Spring season component, Spring Kafka.
Spring season Kafka
Springtime Kafka, or rather Springtime to possess Apache Kafka , is an excellent means to fix explore Kafka on the Spring season methods. It offers easy-to-use themes getting sending texts and normal Spring annotations to possess taking texts.
Configuring the latest customers
step one [ERROR] coffee.lang.IllegalStateException: Failed to weight ApplicationContext 2 step step three As a result of: org.springframework.kidney beans.facility.BeanCreationException: Mistake doing bean with name 'consumerFactory' discussed in classification path financial support [ de / application / 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 . key . 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 investigation [Enjoy [payload=MyClass(Id=201000000041600097, . ] to possess thing [my-topic] 2 3 Because of: com.fasterxml.jackson.databind.exc.InvalidDefinitionException: Dont look after PropertyFilter which have id ‘myclassFilter' ; no FilterProvider designed (as a result of reference strings: de .try .Experiences [ "payload" ] ) 4 from the com .fasterxml .jackson .databind .exc .InvalidDefinitionException .out-of (InvalidDefinitionException .java : 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.
Courses read updating Spring season Kafka
Sessions read throughout the Springtime Boot posting
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 haga clic en este sitio 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.