webwork / docs / differences.html

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
<html xmlns="" lang="en_US" xml:lang="en_US">
  <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
  <title>OpenSymphony Wiki (Offline Version) :: WebWork2 Documentation</title>
  <link type="text/css" href="main.css" rel="STYLESHEET"/>
  <div id="page-logo">
    <a href="index.html">WebWork2 Documentation</a>
    <div class="snip-title">
	  <h1 class="snip-name">Differences between WebWork and WebWork 2
<div id="snip-content" class="snip-content">

 <div class="snip-attachments"></div>
 This list will grow over time, and there are many more differences than this - I'm just scribbling them down here as I find them.
<ul class="star">
<li><a href="index.html">WebWork2</a> has many many more unit tests than <a href="">WebWork</a> (which pretty much has none)</li>
<li>WebWork2 depends on <a href="">XWork</a> (a generic command pattern framework), whereas WebWork 1 was really two things in one package (the MVC framework and the generic command pattern framework).</li>
<li>Webwork2 uses <a href="">OGNL</a> for its expression language.</li>
<li>ActionSupport has moved from webwork.action.ActionSupport to com.opensymphony.xwork.ActionSupport</li>
<li>validation is no longer done in the Action (by default, you can do it there if you want to code it there). Check out the <a href="">Xwork Validation Framework</a>.</li>
<li><a href="">Xwork Interceptors</a> make it so that you don't have to have complicated inheritance hierarchies to achieve pre/post processing.</li>
<li>It has a nifty "2" at the end :-)</li>
<li>CommandDriven interface no longer exists - specify the method to execute in the action declaration in xwork.xml see <a href="">Xwork Configuration</a></li>