■

そういやあ、Gavin KingがSeamをリリースしたときの
TSSのコメントでこんなことを言ってました。

One of the (several) goals of Seam is to bring
Ruby On Rails style productivity to the Java EE platform,
which means we had to be incredibly economical with "framework"
constructs. The idea of the programming model in Seam is that
you don't have create any "extra things" to make your frameworks happy.
You express your business model in entity beans, application logic in
session beans, and then you're able to bind those directly to
the JSP/Facelets page. Any extra layering or patterns are up to you,
Seam doesn't force that on you.

Complexity is the opposite of what Seam is about :-)

要は、RubyOnRailsに近い生産性をJavaEEで出してやるって
ことみたいです。

みんなRailsを相当意識してますね。
Webアプリケーションフレームワークで、
具体的に良い生産性の指標が出たってことですかね。

JavaでRailsを追い越してやる！みたいなね。