On Wed, 2003-11-19 at 11:36, Rob van Maris wrote: > The proposed extension just reuses the builderwriter code that is > already there. > I totally agree that this builderwriter code has its shortcomings. But > this shouldn't be a problem, as the whole point of the extension is just > generating all the datasource files. Used for this purpose, the other > files it generates are usually ignored. I was not sure if the BuilderWriter was missing this functionality. I assumed that the BuilderWriter was a class that could only generate an generic XML from a builder. Thanx
- Re: HACK: MMBase 1.6 and 1.7: Performance: ... Rob Vermeulen
- Re: HACK: MMBase 1.6 and 1.7: Performance: ... Michiel Meeuwissen
- Re: HACK: MMBase 1.6 and 1.7: Performan... Eduard Witteveen
- Re: MMBase 1.6 and 1.7: Performance: JDBC cache Vincent van der Locht
- RE: HACK: MMBase 1.6 and 1.7: Performance: JDBC... Rob van Maris
- CALL ENDS: MMBase 1.6 and 1.7: Performance: JDB... Pierre van Rooden
- Re: Vote: Applications 1 Full Backup export extensio... eduard
- Re: Vote: Applications 1 Full Backup export ext... Eduard Witteveen
- BuilderWriter Pierre van Rooden
- RE: Vote: Applications 1 Full Backup export... Rob van Maris
- Re: Applications 1 Full Backup export e... Eduard Witteveen
- Re: Applications 1 Full Backup export extension Vincent van der Locht
- RE: Vote: Applications 1 Full Backup export extensio... Rob van Maris
- CALL ENDS: Applications 1 Full Backup export extensi... Pierre van Rooden
