[Webwork-devel] 1.2 release

[<ma...@sm...>]

Ok. I think WW is about ready for another release. This
release includes the following new features/changes.
Any objections? 

For 1.3, I think we should include dreamweaver
integration and form centralized validation. Any others
I'm missing?

- Action Chaining - Added the ability to chain actions

- XHTML tags - Renamed our standard UI tags from
standard to xhtml and made them XHTML compliant

- CSS tags - Removed our CSS UI tags

- VXML tags - Moved our VXML UI tags directory location
from standard/vxml to vxml

- Modified Iterator, Subset Iterator, Sort Iterator and
Generator tags do not return exceptions if values are
null. It will be treated as an empty iterator set.

- By default, WW will load its standard prefixes
automatically. This includes webwork.action.standard
and webwork.action.test. You do not have to add these
if you add the webwork prefix property
to add your custom prefixes.

- Added the capability for you to define getAsText() in
property editors that extend WW's
ValidationEditorSupport. However, this will only work
if you register your editor. To make WW work
with property editors defined in BeanInfo, the value
stack return results will need to be refactored to
return the bean the value came from. But, if you to
register and editor, WW will use it.
This means JSP tags that try and represent a string
value of your object will call getAsText() to
return the appropriate l&f. By default, toString() is
used unless you override it to define custom formatting.

- Added primitive and object arrays support. This means
you can have Action attributes that are
primitive arrays or object arrays and WW will convert
them for you. See BeanUtil test for more details.

-Matt