Wo-ow!
cool, that went fast!
Now, I'm definitely for a JSF 1.2 branch, if we can go with that.
We'd probably want to branch the more stable 1.1.x codeline and let trunk evolve to leverage the new 1.2 APIs.
Kind Regards,
John Fallows.
regards
Martin
On 2/14/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> The commons-el code is poor IMHO. The one I donated to Jasper was originally founded within the RI 1.1 donation and benchmarked quite a bit faster at the time.
>
> The one re-written for the EL-API and donated to both Sun and Apache is based on Java CC, and finely tuned for JSF's serialization and stateful lifecycles around VariableMappers and FunctionMappers.
>
> I may be biased, but I think it would be a waste of time to try to modify the commmons-el solution for the EL-API.
>
> BTW, on the topic of JSF 1.2 and findComponent, we've added invokeOnComponent to the spec, implemented much like was discussed here on the dev list and has been implemented and tested within the RI. I, personally, would like to see MyFaces adopt this method early instead of providing a partial solution with perspectives to users.
>
> -- Jacob
>
> >
> >> Wow!. I must have missed that email! Was it donated to MyFaces? I
> >
> >I think it was sent, when you are on vacation ;-)
> >
> >-Matthias
>
--
http://www.irian.at
Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German
Professional Support for Apache MyFaces
--
http://apress.com/book/bookDisplay.html?bID=10044
Author: Pro JSF and Ajax: Building Rich Internet Components, Apress
