To illustrate, have a look at onReturnPageInstance():
T5.4:
http://jumpstart.doublenegative.com.au/jumpstart7/examples/navigation/returntypes1
T5.3:
http://jumpstart.doublenegative.com.au/jumpstart/examples/navigation/returntypes1
HTH,
Geoff
On 15 Nov 2014, at 3:39 am, Thiago
On Fri, 14 Nov 2014 12:26:30 -0200, Robson Pires
wrote:
Hi guys,
Hi! (Bão? :))
I am handling an event in a page A which was bubbling from a component B:
ComponentB.java
componentResources.triggerEvent(BULK_ACTION_SELECTED, new Object[] {
selectedAction, keys}, null);
PageA.java
void
Hi guys,
I am handling an event in a page A which was bubbling from a component B:
ComponentB.java
componentResources.triggerEvent(BULK_ACTION_SELECTED, new Object[] {
selectedAction, keys}, null);
PageA.java
void onBulkActionSelectedFromresourceSearchResults(String context,
long[] keys
Thank you.
On Sat, Aug 30, 2014 at 12:54 PM, Geoff Callender <
geoff.callender.jumpst...@gmail.com> wrote:
> I can't see anything wrong with your code. As requested, here is a new
> example: Event Bubbling With Context:
>
>
> http://jumpstart.doublenegative.com.au/jum
I can't see anything wrong with your code. As requested, here is a new example:
Event Bubbling With Context:
http://jumpstart.doublenegative.com.au/jumpstart7/examples/component/eventbubblingwithcontext
Geoff
On 30 Aug 2014, at 8:44 am, Sumanth wrote:
> There is already a
xplanation please look at this link
http://markmail.org/message/fjev6gt76fpc6akq and even this link which
points out to the previous link.
Hope this helps
http://apache-tapestry-mailing-list-archives.1045711.n5.nabble.com/T5-Event-bubbling-td2423435.html
.
On Sat, Aug 30, 2014 at 12:11 AM, Yubr
ect(String context) {
> dosomething
> }
>
> But I'm getting exception. I've searched jumpstart but their i saw
> examples for event bubbling without context. How to bubble up events which
> have context.
>
> Im pretty new and would like to get a start in the right di
tring context) {
dosomething
}
But I'm getting exception. I've searched jumpstart but their i saw examples
for event bubbling without context. How to bubble up events which have
context.
Im pretty new and would like to get a start in the right direction. If this
question has been prev
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.
usable.
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 not form any hierarchy.
That is why the event
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 complicated logic to handle such configuration,
> if you can not include Pager directly in PagerContainer.
>
> Best regards,
> Cezary
>
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
PagerDemo.tml, and not in PagerContainer.tml
On Tue, Jul 2, 2013 at 11:11 PM, Lance Java wrote:
> Ok, I'm totally stumped.
>
> Event bubbling works here:
> http://tapestry-stitch.uklance.cloudbees.net/eventbubbledemo
>
> But doesn't work here:
> http://tapest
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 PagerCont
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
Yep, figured it out already.
Too much time since using T5, and too much JSF in between. It's good to be
back ;)
- Ville
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/T5-3-rc3-event-bubbling-bug-tp4966490p4970859.html
Sent from the Tapestry - User mailing list ar
On Sun, 06 Nov 2011 12:13:08 -0200, 9902468
wrote:
The saga continues:
I have a "onSuccessFromProductSizeForm" -method on my page. When the
form is
enclosed in a component I get the following error message:
Method
com.orient.web.admin.pages.entity.ProductSizeBulkAdd.onSuccessFromProductS
shows... :)
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/T5-3-rc3-event-bubbling-bug-tp4966490p4969263.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail
O be corrected before the 5.3 is released OR disable it by
> default. Otherwise every app will break that uses event bubbling..
>
> Howard: as you implemented the original feature could you comment if this is
> right?
>
> - Ville
>
> --
> View this message i
should be IMHO be corrected before the 5.3 is released OR disable it by
default. Otherwise every app will break that uses event bubbling..
Howard: as you implemented the original feature could you comment if this is
right?
- Ville
--
View this message in context:
http://tapestry.1045711.n5.nab
Furthermore, correct if I'm wrong, but the event bubbles through the
component hierarchy until the root component (page) or if the event bubbling
is explicitly aborted using event handler return value.
(http://tapestry.apache.org/component-events.html, see event bubbling.)
Thus the algorithm
The form is in the component.
This indicates that the events thrown by the components must be handled by
the component (or page) that declares the component throwing the event in
it's tml?
But how the event bubbling is going to work then?
My component should listen to the form events to be
at is listened by this method" routine I presume?
>
> - Ville
>
> --
> View this message in context:
> http://tapestry.1045711.n5.nabble.com/T5-3-rc3-event-bubbling-bug-tp4966490p4968614.html
> Sent from the Tapestry - User mailing list archive at Nabble.com.
>
> --
re is a component that can trigger the
>> event that is listened by this method" routine I presume?
>>
>> - Ville
>>
>> --
>> View this message in context:
>> http://tapestry.1045711.n5.nabble.com/T5-3-rc3-event-bubbling-bug-tp4966490p4968614.html
>
gt;
> This is a bug in the "check that there is a component that can trigger the
> event that is listened by this method" routine I presume?
>
> - Ville
>
> --
> View this message in context:
> http://tapestry.1045711.n
ened by this method" routine I presume?
- Ville
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/T5-3-rc3-event-bubbling-bug-tp4966490p4968614.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
-
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 ca
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
e event should
> bubble through the component hierarchy until aborted or the root is hit, but
> this does not seem to be the case (anymore)?
>
> I don't even know where to start looking, so any pointers are welcome.
>
> - Ville
>
> --
> View this message in contex
t should
bubble through the component hierarchy until aborted or the root is hit, but
this does not seem to be the case (anymore)?
I don't even know where to start looking, so any pointers are welcome.
- Ville
--
View this message in context:
http://tapestry.1045711.n5.nabble.com
On Tue, Sep 29, 2009 at 11:24 PM, Andreas Pardeike wrote:
> How can I make sure that information from component construction time will
> survive so it can be used when the ajax event is processed?
That's how things works, currently. It's a task for your "service" to
provide that.
Cheers
--
Mas
On 29 sep 2009, at 16.12, Thiago H. de Paula Figueiredo wrote:
One simple question related to this: if I have a service that is
used by
many components and that holds a list of component related
information,
how do I make this request related?
Your service must have the perthread scope. A
Thanks for the reply Thiago.
One simple question related to this: if I have a service that is used by
many components and that holds a list of component related information,
how do I make this request related? That is, if I want i.e. have a list
of all those components nested ids for a given requ
Em Tue, 29 Sep 2009 11:08:01 -0300, Andreas Pardeike
escreveu:
Thanks for the reply Thiago.
You're welcome! :)
One simple question related to this: if I have a service that is used by
many components and that holds a list of component related information,
how do I make this request relate
Em Tue, 29 Sep 2009 03:21:40 -0300, Andreas Pardeike
escreveu:
Thiago,
Hi!
I have a test version up in a project and I wonder why Tapestry
does not support this kind of loose event handling where
components register themselves for zone refreshes or method calls
that are related to events.
al. It's a natural extension to event-bubbling that
otherwise only provides a one-way (up in this case) communication.
/Andreas Pardeike
On 28 sep 2009, at 16.27, Thiago H. de Paula Figueiredo wrote:
Em Mon, 28 Sep 2009 10:41:35 -0300, Cordenier Christophe > escreveu:
Hi
Em Mon, 28 Sep 2009 10:41:35 -0300, Cordenier Christophe
escreveu:
Hi
Hi!
Take a look ComponentEventRequestHandlerImpl, following code are calling
the event on requested Component and Event :
boolean handled = element.triggerContextEvent(parameters.getEventType(),
parameters.getEvent
,
null);
I Hope this helps,
Christophe.
-Message d'origine-
De : Andreas Pardeike [mailto:fsys@gmail.com]
Envoyé : lundi 28 septembre 2009 15:28
À : Tapestry users
Objet : Event bubbling - how to implement a top level catch-all target
Hi
Hi,
My application uses a base class that catches all events that are
not handled by a component or a page on the way up.
At first, I tried to write the handler in my layout component but
since its not the top of the hierarchy, I had to create a base class
that every page extends. There, I have
> 2) Normally, what I do in these situations, is to encapsulate the
> events with a custom event. That hides the details of component from
> users of the component, so even if, eg, form component events change,
> or if I change the guts of the component to operate differently, I can
> still keep t
f the component, so even if, eg, form component events change,
or if I change the guts of the component to operate differently, I can
still keep that "public" contract via the custom event.
Robert
On Jun 15, 2009, at 6/156:07 PM , Piero Sartini wrote:
Hello!
I have a problem with
Hello!
I have a problem with the event bubbling stuff. A form is located inside a
component which in turn is embedded inside my page. Now I am trying to process
the form in my page.
There is more than one component inside the page so there is the need to
specify the component who triggers the
so I
> need to let the page hook when the save event is triggered. I read
> about event bubbling which seems to be what I want although I can't
> seem to make it work. I have the components onSelectedFromSave method
> return false, but the pages onSelectedFromSave method never gets
save event is triggered. I read
about event bubbling which seems to be what I want although I can't
seem to make it work. I have the components onSelectedFromSave method
return false, but the pages onSelectedFromSave method never gets
called unless I comment out the one in the component. I have I
big deal. I do still think it'd be great to cut and paste one of your
explanations of this to the event bubbling section of the docs...
Cheers guys.
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
> Of Josh Canfield
> Sent: 09 Septemb
name convention, but that's
> not necessary for this IMHO.
>
> Now I'll wait for Howard to tell me an obvious reason this can't be done
> that'll make me feel silly... lol
>
> Andy.
>
>> -Original Message-
>> From: Blower, Andy
>> S
be done
> that'll make me feel silly... lol
>
> Andy.
>
> > -Original Message-
> > From: Blower, Andy
> > Sent: 09 September 2008 11:08
> > To: 'Tapestry users'
> > Subject: T5: Event bubbling
> >
> > I'm trying to handl
l wait for Howard to tell me an obvious reason this can't be done
that'll make me feel silly... lol
Andy.
> -Original Message-
> From: Blower, Andy
> Sent: 09 September 2008 11:08
> To: 'Tapestry users'
> Subject: T5: Event bubbling
>
> I'm
I'm trying to handle an event in a parent component of one that fires the event
and it doesn't seem to work unless it's a generic catch all event handler like
onAction(). If I specify the component id like onActionFromThing() or
specifying component="thing" in an OnEvent annotation it doesn't ca
will.
> Basicall I'm looking for the event to behave like a RuntimeException - it
> will keep moving up until it's handled
>
> Toby
>
> - Original Message
> From: Toby Hobson <[EMAIL PROTECTED]>
> To: tapestry
> Sent: Wednesday, 14 May, 200
e a RuntimeException - it will keep moving
up until it's handled
Toby
- Original Message
From: Toby Hobson <[EMAIL PROTECTED]>
To: tapestry
Sent: Wednesday, 14 May, 2008 2:00:43 PM
Subject: Event bubbling
Hi Guys,
I would like to define an area at the top of my border.tml to
Hi Guys,
I would like to define an area at the top of my border.tml to show messages
which may be "flashed" to the user. Ideally pages and nested components will be
able to set the message that will be displayed here. I was thinking of allowing
pages and components to fire a custom event, which
ff: Re: T5 : Event bubbling
Gesendet: Do, 10. Apr 2008
Von: Stephane Decleire<[EMAIL PROTECTED]>
> Thanks Armand.
> Returning 'this' works great !
>
> Stephane
>
> Francois Armand a écrit :
> > Stephane Decleire wrote:
> >> correct behavior of eve
Thanks Armand.
Returning 'this' works great !
Stephane
Francois Armand a écrit :
Stephane Decleire wrote:
correct behavior of event bubbling in T5 (i mean handlers which
returns null values do not catch the event) ?
If yes, what is the solution for an handler to both catch the
Stephane Decleire wrote:
correct behavior of event bubbling in T5 (i mean handlers which
returns null values do not catch the event) ?
If yes, what is the solution for an handler to both catch the event
and show the same page to the user ?
Returning a non null value is the think to do, see
gement of the action ...
}
Is it the correct behavior of event bubbling in T5 (i mean handlers
which returns null values do not catch the event) ?
If yes, what is the solution for an handler to both catch the event and
show the same page to the user ?
Thanks in advance
Stephane
I've found the answer. To achieve this you should return 'true' from
event handler.
Dmitry Shyshkin пишет:
Non null value stop processing of all other event and start page
rendering. But it actually not what I need.
I have a multiple onActivate event handlers with different count of
arguments,
Non null value stop processing of all other event and start page
rendering. But it actually not what I need.
I have a multiple onActivate event handlers with different count of
arguments, and I want to process only one of them.
void onActivate(Long id) {
object = loadobject(id);
// do som
"The event will bubble up the hierarchy, until it is aborted. The event
is aborted when an event handler method returns a non-null value."
(http://tapestry.apache.org/tapestry5/tapestry-core/guide/event.html)
Stephane
Dmitry Shyshkin a écrit :
Hi, all.
Is there a way to stop bubbling of curr
Hi, all.
Is there a way to stop bubbling of current event?
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Steph wrote:
Each time a piece of information is rendered several times in a page.
Say for example in a contact list. Each contact is displayed by a
component including 'remove', 'update', 'details' links.
I already know what you will say ... "move the handler from the page
to the component" ;-
tion between all the events bubbling from B in my C
component ?
In practice, if i have 2 actionlinks A and A' in my B component. I don't
know from which actionlink comes an "action" event bubbling from B in my
page C and so the handling of these events can't be made
tion between all the events bubbling from B in my C
> component ?
> In practice, if i have 2 actionlinks A and A' in my B component. I don't
> know from which actionlink comes an "action" event bubbling from B in my
> page C and so the handling of these events can'
onlink comes an "action" event bubbling from B in my
page C and so the handling of these events can't be made at the page
level ... It's quite annoying for a frequent use case.
Davor Hrg a écrit :
the event type is intact,
but the source changes
onSubmitFromA
onSubmitFrom
' in the
> >> component ?
> >>
> >> I've tried something like that :
> >> @OnEvent(component="the_name_of_my_component_in_the_container.detaillink")
> >>
> >> without success ...
> >>
> >> Any advice is welcom
OnEvent(component="the_name_of_my_component_in_the_container.detaillink")
without success ...
Any advice is welcome
Stephane
Steph a écrit :
Hi,
I've got a strange behavior in event bubbling ...
I have an actionlink in a component :
Show
details ...
If I write an event hand
mponent ?
>
> I've tried something like that :
> @OnEvent(component="the_name_of_my_component_in_the_container.detaillink")
>
> without success ...
>
> Any advice is welcome
>
> Stephane
>
> Steph a écrit :
>
> > Hi,
> >
> > I've got a strange behavior in event bubb
the event of my 'detaillink' in the
component ?
I've tried something like that :
@OnEvent(component="the_name_of_my_component_in_the_container.detaillink")
without success ...
Any advice is welcome
Stephane
Steph a écrit :
Hi,
I've got a strange behavior in event bubb
Hi,
I've got a strange behavior in event bubbling ...
I have an actionlink in a component :
Show
details ...
If I write an event handler in the component, the event is handle
correctly :
@OnEvent (component="detaillink")
Object detailLink(Long id) {
... do the handling
Can you provide a little more information about your setup? How are you
delegating to BlockPage? Is it a page or a component?
On 8/31/07, Imants Firsts <[EMAIL PROTECTED]> wrote:
>
> Hi!
>
> I have a page (MyPage) which displays a form by
> delegating the form rendering to a block in a different
>
Hi!
I have a page (MyPage) which displays a form by
delegating the form rendering to a block in a different
page (BlockPage). MyPage renders fine, but when the
form is submitted it generates Prepare and Submit
events in the BlockPage and they are not propagated
back to MyPage.
Is there a way to r
On 4/13/07, Kristian Marinkovic <[EMAIL PROTECTED]> wrote:
... maybe ff and ie handle this scenario differently... i'll test it
and report my results on monday :)
another solution would be to have a small script in place (onclick)
that checks the incoming events on the div node and triggers th
I'm shocked to hear that ie isn't behaving as expected! ;)
http://www.quirksmode.org/js/introevents.html
On 4/13/07, Diego <[EMAIL PROTECTED]> wrote:
Hello,
I want to use event bubbling to find out what checkbox is click with an
Ajax call.
To do this I attach the EventL
D]>
An
"Tapestry users" <[EMAIL PROTECTED]>
Kopie
Thema
Event bubbling in IE doesn't work
Hello,
I want to use event bubbling to find out what checkbox is click with an
Ajax call.
To do this I attach the EventListener to a div surrounding the checkboxes.
This works in fir
Hello,
I want to use event bubbling to find out what checkbox is click with an
Ajax call.
To do this I attach the EventListener to a div surrounding the checkboxes.
This works in firefox, the id of the checkbox is returned. But in IE the id
of the surrounding div is returned.
Is there a way to
81 matches
Mail list logo
