At 09:22 12/4/01 +0200, Stefan Bodewig wrote: >* tasks provide some way to identify their attributes from the > outside.
+1 on the condition that it doesn't interfere with usage of task instance (ie something like BeanInfos) >* tasks should have access to its own XML representation. > > /Task Object Model instead of XML representation/ +1 >* Task level if and unless attributes. -0 it could be provided as an aspect but I don't see a need for it >* Allow tasks to find out, whether another task has completed successfully. -1 Why ? We have properties - what more do you need? >* provide failonerror like functionality to all tasks. (Provide this > as an aspect?? much like logging aspect or classloader aspect). +1 as an aspect provided functionality Cheers, Pete *-----------------------------------------------------* | "Faced with the choice between changing one's mind, | | and proving that there is no need to do so - almost | | everyone gets busy on the proof." | | - John Kenneth Galbraith | *-----------------------------------------------------*
