I agree, I think it would be interesting to create a plugin that gives
us a seamless full stack: Struts2/Spring/JPA or Struts2/Guice/JPA.
However, one of the advantages of Groovy/Ruby is the fact that the
classes can be updated just by reloading the page and new language
features, such as closures and dynamic properties. This is where rails
really shines, it takes advantage of those language features in the
framework itself. Since we're currently restricted to Java, that limits
what we can do. We can get close, but can we get close enough.
One of the areas where I plan on exploring this question is with
validation. The current validation in s2 is ok for the basic stuff, but
falls short when you start getting complicated validation logic. There
just isn't good support out-of-the-box for this type of thing, so I was
hoping to integrate some Grails validation support into s2/webwork.
Closures are a very elegant way to define validation for a domain
object, the simplicity of a declarative XML type syntax with the power
of a full language.
Tom
Ted Husted wrote:
I would say that Rails is an excellent source of inspiration, but I
don't think Ruby or Rails is magic. Rails incorporates a number of
good ideas, and a "take no prisoners" perspective toward productivity,
but that doesn't mean every idea is perfectly implemented.
It's my belief that we can achieve the same level of productivity in
Java by using tools like Eclipse, Maven, and JPA to their full extent.
I'm especially impressed by the plugins now available with MyEclipse.
With Tomcat and Derby bundled in, we can download Java and MyEclipse
and start writing enterprise-grade applications out of the box.
A key to the success of Rails has been ActiveRecord. Likewise, a key
to creating a highly productive Java stack is adopting and exploiting
JPA. For the type of applications that most people write, especially
with something like Rails, JPA is an ideal technology.
I'm finishing up a JPA/Struts training course now. I'm presenting it
next week, and after I hope to do a series of companion tutorials. I'm
not sure that everyone realizes how close the Java ecosystem may be to
a productivy tipping point, where we might see 2x and 3x gains, just
by aggressively integrating and exploiting the tools we already have
at our fingertips.
-Ted.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]