Bean initialization with no-default constructor and final fields in Spring Boot

In ConfigurationProperties class I have a Map like this:
@ConfigurationProperties(prefix = "some")
public class SomeConfigurationProperties {
    private Map<String, SomeClass> map = new HashMap<>();
...
}
And I want in mentioned SomeClass all fields to be final, so I had to implement no-default constructor and I am fine with that. The one who is not, is spring initializer, so before starting application, I got this error:
 Caused by: java.lang.NoSuchMethodException: some.package.SomeClass.<init>()
I can't set default constructor in SomeClass cause I will get final fields uninitialized:
The blank final field somefield may not have been initialized
How I should setup initialization of bean SomeClass with no-default constructor, but if it can be without XML Spring configuration, because I am using Spring Boot and don't want to mess up with that.

Комментарии

Отправить комментарий

Популярные сообщения из этого блога

FillChar and StringOfChar under Delphi 10.2 for Win64 Release Target

FillChar and StringOfChar under Delphi 10.2 for Win64 Release Target I have a question about a specific programming problem in Delphi 10.2 Pascal programming language. The StringOfChar and FillChar dont work properly under Win64 Release build on CPUs released before year 2012. Expected result of FillChar is just plain sequence of just repeating 8-bit characters in a given memory buffer. Expected result of StringOfChar is the same, but the result is stored inside a string type. But, in fact, when I compile our applications that worked in Delphi prior to 10.2 by the 10.2 version of Delphi, our applications compiled for Win64 stop working properly on CPUs released before year 2012. The StringOfChar and FillChar dont work properly they return a string of different characters, although in a repeating pattern not just a sequence of the same character as they should. Here is the minimal code enough to demonstrate the issue. Please note that the length of the sequence should be at least ...
Далее...

Intuition behind successive squaring.

Intuition behind successive squaring. I was looking at the successive squaring method used commonly in modular exponentiation problems and was wondering why we are able to square the remainder of successive powers of a number. For example for 7327 mod 853: 71 equiv mod 853 72 equiv 49 mod 853 49 74 equiv 492 mod 853 695 78 equiv 6952 mod 853 227 ... 7256 equiv 6282 mod 853 298 During this operation, why is that we square the remainder and how do we know that doing so will relate to the final answer Im struggling to understand the intuition behind this strategy and why this actually works. You are trying to arrive at the answer with as little computation as possible. You could have arrived to the answer by multiplying 7 mod853 to itself 327 times. But that will take forever. Now, note that any integer 327 for example can be expressed in binary. For example, 327 101000111_2. This means that 327 1 2 4 64 256. If you somehow had the values of 71, 72, 74, 764, 7256 mod 8...
Далее...