This topic stems from several discussions (see http://marc.theaimsgroup.com/?t=107419881900008&r=1&w=2), mostly springing from the concept, long-and-short, of being able to "map" <apply> output from the sourcefile just as is possible with targetfiles. I thought long and hard (well, sort of) and decided to implement a <redirector> DataType that would look a lot like the Redirector helper class in the taskdefs package, then streamline that back into <exec>, <apply>, and <java>.
<redirector> can take the following attributes: append, output, error, outputproperty, errorproperty, input, inputstring, logerror, and refid. All but the last mimic those attributes available in the relevant tasks. Nested elements supported include: <outputmapper>, <errormapper>, <inputmapper>, <outputfilterchain>, <errorfilterchain>, <inputfilterchain>. These do what you might expect and provide about every possibility I could think of. These are not compatible with the similar attributes. To keep BC on existing task attributes, my thought was that the attribute on the task would provide a default, for example, if the nested mapper returned no results for a particular file. I am mostly finished with these changes but, for one thing, I don't want to commit these until I can test with mappers that return multiple results (see http://issues.apache.org/bugzilla/show_bug.cgi?id=26364) I am now seeking feedback on the sanity of this design. I haven't explained every in and out here so please ask if there are any questions. Thanks, Matt __________________________________ Do you Yahoo!? Yahoo! Finance: Get your refund fast by filing online. http://taxes.yahoo.com/filing.html --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
