I think he has a great point here. I am deep into developing my application and I have a scary dependence upon Xdoclet in such a way that it has negatively influenced the overall design of my application. It is way to late to go back now. I assume that the next version of Xdoclet will solve most of my problems but the point still remains: If you are generating code, why not generate exactly what you want, exactly the way you want it without the extra layer of translation? I belive we all understand the inherent lossyness, and possibly even artifacting, that can result when translating from one model to another through a constrained (and let's be honest here Xdoclet does not represent 100% of possible configuration permutations) medium.
That being said, I don't wany anyone to take away from this the idea that I don't like Xdoclet. I love Xdoclet, you guys (to quote a script kiddie) r0xx0r my b0X0rZ, XdocL3et 0wNz. -ryan > This is a XDoclet list but I will say something. What do you > think about create just plain Java files and not XDoclets files ? > Today I can understand XDoclet and this is not a problem to me. But if > we are generating files why not create all of them ? To the final user > this does not make any difference. In fact is better because the user > shoud not need to install XDoclet. On my first version I had some very > ... -- Humans are the unfortunate result of a local maximum in the fitness landscape. www.ryanmarsh.com ------------------------------------------------------- This sf.net email is sponsored by: Jabber - The world's fastest growing real-time communications platform! Don't just IM. Build it in! http://www.jabber.com/osdn/xim _______________________________________________ Xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user
