Right now, I'm thinking of a new annotation that would allow you to map a component field directly to a Session attribute; the session attribute keys used by a T3 or T4 app are very predictable and this would allow the T5 app to share data where appropriate without the fuss of using the Session API directly.
On Wed, May 21, 2008 at 1:17 AM, Andy Pahne <[EMAIL PROTECTED]> wrote: > Howard Lewis Ship schrieb: >> >> ... >> I'm still experimenting, but this "dual headed" deployment will be the >> best upgrade path from T3/T4 to T5. >> >> I expect to follow up with new T5 tools to make sharing data between >> the apps easier. >> >> > > > The discussion about the package name got very long, but nobody was > interested in the "new T5 tools to make sharing data [...] easier". > > I am very interested how you will integrate T4 and T5 apps. Having such an > integration would be a viable upgrade path. > > Could you please share your thoughts on the integration tools? > > Thanks, > Andy > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Howard M. Lewis Ship Creator Apache Tapestry and Apache HiveMind --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
