Hello, I'm Plain Old Action Web Framework Fan :) And i'm one of maintainers of IntelliStripes plugin for IDEA. So in this mail i'd like to raise some question related both to core stripes and to plugin.
Last years my 2 choices are Stripes and Grails. There's some good features in Grails that can be migrated to Stripes to make startup time and learning curve even less than now. Here i'd like to talk about more "Convention Over Configuration" in Stripes. Many peoples starting Stripes are using MVC incorrectly. They submit forms and redirect users directly to JSPs, creating actionBeans there with useActionBean tags instead of mapping all HTTP requests to ActionBean and there do redirect/forward/displaying views. In other way Grails forces correct usage of MVC by providing controllers and mapping from URL to controllers only. It can be customized actaully but by default it'd done that way. Also Grails uses conventions for displaying VIEWS (in MVC terms) by implicitly forwarding to GSP in views directory that can not be accesed directly by putting URL. Stripes can introduce and leverage this practice by doing following. 1. Putting emphasis for this practice in tutorials. The need to invoke ActionBean instead of JSP and hiding JSPs under WEB-INF should be advised. 2. Remove single mandatory configuraion param ActionResolver.Packages. By default Stripes can search for action beans in some predefined package. for example - stripes.action. 3. Implement some kind of Grails-like conventions for displaying views from Resolutions. View should be searched in /WEB-INF/views/actionBean/resolutionName file or similar structure. This can be done for example by creation new class DefaultViewResolution. By returning instance of this class from action method one can indicate that default view should be displayed by forwarding to that file. 4. Stripes can impelement some kind of infrastructure scripts/ant tasks/etc provided with core distribution. Those tasks are similar to grails scripts and can be used by developer from command line and by IDE plugin creators to generate ActionBean/View/VIew Directory. Well, although i think those proposals event if most will like them (i dounbt :)) won't be included into core, there's possibility to create functionalities in IDEA plugin. So when creating facet - the rules similar to described above will be used for generating artifacts. Please send me any of your assumptions :) -- Evgeny Shepelyuk Software Architect and Developer, Soft Industry Ltd. Chernihiv, Ukraine http://www.soft-industry.com E-mail: [email protected] tel. +(380)-462-651-415 tel. +(380)-44-229-52-83 tel. +(380)-462-675-244 ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ Stripes-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/stripes-users
