Dmitry :
Could somebody help me to do the following:
@PostContruct public void func() {
webclient.get()...subscribe();
}
webclient call will terminate after func() returns. Most likely it will happen before the first request comes in, but no guarantees. The other option is to block(), which defeats the purpose of being reactive.
What would be the right way to make reactive calls in @PostConstruct methods?
Thank you.
vins :
I created a simple bean.
Synchronous update:
@Component
public class BeanTest {
private String postConstructValue;
@PostConstruct
public void init(){
try {
Thread.sleep(5000);
this.postConstructValue = "Construction done";
} catch (InterruptedException e) {
e.printStackTrace();
}
}
@Scheduled(fixedRate = 500)
public void print(){
System.out.println(
this.postConstructValue
);
}
}
- It took some time for app to start (more than 5 seconds) because we simulated some time consuming process in the post construct. Scheduled print method started printing only after the app started. It started printing "Construction done" message.
Asynchronous update:
@Component
public class BeanTest {
private String postConstructValue;
@PostConstruct
public void init(){
Flux.just("Construction done")
.delayElements(Duration.ofSeconds(5))
.subscribe(s -> this.postConstructValue = s);
}
@Scheduled(fixedRate = 500)
public void print(){
System.out.println(
this.postConstructValue
);
}
}
- Now in this approach, the app started within 2 seconds. Print method starting printing
nullfor few seconds. Then it started printing "Construction done". It does not terminate the Flux postConstruct value update. It happened asynchronously.
Reactive approach is good when you want a non-blocking behavior and getting something done asynchronously. If you think that your component creation should wait for proper construction, you have to block! Otherwise, you can go with second approach.
Guess you like
Origin http://10.200.1.11:23101/article/api/json?id=409958&siteId=1