> yeah, looking at your class diagram I can see what you're saying. A > reference to TemplateEngine is much better
A mistake in diagram: TemplateEngine doesn't have a reference to SubTask. That refernce will tie it to xdoclet. SubTask will pass on an XdocletContext instance to templateEngine and templateengine will pass it on to each tag. So a better design is: A TagContext interface, XDocletContext implements it, and TemplateEngine accepts a TagContext. A setTagContext(TagContext) class is also needed in TemplateEngine, it's called before start(). Agree? > head, so I think that what I've just checked in can happily be dumped. Not really. We're refactoring, right? > Unfortunately I have next to zero international bandwidth atm, so I'm not > really in much of a position to be exchanging code and stuff... but I'm > keen to work through this. fyi I'm in Sydney (GMT+10), and will probably > get into this tomorrow morning (about 10-12 hours away). Now that I've > got your class diagram, if you make a start, then I can work of a TODO > list if you want to do it that way... if not, when I start tomorrow I'll > work off the class diagram as best I can.... let me know I'll try to start it tonight, though I don't know I'll have time or not. Our international bandwidth seems great actually, I'll code when you're asleep and you code when I'm asleep :-) Communication is the key, "UML to understand, UML to communicate", that's why I drew the diagram :o) Ara. _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com _______________________________________________ Xdoclet-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
