axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chuck Williams <>
Subject Re: [Axis2] Databinding structuring proposal
Date Wed, 29 Mar 2006 19:28:52 GMT
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<body bgcolor="#ffffff" text="#000000">
 style="font-size: smaller; font-style: italic; margin-bottom: -2.4em;"><br>
<span>"Ajith Ranabahu" <a class="moz-txt-link-rfc2396E" href="">&lt;;</a></span>
wrote on
<span>03/29/2006 07:37:48 AM</span>:<br>
  <pre wrap="">Hi Kenneth,
See my comments inline
  <blockquote type="cite">
    <pre wrap="">would have been more straightforward to use a straight POJO-based
input model into a template lang like velocity or freemarker.
  <pre wrap=""><!---->
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.&nbsp; Xsl is a broadly known syntax that works well for the
generation of final Java code.&nbsp; 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.&nbsp; 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.&nbsp; That would likely not
have been possible if a more specialized and unfamiliar templating
language was used.<br>

View raw message