webwork2-atlassianblogs.ppt

WEBWORK 2 Agenda WebWork 2 XWork overview Actions Views Interceptors Validation Inversion of Control (IoC) Struts Comparison WebWork 2 Overview ‘Pull-based’ MVC framework Focus on componentization code reuse Implementation of the command pattern Second generation of WebWork Not tied to the web! Currently in beta - but being well used XWork Generic command pattern framework Commands represent a unit-of-work Split off from Webwork 1 Why command pattern? XWork provides… Core command pattern framework for request / response environment Interceptor framework Action chaining IoC componentization framework Runtime attribute validation framework Built-in type conversion using OGNL Doesn’t provide: anything to do with the web! WebWork 2 provides.. Tied to HTTP request / response Integration with session / application scopes Servlet-based dispatcher to turn incoming requests into action/s. Automatically set properties of action based on request parameters View integration (JSP, Velocity etc) User interface / form components Actions An Action is a command. Each action should be a ‘unit of work’ Actions should be simple! Action interface has only one method: interface Action { String execute() throws Exception; } Let’s look at small example… Basic Example: Add Pet Basic Example: Add Pet A basic example of an action, view and configuration. Model: Pet.java (simple bean) Controller: AddPet.java (WW action) View: addpet.jsp Config: xwork.xml Basic Example: Pet Model . . . public class Pet { private long id; private String name; public long getId() … public void setId(long id) … public String getName() … public void setName(String name) … } Basic Example: AddPet action public class AddPet implements Action { protected Pet pet = new Pet(); public String execute() throws Exception { if (pet.getName() == null ) return ERROR; Registry.getPetStore().savePet(pet); return SUCCESS; } public Pet getPet() { return pet; }