On 17-11-2008 at 11:40, Gregg Bolinger wrote:
> For the wonderfully splendedness that is Stripes there is one thing that I
> don't like. Everyone has a different project structure. I'm wondering if
> anyone would be interested in unifying an application development structure
> for Stripes with some sort of app generator. It would be grails/rails -
> esque but totally optional. so something like:
[...]
The main problem that I encounter with any new project layout is
understanding what goes where. So for me, understanding the translation to
a .war and/or .ear file is crucial.
As a result, I prefer an exploded .war / .ear directory structure. For bigger
projects I'll also have a second directory for optional components.
To start, it's then easier for me to have a empty application, that starts up
with an empty page that describes what goes where. Something like:
This is an empty MVC-application using the Stripes framework
- Your views (JSP/...) should go next to this one here: ...
- Your controller (action beans) should go here: ...
- Your model your go here: ...
Naturally, such an empty application will be tailored to the kind of
deployment (.war or .ear file).
Oscar
--
,-_ "[Think before you act.]
/() ) Life is hard, but it's a lot harder when you're stupid."
(__ ( -- Redd Fox
=/ ()
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Stripes-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/stripes-users
