ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shackelford, John-Mason" <Sha...@ncs.com>
Subject RE: polymorphic data types as nested elements
Date Wed, 21 Aug 2002 18:39:17 GMT
Erik

> Am I getting warmer?

You were never coldm, but the additional detail is very helpful. I
understand much better!

John-Mason Shackelford

Software Developer
NCS Pearson - Measurement Services
2510 North Dodge St.
Iowa City, IA 52245
319-354-9200x6214
shacjo@ncs.com

> -----Original Message-----
> From: Shackelford, John-Mason [mailto:ShacJo@ncs.com]
> Sent: Wednesday, August 21, 2002 1:32 PM
> To: 'Ant Users List'
> Subject: RE: polymorphic data types as nested elements
> 
> 
> Erik,
> 
> Ah, the light comes on! Thanks.
> 
> 
> John-Mason Shackelford
> 
> Software Developer
> NCS Pearson - Measurement Services
> 2510 North Dodge St.
> Iowa City, IA 52245
> 319-354-9200x6214
> shacjo@ncs.com
> 
> > -----Original Message-----
> > From: Erik Hatcher [mailto:jakarta-ant@ehatchersolutions.com]
> > Sent: Wednesday, August 21, 2002 1:30 PM
> > To: Ant Users List
> > Subject: Re: polymorphic data types as nested elements
> > 
> > 
> > By using addXXX or addConfiguredXXX you're asking Ant to create the 
> > object for you, so it must be creatable with a no-arg 
> constructor. An 
> > abstract class is not - so you will get some kind of nasty error.
> > 
> > You need to implement the createXXX method so that you create some 
> > concrete object to return back, but your createXXX method can be 
> > declared to return the abstract base class if you desire (but 
> > remember 
> > that introspection is being used, so it *will* find 
> > setters/creators/adders on the actual object returned even if 
> > they are 
> > not declared on the abstract base class).
> > 
> > 	Erik
> > 
> > 
> > Shackelford, John-Mason wrote:
> > > Greetings all,
> > > 
> > > Having combed through Hatcher & Loughran's chapter on 
> > writing custom tasks
> > > (very good BTW),
> > > I am still a bit perplexed as to how ant resolves addXXX 
> > calls against
> > > nested tags. What is not clear to me is how the XXX portion 
> > is used in
> > > conjunction with the argument type.
> > > 
> > > I have a task which is responsible for processing commands. 
> > I define an
> > > abstract class which extends DataType and then subclass it 
> > for various
> > > commands: Get, GenericCommand, etc. The addXXX method on 
> my command
> > > processing task can then take an AbstractCommand object to 
> > work its magic. 
> > > 
> > > If I write the addXXX signature as: 
> > addAbstractCommand(AbstractCommand c),
> > > will the nested command objects be properly populated even 
> > if they contain
> > > getters and setters which are not overriden from 
> > AbstractCommand? Do I need
> > > to add multiple addXXX signatures: AddGet(AbstractCommand c),
> > > AddGenericCommand(AbstractCommand c). (This seems 
> > completely backwards). In
> > > short, what is the cash value of the XXX portion of 
> addXXX if we can
> > > determine type info from the argument?
> > > 
> > > Probably I am missing something basic. Forgive me.
> > > 
> > > John-Mason Shackelford
> > > 
> > > Software Developer
> > > NCS Pearson - Measurement Services
> > > 2510 North Dodge St.
> > > Iowa City, IA 52245
> > > 319-354-9200x6214
> > > shacjo@ncs.com
> > > 
> > > 
> > **************************************************************
> > ************** 
> > > This email may contain confidential material. 
> > > If you were not an intended recipient, 
> > > Please notify the sender and delete all copies. 
> > > We may monitor email to and from our network. 
> > > 
> > **************************************************************
> > **************
> > > 
> > > --
> > > To unsubscribe, e-mail:   
> > <mailto:ant-user-unsubscribe@jakarta.apache.org>
> > > For additional commands, e-mail: 
> > <mailto:ant-user-help@jakarta.apache.org>
> > > 
> > > 
> > > 
> > 
> > 
> > 
> > --
> > To unsubscribe, e-mail:   
> > <mailto:ant-user-unsubscribe@jakarta.apache.org>
> > For additional commands, e-mail: 
> > <mailto:ant-user-help@jakarta.apache.org>
> > 
> 
> **************************************************************
> ************** 
> This email may contain confidential material. 
> If you were not an intended recipient, 
> Please notify the sender and delete all copies. 
> We may monitor email to and from our network. 
> **************************************************************
> **************
> 
> --
> To unsubscribe, e-mail:   
<mailto:ant-user-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:ant-user-help@jakarta.apache.org>

**************************************************************************** 
This email may contain confidential material. 
If you were not an intended recipient, 
Please notify the sender and delete all copies. 
We may monitor email to and from our network. 
****************************************************************************

--
To unsubscribe, e-mail:   <mailto:ant-user-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:ant-user-help@jakarta.apache.org>


Mime
View raw message