Cool. I will leave trails until it hits that point then since Tapestry was a big jump already, I need to spend more time on the actual project then on frameworks :) The suits can only take so much :P I'm glad they let me jump into tapestry.
So would it be available as components or something? Or hivemind services? Greg -----Original Message----- From: James Carman [mailto:[EMAIL PROTECTED] Sent: Thursday, March 16, 2006 10:38 AM To: 'Tapestry users' Subject: RE: A generic edit page? Yes, you kind of have to jump whole-heartedly, feet-first into Trails (unfortunately) at the moment. Although, (as I said previously) we are actively trying to improve that. I've figured out a way to move our DAOs out of Spring and into HiveMind (see the spring-transaction and spring-hibernate3 subprojects of the hivemind javaforge project). I just have to remove the aspects from Trails, at least the ones that have to be woven into "client" classes. I don't think it's reasonable to require that clients use AspectJ in their projects. It's fine if we use it within Trails, but to have to weave in our aspects is a bit heavy-handed IMHO. -----Original Message----- From: Greg Cormier [mailto:[EMAIL PROTECTED] Sent: Thursday, March 16, 2006 10:33 AM To: Tapestry users Subject: RE: A generic edit page? Someone mentioned though Trails kinda takes over, and in the future they want to see it just as a component. So would there be a lot of work in implenting Trails? Greg -----Original Message----- From: Peter Svensson [mailto:[EMAIL PROTECTED] Sent: Thursday, March 16, 2006 10:26 AM To: Tapestry users Subject: Re: A generic edit page? I'm using current subversion in production :) Cheers, PS On 3/16/06, James Carman <[EMAIL PROTECTED]> wrote: > > Howard's blog entry is referring to what Trails does now. Yes, it's > actively under development. > > -----Original Message----- > From: Greg Cormier [mailto:[EMAIL PROTECTED] > Sent: Thursday, March 16, 2006 9:48 AM > To: Tapestry users > Subject: RE: A generic edit page? > > So this Trails is under development now? > > I'd need a more stable solution to launch to production, but reading HLS's > article is excatly what I wanted :) > > <span jwcid="@edit:EditObject" object="ognl:pojo"/> > > That would be nice :) I guess I could write my own component to do this > then? > > -Greg > > --------------------------------------------------------------------- > 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] --------------------------------------------------------------------- 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]
