T5.3. rc3: event bubbling bug?

Hi, T5.3 rc3: I have a page, that has the following tml: t:modal t:id=dialog t:form t:id=productSizeForm clientValidation=false /form /t:modal And the modal component has the following contents: t:container xmlns:t=http://tapestry.apache.org/schema/tapestry_5_3.xsd; div

Tapestry 5.3 rc3 - Page must be specified before initializing for partial page render.

Hi, I get that error, if I use the ajaxResponseRenderer service during the handling of an event, that has originated from a link that does not have it's zone set. I understand the technical reason for this. We have a fairly complex system, and we do not know beforehand what zones the page

Re: Unknown beaneditform save exception

I added @Inject private TypeCoercer typeCoercer; and change the method to return new EnumValueEncoderUserRole(typeCoercer, UserRole.class); that seems to resolve the NPE issue. -- View this message in context:

Re: T5.3. rc3: event bubbling bug?

Expected behavior. The modal component wraps the form, but it isn't the parent/container of the form. That is, if you could @InjectContainer in the form, it would be the page, not the modal component. Basically, the way tapestry determines parent/child is: which template contains the

Re: Tapestry 5.3 rc3 - Page must be specified before initializing for partial page render.

It sounds like you might be better off writing your own ajaxlink component that always does xhr? You can certainly still tie into Tapestry's ajax/zone handling, and asking tapestry to generate the links is simple. Robert On Nov 5, 2011, at 11/56:42 AM , 9902468 wrote: Hi, I get that

Re: Tapestry 5.3 rc3 - Page must be specified before initializing for partial page render.

Yes, this possibility crossed my mind too, but I thought that I'll consult the list before making more things to maintain. Thanks for the input, - Ville -- View this message in context:

Re: T5.3. rc3: event bubbling bug?

Ok, thanks for the info! This has been a really big misunderstanding from my part. Now that I know how it works I just have to think other ways to implement my use case. - Ville -- View this message in context:

Re: T5.3. rc3: event bubbling bug?

This is news to me too (not having worked much with event bubbling) and I think this is probably a widespread misunderstanding, since the Tapestry usage differs significantly from the standard HTML/XML container concept. I'll try to find places in the documentation where this can be made clear.

Beaneditform with two submit buttons?

Is it possible to have two submit buttons for this component? I would like to implement save (the page stays) and submit (done, and go to the welcome page). Thanks. TG -- View this message in context:

Re: Beaneditform with two submit buttons?

On Sat, 05 Nov 2011 21:27:56 -0200, TG tapestry...@hotmail.com wrote: Is it possible to have two submit buttons for this component? I would like to implement save (the page stays) and submit (done, and go to the welcome page). I don' think so, but you can use a Form with a BeanEditor and

Lost parameter binding after zone update

I posted on this before and thought I had resolved it, but I'm seeing it again. When I update a zone by returning a MultiZoneUpdate from an event handler (via an ajax call), one of the components re-rendered as a result of the update has a parameter that is no longer bound. The zone update