> From: Jack Woehr [mailto:[EMAIL PROTECTED] > > Steve Loughran wrote: > > > Even if you could retro-fit every task out there with getters, > > -what about overloaded set operatons? which one should > the get return? > > -what about property assignments. Tasks get their setters with > > properties expanded. > > Hmm. Ah, well. Writing out the project seems to be a fairly obvious > functionality in comparison > to some of the exotic functionality of Ant. I guess it's just one of > those things which in hindsight > the design should have accomodated, but which are difficult > to retrofit > given that the design > did not so accomodate. >
Maybe we are looking at the problem the wrong way. What is what people want to do? Do they want to programatically create some project and then as an after thought they decide to serialize it to XML? (which will not work); Or do they want to create a project programmatically with the intention of serializing it to XML. If the later, then the obvious thing to do us to not create tasks directly but to create our wrapping objects. Actually, you could just as well use Jdom to compose the XML and then either serialize it into XML or produce the Project object out of it (we just need to generate SAX events out of it). So, maybe there is a way to do it that is actually more natural for someone that just knows the ANT-XML syntax. Jose Alberto --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
