myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Martin Marinschek <>
Subject Re: Ajax lifecircle integration
Date Sun, 13 Nov 2005 17:25:44 GMT
IMHO, even for a small and simple inputSuggestAjax, you need to have
the full information the facesContext, the user session and the
component tree state provide to you.

You cannot expect that you want to show the same autocomplete to every
user that comes in - this really is a very seldom case. You want to
depicture I18N, session information and user permissions just like
with a JSF component.

Remember - the JSF framework was an outcome of seeing  the necessity
of componentization, state saving, etc. Why should that be any
different for AJAX components?

Only exception: the performance is bad. Well, with every new
technology, the performance was bad in the beginning when taking the
abstraction to a new level. Then the programmers of the world worked
hard to find remedies to this. And today, we seldom use Assembler to
programm ;)



On 11/11/05, Adam Winer <> wrote:
> Jacob Hookom's also looking at just such an approach, connected
> with a ProcessingContext API of his:
> -- Adam
> On 11/10/05, Sean Schofield <> wrote:
> > >  For things that are flavour (a), you'd want to go through the lifecycle,
> > > but it could be more streamlined by only processing through the lifecycle on
> > > affected components only.
> >
> > Right and Craig mentioned that he was considering working on just such
> > a "shortened" lifecycle impl.  Perhaps we can help him.  I'm going to
> > be brushing up on my AJAX and thinking about this over the next few
> > weeks.  I'll have more to say then.
> >
> > >  Travis
> >
> > sean
> >


Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German

Professional Support for Apache MyFaces

View raw message