Yep. I usually bunch all action type stuff in the action package. Like forms, action utils, value objects used in actions, etc... I guess it more or less represents the presentation part of the package and the service represents the business part. I only see a need to dissect it into these two because the actions should only need to talk to the service layer. The service layer should be talking to reusable components in some other package like com.acme.components.whatever.
robert > -----Original Message----- > From: Rick Reumann [mailto:[EMAIL PROTECTED] > Sent: Friday, September 17, 2004 3:05 PM > To: Struts Users Mailing List > Subject: Re: I'm going back to just using regular Actions.. a question > > > Robert Taylor wrote the following on 9/17/2004 2:58 PM: > > > com.acme.applications.web.foo.account.action > > com.acme.applications.web.foo.account.service > > Yea that was my option 2 I posted. I'm still debating about this one as > well. I can see both approaches being decent: > > > com.acme.applications.web.foo.account.action > com.acme.applications.web.foo.account.form > > com.acme.applications.web.foo.service.action > com.acme.applications.web.foo.service.form > > OR: > > com.acme.applications.web.foo.action.account > com.acme.applications.web.foo.action.service > > com.acme.applications.web.foo.form.account > com.acme.applications.web.foo.form.service > > > I'm leaning towards the later approach since when I'm looking for > something I usually know that I'm looking for a form or an action so I > can then look to that top level and go down. > > -- > 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]
