springs | facebook's rebound | Animation library

When something like this happens, it's usually due to bad ordering of initialization.

The initialization of the Player class goes this way:

1. the name property has its backing field initialized with the _name value
2. the init block is run, and tries to access name
3. the getter of name tries to read the hometown property, but fails because hometown is still not initialized
4. ...if things had gone right, the hometown property would be initialized now with the lazy delegate

So basically you're trying to access hometown before the lazy delegate is configured. If you move hometown's declaration above the init block, you should be fine.

You can see the fix in action on the playground

The problem is that you have 2 times anyRequest() in your configuration. This is no longer allowed starting with Spring Security 5.2.

You already wrote the answer yourself. You already have the for loop to use. Put the @Scheduled on the method with the for-loop, which calls a taskA method in an external class, and which has the @Async annotation.

You can add JwtAuthorizationTokenFilter and call it before each request

In your security config use addFilterBefore()

In ApplicationConf you tell Hibernate to scan the com.package.repository package but your Bus entity class seems to be in the com.package.model package.

Try changing:

If you want benefit from the automatic features of Spring Boot, your @Configuration class must be annotated with @EnableAutoConfiguration.

Since the auto-configuration already creates a DispatcherServlet bound to /, you can safely change your WebAppInitializer class to:

One potential problem could be with your Java package structure. Spring Boot does by default only look for annotated within the Java package (and it's children) that contains the Application class.

If your OktaService is in a location of your package structure, then it won't be found by default. As an example, if you have Application in com.example.myapp.ui and OktaService in com.example.myapp.service, then it won't work. If this is the case, then you can either change your package structure or set the scanBasePackages property in @SpringBootApplication to define a location that covers the entire application.

You can define your own way to handle the exceptions, like this:

I finally solved this by removing the line :