> Using XDoclet for this kind of thing is pushing it a > bit far. I > generally recommend that code generation be used as > a "work-around" for > a technological platform that makes it cumbersome to > write everything by > hand. I mean technologies that require related > information to exist in > many diferent places. (Like EJB, Hibernate, JDO, > Struts etc).
Or better said, where you can express complex behaviour with few metadata... Especially when this complex behaviour needs to be coded again and again... And there are no alternatives like AOP... regards, ===== ----[ Konstantin Pribluda ( ko5tik ) ]---------------- Zu Verstärkung meines Teams suche ich ab Sofort einen Softwareentwickler[In] für die Festanstellung. Arbeitsort: Mainz Skills: Programieren, Kentnisse in OpenSource-Bereich ----[ http://www.pribluda.de ]------------------------ __________________________________ Do you Yahoo!? Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes http://hotjobs.sweepstakes.yahoo.com/signingbonus ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user
