Hello, Thanks for the answers!
I now understood more about the task I investigate: There are nested elements, that require that the application is started. The challenge is: Start the application 1.after the setters executed 2.before the nested elements are added. So the programmer started the application in a setter, to be sure that it is started before the nested element is executed. But I dont like that, because I added a second attribute that defines how the application is started! So I now start the application in every method that "runs" a nested element. E.g. addConfigured... and some others. Is this a good way to do it? Is it right that nested elements are added after the setters have been executed? It seems to work... Greetings Juergen -- Jürgen Knuplesch -----Ursprüngliche Nachricht----- Von: Stefan Bodewig [mailto:bode...@apache.org] Gesendet: Freitag, 12. Februar 2010 10:23 An: user@ant.apache.org Betreff: Re: Setter in my own Anttask On 2010-02-11, Knuplesch, Juergen <juergen.knuple...@icongmbh.de> wrote: > In what sequence the setters are executed? > I guess in the sewuence I wrote them into ma call inside my Antfile. There is no defined order and in fact I'd be surprised if it was the same accross all possible combinations of Java VMs and XML parsers. XML Parsers are allowed attributes in any order (in XML attribute order is insignificant) so even if the setters were invoked in the same order they have been handed down by the XML parser - which they not necessarily are - the final order would still depend on the XML parser. Stefan --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@ant.apache.org For additional commands, e-mail: user-h...@ant.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@ant.apache.org For additional commands, e-mail: user-h...@ant.apache.org
