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()); } }
Adding a custom health check is easy. Just create a new Java class, extend it from the AbstractHealthIndicator and implement the doHealthCheck method. The method gets a builder passed with some useful methods. Call builder.up() if your health is OK or builder.down() if it is not. What you do to check the health is completely … Read more
public static void main(String[] args) { // spring 4.0.0 org.springframework.security.crypto.password.PasswordEncoder encoder = new org.springframework.security.crypto.bcrypt.BCryptPasswordEncoder(); // $2a$10$lB6/PKg2/JC4XgdMDXyjs.dLC9jFNAuuNbFkL9udcXe/EBjxSyqxW // true // $2a$10$KbQiHKTa1WIsQFTQWQKCiujoTJJB7MCMSaSgG/imVkKRicMPwgN5i // true // $2a$10$5WfW4uxVb4SIdzcTJI9U7eU4ZwaocrvP.2CKkWJkBDKz1dmCh50J2 // true // $2a$10$0wR/6uaPxU7kGyUIsx/JS.krbAA9429fwsuCyTlEFJG54HgdR10nK // true // $2a$10$gfmnyiTlf8MDmwG7oqKJG.W8rrag8jt6dNW.31ukgr0.quwGujUuO // true for (int i = 0; i < 5; i++) { // “123456” – plain text – user input from user interface … Read more
I’d call what you’re after an integration test based on the terminology in the Spring reference manual. How about doing something like: import static org.springframework.test.web.ModelAndViewAssert.*; @RunWith(SpringJUnit4ClassRunner.class) @ContextConfiguration({/* include live config here e.g. “file:web/WEB-INF/application-context.xml”, “file:web/WEB-INF/dispatcher-servlet.xml” */}) public class MyControllerIntegrationTest { @Inject private ApplicationContext applicationContext; private MockHttpServletRequest request; private MockHttpServletResponse response; private HandlerAdapter handlerAdapter; private MyController controller; … Read more
I finally was able to figure out a simple solution without the @Query annotation. List<People> findDistinctByNameNotIn(List<String> names); Of course, I got the people object instead of only Strings. I can then do the change in java.
If you are using spring you can do the following: public static HttpServletRequest getCurrentHttpRequest(){ RequestAttributes requestAttributes = RequestContextHolder.getRequestAttributes(); if (requestAttributes instanceof ServletRequestAttributes) { HttpServletRequest request = ((ServletRequestAttributes)requestAttributes).getRequest(); return request; } logger.debug(“Not called in the context of an HTTP request”); return null; }
This is to do with Tomcat not being able to load previously serialized web sessions that had been saved on an earlier shutdown. This may be because Tomcat didn’t shutdown cleanly and so session objects got corrupted during serialization. One way to make this error go away would be to disable session persistence across restarts. … Read more
Take a look at uncle Bob’s Package Design Principles. He explains reasons and motivations behind those principles, which I have elaborated on below: Classes that get reused together should be packaged together so that the package can be treated as a sort of complete product available for you. And those which are reused together should … Read more
Yes you can do more than one. Be sure to set ignoreUnresolvablePlaceholders so that the first will ignore any placeholders that it can’t resolve. <bean id=”ppConfig1″ class=”org.springframework.beans.factory.config.PropertyPlaceholderConfigurer”> <property name=”ignoreUnresolvablePlaceholders” value=”true”/> <property name=”locations”> <list> <value>classpath*:/my.properties</value> </list> </property> </bean> <bean id=”ppConfig2″ class=”org.springframework.beans.factory.config.PropertyPlaceholderConfigurer”> <property name=”ignoreUnresolvablePlaceholders” value=”false”/> <property name=”locations”> <list> <value>classpath*:/myOther.properties</value> </list> </property> </bean> Depending on your application, you … Read more
From Spring Boot 2.2, it is at last possible to define an immutable class decorated with @ConfigurationProperties. The documentation shows an example. You just need to declare a constructor with the fields to bind (instead of the setter way) and to add the @ConstructorBinding annotation at the class level to indicate that constructor binding should … Read more