that went into the wrong thread, right?
Thanks Ed, thanks Jacob! It's great to have something like this in a
spec so fast.
We can surely talk about this on J1 - maybe we should do a meetup
together where we can
discuss things like that?
On any of the evenings?
regards,
Martin
On 2/15/06, Jacob Hookom <[EMAIL PROTECTED]> wrote:
> Heheh, the system (JCP) does work! We owe it to Ed Burns for graciously
> examining the last minute proposal and seeing it through with proper
> testing and implementation within Sun.
>
> I know a lot of us have been talking about coming up with a good
> solution for AJAX and invokeOnComponent is the API piece we needed for
> sure (as discussed on myfaces-dev and elsewhere). Hopefully the two
> implementation teams can collaborate ideas again and come back with a
> common method of communication or a JS Agent that can be leveraged by
> component developers for lightweight client to server communication and
> rendering (@ J1?).
>
> Taking a page from Hibernate's Criteria object and use of Projections--
>
> // developer code
> UIViewRoot root = faces.getViewRoot();
> root.invokeOnComponent(faces, "_id0:myTable:34:message",
> Lifecycle.renderAll());
>
> // Lifecycle Class
> public static ComponentCallback renderAll = new ComponentCallback() {
> public void invoke(FacesContext faces, UIComponent instance) {
> instance.renderAll(faces);
> }
> };
>
> Again, we really need to thank Ed!!
>
>
> Martin Marinschek wrote:
>
> >Wo-ow!
> >
> >cool, that went fast!
> >
> >Now, I'm definitely for a JSF 1.2 branch, if we can go with that.
> >
> >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
> >
> >
> >
>
>
> --
> Jacob Hookom - Minneapolis
> ----------------------------
> JSF-EG, JSF-RI, EL, Facelets
>
>
--
http://www.irian.at
Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German
Professional Support for Apache MyFaces
