Re: T5 - Forms created inside a loop don't fire onSuccess methods

2010-01-31 Thread Thiago H. de Paula Figueiredo
On Sun, 31 Jan 2010 16:09:11 -0200, lebenski wrote: Hi, Hi! This is my code: ... I'm obsering that submitting this form does not fire onSuccessFromPickCommentForm or even just onSuccess, onValidateForm etc. Is this because i've created multiple forms with the same i

Re: [ANNOUNCEMENT] Introducing Tynamo!

2010-01-31 Thread Thiago H. de Paula Figueiredo
On Sun, 31 Jan 2010 00:40:13 -0200, Kalle Korhonen wrote: Application scope? Why not just use a static property? Better yet: a field in a singleton service. By the way, servlet's application scope is an inherently badly idea, specially when you think about threading. -- Thiago H. de Pa

T5 - Forms created inside a loop don't fire onSuccess methods

2010-01-31 Thread lebenski
Hi, This is my code: ... This results in multiple forms getting rendered on my page; pickCommentForm, pickCommentForm_0, pickCommentForm_1 etc. I'm obsering that submitting this form does not fire onSuccessFromPickCommentForm or even just onSuccess, onValidateForm etc. Is

Re: TestNG & Injecting Testify services into pages

2010-01-31 Thread akochnev
Paul, things are working again , thanks for your help. Where I was running into trouble was that looking at the debugger, the field shows up as null up until the point the field is accessed for the first time (at which point the whole lookup of the injected field seems to occur). So, in the de

Re: [ANNOUNCEMENT] Introducing Tynamo!

2010-01-31 Thread sodium
Yup, static property works for me most of the time. Just a thought anyway since Jboss Seam has application scope as well. I agree its not really a needed feature for Tynamo. However, i do find some features of Jboss Seam quite likable compared to Tap5, such as its web remoting, i just find it eas

Re: from tapestry5 quickstart to jumpstart?

2010-01-31 Thread David Blevins
On Jan 31, 2010, at 2:19 AM, faye alaska wrote: I read in several threads about conflicts of OpenEJB and Hibernate on ASM. I am wondering how you got around it or was it an old issue to worry about. It's an old issue. We eliminated the ASM dependency (repackaged it) so that no conflict