I started out with tpestry maybe six months ago and had only suffered badly mangled JSP/STL before that. I happened upong Trails and haven't moved an inch after that. The only "extra" things you need to do is do run "ant create-edit-page" if you really need to have a trailsified editpage you want to change, otherwise just add the @Entities and access them from homegrown pages all the way. Acegi security and Lucene search included in the box. Would have taken me months, to say the least.
Cheers, PS On 4/26/06, albartell <[EMAIL PROTECTED]> wrote: > > I looked into Trails awhile ago (https://trails.dev.java.net/) and was > quite > impressed with its ability to get me up and running with a CRUD > application > in no time flat (like minutes instead of days). The only problem in my > mind > is that I would rather have it generate ALL of the source code out of the > gate and let me maintain it from there. The Trails code instead has you > only modify the things you need to modify to meet your needs. At first > this > seemed like a great a would seem to be a time saver, but I didn't get that > feel. It may be that I just need to spend more time in the code of Trails > to gain a better understanding. > > Something that deserves to be checked out to say the least. > > Aaron Bartell > http://mowyourlawn.com/blog > > -----Original Message----- > From: John Coleman [mailto:[EMAIL PROTECTED] > Sent: Wednesday, April 26, 2006 4:51 AM > To: Tapestry users > Subject: Re: [OT] OMG! A dynamic div component in JSF > > yes, I agree, and there has been many mentions here, of a need for tools > to > crank out Tapestry apps' > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
