Click here to Skip to main content
15,886,258 members

What are the prerequisites of returning complex data types like List from a Spring controller class via Ajax?

Lion 2012 asked:

Open original thread
I'm working with Spring MVC 3.0.2 with Hibernate using JSP. I'm using RESTful (annotated) controllers in Spring. Many a times, I need to return a java.util.List using Ajax (to and) from the Spring controller class which is mapped with appropriate (mostly GET and POST) requests. Something like the one shown below.

Java
@RequestMapping(method=RequestMethod.POST, value="ajax/TempAjax")
    
public @ResponseBody List<Country>getStateList(@ModelAttribute("someBean") 
SomeBean someBean, BindingResult error, HttpServletRequest request, 
HttpServletResponse response)
{
    Session session=NewHibernateUtil.getSessionFactory().getCurrentSession();
    session.beginTransaction();

    List<Country>list=session.createQuery("from State where countryId = 
   "+request.getParameter("countryId")+" order by stateId").list();

    session.flush();
    session.getTransaction().commit();
    return list;
}


What I'm trying to do is when a country is selected from a Country select box, corresponding states of that country should be populated from the database in the State select box according to the countryId passed to the Spring controller class via Ajax.

I'm not sure but the Spring MVC 3.0.2 should support some direct mechanism like JSON. Could you please let me know what are the prerequisites of using Ajax to accomplish such task in Spring MVC. If possible, could you please give me some example. I have searched on Google but I didn't realize the basic requirements as I'm using such stuff very first time.
Tags: Java, Ajax

Plain Text
ASM
ASP
ASP.NET
BASIC
BAT
C#
C++
COBOL
CoffeeScript
CSS
Dart
dbase
F#
FORTRAN
HTML
Java
Javascript
Kotlin
Lua
MIDL
MSIL
ObjectiveC
Pascal
PERL
PHP
PowerShell
Python
Razor
Ruby
Scala
Shell
SLN
SQL
Swift
T4
Terminal
TypeScript
VB
VBScript
XML
YAML

Preview



When answering a question please:
  1. Read the question carefully.
  2. Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
  3. If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
  4. Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.
Let's work to help developers, not make them feel stupid.
Please note that all posts will be submitted under the http://www.codeproject.com/info/cpol10.aspx.



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900