Thanks guys, I think I might be able to handle the event in the pager.
Ultimately the event needs to update a binding (the current page) and
return the zone body to be rendered. I can probably pass the binding and
the zone in the PagerContainerModel environmental. It's a bit messy but
should work.
On Tue, 02 Jul 2013 17:08:24 -0300, Lance Java
wrote:
Ah, gotcha. Can you elaborate on this complicated logic?
Hmm, that complicated logic will be complicated. :P Tapestry has basically
three ways of passing data between components, mixins and pages:
1) Component and mixin parameters (t
Ah, gotcha. Can you elaborate on this complicated logic?
On 2 Jul 2013 20:30, "Cezary Biernacki" wrote:
> Hi Lace,
>
> PagerContainer is not a parent to Pager.
> Pager is part of PageDemo page.
> It is just rendered in body of of PagerContainer,
> but it is not belong to PagerContainer, they do
Hi Lace,
PagerContainer is not a parent to Pager.
Pager is part of PageDemo page.
It is just rendered in body of of PagerContainer,
but it is not belong to PagerContainer, they do not form any hierarchy.
That is why the event bubbling seems not to work in this case.
You would need more complica
Can you verify that container of stitch.pager is PageContainer using
ComponentResources.getContainer()?
I can suggest its parent is actually PagerDemo.
Can you move handlers there and check if bubbling works there?
The only difference in your examples is that stitch.pager physically
located in Pa
Ok, I'm totally stumped.
Event bubbling works here:
http://tapestry-stitch.uklance.cloudbees.net/eventbubbledemo
But doesn't work here:
http://tapestry-stitch.uklance.cloudbees.net/pagerdemo
I have eventlinks in Pager.tml
Event1
Event2
Event3
And I have handlers in PagerContainer.java
Hmm... I've stripped my example down to it's bare bones and events are now
bubbling up... I must be doing something stupid in my original code.
And yes, the parent component is in the components package, it's in
mybasepackage.components.
On 2 July 2013 16:19, Howard Lewis Ship wrote:
> This is
This is odd; it feels like something in Tapestry that's too rock-solid to
fail. Is there any chance the parent class is not being instrumented as a
component class? What package is it in?
On Tue, Jul 2, 2013 at 1:58 AM, Lance Java wrote:
> As I said in my previous message, I've tried triggerEven
As I said in my previous message, I've tried triggerEvent on the
ComponentResources and ComponentResources.getContainerResources(). Neither
bubble up to the parent.
Hi,
ComponentResources.triggerEvent(...) is the way to go, isn't it?
Parent.java:
@OnEvent(component = "child", value = "childEventCall")
void childEventCall(final String someString, final int someInt) {
//dosomething
}
Child.java:
void onSomeEvent() {
_resources.tri
No typos, if I move the event handler from parent to child it fires as
expected.
I've also tried ComponentResources.triggerEvent(...) and
ComponentResources.getContainerResources().triggerEvent(...) in the child
but nothing seems to bubble up.
FYI This is tapestry 5.3.7
Are you sure that your problem is not something trivial like e.g. a typo?
Cezary
On Mon, 1 Jul 2013 22:23:39 +0100 Lance Java
wrote:
I'm scratching my head over this one... hoping someone can point it out.
I've got a page which renders a parent component.
The parent component renders a child
I'm scratching my head over this one... hoping someone can point it out.
I've got a page which renders a parent component.
The parent component renders a child component.
The child component renders an eventlink.
I've created an event handler in the parent component but tapestry can't
seem to fin
13 matches
Mail list logo
