I have a copy of RAD here, but I've purposely stayed away from it because I had some bad experience with it and WSAD before it... recently, it screwed up doing J2EE security configuration and I spent two days trying to understand the XML it spit out, finally got it and fixed it by hand. Unfortunatley, I've had more bad experiences like that with IDEs than the good "this saved me a bunch of time!" experiences. Others have had just the opposite experiences I know.
-- Frank W. Zammetti Founder and Chief Software Architect Omnytex Technologies http://www.omnytex.com On Wed, August 10, 2005 1:58 pm, [EMAIL PROTECTED] said: > > WebSphere Application Developer has a Struts Diagraming tool that will let > you create a skeleton struts application using drag and drop. It does > very > well. It will populate your struts-config.xml and create skeleton JSPs, > ActionClasses, FormObjects, and the like. No actual "code" generation, > just the shell. > > If you are looking for something a little more robust, the Rational rapid > developer will do the same thing using UML and will Shell out you > application based on your model. Again little actual code generation, but > it will give lesser developers a good starting point using real > design/archetecture. > > > > > "Frank W. > Zammetti" > <[EMAIL PROTECTED] To > com> "Struts Users Mailing List" > <user@struts.apache.org> > 08/10/2005 01:34 cc > PM "Struts Users Mailing List" > <user@struts.apache.org> > Subject > Please respond to RE: Nice try (was Java code > "Struts Users generator including Struts 1.2) > Mailing List" > <[EMAIL PROTECTED] > he.org> > > > > > > > > Anyone who has read this list for a while knows my feeling on automated > code generation... saying it's a crime against humanity might be > overstating my opinion a bit, but not by much :) > > I think Greg says it well though... I never had a problem using the > application wizard in Visual C++... it just created a very simple skeleton > application, everything else was up to me. I have no problem with that. > Plug-ins that generate simple beans I can live with. Utilities that let > me enter a list of basic information on class members and spit out the > skeletal class code for me are fine. > > Those tools that take in a WSDL file and spit out a very basic Web Service > client from it are OK, barely... they haven't crossed that line I don't > want crossed yet, but they are on the way... > > I remember having to deal with some Swing code that was created by a > junior programmer using some IDE (I forget which frankly, it's not on the > market any more - I want to say it was IBM's old one before WSAD, but I > might be wrong). The code was such an immense tangle of crap it still > makes me shudder to think of it all these years later. THAT is the kind > of code generator that will NEVER be allowed in my shop, no matter how > productive it might make lesser developers. I don't care how easy and > fast it is to drag some pictrues on a canvas, draw some lines to show > interactions, enter a little bit of additional info and get essentially a > whole applicatio out... that kind of stuff won't go on where I have any > say in the matter. The cost in the long-run so far outweighs the > immediate benefits as to be laughable, or so has been my experience > anyway. > > -- > Frank W. Zammetti > Founder and Chief Software Architect > Omnytex Technologies > http://www.omnytex.com > > On Wed, August 10, 2005 1:18 pm, Lindholm, Greg said: >> That's a very narrow view of code generators. >> There are plenty of domains where the generator is used once to give the >> programmer a starting point. >> (I'm not commenting on nor judging this guys stuff.) >> >> -----Original Message----- >> From: Leon Rosenberg [mailto:[EMAIL PROTECTED] >> Sent: Wednesday, August 10, 2005 1:05 PM >> To: 'Struts Users Mailing List' >> Subject: AW: Nice try (was Java code generator including Struts 1.2) >> >> Hmm... I think you clearly offence the rule one for generators: >> generated code should never be touched! >> >> Regards >> leon >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
