Skip to main content

SpringControllerClass

ParameterizableViewController
===========================
In order to display webpage without processing request, then instead of taking separate user
defined controller class we can configure this class by specifying view name "viewName" property
value. This is usefull to display webpage for hyperlink generated request. Ex: aboutUs, contactUs.

UrlFileNameViewController
=========================
Actually this is alternate of ParameterizableViewController classes configuration to render multiple
webpages/views without having any request processing for multiple hyperlink generated request like
aboutUs, contactUs.

AbstractController
=================
Generally for hyperlink generated request to get dynamic content having request processing we
should go for AbstractController. There is no form submission in request but request processing
required to display dynamic webpage as output. Ex: ListOfEmployees, viewProfiles.

AbstractCommandController
=========================
If our source page having form page with no server side form validation and client
side form validation optional and no form handling then we go for AbstractCommandController.

SimpleFormController:
========================
The simpleFormCOntroller display from page based on "formbased values if the request is initial phase request." ic there is no need taking seprate parametrized view controller for launching from page.

If our source page having form page with form validation, form handling and looking
to get Dest page either as static or dynamic page having request processing then we
use SimpleFormController.

MultiActionController
=====================
When formpage contains multiple submit buttons then instead of taking multiple AbstractCommandController
or SimpleFormController takes single MultiActionController having multiple user-defined methods to process
request of multiple submit buttons on one per method basis.
or
If sourcepage is form submission having multiple submit buttons with optional form validation and
is required dest page is static or dynamic webpage that should come after request processing then
we should go for MultiActionController. Ex: Insert, Update, Delete, View, Cancel in one form.

AbstractWizardFormController
=============================
So for we worked with single form page based controller classes like SimpleFormController or
MultiActionController and etc... in order to work with multiple form pages that comes in a sequence
having wizard style we need to use AbstractWizardFormController by specifying list of form pages
to display in a sequence. For this we use _cancel, _finish, _target..

Annotation we are using in Spring:
@Name
@Controller
@Autowired
@Resource
@RequestMapping
@Required
@Component
@Repository
@Service
@Inject
@ExceptionHandler

Comments

Post a Comment

Popular posts from this blog

Mockito interview Questions

1.       Question 1. What Is Mockito? Answer : Mockito allows creation of mock object for the purpose of Test Driven Development and Behavior Driven development. Unlike creating actual object, Mockito allows creation of fake object (external dependencies) which allows it to give consistent results to a given invocation. 2.       Question 2. Why Do We Need Mockito? What Are The Advantages? Answer : Mockito differentiates itself from the other testing framework by removing the expectation beforehand. So, by doing this, it reduces the coupling. Most of the testing framework works on the "expect-run-verify". Mockito allows it to make it "run-verify" framework. Mockito also provides annotation which allows to reduce the boilerplate code. 3.       Question 3. Can You Explain A Mockito Framework? Answer : In Mockito, you always check a particular class. The dependency in that class is injected using m...
2 comments
Read more

REST Methods

GET ============================================= HTTP GET method is used to **read** (or retrieve) a representation of a resource. According to the design of the HTTP specification, GET requests are used only to read data and not change it. Therefore, when used this way, they are considered safe. That is, they can be called without risk of data modification or corruption. Means calling it once has the same effect as calling it 10 times. Additionally, GET is idempotent which means that making multiple identical requests ends up having the same result as a single request. Donot expose unsafe operations via GET. It should never modify any resources on the server. Example: ------------    GET http://www.example.com/customers/12345/orders POST =================================== -> The POST verb is most-often utilized to **create** new resources. In particular, it's used to create subordinate resources. -> That is, subordinate to some other (e.g. parent) reso...
Post a Comment
Read more