On Sat, 13 Oct 2001, Dmitri Colebatch wrote: > > 1. change <XDoclet:foo:bar syntax to <XdtFoo:bar > 2. start working through the methods in Subtask that should be elsewhere > and moving them, also changing the templates )o: >
ok, (1) is kinda done... what I've done is made it accept both "<XDoclet:method" and "<XDtPrefix:method" syntax. Note the capital D in "<XDt". I've done this so that its backwards compatable for smooth(er) migration. What now needs to be done is all the methods that are used in the various subclasses of SubTask need to be migrated to new implementations of XDocletTagSupport, mappings created in the xdoclet-mappings.properties file, and the templates changed. I'm not keen to start this now as I think its fairly important that now that we can have namespaces we put them in the right place... ie. group the methods in appropriately named classes. Ara have you got any thoughts on what of the current functionality should go where? I'm picturing something like: tagsupport.ejb.PersistentFieldSupport tagsupport.ejb.SecuritySupport etc... but not really in the mode of thinking for this right now. I'll start going through these tomorrow, but I'm wondering if maybe I should collapse this branch in its current state because it is backwards compatable, and it allows people doing new work to use the new syntax.... thoughts? btw - I did some fairly heavy refactorings on TemplateEngine.generate because the first time I did this I got a bug... so I went back and started from scratch, but refactored first because of the size of that generate method. Have a look at it and let me know what you think. There is still more that could be done, but I think it looks a lot more readable. cheesr dim _______________________________________________ Xdoclet-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
