Closed wilkinsona closed 9 years ago
Hi @wilkinsona, first of all thanks for this solution, it has been of great help for me. And, how about this issue using Spring Webflux and Netty?
I've had the same issue, and temporally I did this to solved it:
@Bean
public NettyReactiveWebServerFactory getNettyReactiveWebServerFactory() {
return new NettyReactiveWebServerFactory();
}
But, it think that it's a similar issue.
Thanks very much for letting us know, @brianou7. That is indeed a similar issue. I've opened https://github.com/spring-projects/spring-boot/issues/22275 so that we can fix it.
@Bean public NettyReactiveWebServerFactory getNettyReactiveWebServerFactory() { return new NettyReactiveWebServerFactory(); }
I am new to working within the bowels of Spring-webflux, however do I need to add this bean in the test (that uses the DynamoDBLocal Embedded DB)?
@shapan1 No, that shouldn't be necessary due to the fix made for https://github.com/spring-projects/spring-boot/issues/22275. If you believe it is necessary and would like us to take a closer look, please open a new issue with a minimal sample that reproduces the problem.
LocalDynamoDB depends on some of Jetty, but not all of the bits that Boot needs. We need to tighten up the classpath conditions.
A workaround is to add a
@Bean
that forces the use of Tomcat:Stack Overflow question: http://stackoverflow.com/questions/32862876/springboot-and-dynamodb-local-embedded/32921693#32921693