Tapestry UI Components

This is what I was talking about. Trails isn't necessarily needed if we can leverage Tapestry correctly. However, Trails can be used for quick admin apps and maybe special circumstances. The point is to arm ourselves with as much ammo as possible. Definitely watch the second one when you get 5 minutes.

There are 2 screencasts of what I was talking about. The first one of these is like a bean edit form, which is not bad, with enough practice it should be easy enough to work with but still lacks some ease of use:
http://tapestry.apache.org/tapestry5/screencast_4.html

Here is one displaying a data table component with paging capability and the ability to override and hide individual fields. This is very good.
http://tapestry.apache.org/tapestry5/screencast_5.html

Here is a list of the components it provides, which is weaker than .NET but still good enough.
http://tapestry.apache.org/tapestry5/tapestry-core/component-parameters.html