Learn how to intergrate existing Struts applications with the Next Big Thing: Apache Struts 2. After completing the course, you will be equipped to migrate or create professional Struts 2 applications.
The course covers migrating existing applications to Struts 2, with a focus on upgrading the most important asset of all: the grey matter between your ears. Along with migration issues, the course covers advanced development topics, such as creating a data access layer, securing web applications, and creating tag-based user interface components.
This course is intended for experienced Struts developers who to want to ramp up quickly and start developing with Struts 2 right away.
Experienced Struts developers and programmers who are considering Struts 2 for a current or upcoming project.
- Migrate Struts 1 classes and resources to Struts 2 equivalents
- Build a working Struts 2 web application
- Understand how to test and debug Struts 2 applications
- Explore new features and key best practices
- Sessions include a presentation and a workshop.
- Presentations are reinforced by workshops designed to explore common problems and best practice solutions.
- Workshops are described with standard use cases.
- Source code for the completed workshops is available through the Struts from Square One site.
- Other course materials are available through this site (Struts University).
|To benefit from this workshop training course, participants should have experience developing Java web applications with Struts, or another MVC framework (WebWork, Spring MVC, Tapestry). Experience with a modern Java IDE, such as Eclipse, IDEA, or NetBeans, is also beneficial.|
|Session||Presentation||Use Case||Day 1 - Carpe Diem|
|1-1||Migrating to Apache Struts 2||Migrate||We step through migrating a Struts 1 application to Struts 2 through a series of mini-labs. (More ...)|
|1-2||Building Struts 2 Applications||Welcome||We introduce the workshop outline and related materials. Then, we explore and extend a simple "Hello World" application that demonstrates the basics of web application infrastructure. (More ...)|
|1-3||Jumpstarting JUnit||Retain||The framework encourages a layered architecture, which implies a layered approach to testing. We look at interacting with the business layer through unit tests. (More ...)|
|1-4||Capturing Input||Register||Forms play a strong role in most web applications. How does Struts 2 help us harvest data submitted by a form? (More ...)|
|Day 2 - Plumbing Matters|
|2-1||Validating Input||Register ext||Now that we are up and running, we ask "How do we get there from here?" (More ...)|
|2-2||Test-Driving Web Development||Menu||Once we know the business layer is sound, we can test the presentation layer too. (More ...)|
|2-3||Mapping Workflows||Logout, Login||The action mappings work closely with the result types to guide clients through the application. (More ...)|
|Day 3 - Looking Good|
|3-1||Localizing Content||Localize||To reach the broadest audience, some applications support more than one language. Even if your application supports one language, the message resources are an effective tool for managing shared phrases throughout the application. (More ...)|
|3-2||Displaying Dynamic Content||Profile||Creating interactive screens can be the most rewarding and the most frustrating part of web development. Struts Action relies on JSP tags to display application state. (More ...)|
|3-3||Polishing the User Interface||Subscribe||Now that we have it working, let's make it pretty! (More ...)|
|3-4||Best Practices||Following best practices can help make an application faster to create and easier to maintain. (More ...)|
We hit the ground running by migrating a simple "hello world" application from Struts 1 to Struts 2, and exploring the data access layer for the MailReader example application.
We introduce the workshop outline and related materials. How will the workshop be presented? What will the workshop accomplish?
We fill in the blanks of web development by examining the sprockets and gears of framework internals.
- Infrastructure, infrastructure, infrastructure
- Test first
We focus on the glitz and glamor of the user interface, and then review best practices.
- Input matters
- Trust but verify
- Click-thru tests
- Who, who are you
- Think global, act local
- Getting it back
- Making it pretty