Yes Volker,
It's surely a good candidate for a common project: I started with a4j and
fastly gave up: no JSF Lifecycle, I had to use json to communicate with
components, a real nightmare. For me, the two most important added values of
Tobago are:
- native JSF lifecycle and component approch
I agree with volker.
-Matthias
On 9/25/07, Volker Weber [EMAIL PROTECTED] wrote:
Hi,
just to put my 2¢ here and to show the advantages of tobago ;-)
In tobago the ajax requests are full integrated into the lifecycle.
We did this by taking and extending a copy of the Lifecycle impl from
Michael,
The problem that you are having isn't a JSF problem, and really isn't
a problem or bug at all. You have chosen to use A4J region and
ajaxSingle=true. By doing so, you have chosen to break the JSF
lifecycle. By bypassing the normal decode and rendering of the JSF
components (especially
Andrew,
all suggested solutions are nearly the same.
I would have to reset the components manually which is from my point of
view impossible and not manageable.
I will add this issue to the ajax4jsf forum in order to get a statement
from their point of view.
OT:
I am just curious which ajax
Hi!
I am just curious which ajax framework do you use/recommend?
It is not meant as a recommendation, I have no further experience with
other ajax frameworks.
I use the pprPanelGroup from tomahawk-sandbox.
Compared to the other ajax frameworks the pprPanelGroup might be too
limited, don't
Hi,
just to put my 2¢ here and to show the advantages of tobago ;-)
In tobago the ajax requests are full integrated into the lifecycle.
We did this by taking and extending a copy of the Lifecycle impl from myfaces.
All phases are execuded as on normal requests execpt the process*
methods are not
6 matches
Mail list logo
