On 10/23/07, Ted Husted <[EMAIL PROTECTED]> wrote: > Why not make this "name.extension", and make it part of the core framework? > > Instead of just having one default result, we could have a default > result for various extension types. Not just for this plugin, but for > all XWork2 applications.
Not a bad idea, but it would need more thought and testing before I'd put something like that in core. Even if we did, the rest plugin would still need to have its own ActionInvocation due to its automatic result processing. > I'd suggest that then we just call this the "Rails" plugin, but I > believe that Rails is a protected mark. In any event, we might want to > start thinking of this plugin as a way to run Rails-type applications > in a Struts environment, and perhaps come up with a name that > communicates that goal. Right, the rails people would complain but even if they wouldn't there is now way this plugin could be considered on par with Rails. Rails is much, much bigger than just a few Rest conventions and even if you could replicate most of its functionality in Java, you still couldn't match the benefits Ruby gives you. No, I'm very happy for Rails the way it is and if you really want it on the JVM, use JRuby or even Grails for a closer to Java match. I barely have enough time to write a little plugin that lets you use Rest conventions in Struts 2, so replicating something as big as Rails is out of the question for me :) > Oh, I don't know. Throw in JPA and some Maven archetypes, and you > could hit the ground running for the common use cases. A key technique > might be to develop archetypes that we could run for adding new > pages/actions/entities/tests to existing applications. Between POJO > Actions and codebehinds, we might be able to do useful CRUD with zero > lines of Struts framework code. > > MyEclipse has some stunning DAO generation and JPA integration > capabilities. For what we can't do with our plugins, we might be able > to do with Eclipse plugins. Heh, it is the cobbled-together Java solutions that drive many people to Rails in the first place :) I do think there is value in the Appfuse approach and would like them to do more to encourage faster, full-stack development. In summary, this plugin is not about replicating Rails, but just applying its Rest design to Struts apps. If folks want to try more, feel free to start a new plugin based on this plugin, but I'd like to keep the focus on the key components of Rest. Don --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
