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 arbituary any OGNL expression. See here for more details

* Release Notes
* Changelog
* Download here

This release is backwords compatible with WebWork 2.2.5 and is a drop
in replacement.

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

The WebWork Development Team

Posted by Rainer Hermanns at 03:29 PM | Permalink | Comments (9)

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, 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.

• Release notes
• Changelog
• Download here

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.

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

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 Struts 2.

The WebWork Development Team

Posted by Rainer Hermanns at 09:46 AM | Permalink | Comments (2)

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 here

Thanks to the entire WebWork team for all their hard work.

The WebWork Development Team

Posted by Rainer Hermanns at 07:02 PM | Permalink | Comments (3)

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 WebWork team for all their hard work, especially during the past couple of months.

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.

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

The WebWork Development Team

Posted by Rainer Hermanns at 09:01 PM | Permalink | Comments (1)

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 WebWork team for all their hard work, especially during the past couple of weeks.

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

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.

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

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

The WebWork Development Team

Posted by Rainer Hermanns at 09:51 PM | Permalink | Comments (1)

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.

Posted by Patrick Lightbody at 05:08 AM | Permalink | Comments (8) | TrackBacks (0)

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 find your application is easier to use now!

Ajax Case Study - Simple Validations Reduce Costs/Increase Usability:

In a follow-up to his previous post, Jesper Rønn-Jensen looks yet again at business uses of Ajax technologies - specifically a 'case study' looking at one of his recent usability issues.

As a followup to my earlier post ‘AJAX performance stats, ROI, and business value‘, I decided that I’d share with you some considerations on a recent project I was involved in.

Anyways, I want to give you some of the details on why we decided to implement AJAX 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.

He mentions 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.

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.

(Via Ajaxian Blog.)

Posted by Patrick Lightbody at 07:44 PM | Permalink | Comments (15) | TrackBacks (0)