Skip to main content

Spring - the webapplicationcontext

The WebApplicationContext contains all web-related beans responsible for making your logic accessible to users. These may include beans to handle multilingual websites and beans defining mappings from incoming requests to controllers. The WebApplicationContext will be initialized by the DispatcherServlet. When using default values, it will be of class XMLWebApplicationContext.


The WebApplicationContext is a child context of the ApplicationContext, which will contain middle-tier services such as transactional service layer objects, data sources, and data access objects.

It's a best practice to keep a clear separation between middle-tier services and web-related components.

The XmlWebApplicationContext is used by the DispatcherServlet to model the model the workflow involved with web applications. The DispatcherServlet inspects the WebApplicationContext for declarations of some special beans of some special beans used to execute the workflow. Some of them will have defaults; some of them you will have to provide yourself. Those beans are:
. A handlerMapping is responsible for determining the appropriate controller to dispatch a request to.
. A ViewREsolver is capable of mapping logic view names to actual views, such as a JavaServer page, a Velocity template. to apply to the contents of the model
. A localeREsolver will resolve the locale to use when rendering a view or prforming other language-dependent logic.
. A MultipartResolver provides support for uploading files with HTTP, for instance by using Commons FieldUpload.
. HandlerExceptionResolvers provide support for catching unexpected exceptions and , for example, informing the user by providing a predfefined view displaying information about the exception.

. Controllers provide the interactional logic of your web application and access to collaborators from your middle tier, which provide actual business services, which should be independent of any particular interface type.
. HandlerInterceptors provide the capability to intercept incoming HTTP requests. Interceptors are useful to add additional crosscutting behavior to your web infrastructure, such as security, loggin , and auditing.

WebApplicationContext inherits all functionality of the ApplicationContext. Beyond that, it holds a reference to the ServletContext.

Comments

Popular posts from this blog

Stretch a row if data overflows in jasper reports

It is very common that some columns of the report need to stretch to show all the content in that column. But  if you just specify the property " stretch with overflow' to that column(we called text field in jasper report world) , it will just stretch that column and won't change other columns, so the row could be ridiculous. Haven't find the solution from internet yet. So I just review the properties in iReport one by one and find two useful properties(the bold highlighted in example below) which resolve the problems.   example:
<band height="20" splitType="Stretch"> <textField isStretchWithOverflow="true" pattern="" isBlankWhenNull="true"> <reportElement stretchType="RelativeToTallestObject" mode="Opaque" x="192" y="0" width="183" height="20"/> <box leftPadding="2"> <pen lineWidth="0.25"/> …

JasperReports - Configuration Reference

Spring - Operations with jdbcTemplate

This class manages all the database communication and exception handling using a java.sql.Connection that is obtained from the provided DataSource. JdbcTemplate is a stateless and threadsafe class and you can safely instantiate a single instance to be used for each DAO.


Use of Callback Methods
JdbcTemplate is based on a template style of programming common to many other parts of Spring. Some method calls are handled entirely by the JdbcTemplate, while others require the calling class to provide callback methods that contain the implementation for parts of the JDBC workflow. This is another form of Inversion of Control. Your application code hands over the responsibility of managing the database access to the template class. The template class in turn calls back to your application code when it needs some detail processing filled in. These callback methods are allowed to throw a java.sql.SQLException, since the framework will be able to catch this exception and use its built-in excepti…