I followed the solution in the following link, and it works fine: Access Spring beans from a servlet in JBoss public class MyServlet extends HttpServlet { @Autowired private MyService myService; public void init(ServletConfig config) { super.init(config); SpringBeanAutowiringSupport.processInjectionBasedOnServletContext(this, config.getServletContext()); } }
Since SpringBoot 1.4, all the classes changed and deprecated https://github.com/spring-projects/spring-boot/wiki/Spring-Boot-1.4.0-M2-Release-Notes. Replace the Runner and Configuration with the ones below. SpringRunner will detect the test framework for you. @RunWith(SpringRunner.class) @SpringBootTest(classes = { FileService.class, AppProperties.class, DownloadConfigEventHandler.class }) @EnableConfigurationProperties public class ConfigMatrixDownloadAndProcessingIntegrationTests extends ConfigMatrixDownloadAbstractTest { // @Service FileService @Autowired private FileService fileService; // @Configuration AppProperties @Autowired private AppProperties … Read more
Spring 4 and older support the ability to automatically collect all beans of a given type and inject them into a collection or array. Here is an example: @Component public class Car implements Vehicle { } @Component public class Bus implements Vehicle { } @Component public class User { @Autowired List<Vehicle> vehicles; // contains both … Read more
You can also use the @Value annotation within the constructor: class Test( @Value(“\${my.value}”) private val myValue: Long ) { //… } This has the benefit that your variable is final and none-nullable. I also prefer constructor injection. It can make testing easier.
Just run a mvn clean package and then restart the spring boot application from either Eclipse/IntelliJ.
public enum ReportType { REPORT_1(“name”, “filename”), REPORT_2(“name”, “filename”); @Component public static class ReportTypeServiceInjector { @Autowired private DataPrepareService dataPrepareService; @PostConstruct public void postConstruct() { for (ReportType rt : EnumSet.allOf(ReportType.class)) rt.setDataPrepareService(dataPrepareService); } } […] } weekens’ answer works if you change inner class to static so spring can see it
You can absolutely inject mocks on MyLauncher in your test. I am sure if you show what mocking framework you are using someone would be quick to provide an answer. With mockito I would look into using @RunWith(MockitoJUnitRunner.class) and using annotations for myLauncher. It would look something like what is below. @RunWith(MockitoJUnitRunner.class) public class MyLauncherTest … Read more
Normally, both will work, you can autowire interfaces or classes. There’s probably an autoproxy generator somewhere in your context, which is wrapping your boo bean in a generated proxy object. This proxy object will implement TheInterface, but will not be a TheClass. When using autoproxies, you need to program to the interface, not the implementation. … Read more
I want to test in isolation class A. You should absolutely mock B, rather than instantiate and inject an instance of B. The point is to test A whether or not B works, so you should not allow a potentially broken B interfere with the testing of A. That said, I highly recommend Mockito. As … Read more
I know about these two options: Use @SpyBean annotation from spring-boot-test as the only annotation @Autowired @InjectMocks private ProductController productController; @SpyBean private ProductService productServiceSpy; Use Java reflection to “autowire” the spy object, e.g. ReflectionTestUtils @Autowired private ProductController productController; @Autowired private ProductService productService; @Before public void setUp() { ProductService productServiceSpy = Mockito.spy(productService); ReflectionTestUtils.setField(productController, “productService”, productServiceSpy); }