While reading the thread "Expanding ALL properties manually" [1] on the
user list
I got an idea: could a ResourceCollection support filterchains for its
own? In consequence
all tasks "just" supporting RCs would also support filterchains as well.
The main idea is that RC iterates over the nested resources.
Filterchains only are
important if you access the content - via input/output streams.
So the actual use
<resources>
<files/>
<url/>
</resource>
wouldnt make any difference. When you add a filterchain
<resources>
<files/>
<url/>
<filterchain/>
</resource>
the 'resources' would wrap the nested resources, so that the streams are
passed
through the filterchain.
'resources' would be modified in the base class
BaseResourceCollectionContainer.
The 'chaining' could be done via ResourceUtils.copyResource().
Consequence: the task couldnt do an 'instanceof' comparison (e.g. for
type casting) because
it only holds the wrapper. Mmh - not nice...
What do you think?
Jan
[1] http://marc.theaimsgroup.com/?l=ant-user&m=113449879022522&w=2
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
