Erik Hatcher wrote:
addXXX, addConfiguredXXX, and createXXX are all consulted. There is a createParam method on the CallTarget (corresponds to <antcall>) class.
Nested elements do not have to be DataType's to work - it simply takes the object corresponding to the adder/creator method and populates it with the same logic in IntrospectionHelper.
I'd recommend you browse through IntrospectionHelper to understand how this stuff works better. All the answers lie there!
Erik
Shackelford, John-Mason wrote:
Greetings,
This is probably a lame question, but I am having trouble understanding how
the Ant task passes in the properties specified in the <property name=""
value=""/> subelements. There is only one addXXX method and it adds a
reference, but Property isn't a DataType so that's not it(?). When Ant can't
find another class to match an element, does it test to see if it is a task
and then attempts to execute it? I was under the impression that a task had
to be some sort of container to support executable subelements, but my
understanding is obviously shaky. There doesn't appear to be anything in
Task that would handle property subelements natively. What am I missing?
John-Mason Shackelford
Software Developer NCS Pearson - Measurement Services 2510 North Dodge St. Iowa City, IA 52245 319-354-9200x6214 [EMAIL PROTECTED]
**************************************************************************** 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:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
