Yes, I'm guilty of this. I'm not sure how bad I am about this, but the real question is how do I learn not to. The design patterns I use seem to work just fine. I've been trained several places, including Sun, but it was in the past.
James, maybe you could help me here. Do you have an article similar to the one you made that would help me better understand what my programming patterns should look like. As for including logic in domain objects, I only use logic that directly relates to that object. I'm referring the the wiring of the interface to the domain. If that makes sense. Again I'm no expert, but I've changed my patterns many times over the years. Seems like every method I've learned has become the wrong way at one time or another. So I someone can give pointer I'm listening. And not ten books I need to read, I've read so many book I'm sure just cutting to the point would be quicker for me. Maybe something like "this is not how to do it and this is the right way" type of article. James Carman wrote: >You have to be careful not to create an "anemic domain model" >(http://www.martinfowler.com/bliki/AnemicDomainModel.html) when you approach >your architecture this way (I'm guilty of this). Some stuff should actually >go in the User class itself as opposed to being in a service. > >-----Original Message----- >From: Stanczak Group [mailto:[EMAIL PROTECTED] >Sent: Thursday, June 02, 2005 5:28 AM >To: [email protected] >Subject: Re: What should be a service? > >I'm very new to this as well, but shouldn't a service be anything that >has action on your data? What I mean is say you have a user object. >That's your data. Then anything that acts upon that data should be a >service. So login, email, password recovery etc... should all be actions >that act on that data the user object. Then the part that you build is >the logic that routes the users actions to the proper services. In my >mind that's where I draw the line. Each service can use another services >resources, but I wouldn't have one service that controls all the logical >flow of my program. So I guess to summarize, HiveMind is used to >encapsulate actions (aka, services) into manageable modules. Again I'm >sure I'm not completely correct because I'm also new to HiveMind as well. > >Glen Stampoultzis wrote: > > > >>Sounds sensible however a service being a component doesn't really tie >>it down for me much. I guess there is no clear boundary. >> >>On 6/2/05, belaran <[EMAIL PROTECTED]> wrote: >> >> >> >> >>>The way i see it a "service" should be component... >>>For instance, >>>For a simple web app using hivemind, you could a DAO service to access >>> >>> >the database , a bizness service that's actually those the work and maybe a >third service, that'll realize the XML/XSL transformation. > > >>>That's my point of view, but i'm still a beginner, so maybe i'm wrong.... >>> >>>Belaran >>> >>> >>>2005/6/2, Glen Stampoultzis <[EMAIL PROTECTED]>: >>> >>> >>> >>> >>> >>>>Was just wanting to get some peoples opinions on what sort of things >>>> >>>> >should be made into hivemind services? > > >>>>It seems to me that it would be pretty easy to go crazy and make all >>>> >>>> >sorts of services but I'm thinking that would probably be a bad idea. Where >do you stop? I'd be interested in hearing real life services people have >created. > > >>>>Regards, >>>> >>>>Glen Stampoultzis >>>> >>>> >>>> >>>> >>>> >>>> >>> >>> >>> >>> >>--------------------------------------------------------------------- >>To unsubscribe, e-mail: [EMAIL PROTECTED] >>For additional commands, e-mail: [EMAIL PROTECTED] >> >> >> >> >> >> > > > -- Justin Stanczak Stanczak Group 812-735-3600 "All that is necessary for the triumph of evil is that good men do nothing." Edmund Burke ..________...............__................. ./ _____/..____..._____/..|_..____...____.... /...\..____/.__.\./....\...__\/.._.\./._..\.... \....\_\..\..___/|...|..\..|.(..<_>.|.<_>..).... .\______../\___.._\__|../__|..\____/.\____/...... ........\/.....\/.....\/.......................... --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
