Archive for the ‘Java’ Category

Unsatisfied Dependency Exception : CDI 1.1 + Bean Validation + GlassFish 4.0 -> requires jersey-gf-cdi.jar upgrade

with one comment

Recently,  I faced Unsatisfied Dependency Exception, when trying to integrate BeanValidation with CDI 1.1 . Independently (without integration) everything worked fine. Looks like, the present Glassfish version 4.0 doesn’t support CDI 1.1 + Bean Validation together.

To be still clearer, Jersey (reference implementation for JAX-RS)  jar related to CDI  i.e., jersey-gf-cdi.jar in GF-4.0 version, is not supporting this integration .

I made the below changes, for Bean Validation integration with CDI 1.1 in Glassfish 4.0 to work.

Applicaiton Server used : Glassfish 4.0

Technology : JEE-7, CDI 1.1

Exception Trace :

org.glassfish.hk2.api.UnsatisfiedDependencyException: There was no object available for injection at Injectee(requiredType=Foo,parent=Foo,qualifiers={@foo()}),position=-1,optional=false,self=false,unqualified=null,350112977)

at org.jvnet.hk2.internal.ThreeThirtyResolver.resolve(
at org.jvnet.hk2.internal.Utilities.justInject(
at org.jvnet.hk2.internal.ServiceLocatorImpl.inject(
at org.jboss.weld.bean.ManagedBean.create(
at org.jboss.weld.context.unbound.DependentContextImpl.get(


Solution :

  • Download jersey-gf-cdi-2.0.jar . Download specifically 2.0 version for glassfish4.0. If other higher versions 2.10 are used, incompatibilty with other jars (firstly with jersey-server.jar) will arise.

  • Rename the jar to jersey-gf-cdi.jar
  • Replace it in glassfish4.0/glassfish/modules/
  • Delete osgi-cache folder -> Path : glassfish4.0/glassfish/domains/domain1/osgi-cache
  • Refresh and restart glassfish. New osgi-cache will be created in domain 1 with the latest jersey-gf-cdi.jar. Problem will be solved 🙂

This issue will be resolved in Glassfish-4.0.1 version (not released yet). We’ll have to do the above till GF-4.0.1 is released.

Have a great day 🙂

Reference :

CDI – Lifecycle Management by Container

with 3 comments

We know that, CDI Managed Beans are contextual. Their lifecycle management is done by the container. One of its main advantages is type-safe dependency injection.

But how does it do it?
In the below code, during application initialization process, the container checks for Type-Safe Resolution for News bean annotated with @Inject and then instantiates it.


Here the container checks ,

  • if the bean type is equal to the required type(type: News here) at the injection point in Consumer Bean class.
  • if the qualifier of bean is equal to the required qualifier at the injection point.
  • (If no qualifier specified , then default qualifier is @Default)

public class News {
  public String getLatestNews(){
    return "FIFA 2014 WorldCup";

@Path(value = "consumer")
public class Consumer {

  private News news;

  public String tweetLatestNews(){
    return news.getLatestNews();

Any mismatch will result in unsatisfied or ambiguous dependency problem.




EJB class able to render REST WebService via Annotation

with 3 comments

Advancements in Java, especially the advent of JEE6 and JEE7  has eased the way we code.
Deployment descriptors for Servlet classes, Entity classes, Web Services are being replaced by annotations, thus advancing towards the concept of Convention over Configuration.

Below is a simple example on how to make a Session Bean class provide a RESTful WebService using annotations.

Here I have used JEE 7 and GlassFish 4 Application Server.
Note: As of now, JEE7 is  compatible only with GlassFish 4.

Here I have considered WebsterPublications example which has,

  •  DictionaryEntity – Entity class
  •  DictionaryResource – EJB+REST Service Provider Class

STEP 1: Create

@Table(name = "WP_DICTIONARY")
public class DictionaryEntity {

    private Long id;

    @NotNull(message = "Enter a word")
    private String word;

    @NotNull(message = "Enter the word's meaning")
    private String meaning;

    //Getters , Setters

Attributes can be annotated with constraints like @NotNull, @Pattern and can be made to through message during runtime, when violations occur.

STEP 2: Create

@Path(value = "dictionary")
public class DictionaryResource {

    @PersistenceContext(unitName = "webster")
    private EntityManager em;

    @Path(value = "wordlist")
    public List<DictionaryEntity> getWordList(){
        Query query=em.createQuery("select d from DictionaryEntity d");
        List<DictionaryEntity> wordList=query.getResultList();
        return wordList;

Here we can notice that this class apart from acting as a Stateless Bean also provides a RESTful WebService.
i.e., stateless session bean class providing the output object via REST WebService (Here JSON object got as Output).

Mapping the persistence unit and connection pooling in glassfish server is done (default Derby DB used).

STEP 3: Create

Since DictionaryResource acts like a Servlet by providing WebService, it’s essential to provide its entry in web.xml.
But this can also be done through annotation even.

WebsterRESTConfig class is created that extends Application and adds DictionaryResource as its resource class.Like DictionaryResource various other resource class can also be added."webresources")
public class WebsterRESTConfig extends Application {

    public Set<Class<?>> getClasses() {
        Set<Class<?>> resources = new java.util.HashSet<>();
        return resources;

   private void addRestResourceClasses(Set<Class<?>> resources) {

Here @ApplicationPath is equivalent to the servlet-mapping URL-Pattern that we would specify in web.xml.

Also note, while instantiating Set<Class<?>> resources = new java.util.HashSet<>(); I haven’t used generics in HashSet<> but have just used a plane Diamond notation. This is one of the light-weight changes in Java SE 7.

Now when we give the path as:


The result is obtained as below.


In my this post I wanted to highlight on the concept of Convention Over Configuration which is taking a great leap as the advancements in JEE versions are happening.Without even taking the pain to write the conventional web.xml deployment descriptor, we are now that able to  configure those settings by using simple annotations at the right place.

You can find the above source code in my GitHub repository. 

I wish you all a BLASTFUL 2014 🙂

Reflection – Dynamic Typing

with 4 comments

Today wanted to add some quick notes on my findings on Dynamic Languages.

To start with, lets look into Reflection.

REFLECTION” –  in common generic terms means a Mirror Image of something.

It carries the same meaning in Java. It means getting the mirror image of a class.
The microscopic details of a class can be explored during the runtime by specifying the class name dynamically. During this process the JVM interacts with the object of unknown type.

Let’s see an example,

public static void main(String[] args) {
	try {
		Class class1=Class.forName("aish.vaishno.musicstore.dao.MusicStoreDaoImpl");
		Package package1=class1.getPackage();
		System.out.println("Package Name with Version : "+package1);

		String canonicalName=class1.getCanonicalName();
		System.out.println("\nCanonical/Standard name of Field class: "+canonicalName);

		Method[] methods=class1.getMethods();
		System.out.println("\nMethods present in Field class:");
		for (int i = 0; i < methods.length; i++) {

                Class[] classes=class1.getInterfaces();
                System.out.println("Interface implemented: ");
                for (int i = 0; i < classes.length; i++) {
	} catch (ClassNotFoundException e) {

While specifying the className dynamically, the .class file of that particular class is opened and examined during the runtime .By Reflection, the package ,Method , Interface, modifier informations and etc.,can be retrieved.

But the demerits of this is ,

  • It slows down the performance
  • private fields and methods can be accessed.

Reflection concept is used in ,
Spring – while scanning through the packages.
ORM– when data from database is being mapped to the attributes in Entity Bean.
Likewise in Serialisation/Deserialisation, Remote Method Invocation and etc.,

Dynamic Language plays a major role in Rapid Application Development(RAD).

Groovy and Dynamic Language updates coming up.



Written by thangaveluaishwarya

August 9, 2013 at 9:48 PM

Spring + JPA – Example with Exception/Error – Fixing

with 7 comments

In this post ,I have given a  simple example on how to use JPA in Spring Framework.
You can find the source code of the below example in my Github link here.

I have considered a MusicStore example, where i just get the list of Songs from the database.


Framework: Spring
Persistence API : JPA 2.0
Build : Maven
Database : MySQL
JPA Provider : Hibernate-JPA Provider

While I was working on integrating JPA into Spring , I felt that, the most important part to concentrate on , is the CONFIGURATION area.

So,let’s get started with application-context.xml and persistence.xml


<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns=""

<context:component-scan base-package="aish.vaishno.*" />    
<tx:annotation-driven transaction-manager="transactionManager"/>
<bean id="transactionManager"
     <property name="entityManagerFactory" ref="entityManagerFactory" />

 <bean id="entityManagerFactory"
p:dataSource-ref="dataSource" p:persistenceUnitName="simple-jpa">
 <bean id="dataSource" class="org.springframework.jdbc.datasource.DriverManagerDataSource">
        <property name="driverClassName" value="com.mysql.jdbc.Driver"/>
        <property name="url" value="jdbc:mysql://localhost:3306/MUSIC_STORE"/>
        <property name="username" value="music_store"/>
        <property name="password" value="music_store"/>  

  • DIFFERENCE BETWEEN <context:annotation-config> AND <context:component-scan base-package=”…..”>

<context:annotation-config> -Enables the usage of JPA annotations(@Service, @Component, @Repository, @Controller  and etc.,)
<context:component-scan base-package=”…..”> – This component-scan tag also enables the usage of JPA annotations.

Then the difference ???

(i) annotation-config —> enables the usage of JPA annotations , only in the beans specified in the context.xml whereas (ii) component-scan —> scans through all the packages specified, records all the  project beans having JPA annotations, into this context.xml. Therefore it enables JPA annotaion usage in (beans specified in context.xml)+(Project Beans).

Inshort, <component-scan> extends <annotation-config>.

When we use <component-scan> in the app-context.xml, it’s not necessary to use  <annotation-config> again.

Even if both  the tags are specified, it’s not a problem because, the spring container would take care of running the process only once.

  • <tx:annotation-driven transaction-manager=”transactionManger”/> – It checks for @Transactional annotation  in any of the classes. This tag is like a Transactional Switch that turns on the transactional behaviour.Here Transaction Manager is being injected .
  • <bean id=”transactionManager”>– Here Transaction Manager is setup.

Here EntityManagerFactory is being injected.

  • <bean id=”entityManagerFactory”>– Here EntityManagerFactory is setup .Data Source reference and Persistence UnitName Reference is specified.
  • <bean id=”dataSource”> – DB connection details are specified.
  • Persistence UnitName Reference – Based on the PersistenceUnit name, the corresponding portion of persistence.xml is accessed (a Project can have multiple persistenceUnitNames)


<?xml version="1.0" encoding="UTF-8"?>
<persistence version="2.0" xmlns="" xmlns:xsi="" 
  <persistence-unit name="simple-jpa" transaction-type="RESOURCE_LOCAL">
      <property name="hibernate.dialect" value="org.hibernate.dialect.MySQLDialect"/> 
      <property name="hibernate.show_sql" value="true"/>
      <property name="hibernate.max_fetch_depth" value="3"/> 

Here in persistence.xml,

  • persistence-unitName is declared
  • provider – In this example, I have used Hibernate provider.
  • Entity Bean Class is specified
  • properties- Few settings(like showSQL=true) required are specified.

Configuration part is over. Now that, it’s time to use the annotations in our Dao class to make the Spring – JPA work.


DaoInterface :

public interface IMusicStoreDao {
   public List getMusicList();

DaoImplementation :

@Service(value = "MusicCollections")
@Repository(value = "MusicCollections")
public class MusicStoreDaoImpl implements IMusicStoreDao{

  @PersistenceContext(unitName = "simple-jpa")
    private EntityManager entityManager;

     public List getMusicList(){
     List musicDetailsList= entityManager.createQuery("select c from MusicDetails c").getResultList();
     return musicDetailsList;


public class Executer {
   public static void main(String[] args){
        ApplicationContext applicationContext=new ClassPathXmlApplicationContext("META-INF/app-context.xml");
        IMusicStoreDao musicStoreDao=(IMusicStoreDao) applicationContext.getBean("MusicCollections");
        System.out.println("MusicList: \n"+musicStoreDao.getMusicList());

Now , when you run this main class, for sure , you would only get Errors and Exceptions :-P.
Because, we have not yet added the DEPENDENCY JARS.
Below , I have given a note on the Errors and Exceptions that would arise and the corresponding jars to be added to clear that particular problem.

You can find the Maven dependency tags for the below jars in my Github pom.xml


  • ERRORException in thread “main” java.lang.ClassFormatError: Absent Code attribute in method that is not native or abstract in class file javax/transaction/SystemException. 
  • JAR: javaee5-api.jar . Do not forget to specify the scope as “provided”, otherwise the error will still persist.
  • ERROR: Exception in thread “main” java.lang.ClassFormatError: Absent Code attribute in method that is not native or abstract in class file javax/persistence/EntityManager.
  • JAR: hibernate-jpa2-api.jar
  • EXCEPTION: ClassNotFoundException : org.hibernate.ejb.HibernatePersistence
  • JAR: hibernate-entitymanager.jar
  • ERROR: NoClassDefFoundError: org/slf4j/impl/StaticLoggerBinder
  • JARS: slf4j-api.jar, slf4j-jcl-over.jar ( scope-RUNTIME ), slf4j-log4j12.jar ( scope-RUNTIME )
  • Do not forget to add the respective JDBC jar.

Now the program can be executed.



Have a great day 🙂

(Spring – MVC+Hibernate –> Annotation based), MySql , Maven, JSON – Simple Example

with 20 comments

Hi! For the past few days, I have been trying out on Spring – MVC, Hibernate, Maven, MySql and JSON . So I thought, if I could blog about it today with a simple example.

In this post , I have used Hibernate to persist data in the back end  and JSON to display results in the front end.

You can get the below example’s complete source code from my GitHub link here —>

Let’s take a look at it now.


  •  Tool used : NetBeans 7.3
  •  Framework : Spring-mvc-archetype – 3.X
  •  JPA: Hibernate
  •  Build : Maven 2.2
  •  Database Server : MySql
  •  WebApp Server :Tomcat 7

I have considered MusicStore example where I Add Songs and display a list of Songs.



Flow of Application



  • Create Table 
  • To give Grant permission for accessing the Database- 

GRANT ALL PRIVILEGES ON MUSIC_STORE.* TO ‘music_store’@’localhost’ IDENTIFIED BY ‘music_store’;

Folder Structure

Folder Structure


I have used Maven coupled Spring-mvc-archetype.

This Spring-mvc-archetype makes me too comfortable providing me the template as such.My duty is to just to work on the main coding part.


@Table(name = "MUSIC_COLLECTIONS")
public class MusicDetails implements Serializable {

 @Column(name = "MC_ID")
 private Integer musicID;

@Column(name = "MC_LANGUAGE")
 private String musicLanguage;

 @Column(name = "MC_TYPE")
 private String musicType;

 @Column(name = "MC_SONG_NAME")
 private String songName;

public Integer getMusicID() {
 return musicID;

public void setMusicID(Integer musicID) {
 this.musicID = musicID;

public String getMusicLanguage() {
 return musicLanguage;

public void setMusicLanguage(String musicLanguage) {
 this.musicLanguage = musicLanguage;

public String getMusicType() {
 return musicType;

public void setMusicType(String musicType) {
 this.musicType = musicType;

public String getSongName() {
 return songName;

public void setSongName(String songName) {
 this.songName = songName;

Now let’s connect our applicationProject with the database.



<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE hibernate-configuration PUBLIC "-//Hibernate/Hibernate Configuration DTD//EN"
  <!-- Database connection settings -->
  <property name="connection.driver_class">com.mysql.jdbc.Driver</property>
  <property name="connection.url">jdbc:mysql://localhost:3306/MUSIC_STORE</property>
  <property name="connection.username">music_store</property>
  <property name="connection.password">music_store</property>
  <!-- JDBC connection pool (use the built-in) -->
  <!--<property name="connection.pool_size">20</property>-->
  <property name="hibernate.c3p0.acquire_increment">3</property>
<property name="hibernate.c3p0.idle_test_period">14400</property>
<property name="hibernate.c3p0.timeout">25200</property>
<property name="hibernate.c3p0.max_size">15</property>
<property name="hibernate.c3p0.min_size">3</property>
<property name="hibernate.c3p0.max_statements">0</property>
<property name="hibernate.c3p0.preferredTestQuery">select 1;</property>
  <!-- SQL dialect -->
  <property name="dialect">org.hibernate.dialect.MySQLDialect</property>
  <!-- Enable Hibernate's automatic session context management, in this case the session will be close after each transaction! -->
  <property name="current_session_context_class">thread</property>
  <!-- Disable the second-level cache -->
  <property name="cache.provider_class">org.hibernate.cache.NoCacheProvider</property>
  <!-- Echo all executed SQL to stdout -->
  <property name="show_sql">true</property>
  <!-- auto create tables -->
  <property name="">update</property>
  <!-- Mappings -->
  <mapping class="aish.vaishno.musicstore.pojo.MusicDetails"/>
  • line 8 , connection with the particular DB with specific grant permitted username and password is specified
  • In line 31 POJO class maping is specified.


public class HibernateSessionManager {

 private static SessionFactory sessionFactory = buildSessionFactory();

 private static SessionFactory buildSessionFactory(){
   sessionFactory=new Configuration().configure("/hibernate.cfg.xml").buildSessionFactory();
   return sessionFactory;
 catch(Throwable ex){
   System.err.println("Session Factory Initialization error"+ex);
   throw new ExceptionInInitializerError(ex);

 public static SessionFactory getSessionFactory() {
   return sessionFactory;

 public static void shutdownConnection(){

Specify mySql-connector-java.jar and javassist.jar dependency in pom.xml to establish connection with DB




    • MusicStore DAO Interface creation:

Here I have created 2 methods as specified earlier,
 One method:  to add new songs
Second method: to get the List of Songs available

public interface IMusicStoreDao {

   public String addSong(MusicDetails musicDetails);
   public List getSongList();

  • Music Store Dao Implementation Class:

Here I have specified @Service inorder to inject it into Service Layer class.

public class MusicStoreDaoImpl implements IMusicStoreDao{

 public String addSong(MusicDetails musicDetails) {
   SessionFactory sessionFactory= HibernateSessionManager.getSessionFactory();
   Session session=sessionFactory.openSession();
   Transaction transaction=session.beginTransaction();
     return "Music Details has been entered";
   }catch(HibernateException hb){
     return "Sorry some problem has occured. Try Again";

 public List getSongList() {
   SessionFactory sessionFactory=HibernateSessionManager.getSessionFactory();
   Session session=sessionFactory.getCurrentSession();
   Transaction transaction=session.beginTransaction();
     List songList=session.createQuery("from MusicDetails").list();
     return songList;


  •     Service Layer Interface Creation :
public interface IMusicStoreService {
  public String addSong(MusicDetails musicDetails);
  public List getSongList();
  •    Music Service Implemetation Class Creation :

I have annotated this class with @Service because later , in the controller I will be Injecting this class.You can see that IMusicStoreDao is Autowired which means I have injected it in this class and that is why I specified @Service annotation in MusicStoreDao class.

public class MusicStoreServiceImpl implements IMusicStoreService{

 private IMusicStoreDao musicStoreDao;

 public String addSong(MusicDetails musicDetails) {
   return musicStoreDao.addSong(musicDetails);

 public List getSongList() {
    return musicStoreDao.getSongList();

I have also specified @ComponentScan in Configuration class to scan through the packages containing the respective classes with @Service annotation.



I have Autowired IMusicStoreService class

public class HomeController {

 private IMusicStoreService musicStoreService;

 public ModelAndView test(HttpServletResponse response) throws IOException{
    return new ModelAndView("home","musicDetForm",new MusicDetails());

 @RequestMapping(value="AddSong",method = RequestMethod.POST)
 public String addSong(@ModelAttribute("musicDetForm") MusicDetails musicDetails){
    return musicStoreService.addSong(musicDetails);

 @RequestMapping(value="SongList/",method = RequestMethod.GET)
 public List<MusicDetails> getSongList(){
    return musicStoreService.getSongList();

Below are few runtime dependencies to be added in pom.xml to avoid Logging Factory and Load Class error.



1.ADD SONG :  I created the form using Simple-Spring Form Handling.You can find details about it in this link, refer to 

and I have displayed the result .





2.SONG LIST DISPLAY :Here I have used JSON format to display result.

  •   JSON(Java Script Object Notation) is a data transfer format,used for exchanging data between client and server-side application.
  • It is much like XML. No, actually it is easier than XML bcoz it is easy to understand, language independent and has parsers available for most of the languages(one eg: eval()).
  • It provides me the flexibility of writing just one application and runnning it on any type of application.

For this application, all that u need to know about JSON is, just

  • add the below Jackson Library dependency into the pom.xml
  • Specify @ResponseBody JSON-REST Service.
  • Specify the Mapping properly in the Controller .

The “REST” JSON will take care.

Now when you hit the URL link, the JSON result will be as below for SongList.

That’s it.. 🙂

Hope it’s informative.. Have a great day !!!!

Written by thangaveluaishwarya

July 12, 2013 at 10:09 AM

Simple Form Handling and Performing Dependency Injection in Spring MVC Framework using NetBeans

with 6 comments

  I thought  working on Spring MVC Framework– to handle xml, configurations etc.,was a geeky kindaa job.  But I also recently learnt that , working on it using an IDE like NetBeans which provides the Spring MVC Template(pom.xml, MVC Configurations etc.,) and also the Maven build  has made me focus mainly on the design and coding part of my project , thus saving my time and leaving me unstrained .

Below I have created Simple Form Handling Application using Spring MVC Framwork(3.X).In this sample,I have also implemented Dependency Injection – annotation based .

IDE used:NetBeans 7.3

Build used:Maven 2.2

JspConsider 2 Jsp’s

Jsp 1  : MusicForm.jsp contains the text boxes to be entered.

Jsp 2 : Output.jsp conatins the TEXTS of,

  •          Object transferred from Jsp 1
  •          Object got through DEPENDENCY INJECTION


1.Bean : SongDetails Bean with setters and getters is created

2.Interface : IMusicService Interface is created. It has three unimplemented methods play(), pause(), stop();

3.Service Implementation class :MusicServiceImpl class that implements the above interface and its unimplemented methods is created.

public class MusicServiceImpl implements IMusicService{
 public String play() {
 return "Music is played on!!!";

 public String pause() {
 return "Music has been PAUSED !";

 public String stop() {
 return "Music Stopped";

Note  that there is @Service annotation before the class name… Please have it in mind.Will tell you why, when it’s time of usage has come.

4. Jsp and Controller:

4.a) HomePage(MusicForm) Jsp and Controller :


Here in MusicForm.jsp, the details to be transferred is enclosed in a form.Form has the following attributes,

  • Method type – GET/POST is specified here.
  • commandName -Here we can specify name of the Object , that carries the SongDetails (above commandName is songDetForm )
  • action- Here OutCome jsp name, where the details are to be transferred is specified.

For the above Jsp , controller method has to be written.The flow goes like this,

  • ModelAndView object is created
  • ViewName is set
  • SongDetails Object is initialised and set as songDetForm (must be same as commandName in jsp).

4.b)Output jsp and Controller:


Here in this Controller,

  • Output jsp name is given as the Request mapping value
  • Request method is POST as specified in First Jsp
  • View Name is set.
  • Then Two Objects are set—->1.songDetForm, 2.object got through dependency injection
  • To set songDetForm obj,
  1. Object is got from HomePageController method via @ModelAttribute(“songDetForm”)SongDetails songDetails. This means , object or attribute in the name “songDetForm” is assigned to songDetails object.
  2. This object is then added in a HashMap
  • To set Dependency injection object,
  1. IMusicService private instance is created .It is annotated with @Autowired.
  2. Apart from this, @Service annotation has to be specified on the ServiceImplementation class . This means, MusicServiceImpl class is at Service which can be injected ,when @Autowired annotation is used over its Interface instance.
  3.  In MVC Configuration, the package be scanned is specified and Component Scan is done.
  4. then dependencyObject is  added in the Controller method map.
  • Both these objects along with viewName are set in mv and mv is returned.

The controller sourcecode will look like,

public class HomeController {

 private IMusicService iMusicService;

 public ModelAndView homePage(){
 //Method 1:
 ModelAndView mv=new ModelAndView();
 mv.addObject("songDetForm",new SongDetails());
 return mv;

 //Method 2:                  viewName      Obj Key        Obj Value
 // return new ModelAndView("MusicForm","songDetForm",new SongDetails());

 @RequestMapping(value ="/Output", method = RequestMethod.POST)
 public ModelAndView processSongDetails (@ModelAttribute("songDetForm") SongDetails songDetails){
 Map<String,Object> obj=new HashMap<String,Object>();
 obj.put("iMusicService", iMusicService);
//                                            viewName  Obj
 ModelAndView modelAndView = new ModelAndView("Output", obj);
 return modelAndView;
  • In the respective Output.jsp , the respective objects are got.

5. Clean the project.

6.Build it using Maven… The most advantageous part about Maven is , I needn’t have to strain myself to provide any dependency jars, specify its classpath etc.,  everytime. Maven took care of that part by itself, thus making my code-writing easy and simple.

7.Run it.

The output will be as follows…


That’s it about Form Handling and Dependecy Injection in Spring MVC Framework.

You can find and download the above source code from this link.

Written by thangaveluaishwarya

June 22, 2013 at 3:49 AM