Actually, Tim, the author of Stripes, provided key feedback during the early design stages of Struts 2 and XWork, the core bit of Struts 2, contains code borrowed from Stripes. I've personally found Stripes to be a great example of a framework that fulfills a certain vision of an action-based MVC framework, so while Struts 2 has more features and I'd argue more flexibility, Stripes is more consistent to its vision and has attracted a deservedly passionate following. And I do agree - if a server-side component framework is what you want, hard to get much better than Wicket.
And if I'm not mistaken Struts2 still doesn't have a simple way like this to have two different events for the same action. I've also lost the link to the workaround in the Struts2 documentation using a boolean for each event name, then testing for which boolean is set to true before invoking the correct method.