Personnaly, I would prefer to clearly separate model from Stripes.
project-name
-- models
----- User.java
-- stripes-app
---- controllers
------- LoginAction.java
---- views
------- Login.jsp
And if you want to put your JSPs in WEB-INF, it would look like.
project-name
-- models
----- User.java
-- stripes-app
---- controllers
------- LoginAction.java
---- views
------- WEB-INF/pages/Login.jsp
Christian
________________________________
From: Gregg Bolinger [mailto:[EMAIL PROTECTED]
Sent: Monday, November 17, 2008 12:40 PM
To: Stripes Users List
Subject: [Stripes-users] Unifying Stripes Application Structure
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:
project-name
-- stripes-app
---- controllers
------- LoginAction.java
---- views
------- Login.jsp
---- models
------- User.java
etc etc
etc etc
I'm not dead set on that layout but I really think that if you (again,
optionally) have something like this available then initial app creation
becomes even simpler, especially for n00bs. I had started something like this
but it was based on a project structure that I liked. So it would really have
only catered to me.
What say ye?
Gregg
-------------------------------------------------------------------------
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
