On 4/10/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Let's face it... this is confusing! I understand the interplay with dependency injection and how the Action interfaces fills this contract. Not real sure about ModelDriven however (or is it ScopedModelDriven). I also realize the infamous OGNL has values pushed/popped on a stack and there are a variety of ways to access them in other places. What we need is a clear example that is more involved than Person.java to realize how all the parts interrelate.
Towards the end of creating a bigger example, I setup a Petstore site on Google Code, with the hope of extending the Spring MVC/Struts 1 example with a S2 example too. * http://code.google.com/p/sq1-petstore/ Though, I'll probably do a YUI example first. If someone wants to work on an a S2 Petstore, that would be great.
If you look at the Struts 2 + Spring 2 + JPA + AJAX <http://struts.apache.org/2.x/docs/struts-2-spring-2-jpa-ajax.html>you will discover even this *fresh* example does not illustrate the S2 way of minimizing configuration via Struts-style wildcards. It's just bits and parts -- and what the heck was the TopLink stuff? Developers are pulling ideas from this half-documented site and pushing code into their SCM. I honestly think for S2 to be successful, we need a better staring point as an example. Many of the online samples return 404 when clicked. What we currently have is not representative of an enterprise web-site. Too trivial or too complex is too bad. I would happily publish my S2 web app as a demonstration once I am certain it utilizes the *correct* S2 techniques and not just something I was able to get working.
You'd probably have to do it the other way around. Set it up on Google Code or someplace first, and then ask for feedback.
Another thing is the subject line for these messages! The answer to your problem might be in this message or that, but you'll skip it because the subject does not sound correlated to your issue. I can hear it now – "everyone save the messages and search your archives." I want S2 to succeed as badly as those of you on this message group, however, the hit-and-miss approach of coding, reading about a better technique, refactoring, then coding it again is numbing. We need a concise and unified blueprint "that remains in lock-step with the prevailing S2 version" before building the web app!
Thanks for volunteering!
If this is expected to compete with the challengers, this needs to be completed soon. I have a buddy doing RoR. If what he is telling me about the ease of development is even 10% fact, it won't be long before S2 is SYesterday. 10% is a wonderful Rate-of-Return
I don't think anyone here is jealous of RoR. If my team wanted to use it, I wouldn't hesitate. I expect most of the other Struts committers feel the same way. I know other committers use RoR from time to time too. It's not an election of remedies. I don't think any of us will ever see the day when there is one web application framework, or, for that matter, one web platform. -Ted. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
