Re: [Axis2] Databinding structuring proposal

[Chuck Williams]

"Ajith Ranabahu" <[EMAIL PROTECTED]> wrote on 03/29/2006 07:37:48 AM: Hi Kenneth, See my comments inline would have been more straightforward to use a straight POJO-based input model into a template lang like velocity or freemarker. I'm not familiar with the velocity or freemarker template languages but In any case I guess we'll be introducing another dependancy! Also if we special case the templating language, it makes things harder for the people who would need to tweak the code generator. As someone who's tweaked the code generator to add support for choice particles, recursive data types, etc., I'd like to second Ajith's point.  Xsl is a broadly known syntax that works well for the generation of final Java code.  Having the code generator structured as it is now, creating a POJO representation of the schema, transforming that into a DOM, and then using xsl to transform the DOM into Java classes, is clean, easy to understand, and quite flexible.  I was able to read and understand the code, and then extend it with the features we needed, in about a day while learning axis2.  That would likely not have been possible if a more specialized and unfamiliar templating language was used. Chuck