We use option one - separate packages for actions, forms, dao, services,
util, etc.
Rick Reumann
<[EMAIL PROTECTED]
.net> To
Struts Users Mailing List
09/17/2004 02:41 <[EMAIL PROTECTED]>
PM cc
Subject
Please respond to I'm going back to just using
"Struts Users regular Actions.. a question
Mailing List"
<[EMAIL PROTECTED]
he.org>
After thinking about the flavors of Dispatch actions I use, and after
having used them as my primary type of Actions for the past 3+ years,
I've decided to go back to just using regular Actions. I like the
modular self contained Actions.
My question is more of design practice for those that just use standard
Actions. How do you design your packages? For example...
EmployeeUpdateAction:
1) package com.acme.ui.action.employee;
or
2) package com.acme.ui.employee.action;
or just put them all in one package:
3) package com.acme.ui.action;
I'm leaning towards option 1 myself. Other thoughts?
--
Rick
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]