On Tue, 4 Dec 2001, Ben Johnson wrote: > In evaluating this as a tool, I tend to differentiate between standard > (stuff in the EJB spec or other APIs (weblogic, struts, etc)) and > conventional (common patterns, best practices, etc). I would like to > see the standard stuff enabled as the default, and the conventional > requiring explicit enabling.
ok, fair enough... the only change I see is (as you've already said) data objects... I'm trying to think of other things, but cant... > I'm not saying the conventional stuff isn't useful. Many conventions > are tedious to implement, and xdoclet can fill those gaps very nicely. > For people who use data objects, xdoclet is a godsend. The trouble is > that having certain conventions on by default moves closer to a > corollary of "one man's trash is another man's treasure." yep, agreed > My suggestion remains to have the default behavior to not introduce > anything (even the static final members of the Home interface) other > than producing the corresponding declarations in standard interfaces and > deployment files. Even the CMP subclass of the Bean should be > unnecessary. > > Andrew suggested just leaving out the subtask from the ant script, but > that doesn't work - I'll address that separately. yeah, thats on my list... the optional subtasks... atm session is compulsory, I've almost checked in the fix for that. I'll look at dataobjects next - pretty easy that one, so shouldn't cause any strife. I'm assuming Ara that you're happy with an isSubTaskDefined wrap around the relevant dataobject bits of code in the entity templates? cheers dim _______________________________________________ Xdoclet-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
