| Class Date and Time |
Price
|
|
|---|---|---|
|
$2,375.00
or 5 vouchers
vouchers
|
||
| $2,375.00 or 5 vouchers vouchers | ||
| $2,375.00 or 5 vouchers vouchers | ||
| $2,375.00 or 5 vouchers vouchers | ||
| $2,375.00 or 5 vouchers vouchers | ||
| $2,375.00 or 5 vouchers vouchers | ||
| $2,375.00 or 5 vouchers vouchers | ||
| $2,375.00 or 5 vouchers vouchers | ||
| $2,375.00 or 5 vouchers vouchers | ||
| $2,375.00 or 5 vouchers vouchers |
This course enables the experienced Java developer to use the Spring application framework to manage objects in a lightweight "IoC" (inversion-of-control) container; to create simple and complex web applications; and to manage persistent objects using Spring's support for DAOs and transaction control. Spring is a far-reaching framework that aims to facilitate all sorts of Java development, including every level of multi-tier distributed systems. Here we focus on the Core and Web/MVC modules, with a lighter (but by no means dismissive) touch on persistence through DAO and ORM modules.
The Core module gives the developer declarative control over object creation and assembly; this is useful for any tier of any Java application. So is Spring's validation framework, and so we study these things in a mix of standalone (Java SE) applications and web applications. Then students build web applications that use the Spring MVC framework to rationalize their designs into coherent request/response cycles. They use Spring command objects to manage HTML forms and their data, and connect these to the validation framework. We connect our applications to persistent stores and study the DAO and ORM modules, to better understand JDBC and JPA persistence models and declarative transaction control.
Each student in our Live Online and our Onsite classes receives a comprehensive set of materials, including course notes and all the class examples.
Experience in the following areas is required:
Our computer technical requirements and setup process is easy, with support just a click away.

Posted on May 14, 2010 by rsakowski
In previous articles, I talked a lot about the Model/View/Controller design pattern. Using it is recommended for all programming ...