<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
    <title>WebWork</title>
    <link rel="alternate" type="text/html" href="http://blogs.opensymphony.com/webwork/" />
    <link rel="self" type="application/atom+xml" href="http://blogs.opensymphony.com/webwork/atom.xml" />
   <id>tag:blogs.opensymphony.com,2008:/webwork/3</id>
    <link rel="service.post" type="application/atom+xml" href="http://blogs.opensymphony.com/mt/mt-atom.cgi/weblog/blog_id=3" title="WebWork" />
    <updated>2007-07-21T15:54:32Z</updated>
    
    <generator uri="http://www.sixapart.com/movabletype/">Movable Type 3.2</generator>
 
<entry>
    <title>WebWork 2.2.6 released (Security Fix)</title>
    <link rel="alternate" type="text/html" href="http://blogs.opensymphony.com/webwork/2007/07/webwork_226_released_security.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://blogs.opensymphony.com/mt/mt-atom.cgi/weblog/blog_id=3/entry_id=403" title="WebWork 2.2.6 released (Security Fix)" />
    <id>tag:blogs.opensymphony.com,2007:/webwork//3.403</id>
    
    <published>2007-07-21T15:29:13Z</published>
    <updated>2007-07-21T15:54:32Z</updated>
    
    <summary>Opensymphony and the WebWork team are proud to announce the release of WebWork version 2.2.6. This release, approximately 3 months after WebWork 2.2.5, is a maintainance release, due to a critical security issue found in XWork, allowing users to execute...</summary>
    <author>
        <name>Rainer Hermanns</name>
        
    </author>
    
    <content type="html" xml:lang="en" xml:base="http://blogs.opensymphony.com/webwork/">
        <![CDATA[<p>Opensymphony and the WebWork team are proud to announce the release of<br />
WebWork version 2.2.6.</p>

<p>This release, approximately 3 months after WebWork 2.2.5, is a<br />
maintainance release, due to a <strong>critical security issue</strong> found in XWork,<br />
allowing users to execute arbituary any <span class="caps">OGNL </span>expression. See <a href="http://wiki.opensymphony.com/display/WW/1.2.3+Press+Release">here</a> for more details</p>

<p>   * <a href="http://wiki.opensymphony.com/display/WW/WebWork+2.2.6">Release Notes</a><br />
   * <a href="http://jira.opensymphony.com/secure/IssueNavigator.jspa?reset=true&amp;pid=10030&amp;fixfor=21702">Changelog</a><br />
   * <a href="http://www.opensymphony.com/webwork/download.action">Download here</a></p>

<p>This release is backwords compatible with WebWork 2.2.5 and is a drop<br />
in replacement.</p>

<p>We would like to thank both users and contributors of WebWork for<br />
helping out, submiting patches, testing, providing feedback and<br />
participating in various discussion.</p>

<p>The WebWork Development Team</p>]]>
        
    </content>
</entry>
<entry>
    <title>WebWork 2.2.5 released</title>
    <link rel="alternate" type="text/html" href="http://blogs.opensymphony.com/webwork/2007/04/webwork_225_released.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://blogs.opensymphony.com/mt/mt-atom.cgi/weblog/blog_id=3/entry_id=394" title="WebWork 2.2.5 released" />
    <id>tag:blogs.opensymphony.com,2007:/webwork//3.394</id>
    
    <published>2007-04-14T09:46:34Z</published>
    <updated>2007-04-14T09:55:14Z</updated>
    
    <summary>OpenSymphony and the WebWork team are proud to announce the release of WebWork version 2.2.5. This 2.2.5 release, 6 months after WebWork 2.2.4, marks the final chapter for the WebWork framework. Struts 2, its successor, had its first GA release,...</summary>
    <author>
        <name>Rainer Hermanns</name>
        
    </author>
    
    <content type="html" xml:lang="en" xml:base="http://blogs.opensymphony.com/webwork/">
        <![CDATA[<p><a href="http://www.opensymphony.com">OpenSymphony</a> and the <a href="http://www.opensymphony.com/webwork">WebWork</a> team are proud to announce the release of WebWork version 2.2.5. </p>

<p>This 2.2.5 release, 6 months after WebWork 2.2.4, marks the final chapter for the WebWork framework. </p>

<p><a href="http://struts.apache.org/2.x/">Struts 2</a>, its successor, had its first GA release, and in a final push, the WebWork team wanted to do a big effort to bring in as many optimizations and bug fixes as possible before shifting developer focus.</p>


<ul>
<li><a href="http://www.opensymphony.com/webwork/wikidocs/WebWork%202.2.5.html">Release notes</a></li>
<li><a href="http://jira.opensymphony.com/secure/IssueNavigator.jspa?reset=true&amp;pid=10030&amp;fixfor=21672">Changelog</a></li>
<li><a href="http://www.opensymphony.com/webwork/download.action">Download here</a></li>
</ul>



<p>This release is fully backwards compatible with WebWork 2.2.4. You can just replace the existing WebWork and XWork jars with the news ones from 2.2.5.</p>

<p>Like always, we would like to thank both regular users and contributors, for helping out, submitting patches, testing, and providing general feedback. </p>

<p>The development of WebWork 2 and XWork 1 slowly grinds to a halt, so if you're looking for bleeding edge technologies or new features, you are more than welcome to try <a href="http://struts.apache.org/2.x/">Struts 2</a>.</p>

<p>The WebWork Development Team</p>]]>
        
    </content>
</entry>
<entry>
    <title>WebWork 2.2.4 released</title>
    <link rel="alternate" type="text/html" href="http://blogs.opensymphony.com/webwork/2006/09/webwork_224_released.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://blogs.opensymphony.com/mt/mt-atom.cgi/weblog/blog_id=3/entry_id=345" title="WebWork 2.2.4 released" />
    <id>tag:blogs.opensymphony.com,2006:/webwork//3.345</id>
    
    <published>2006-09-04T19:02:55Z</published>
    <updated>2006-12-06T07:35:05Z</updated>
    
    <summary>OpenSymphony and the WebWork team are proud to announce the release of WebWork version 2.2.4. WebWork 2.2.4 is a quickfix release for the latest findings and reported issues. The included docs were not updated since the 2.2.3 release! Changelog Download...</summary>
    <author>
        <name>Rainer Hermanns</name>
        
    </author>
    
    <content type="html" xml:lang="en" xml:base="http://blogs.opensymphony.com/webwork/">
        <![CDATA[<p><a href="http://www.opensymphony.com">OpenSymphony</a> and the <a href="http://www.opensymphony.com/webwork">WebWork</a> team are proud to announce the release of WebWork version 2.2.4. <br />
WebWork 2.2.4 is a quickfix release for the latest findings and reported issues. <br />
The included docs were not updated since the 2.2.3 release!</p>


<ul>
<li><a href="http://jira.opensymphony.com/secure/IssueNavigator.jspa?reset=true&amp;pid=10030&amp;fixfor=21670">Changelog</a></li>
<li><a href="http://www.opensymphony.com/webwork/download.action">Download here</a></li>
</ul>



<p>Thanks to the entire <a href="http://www.opensymphony.com/webwork/members.action">WebWork team</a> for all their hard work.</p>

<p>The WebWork Development Team</p>]]>
        
    </content>
</entry>
<entry>
    <title>WebWork 2.2.3 released</title>
    <link rel="alternate" type="text/html" href="http://blogs.opensymphony.com/webwork/2006/08/webwork_223_released.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://blogs.opensymphony.com/mt/mt-atom.cgi/weblog/blog_id=3/entry_id=335" title="WebWork 2.2.3 released" />
    <id>tag:blogs.opensymphony.com,2006:/webwork//3.335</id>
    
    <published>2006-08-23T21:01:21Z</published>
    <updated>2006-12-06T07:34:33Z</updated>
    
    <summary>OpenSymphony and the WebWork team are proud to announce the release of WebWork version 2.2.3. WebWork 2.2.3 is mainly a bugfix release with some additions, improvements and backports from Struts 2.0. Release notes Changelog Download here Thanks to the entire...</summary>
    <author>
        <name>Rainer Hermanns</name>
        
    </author>
    
    <content type="html" xml:lang="en" xml:base="http://blogs.opensymphony.com/webwork/">
        <![CDATA[<p><a href="http://www.opensymphony.com">OpenSymphony</a> and the <a href="http://www.opensymphony.com/webwork">WebWork</a> team are proud to announce the release of WebWork version 2.2.3. <br />
WebWork 2.2.3 is mainly a bugfix release with some additions, improvements and backports from Struts 2.0.</p>


<ul>
<li><a href="http://www.opensymphony.com/webwork/wikidocs/WebWork%202.2.3.html">Release notes</a></li>
<li><a href="http://jira.opensymphony.com/secure/IssueNavigator.jspa?reset=true&amp;pid=10030&amp;fixfor=21640">Changelog</a></li>
<li><a href="http://www.opensymphony.com/webwork/download.action">Download here</a></li>
</ul>



<p>Thanks to the entire <a href="http://www.opensymphony.com/webwork/members.action">WebWork team</a> for all their hard work, especially during the past couple of months.</p>

<p>This release will be the last of the 2.2 series and we want to thank the entire OpenSymphony community for all their work, contributions, suggestions and comments in the past years. </p>

<p>All developer efforts will now concentrate on Apache Struts Action 2.0 which will form the next generation of action based web frameworks.</p>


<p>The WebWork Development Team</p>]]>
        
    </content>
</entry>
<entry>
    <title>WebWork 2.2.2 released</title>
    <link rel="alternate" type="text/html" href="http://blogs.opensymphony.com/webwork/2006/03/webwork_222_released.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://blogs.opensymphony.com/mt/mt-atom.cgi/weblog/blog_id=3/entry_id=279" title="WebWork 2.2.2 released" />
    <id>tag:blogs.opensymphony.com,2006:/webwork//3.279</id>
    
    <published>2006-03-23T21:51:10Z</published>
    <updated>2006-12-06T07:33:53Z</updated>
    
    <summary>OpenSymphony and the WebWork team are proud to announce the release of WebWork version 2.2.2. WebWork 2.2.2 is mainly a bugfix release with some additions and improvements for the view components. Release notes Changelog Download here Thanks to the entire...</summary>
    <author>
        <name>Rainer Hermanns</name>
        
    </author>
    
    <content type="html" xml:lang="en" xml:base="http://blogs.opensymphony.com/webwork/">
        <![CDATA[<p><a href="http://www.opensymphony.com">OpenSymphony</a> and the <a href="http://www.opensymphony.com/webwork">WebWork</a> team are proud to announce the release of WebWork version 2.2.2. <br />
WebWork 2.2.2 is mainly a bugfix release with some additions and improvements for the  view components.</p>


<ul>
<li><a href="http://www.opensymphony.com/webwork/wikidocs/Release%20Notes.html">Release notes</a></li>
<li><a href="http://jira.opensymphony.com/secure/IssueNavigator.jspa?reset=true&amp;pid=10030&amp;fixfor=21600">Changelog</a></li>
<li><a href="http://www.opensymphony.com/webwork/download.action">Download here</a></li>
</ul>



<p>Thanks to the entire <a href="http://www.opensymphony.com/webwork/members.action">WebWork team</a> for all their hard work, especially during the past couple of weeks.</p>


<p>Amazing efforts have finally come to a good end, nonetheless marking the starting point for an even greater effort. </p>

<p>This release will be the last of the 2.2 series and we want to thank the entire OpenSymphony community for all their work, contributions, suggestions and comments in the past years. </p>

<p>We are now starting the migration process to Apache Struts Action 2.0 which will form the next generation of action based web frameworks.</p>

<p>Good luck to all of us in making the Struts/WebWork merger a success.</p>

<p>The WebWork Development Team</p>]]>
        
    </content>
</entry>
<entry>
    <title>Interview about Struts Action 2.0 </title>
    <link rel="alternate" type="text/html" href="http://blogs.opensymphony.com/webwork/2006/03/interview_about_struts_action.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://blogs.opensymphony.com/mt/mt-atom.cgi/weblog/blog_id=3/entry_id=270" title="Interview about Struts Action 2.0 " />
    <id>tag:blogs.opensymphony.com,2006:/webwork//3.270</id>
    
    <published>2006-03-09T05:08:24Z</published>
    <updated>2006-03-09T05:08:33Z</updated>
    
    <summary>I was interviewed by IndicThreads.com about WebWork, Struts, and the merger. Check it out - hopefully it will shed some light on how the merger is going. Check it out here....</summary>
    <author>
        <name>Patrick Lightbody</name>
        
    </author>
    
    <content type="html" xml:lang="en" xml:base="http://blogs.opensymphony.com/webwork/">
        <![CDATA[<p>I was interviewed by IndicThreads.com about WebWork, Struts, and the merger. Check it out - hopefully it will shed some light on how the merger is going. Check it out <a href="http://www.indicthreads.com/interviews/415/struts_action_framework_2_webwork.html">here</a>.</p>]]>
        
    </content>
</entry>
<entry>
    <title>WebWork makes web apps easier to use</title>
    <link rel="alternate" type="text/html" href="http://blogs.opensymphony.com/webwork/2006/02/webwork_makes_web_apps_easier.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://blogs.opensymphony.com/mt/mt-atom.cgi/weblog/blog_id=3/entry_id=263" title="WebWork makes web apps easier to use" />
    <id>tag:blogs.opensymphony.com,2006:/webwork//3.263</id>
    
    <published>2006-02-11T19:44:48Z</published>
    <updated>2006-02-11T19:44:56Z</updated>
    
    <summary>Posted on Ajaxian.com today, there is a good argument that applications that use AJAX for validation are easier to use. WebWork has built in support for this style of validation, so give it a shot and see if your users...</summary>
    <author>
        <name>Patrick Lightbody</name>
        
    </author>
    
    <content type="html" xml:lang="en" xml:base="http://blogs.opensymphony.com/webwork/">
        <![CDATA[<p>Posted on Ajaxian.com today, there is a good argument that applications that use <span class="caps">AJAX </span>for validation are easier to use. WebWork has built in support for this style of validation, so give it a shot and see if your users find your application is easier to use now!</p>

<p><a href="http://ajaxian.com/archives/ajax-case-study-simple-validations-reduce-costsincrease-usability">Ajax Case Study - Simple Validations Reduce Costs/Increase Usability</a>:</p>

<blockquote><p><img src="http://ajaxian.com/wp-content/images/edit_multi.gif" alt="" border="0" width="200" height="154" align="left"/></p>

<p>In a follow-up to his <a href="http://justaddwater.dk/2006/01/14/ajax-performance-stats-roi-and-business-value/">previous post</a>, Jesper R&oslash;nn-Jensen looks yet again at business uses of Ajax technologies - specifically a 'case study' looking at one of his recent usability issues.</p>

	<blockquote>
	<p>
As a followup to my earlier post &lsquo;AJAX performance stats, <span class="caps">ROI, </span>and business value&lsquo;, I decided that I&rsquo;d share with you some considerations on a recent project I was involved in.<br />
</p>
	<p>
Anyways, I want to give you some of the details on why we decided to implement <span class="caps">AJAX </span>validations in this particular web application. We had a complex interface where the user had to enter a lot of information about a lot of users. In this particular solution, the typical usage scenario is that an employee has data about multiple users to enter: That could for example be name, age, social security numbers etc.<br />
</p>
	</blockquote>

<p>He <a href="http://justaddwater.dk/2006/02/08/ajax-businesscase/">mentions</a> the two models that they looked at - the 'Edit one object at a time' idea and the 'Edit multiple objects at the same time' school of thought. For each, they give an example, including a sample screenshot of the method.</p>

<p>While both methods had their strengths, the real time-saver came in the form of the Ajax-based validations on the data that was being entered. Spotlighting an incorrect field with a red highlight reduces the guesswork without detracting from their entry work.</p></blockquote>

<p>(Via <a href="http://ajaxian.com">Ajaxian Blog</a>.)</p>]]>
        
    </content>
</entry>
<entry>
    <title>WebWork 2.2.1: Released</title>
    <link rel="alternate" type="text/html" href="http://blogs.opensymphony.com/webwork/2006/02/webwork_221_released.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://blogs.opensymphony.com/mt/mt-atom.cgi/weblog/blog_id=3/entry_id=250" title="WebWork 2.2.1: Released" />
    <id>tag:blogs.opensymphony.com,2006:/webwork//3.250</id>
    
    <published>2006-02-04T00:24:16Z</published>
    <updated>2006-12-06T07:32:56Z</updated>
    
    <summary>OpenSymphony and the WebWork team are proud to announce the release of WebWork version 2.2.1 (download now). WebWork 2.2.1 is a bugfix release for the 2.2 release a month ago. (full release notes): Improved QuickStart tool makes development easier than...</summary>
    <author>
        <name>Rainer Hermanns</name>
        
    </author>
    
    <content type="html" xml:lang="en" xml:base="http://blogs.opensymphony.com/webwork/">
        <![CDATA[<p><a href="http://www.opensymphony.com">OpenSymphony</a> and the <a href="http://www.opensymphony.com/webwork">WebWork</a> team are proud to announce the release of WebWork version 2.2.1 (<a href="http://www.opensymphony.com/webwork/download.action">download now</a>). WebWork 2.2.1 is a bugfix release for the 2.2 release a month ago. (<a href="http://www.opensymphony.com/webwork/wikidocs/WebWork%202.2.1.html">full release notes</a>):</p>


<ul>
<li>Improved QuickStart tool makes development easier than ever</li>
<li>Tons more documentation with over 900 <span class="caps">PDF </span>pages!</li>
<li>Improved Client side validation using <span class="caps">AJAX </span>or plain JavaScript</li>
<li>Updated <span class="caps">JSR168</span>/Portlet support for several popular Portal servers, including Pluto, <span class="caps">IBM</span> WebSphere, eXo Portal...</li>
<li>New Tags: Debug, UpDownSelect, Tree</li>
<li>Added Maven support</li>
<li>More and better webapp samples</li>
</ul>



<p>Thanks to the entire <a href="http://www.opensymphony.com/webwork/members.action">WebWork team</a> for all their hard work, especially during these last few weeks as the final touches were put in place.</p>

<p>Special thanks to Nils-Helge Garli for contributing his portletwork project which now forms the core portlet integration code.</p>]]>
        
    </content>
</entry>
<entry>
    <title>WebWork 2.2: Released and ready for Struts!</title>
    <link rel="alternate" type="text/html" href="http://blogs.opensymphony.com/webwork/2006/01/webwork_22_released_and_ready.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://blogs.opensymphony.com/mt/mt-atom.cgi/weblog/blog_id=3/entry_id=224" title="WebWork 2.2: Released and ready for Struts!" />
    <id>tag:blogs.opensymphony.com,2006:/webwork//3.224</id>
    
    <published>2006-01-11T16:26:02Z</published>
    <updated>2006-01-11T17:32:47Z</updated>
    
    <summary>OpenSymphony and the WebWork team are proud to announce the release of WebWork version 2.2 (download now). This release is the biggest release ever for WebWork and there are plenty of reasons why (full release notes): Full support for Java...</summary>
    <author>
        <name>Patrick Lightbody</name>
        
    </author>
    
    <content type="html" xml:lang="en" xml:base="http://blogs.opensymphony.com/webwork/">
        <![CDATA[<p><a href="http://www.opensymphony.com">OpenSymphony</a> and the <a href="http://www.opensymphony.com/webwork">WebWork</a> team are proud to announce the release of WebWork version 2.2 (<a href="http://www.opensymphony.com/webwork/download.action">download now</a>). This release is the biggest release ever for WebWork and there are plenty of reasons why (<a href="http://www.opensymphony.com/webwork/wikidocs/WebWork%202.2.html">full release notes</a>):</p>


<ul>
<li>Full support for Java 5 Annotations and Generics</li>
<li>Rich <span class="caps">AJAX </span>support using <a href="http://getahead.ltd.uk/dwr"><span class="caps">DWR</span></a> and <a href="http://dojotoolkit.org">Dojo</a></li>
<li>New QuickStart tool makes development easier than ever</li>
<li>Tons more documentation with over 900 <span class="caps">PDF </span>pages!</li>
<li>Client side validation using <span class="caps">AJAX </span>or plain JavaScript</li>
<li>Built in support for Continuations</li>
<li><span class="caps">JSR168</span>/Portlet support for several popular Portlet servers, including Pluto</li>
<li>Rich UI template framework with native support for <span class="caps">JSP,</span> FreeMarker, and Velocity</li>
<li>Native support for Spring and Pico <span class="caps">IOC </span>containers</li>
<li>More intelligent error reporting</li>
<li>Developer Mode makes building webapps even easier with improved error reporting</li>
<li>Simplified tag syntax</li>
<li>Advanced data binding framework that works with any object, including domain objects</li>
</ul>



<p>This release marks an important milestone in the WebWork history: the last major release under the WebWork and OpenSymphony names. While future minor releases will continue to take place (including 2.2.x and 2.1.x releases), all major work will now fold in to the <a href="http://struts.apache.org/struts-action/index.html">Struts Action Framework</a>, version 2.0. You can use WebWork 2.2 as an early preview of Struts Action Framework 2.0, but you can also expect many other great improvements to be added between now and then.</p>

<p>Thanks to the entire <a href="http://www.opensymphony.com/webwork/members.action">WebWork team</a> for all their hard work, especially during these last few weeks as the final touches were put in place.</p>

<p><strong>Getting started</strong></p>

<p>We think the best way to get started with any technology is to try it out right away. That's why we've made WebWork the easiest web development platform to get started with. You can use the QuickStart feature (read the docs on QuickStart to learn how you can use this important tool with your own projects):</p>


<ul>
<li>Open a command prompt to the root directory of the distribution</li>
<li>Using a Java 5 <span class="caps">JDK, </span>execute: <strong>java -jar webwork-2.2.jar quickstart:showcase</strong></li>
<li>Open your browser to the <span class="caps">URL</span>: <strong>http://localhost:8080/showcase</strong></li>
<li>Feel free to edit any of the sources (.java, .jsp, etc) in: <strong>webapps/showcase</strong></li>
<li>Reload your browser to see the changes right away</li>
</ul>

]]>
        
    </content>
</entry>
<entry>
    <title>WebWork 2.2 Beta 4 Released</title>
    <link rel="alternate" type="text/html" href="http://blogs.opensymphony.com/webwork/2005/12/webwork_22_beta_4_released.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://blogs.opensymphony.com/mt/mt-atom.cgi/weblog/blog_id=3/entry_id=214" title="WebWork 2.2 Beta 4 Released" />
    <id>tag:blogs.opensymphony.com,2005:/webwork//3.214</id>
    
    <published>2005-12-02T14:45:24Z</published>
    <updated>2005-12-02T14:49:01Z</updated>
    
    <summary>WebWork 2.2 Beta 4 is now out. This release includes various bug fixes and minor feature improvements, but the biggest change by far is the documentation. With the help from the amazing WebWork team, including Jay, Rene, tm_jee, and Rainer,...</summary>
    <author>
        <name>Patrick Lightbody</name>
        
    </author>
    
    <content type="html" xml:lang="en" xml:base="http://blogs.opensymphony.com/webwork/">
        <![CDATA[<p>WebWork 2.2 Beta 4 is now out. This release includes various bug fixes and minor feature improvements, but the biggest change by far is the documentation. With the help from the amazing WebWork team, including Jay, Rene, tm_jee, and Rainer, WebWork now has much more documentation. Please click <a href="http://www.opensymphony.com/webwork/download.action">here</a> to download the latest beta release. Be sure to check the documentation, including the migration notes for a complete list of what has changed.</p>]]>
        
    </content>
</entry>
<entry>
    <title>WebWork joining Struts</title>
    <link rel="alternate" type="text/html" href="http://blogs.opensymphony.com/webwork/2005/11/webwork_joining_struts.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://blogs.opensymphony.com/mt/mt-atom.cgi/weblog/blog_id=3/entry_id=213" title="WebWork joining Struts" />
    <id>tag:blogs.opensymphony.com,2005:/webwork//3.213</id>
    
    <published>2005-11-27T19:47:15Z</published>
    <updated>2005-11-27T20:04:31Z</updated>
    
    <summary>Yes, it&apos;s true. The WebWork development team (Jason and I) have been working with the Struts development team (Don Brown and Ted Husted) and have come to the conclusion that the best thing for Java community would be to merge...</summary>
    <author>
        <name>Patrick Lightbody</name>
        
    </author>
    
    <content type="html" xml:lang="en" xml:base="http://blogs.opensymphony.com/webwork/">
        <![CDATA[<p>Yes, <a href="http://www.mail-archive.com/dev%40struts.apache.org/msg13815.html">it's true</a>. The WebWork development team (Jason and I) have been working with the Struts development team (Don Brown and Ted Husted) and have come to the conclusion that the best thing for Java community would be to merge WebWork in to Struts.</p>

<p>Read Ted's email <a href="http://www.mail-archive.com/dev%40struts.apache.org/msg13815.html">here</a>, but the gist of it is this: WebWork is a great technology, and Struts is a great community. It's a perfect match and bringing the two together will only be better for WebWork and Struts users alike. The only down side for me is that I'll be working less with OpenSymphony, but I believe that is a small price for all the great benefits that come from this merger.</p>

<p>Just to be clear, WebWork is <strong>not</strong> going away. WebWork 2.2 is still coming out any day now, and there may even be a WebWork 2.3. But new minor/major versions won't be coming out under the WebWork name for much longer. Instead, they will be released under the Struts incubator program with the intent to eventually become Struts Action Framework 2.0.</p>

<p>So don't worry, WebWork 2.1.8, 2.2.1, and other bug fix releases will continue to come out and we will support the WebWork community as long as needed. In addition, we'll make compatibility with both Struts and WebWork a high priority, so future releases may help with that. To be clear: <strong>no one is leaving WebWork and it will continue to be supported for a very long time</strong>.</p>

<p>With this renewed energy, larger development team, and larger community, the combined efforts of Struts and WebWork will surely make the Struts platform the easiest, fastest, and most powerful Java web framework available. We hope that all the WebWork users and developers are as excited about this as we are and are ready to take WebWork to the next level.</p>]]>
        
    </content>
</entry>
<entry>
    <title>WebWork 2.2 Beta 3 Released</title>
    <link rel="alternate" type="text/html" href="http://blogs.opensymphony.com/webwork/2005/10/webwork_22_beta_3_released.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://blogs.opensymphony.com/mt/mt-atom.cgi/weblog/blog_id=3/entry_id=207" title="WebWork 2.2 Beta 3 Released" />
    <id>tag:blogs.opensymphony.com,2005:/webwork//3.207</id>
    
    <published>2005-10-31T02:45:56Z</published>
    <updated>2005-10-31T02:46:29Z</updated>
    
    <summary>You can get it here. This release includes many bug fixes (thanks to the community!) and also is the first release to include a snapshot of the documentation from the wiki. The final steps for a 2.2 final release are...</summary>
    <author>
        <name>Patrick Lightbody</name>
        
    </author>
    
    <content type="html" xml:lang="en" xml:base="http://blogs.opensymphony.com/webwork/">
        <![CDATA[<p>You can get it <a href="https://webwork.dev.java.net/files/documents/693/23275/webwork-2.2-beta-3.zip">here</a>. This release includes many bug fixes (thanks to the community!) and also is the first release to include a snapshot of the documentation from the wiki. The final steps for a 2.2 final release are to make the wiki-based documentation top-notch and to close out all remaining bugs. We hope to do this very soon!</p>]]>
        
    </content>
</entry>
<entry>
    <title>WebWork + Ivy = Awesome</title>
    <link rel="alternate" type="text/html" href="http://blogs.opensymphony.com/webwork/2005/09/webwork_ivy_awesome.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://blogs.opensymphony.com/mt/mt-atom.cgi/weblog/blog_id=3/entry_id=197" title="WebWork + Ivy = Awesome" />
    <id>tag:blogs.opensymphony.com,2005:/webwork//3.197</id>
    
    <published>2005-09-23T06:17:50Z</published>
    <updated>2005-09-23T06:20:19Z</updated>
    
    <summary>As WebWork 2.2 wraps up, the only remaining task is documentation. One of the documentation efforts I&apos;ve always hated is explaining the dependencies. Now that WebWork uses Ivy, we no longer have to do this. Instead, in the distribution, the...</summary>
    <author>
        <name>Patrick Lightbody</name>
        
    </author>
    
    <content type="html" xml:lang="en" xml:base="http://blogs.opensymphony.com/webwork/">
        <![CDATA[<p>As WebWork 2.2 wraps up, the only remaining task is documentation. One of the documentation efforts I've always hated is explaining the dependencies. Now that WebWork uses Ivy, we no longer have to do this. Instead, in the distribution, the depdencies are <a href="http://www.opensymphony.com/webwork/dependencies/opensymphony-webwork-default.html">clearly graphed out</a>. If you're not using Ivy or Maven2, you probably should take a look. I was a skeptic at first, but it really does make life easier.</p>

<p><em>Note: apologies about the weird formatting in that example -- the site <span class="caps">CSS </span>is clashing with the pages. It doesn't normally look like that.</em></p>]]>
        
    </content>
</entry>
<entry>
    <title>WebWork in Action now available</title>
    <link rel="alternate" type="text/html" href="http://blogs.opensymphony.com/webwork/2005/09/webwork_in_action_now_availabl.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://blogs.opensymphony.com/mt/mt-atom.cgi/weblog/blog_id=3/entry_id=193" title="WebWork in Action now available" />
    <id>tag:blogs.opensymphony.com,2005:/webwork//3.193</id>
    
    <published>2005-09-23T06:02:07Z</published>
    <updated>2005-09-23T06:05:30Z</updated>
    
    <summary>After far too long, Jason and I are pleased to announce that WebWork in Action is now available in eBook format and will soon be on shelves. WebWork in Action covers WebWork version 2.1.7 (plus some 2.2 features) in more...</summary>
    <author>
        <name>Patrick Lightbody</name>
        
    </author>
    
    <content type="html" xml:lang="en" xml:base="http://blogs.opensymphony.com/webwork/">
        <![CDATA[<p>After far too long, Jason and I are pleased to announce that <a href="http://www.manning.com/books/lightbody">WebWork in Action</a> is now available in eBook format and will soon be on shelves. WebWork in Action covers WebWork version 2.1.7 (plus some 2.2 features) in more depth than any other publication currently available. We hope you enjoy it.</p>

<div align="center">
<img src="http://www.manning.com/assets/products/lightbody/lightbody_cover150.jpg"/>
</div>

<blockquote><p>"My developers love it! We have already improved a couple of applications because of this book."<br />
- Rickard Öberg, Software Architect, Senselogic, Founder of XDoclet and WebWork OpenSource projects.</p>

<p>"Well organized and covers all the bases!"<br />
- Anoop Ranganath, Senior Architect, Green Bar Software</p>

<p>"Wow! People developing web apps need this. It?s very, very good!"<br />
- Berndt Hamboeck, Senior Architect, Sybase</p>

<p>The WebWork framework implements a simple command/ business-logic and <span class="caps">MVC </span>design. It provides out-of-the-box functionality developers need to build well-designed applications that are modular and reusable. Written by its two primary developers, WebWork in Action is the first book to focus entirely on WebWork. Like a true "In Action" book, it is both a tutorial on WebWork and a sourcebook for its use in demanding, real-world applications.</p>

<p>Starting with "Hello World" the Webwork way, the book immerses the reader in practical, how-to material. You will soon know how to configure WebWork and gradually and incrementally master the robust and powerful uses of the framework. WebWork in Action uses the same basic, continuing example used in Manning's Hibernate in Action to show how to integrate WebWork with the popular Hibernate persistence framework.</p>

<p>What's Inside</p>

<p>    * Handling data and displaying content with Expression Language and Tag Libraries<br />
    * Inversion of Control and WebWork actions<br />
    * VelocityType conversion and data validation<br />
    * Internationalization and component-oriented design<br />
    * Integration of web applications into the Hibernate persistence framework<br />
    * Webwork best practices and architecture </p></blockquote>]]>
        
    </content>
</entry>
<entry>
    <title>Spring and WebWork, together</title>
    <link rel="alternate" type="text/html" href="http://blogs.opensymphony.com/webwork/2005/09/spring_and_webwork_together.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://blogs.opensymphony.com/mt/mt-atom.cgi/weblog/blog_id=3/entry_id=192" title="Spring and WebWork, together" />
    <id>tag:blogs.opensymphony.com,2005:/webwork//3.192</id>
    
    <published>2005-09-23T05:56:06Z</published>
    <updated>2005-09-23T05:59:25Z</updated>
    
    <summary>As I have already mentioned, the WebWork team is fully committed to cooperating with existing Java community members. To fully demonstrate that commitment, WebWork has done what it should have done a long time ago: adopted Spring as the official...</summary>
    <author>
        <name>Patrick Lightbody</name>
        
    </author>
    
    <content type="html" xml:lang="en" xml:base="http://blogs.opensymphony.com/webwork/">
        <![CDATA[<p>As I have <a href="http://blogs.opensymphony.com/webwork/2005/09/rife_and_webwork_together.html">already mentioned</a>, the WebWork team is fully committed to cooperating with existing Java community members. To fully demonstrate that commitment, WebWork has done what it should have done a long time ago: adopted Spring as the official IoC container. WebWork's own IoC container is deprecated as of version 2.2 beta 2.</p>

<p>On top of that, we recently updated how Spring integration works and made it even simpler to plug in. See the updated documentation <a href="http://wiki.opensymphony.com/display/WW/Spring">here</a>. </p>]]>
        
    </content>
</entry>

</feed> 

