(And so should some complex things.) You shouldn't have to write four different classes just to change a password. Traditional J2EE architectures require that developers spend more time writing code to make the frameworks happy, than they ever get to spend writing code to make the user happy. Seam lets you reduce the size of your code dramatically. And that reduces bugs. And it makes refactoring easier. And it makes delivering new functionality quicker. Productivity matters. But with Seam, JSF, EJB 3.0 and jBPM, you don't need to sacrifice the ability to handle complex problems just to achieve great productivity.