Howard Lewis Ship discusses how to add extend class functionality at runtime via meta-programming for Java using Tapestry Plastic.

Finally, he finished with an interesting thought – that one of the main scalability issues with any web framework is people i.e. the competencies and preferences of the developers on the team.

Arguably, Struts 1.x is end of life. There are plenty of other Java server-side web frameworks: JSF (the standard), Wicket, Tapestry, Struts 2, Echo, Spring MVC, etc. Do you have any market data on what developers are adopting after Struts 1.x?

I've been working with Wicket for almost a year. We've just released our first product that uses Wicket for the user interface, and so it seems like a good time to take stock. Here's the executive summary: Wicket rocks!

I still think that Tapestry is one of the best platforms to be developing your Web application on. Having said that I think that there are some issues that need to be addressed to help improve Tapestry‘s adoption into the Java community

If you are looking for something lightweight that will take a few minutes to learn, Wicket is not for you. If you are looking for a component-oriented approach, Wicket is a contender. It requires some up front investment of time, and the documentation isn

Once setup correctly WTP is easy to use. This document exists to so that new users can setup WTP without hours of troubleshooting and experienced users don't forget anything.