Hi,
T5.3 rc3:
I have a page, that has the following tml:
And the modal component has the following contents:
http://tapestry.apache.org/schema/tapestry_5_3.xsd";>
I thought, that when the form is submitted, the modal component could listen
to onFailure + onSub
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 contain
I added
@Inject
private TypeCoercer typeCoercer;
and change the method to
return new EnumValueEncoder(typeCoercer, UserRole.class);
that seems to resolve the NPE issue.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Unknown-beaneditform-save-ex
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 component
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 e
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:
http://tapestry.1045711.n5.nabble.com/Tapestry-5-3-rc3-Page-must-be-specified-before-initializing-for-partia
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:
http://tapestry.1045711.n5.nabble.com/T5-3-rc3-event-bubbling-bug-tp4966490p4966901
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.
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:
http://tapestry.1045711.n5.nabble.com/Beaneditform-with-two-submit-buttons-tp4967644p49676
On Sat, 05 Nov 2011 21:27:56 -0200, TG 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 your submit
buttons
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 occurs
11 matches
Mail list logo
