I solved the problem with JasperReports by copying everything from the webworks-default package in xwork.xml and deleting the JasperReports section. So that takes care of that.

I am unimpressed by the Webwork documentation. It looks like it was written on the back of a napkin. I think the biggest argument I have with it is that the tutorial only covers POST. Not GET. Just POST. You have a form, you submit, and then you get the results back. That's lovely, but there's no tutorial for what to do when you're not posting a form. I just want a droplet. Is that so wrong?

I looked at for a bit, and looked at the chicken scratchings on the wiki regarding a ModelDriven interface. Finally, I tried figure out how AppFuse was doing it.

Somewhere in the middle of this, I realized that Spring and xWork (WebWork's IoC layer) were interacting in a way that was not in the Wiki or even using the same class as described in the Wiki. So I tried to figure that out as well. I think I understand it mostly.

So. Here's the UserAction class diagram.

Note how there are various services that must be configured on the action.

Then there's a userList.jsp page that must be rendered. Here's how it all gets laid out.

Keep in mind I still have no clear idea about how Spring and xWork are magically talking to each other, but it seems to work.