Return-Path: Delivered-To: apmail-jakarta-ant-dev-archive@apache.org Received: (qmail 76431 invoked from network); 30 Jan 2002 08:32:38 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 30 Jan 2002 08:32:38 -0000 Received: (qmail 22217 invoked by uid 97); 30 Jan 2002 08:32:46 -0000 Delivered-To: qmlist-jakarta-archive-ant-dev@jakarta.apache.org Received: (qmail 22201 invoked by uid 97); 30 Jan 2002 08:32:46 -0000 Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Ant Developers List" Reply-To: "Ant Developers List" Delivered-To: mailing list ant-dev@jakarta.apache.org Received: (qmail 22182 invoked from network); 30 Jan 2002 08:32:46 -0000 Message-Id: <200201300832.g0U8Wi408763@mail012.syd.optusnet.com.au> Content-Type: text/plain; charset="utf-8" From: Peter Donald To: "Ant Developers List" Subject: Re: [myrmidon] add TaskContext.getService() Date: Wed, 30 Jan 2002 19:29:03 +1100 X-Mailer: KMail [version 1.3.2] References: In-Reply-To: X-Wisdom-Cookie: . MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Hi, On Sat, 26 Jan 2002 17:14, Adam Murdoch wrote: > > I tend to think of services as different from types. Services > > persist over > > the length of the ant "execution" or at least the "workspace > > execution" or > > whatever term we were using for this. Types are created by tasks while > > serviuces never can be etc. > > Exactly. And that's why they would use different roles, to distinguish > between what they are and how they should be used. But that doesn't mean > the same infrastructure shouldn't be available to both services and > data-types. I think we mean different things when we are talking about services vs types. When I think of services I tend to think that the services are a semi-singleton available throughout the execution of all tasks. Where types are created and used as needed. For instance - consider the Javac task. It would use the JavacExecManager service. Depending on parameters passed in the JavacExecManager would use a JavaCompilerAdaptor object (ie Jikes, Modern, GCJ whatever). So in this case the task does not directly interact with the GCJ/Jikes/etc types but instead acts through the service which would in turn use the types. Thoughts? -- Cheers, Pete *------------------------------------------------------* | Hlade's Law: If you have a difficult task, give it | | to a lazy person -- they will find an easier | | way to do it. | *------------------------------------------------------* -- To unsubscribe, e-mail: For additional commands, e-mail: