Stéphane Nicoll opened SPR-15283 and commented
I am integrating WebTestClient for integration tests scenario and being able to lazily resolve the baseURI to use would help me a lot. When a random port is chosen, it is published very late in the lifecycle of the application context so right now it works because I rely on the fact that the WebTestClient is going to be injected in a test (and that happens after).
But that's not very elegant and if I could give a consumer that would be called on first request, that would be much more elegant and robust. Or any way for me to lazily set the base URI.
Affects: 5.0 M5
Comment From: spring-projects-issues
Rossen Stoyanchev commented
Is this still an issue, and if so what kind of API change do you imagine?
Comment From: spring-projects-issues
If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed.
Comment From: spring-projects-issues
Closing due to lack of requested feedback. If you would like us to look at this issue, please provide the requested information and we will re-open the issue.