To use themes in your web application, you must set up an implementation of the org.springframework.ui.context.ThemeSource interface. The WebApplicationContext interface extends ThemeSource but delegates responsibilities to a dedicated implementation. By default, the delegate is an org.springframework.ui.context.support.ResourceBundleThemeSource implementation that loads properties files from the root addAttribute("message", "Hello World!"); return "index"; } } Kotlin import org.springframework.ui.set @Controller class HelloController { @GetMapping("/hello") fun handle(model: Model): String

"getDescription()" method to BeanDefinition interface (exposing the value of the XML bean description element) * AbstractFactoryBean uses bean ClassLoader for the generation of early singleton proxies * Pr through lock on unified monitor * added "container-class" attribute to "jms:listener-container" element, for specifying a custom implementation class * MessageListenerAdapter and JmsInvokerServiceExporter support for a target as last element in "interceptorNames" in favor of "targetName" * ProxyFactoryBean assumes a target bean if type cannot be determined for last element in "interceptorNames" list *

AutowiredAnnotationBeanPostProcessor to correctly cache a collection with a single autowired bean as element * fixed AutowiredAnnotationBeanPostProcessor to not cache special dependencies such as request and in case of Spring jars deployed as shared libs * added "context:property-override" configuration element, as a sibling to "context:property-placeholder" Package org.springframework.core * introduced as suggested class name * added "depends-on" attribute to "lang:bsh/groovy/jruby" configuration element Package org.springframework.test * TestContextManager ignores default TestExecutionListeners that

BeanWrapper interface) * BeanWrapper supports well-known collection implementation types for generic element conversion again (like Spring 2.0) * TypeConverterDelegate protects its text conversion step against an") ignores non-static inner and local classes * "context:property-placeholder" configuration element does not require a "location" attribute (for system properties) Package org.springframework.core correctly detect an existing global transaction (ignoring local tx contexts) Package org.springframework.ui * fixed ModelMap's "mergeAttributes" to correctly copy new attributes into the model * added "containsAttribute"

support for a target as last element in "interceptorNames" in favor of "targetName" * ProxyFactoryBean assumes a target bean if type cannot be determined for last element in "interceptorNames" list * ClassPathXmlApplicationContext (for Apache CXF compatibility) * added "registration" attribute to mbean-export element, accepting "failOnExisting"/"ignoreExisting"/"replaceExisting" * CommonAnnotationBeanPostProcessor the session bean object * added "cache-session-bean" attribute to "jee:remote-slsb" configuration element * Spring 2.5 "jee:*" config elements use resource-ref="true" by default (non- resource-ref names

support for a target as last element in "interceptorNames" in favor of "targetName" * ProxyFactoryBean assumes a target bean if type cannot be determined for last element in "interceptorNames" list * ClassPathXmlApplicationContext (for Apache CXF compatibility) * added "registration" attribute to mbean-export element, accepting "failOnExisting"/"ignoreExisting"/"replaceExisting" * CommonAnnotationBeanPostProcessor the session bean object * added "cache-session-bean" attribute to "jee:remote-slsb" configuration element * Spring 2.5 "jee:*" config elements use resource-ref="true" by default (non- resource-ref names

...................................................................... 30 3.10. Using the alias element to add aliases for existing beans ....................................................... 30 3.11 it; it's not an all-or-nothing solution. Existing frontends using WebWork, Struts, Tapestry, or other UI frameworks can be integrated perfectly well with a Spring-based middle-tier, allowing you to use the thing you need to do is wire up your business logic using an ApplicationContext and integrate your Web UI layer using a WebApplicationContext. Remoting usage scenario When you need to access existing code

...................................................................... 28 3.10. Using the alias element to add aliases for existing beans ....................................................... 29 3.11 it; it's not an all-or-nothing solution. Existing frontends using WebWork, Struts, Tapestry, or other UI frameworks can be integrated perfectly well with a Spring-based middle-tier, allowing you to use the thing you need to do is wire up your business logic using an ApplicationContext and integrate your Web UI layer using a WebApplicationContext. Remoting usage scenario When you need to access existing code

...................................................................... 30 3.10. Using the alias element to add aliases for existing beans ....................................................... 31 3.11 it; it's not an all-or-nothing solution. Existing frontends using WebWork, Struts, Tapestry, or other UI frameworks can be integrated perfectly well with a Spring-based middle-tier, allowing you to use the thing you need to do is wire up your business logic using an ApplicationContext and integrate your Web UI layer using a WebApplicationContext. Remoting usage scenario When you need to access existing code

...................................................................... 41 3.10. Using the alias element to add aliases for existing beans ....................................................... 42 3.11 it; it's not an all-or-nothing solution. Existing frontends using WebWork, Struts, Tapestry, or other UI frameworks can be integrated perfectly well with a Spring-based middle-tier, allowing you to use the thing you need to do is wire up your business logic using an ApplicationContext and integrate your Web UI layer using a WebApplicationContext. Remoting usage scenario When you need to access existing code