I found this gem on the strut-user list tonight.
This is a JavaDoc-like set of html and css files for browsing the
taglib documentation. Here's what this target does (I ran this
about 15 minutes ago):
This target will generate a grid-like view of the taglibs and their
attributes so that you can see every tag in a typical package side
by side. This helps when comparing which tags implement a certain
attribute, by allowing you to view them side by side and not have to
look up each tag by hand. (also about 15 minutes ago)
Project by Mohan Kishore, posting by James Mitchell.
The stats on the bottom right of this site are definitely wrong. At the time of this writing, it says I've had 4,351 hits today. Yeah right. I did, however, discover that I have been linked to in a major article and I'm getting a fair bit of traffic from that. The article is called Generate Web Output in Multiple Formats and Languages with StrutsCX and is hosted by DevX.com.
Why did the author include a link to this site? Because I'm hosting a demo of the StrutsCX application. I hope to use ideas from this app when I develop the XSL/XML rendering of resumes for my struts-resume app that I may/may not ever finish. I do plan on finishing it someday, but since I'm my own client - there's no deadline, no pay, and little motivation. But it is very cool to have my own reference application that I can play with to try new stuff. I definitely dig that. I can guarantee that as soon as I get indexed property validation working, it'll be in there - and that will also motivate adding many child items (i.e. skills, education, etc.) to the resume item.
I have to admit that this webwork tutorial makes WebWork look easy. In comparing this to Struts, it seems as if the Form and Action are the same thing. I wonder if I could use
BeanUtils.copyProperties(wwAction, POJO) like I am with Hibernate/Struts currently.
The funny thing is that XDoclet has made it so easy (IMO) that I don't write ActionForm's anymore. All I really write is Actions, JSPs, DAOs and Services (a.k.a. Managers). So, with my current architecture I'm using, it actually looks like more work to use WebWork's Actions than Struts Actions. Especially since I have to write my validation in my Action. The XDoclet/Validator combo makes this super simple with Struts (and would with WW if they'd adopt it ;-). The only time I've been writing forms lately is when I have a form with indexed properties. Then I create a childForm that extends the generated form and has the appropriate accessors/mutators for the indexed properties.
The one thing the article does bring to light is how much cleaner Velocity is. JSP 2.0 will make JSP's a lot easier, but Velocity looks like it's already there. The one thing that worries me about using Velocity is that, according to their homepage, they haven't had a release in 8 months and their last release was a Release Candidate. What the?! Seems like someone might be dropping the ball on that project.