> Something inside of me screams out that if you're ending up with 1mb > of > code just to spit out an ejb-jar.xml, then something is horribly > wrong. > Especially when you consider the myriad of modules that are > available. > xdoclet could well end up being 10mb if you want to generate your > web.xml, ejbs, and a couple of vendor specific descriptors. Not good!
I'm in your side. I think what we need is not a one side fits all solution. Generating classes for all xml elements is based on teh assumption that we're going to something complicated in those classes. More flexibility, you know. In most cases, for more elements, we just need the template file. For some elements we need the flexibility. So a better solution would be: - generate a velocity template, with foreach/blabla there - If ejb-ref element for example has a sophisticated logic then use the class-per-element strategy but only for this element. Ara. __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user
