On Wednesday 23 April 2003 17:41, Dominique Devienne wrote: > Let's turn around your question: Tell me of a (string) role (beside the > special task/type cases) that would not be an interface? What good a bean > is, if it's not of an expected Java type? What method or field are you > going to use/call on it? > > I agree with Costin, all tasks/types become simply beans. You should be > able to use any one of these beans in any place it's suitable to use it, > i.e. any time the Java type/role requested is part of the bean's type (in > the isAssigneableFrom() sense). > > The type being requested depends on who requests it. Inside or outside > targets, it's any bean. And I mean really any bean: Doesn't need to > implement anything Ant-related. This is implicitly what we call today a > datatype, and they can be id'd. The subset of these beans that also have an > execute method are also implicitly tasks. The different subsets of these > beans that implements FileSelector are suitable to use within filesets, and > tasks deriving from MatchingTask since we're talking about it. > > I fail to see what is wrong with this scenario. --DD
The only problem is the namespace problem. But this is not a huge restriction. Peter.
