Spring Boot docs on error handling: http://docs.spring.io/spring-boot/docs/current/reference/htmlsingle/#boot-features-error-handling. One way you can control the JSON is by adding a @Bean of type ErrorAttributes. @Bean ErrorAttributes errorAttributes() { return new MyErrorAttributes(); }
A @Controller is a more flexible way to define a form / wizard. You are supposed to map methods to requests based on requested path / request parameters / request method. So instead of defining a list of views and processing the request based on some required “step” parameter, you can define the steps of … Read more
Use this class: http://static.springsource.org/autorepo/docs/spring/3.2.0.M1/api/org/springframework/cache/support/CompositeCacheManager.html like this: <cache:annotation-driven cache-manager=”cacheManager” /> <bean id=”cacheManager” class=”org.springframework.cache.support.CompositeCacheManager”> <property name=”cacheManagers”> <array> <ref bean=”cacheManager1″ /> <ref bean=”cacheManager2″ /> </array> </property> <property name=”addNoOpCache” value=”true” /> </bean>
In spring 3.0 there is an annotation: @Lazy(false). But note that beans are eager by default.
In your configuration class, use @EnableTransactionManagement annotation. Define a transaction manager in this class as: @Bean(name=”txName”) public HibernateTransactionManager txName() throws IOException{ HibernateTransactionManager txName= new HibernateTransactionManager(); txName.setSessionFactory(…); txName.setDataSource(…); return txName; } There on, in your class/method that executes transactional job(s), annotate as follows: @Transactional(“txName”) or @Transactional(value = “txName”) This is how you would tie a name … Read more
Indeed you can implement a custom strongly typed security annotation, though this is rather bothersome. Declare your annotation enum Permission { USER_LIST, USER_EDIT, USER_ADD, USER_ROLE_EDIT } @Target(ElementType.METHOD) @Retention(RetentionPolicy.RUNTIME) @interface Permissions { Permission[] value(); } Declare the custom implementation of org.springframework.security.access.ConfigAttribute to be used by security pipeline class SecurityAttribute implements ConfigAttribute { private final List<Permission> permissions; … Read more
After taking a look at SpEL specification and combined with @javaguy’s answer I came up with this: @Value(“${my.list.of.strings:}#{T(java.util.Collections).emptyList()}”) private List<String> myList;
They cannot be optional, no. If you need that, you need two methods to handle them. This reflects the nature of path variables – it doesn’t really make sense for them to be null. REST-style URLs always need the full URL path. If you have an optional component, consider making it a request parameter instead … Read more
this worked, registry.addResourceHandler(“/resources/**”).addResourceLocations(“/resources/”); and in the jsp files I referred to the static resources like <link href=”https://stackoverflow.com/questions/25061237/resources/css/bootstrap.css” rel=”stylesheet” media=”screen”>
@ResponseStatus(HttpStatus.OK) means that the request will return OK if the handling method returns normally (this annotation is redundant for this case, as the default response status is HttpStatus.OK). If the method throws an exception, the annotation does not apply; instead, the status will be determined by Spring using an exception handler. How can I handle … Read more