You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by Martin Marinschek <ma...@gmail.com> on 2006/04/04 05:47:33 UTC
invokeOnComponent
Hey guys,
I don't want to sound impudent - but can I ask for an extension for
the invokeOnComponent?
Invoke on component is great for one, two, four components, but there
are times when I want to walk the whole tree, executing something on
certain components, changing properties, etc. Very useful together
with phase-listeners.
Is there a way to add something like
walkTree
or
invokeComponent
without a client-id parameter?
regards,
Martin
--
http://www.irian.at
Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German
Professional Support for Apache MyFaces
Re: invokeOnComponent
Posted by Martin Marinschek <ma...@gmail.com>.
Don't get you.
You mean the treewalk was suggested, but turned down? I definitely
want to have invokeOnComponent, just would want to do a treewalk, too,
if necessary.
It's all about adding custom lifecycle phases, which will work with
any component, but don't need a change in the component itself.
regards,
Martin
On 4/4/06, Jacob Hookom <ja...@hookom.net> wrote:
> This was brought up, but we were looking for a way to selectively
> process known components (even to themselves) from the client. Kind of
> riding the point that we can't externally provide a strategy to walk the
> component tree, but needed something efficient without introducing a
> full tree walk by the components themselves.
>
> I'm all for more cool features for JSF 1.2--
>
>
>
> Martin Marinschek wrote:
> > Hey guys,
> >
> > I don't want to sound impudent - but can I ask for an extension for
> > the invokeOnComponent?
> >
> > Invoke on component is great for one, two, four components, but there
> > are times when I want to walk the whole tree, executing something on
> > certain components, changing properties, etc. Very useful together
> > with phase-listeners.
> >
> > Is there a way to add something like
> >
> > walkTree
> >
> > or
> >
> > invokeComponent
> >
> > without a client-id parameter?
> >
> > regards,
> >
> > Martin
> >
> > --
> >
> > http://www.irian.at
> >
> > Your JSF powerhouse -
> > JSF Consulting, Development and
> > Courses in English and German
> >
> > Professional Support for Apache MyFaces
> >
> >
>
>
> --
> --------------------------
> Sent from my FrankenBerry Wireless Handheld
>
>
--
http://www.irian.at
Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German
Professional Support for Apache MyFaces
Re: invokeOnComponent
Posted by Jacob Hookom <ja...@hookom.net>.
This was brought up, but we were looking for a way to selectively
process known components (even to themselves) from the client. Kind of
riding the point that we can't externally provide a strategy to walk the
component tree, but needed something efficient without introducing a
full tree walk by the components themselves.
I'm all for more cool features for JSF 1.2--
Martin Marinschek wrote:
> Hey guys,
>
> I don't want to sound impudent - but can I ask for an extension for
> the invokeOnComponent?
>
> Invoke on component is great for one, two, four components, but there
> are times when I want to walk the whole tree, executing something on
> certain components, changing properties, etc. Very useful together
> with phase-listeners.
>
> Is there a way to add something like
>
> walkTree
>
> or
>
> invokeComponent
>
> without a client-id parameter?
>
> regards,
>
> Martin
>
> --
>
> http://www.irian.at
>
> Your JSF powerhouse -
> JSF Consulting, Development and
> Courses in English and German
>
> Professional Support for Apache MyFaces
>
>
--
--------------------------
Sent from my FrankenBerry Wireless Handheld