I'm here. :-)
Actually, Ravi Ramaiah is also listed as a volunteer, although the web site
hasn't been updated with new pages yet. I did start on this a while ago,
but it's been on the backburner for some time now. In the meantime, Ravi
and David have been making progress, and I think both have overtaken where
I was when I stopped.
I agree with your ideas on using templates. Dealing with the copyright
notice was one of the things I didn't have a particularly clean solution
for, and dealing with different coding conventions is one I didn't have a
solution for at all.
Recently, I started wondering if it would be possible to do all of this
(meaning generating beans from an XML definition) using XSLT, instead of
writing Java code to do it. Unfortunately, I don't yet know enough XSL to
know if it's possible to generate multiple output files from a single input
XML file, but if it is, I think this would be a pretty cool way to go. (And
if it isn't possible directly, then it might be possible to parse the XML
file and invoke an XSLT processor on the resulting nodes, one per bean.) If
you wanted to change the copyright notice, you would just change the text
in the XSL stylesheet, and you're done. Same thing for Javadoc comment
format, etc.
--
Martin Cooper
At 11:57 AM 9/21/01, Baldree, Matthew wrote:
>It looks like you have most of it complete. I have a few suggestions from
>generators I wrote. I would add the ability to generate classes using
>templates - JSP, ActionForm, and Action. Each template would have tokens
>that would be replaced by appropriate generated text. The templates allow
>the user to customize standard text such as javadoc, license info, method
>signatures, standard logic, etc. In addition, I would allow the user to
>create their own tokens, token rules, and specify what templates these rules
>apply. This allows users to easily extend the generation logic.
>
>-----Original Message-----
>From: Ravindran Ramaiah [mailto:[EMAIL PROTECTED]]
>Sent: Friday, September 21, 2001 12:19 PM
>To: '[EMAIL PROTECTED]'
>Subject: RE: TODO 1.1 - Tools - ActionForm Code Generator
>
>
>Code existing on http://www.husted.com/about/struts/codemaker.htm
>can
>
>1. Generates JSPs along with ActionForm and Action classes.
> Configuration is done through XML. (Two pass generator)
>2. Can also be used to generate only the Form and Action classes
> from the existing JSPs.
>
>Ravi
>
>-----Original Message-----
>From: David Winterfeldt [mailto:[EMAIL PROTECTED]]
>Sent: Friday, September 21, 2001 12:42 PM
>To: [EMAIL PROTECTED]
>Subject: Re: TODO 1.1 - Tools - ActionForm Code Generator
>
>
>You might want to look at what has already been
>started. I started something basic and Ravi has been
>working on something that generates code based on your
>JSP page.
>
>Struts CodeMaker by Ravindran Ramaiah - Generate
>Struts application by reading configuration file or
>JSP files.
>http://www.husted.com/about/struts/codemaker.htm
>
>Struts Generator by David Winterfeldt - Based on the
>generator.xml and a table/query an xml file is
>generated. Based on the generated xml file a primary
>key class, data bean class, jdbc class, and an
>ActionForm (Struts) can be generated.
>
>General link to other resources on Ted Husted's site.
>http://www.husted.com/about/struts/resources.htm
>
>David
>
>--- "Baldree, Matthew" <[EMAIL PROTECTED]>
>wrote:
> > I was reviewing Struts 1.1 TODO list and have an
> > interest in developing the
> > XML -> ActionForm Code Generator. I have a generic
> > generator framework that
> > supports specific generator component plugins. I
> > could easily write a plugin
> > to generate the ActionForms. However, I noticed
> > Martin Cooper is the
> > volunteer. How can I get in contact with him to
> > inquire if there is still a
> > need for this tool, status of work of any that has
> > been done, etc.
> >
> > Matt Baldree
> >
> >
> >
> >
>
>
>__________________________________________________
>Terrorist Attacks on U.S. - How can you help?
>Donate cash, emergency relief information
>http://dailynews.yahoo.com/fc/US/Emergency_Information/