Skip to main content

Spring MVC



spring mvc framework is based on model - view - controller design pattern which separates the application logic in to 3 layers.

dispatcher servlet - intercepts all the incoming requests to the application and consults handler mapping to distinguish the controller to be used.

handler mapping - is responsible for finding out the controller who can handle the incoming request. mapping of requested url and the controller class method is done by xml configuration or annotations.

controller - controller will directly use the application classes to process the business request and attach the output to a model. the model will be sent to the view to render. view resolver will take of identifying the view to be rendered.

view resolver - will find the physical file to be rendered from the logical file name sent by the controller.

view - are physical files which can be jsp, velocity template etc.

web.xml - is the web deployment descriptor. declares the contextloaderListner and dispatcherServlet with root-context.xml and servlet-context.xml. it specifies a url mapping for requests to be handled by dispatcher servlet.


 root-context.xml - is loaded upon application startup by springs contextloadlistner class. specifies configuration for root spring container which will be shared by all the servlets and filters.

servlet-context.xml -

is loaded by dispatcher servlet. configurations in the servlet-context.xml is used by dispatcher servlet for all the request coming.
few configurations:
annotation driver - annotations or xml
resources mapping - maps static resourses like images, css which donot have to go through controllers.
internalresoursesviewresolver - tells the view resolver how to get the physical view name from logical name.

context:component-scan - packages to be scanned when using annotation based strategy.


Controller

@controller - specifies the class is a spring controller.
@RequestMapping - species the url to be handled by the method



Ref
http://www.codejava.net/frameworks/spring/spring-mvc-beginner-tutorial-with-spring-tool-suite-ide


Comments

Post a Comment

Popular posts from this blog

Oracle Database 12c installation on Ubuntu 16.04

This article describes how to install Oracle 12c 64bit database on Ubuntu 16.04 64bit. Download software  Download the Oracle software from OTN or MOS or get a downloaded zip file. OTN: Oracle Database 12c Release 1 (12.1.0.2) Software (64-bit). edelivery: Oracle Database 12c Release 1 (12.1.0.2) Software (64-bit)   Unpacking  You should have following two files downloaded now. linuxamd64_12102_database_1of2.zip linuxamd64_12102_database_2of2.zip Unzip and copy them to \tmp\databases NOTE: you might have to merge two unzipped folders to create a single folder. Create new groups and users Open a terminal and execute following commands. you might need root permission. groupadd -g 502 oinstall groupadd -g 503 dba groupadd -g 504 oper groupadd -g 505 asmadmin Now create the oracle user useradd -u 502 -g oinstall -G dba,asmadmin,oper -s /bin/bash -m oracle You will prompt to set to password. set a momorable password and write it down. (mine is orac
9 comments
Read more

DBCA : No Protocol specified

when trying to execute dbca from linux terminal got this error message. now execute the command xhost, you probably receiving No protocol specified xhost:  unable to open display ":0" issue is your user is not allowed to access the x server. You can use xhost to limit access for X server for security reasons. probably you are logged in as oracle user. switch back to default user and execute xhost again. you should see something like SI:localuser:nuwan solution is adding the oracle to access control list xhost +SI:localuser:oracle now go back to oracle user and try dbca it should be working
2 comments
Read more

Java Head Dump Vs Thread Dump

JVM head dump is a snapshot of a JVM heap memory in a given time. So its simply a heap representation of JVM. That is the state of the objects. JVM thread dump is a snapshot of a JVM threads at a given time. So thats what were threads doing at any given time. This is the state of threads. This helps understanding such as locked threads, hanged threads and running threads. Head dump has more information of java class level information than a thread dump. For example Head dump is good to analyse JVM heap memory issues and OutOfMemoryError errors. JVM head dump is generated automatically when there is something like OutOfMemoryError has taken place.  Heap dump can be created manually by killing the process using kill -3 . Generating a heap dump is a intensive computing task, which will probably hang your jvm. so itsn't a methond to use offetenly. Heap can be analysed using tools such as eclipse memory analyser. Core dump is a os level memory usage of objects. It has more informaiton t
Post a Comment
Read more