I'm just in the "putting humpty-dumpty back together again" stage on this. That's the challenge of meta-programming Java; if you don't get it right, it's very hard to debug.
On Mon, Feb 15, 2010 at 9:39 AM, Kalle Korhonen <[email protected]> wrote: > Me too! For conversations, carrying the conversationid as a query > parameter would be the most natural option. Query parameters also have > lots of interesting use cases to distinguish between page initial > context and current context. Hope this makes its way to T5.2! > > Kalle > > > On Sun, Feb 14, 2010 at 11:54 PM, Massimo Lusetti <[email protected]> wrote: >> On Sun, Feb 14, 2010 at 5:21 PM, Howard Lewis Ship <[email protected]> wrote: >> >>> And, BTW, once I get all the new class transformation APIs settled >>> out, it will be easy to add the logic to inject an event handler >>> method with a query parameter rather than event context. >> >> Really?! Well this would be a great plus for us using T5 to serve some >> sort of "business service through" http... great! >> >> Cheers >> -- >> Massimo >> http://meridio.blogspot.com >> >> --------------------------------------------------------------------- >> 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] > > -- 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]
