Guys,
I'm trying to work out how to fix the AjaxFormLoop example in Jump Start.
http://jumpstart.doublenegative.com.au:8080/jumpstart/examples/tables/ajaxformloop1
The code recommends that it should use conversations instead of session
persistence. I've changed the code to use conversations but
On Sat, 13 Mar 2010 12:20:52 -0300, Pierce T. Wetter III
wrote:
T5 already has some magic elements, a.k.a. directives, such as
t:body,
t:parameter, t:block, t:content and t:remove. I don't want to
introduce magic component types as well.
Agreed, but does it seem unreasonable to have
As you may have seen from my blog posting, I just added live service
reloading to Tapestry 5.2. I'd encourage users to give 5.2 a whirl
and make sure that the changes I've made work across different
platforms and servlet containers, and that there is no performance
impact.
As with pages and compo
>> I think the issue is for someone relatively new to T5, they don't
>> know/understand why fails. To
>> them it just seems buggy and/or inconsistent. The basic mechanisms
>> look the same, but they don't act the same. That causes confusion.
>
> I agree. I don't use the syntax.
Me three.
