I've been kind of avoiding putting things into the Request object when there's an alternative, via per-thread services, to store such data in a service, in a typesafe manner. However, I'm not against some refactoring so that a single solution can work for 5.1 and 5.2.
Remember that a real goal would be to make the upgrade from 5.1 to 5.2 so simple that writing compatibility for 5.1 is not an issue. On Tue, Jul 27, 2010 at 4:14 AM, Christophe Cordenier <[email protected]> wrote: > Hi > > Please refering to this message from the mailing list > http://markmail.org/thread/7gduddrfgt6atd46 for full stack > > Actually, if i understand well Kalle's problem, the real problem is that he > wants to make its security API compatible with T5.1 and T5.2. > > To store the active page name, currently we use instance variable is used in > RequestGlobalsImpl, but shouldn't we store this information in the request > scope instead ? That would help people to get T5.2 compatilble API from T5.1 > projects... > > -- > Regards, > Christophe Cordenier. > > Committer on Apache Tapestry 5 > Co-creator of wooki @wookicentral.com > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
