[jsr-314-open] AJAX library in JSF 2.0

[Werner Punz]

Hello if I may also add a comment here, I hope having done some work on the
MyFaces implementation javascriptsjustifies that I am adding a comment here.

You cannot really compare the Ajax library of jsf2 to anything else, since
most webframeworks want to build an all in one solution while jJsf2 just
wants to build
clear paths and foundations to others build upon. Sort of the core of an
ajax library nothing more.

For me I have the feeling that it is a solid foundation which is not perfect
yet
but it is a good start to enhance upon. It is also good to have a specified
ajax path. On both the server side and client side.

But I agree with the Rich Faces guys here, it is not done yet, there is a
lot of room to improvment, but
before doing that, a requirement analysis has to be done what still is
needed before implementing
every kitchen sink corner case there is.

There is so much library specific stuff in many of those which can be solved
often in different ways so it does not make
sense to get every feature of every library in, this would open a cross
compatibility pandoras box for everyone, just for the sake of saving a few
hours of porting time. This pushes some workload on the library authors, but
in the end it helps
to make all the libraries more compatible to each other.

I will give an example, below mentioned is the statuses I dont think this
needs to be in the core spec, since the foundation of this
is the listener system, every component lib can introduce statuses by using
the listener system. Queue control however is something which in my opinion
belongs to the core spec in the long run (same goes for different transports
outside of xhr to cover some html induce corner cases like file upload
controls,  and also Comet/ HTML5 Websockets in the future).


Werner Punz






On Sun, Sep 13, 2009 at 4:25 AM, Dan Allen <dan.j.allen at gmail.com> wrote:

> ---------- Forwarded message ----------
> From: Ryan de Laplante <ryan at ijws.com>
> Date: Sat, Sep 12, 2009 at 11:15 AM
> Subject: AJAX library in JSF 2.0
> To: jsr-314-comments at jcp.org
>
> Hi,
>
> I read about the new RichFaces 4.0 being built for JSF 2.0 here:
>
> http://www.jroller.com/a4j/entry/richfaces_4_0_0_alpha1
>
> They are still using AJAX4JSF instead of JSF 2.0's built-in AJAX library
> because:
>
>  JSF 2 Ajax implementation still very limited and not contains our
>> autoupdatable zones, limitations for autoupdate, statuses, table partial
>> updates, server side processing options and so on. Queue in JSF not
>> configurable at all..
>>
>> Some of these points could be solved at application level by using some
>> event's handling for example. But for some features - you will even not have
>> a point to attach the functionality to. If the features that we provides
>> with our ajax enchancements was implemented in JSF - we would not started
>> reimplementing the weel for sure ;)
>>
> This makes me worry that none of the majorJSF UI component libraries will
> be using the built-in AJAX library because it doesn't have enough features.
>  Will JSF 2.1 complete the AJAX functional requirements of RichFaces and
> IceFaces?
>
> Can anyone comment on how the JSF 2.0 AJAX library compares to other major
> Java web frameworks?  Is it on-par, ahead of, or behind other web
> frameworks?
>
> -----
>
> Another question I have is about hiding managed beans from views.  If I
> were to build a JSF 2.0 application that lets users customize the screens
> with themes/skins, I would not want them to be able to access any and every
> scoped bean in the system.  To have this level of control I might need to
> use a web framework that gives me more control such as Struts 2, because it
> uses Freemarker and/or Velocity.
>
> Have you heard of anyone mixing JSF with Freemarker?
>
>
> Thanks,
> Ryan
>
> --
> Ryan de Laplante - Senior Programmer
> It Just Works Software Corporation
> 17 Colborne St. E #202 Orillia, ON L3V1T4
> Tel: 705-326-4254 ext 132
> Fax: 647-341-9336
> ryan at ijws.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jsr-314-open-mirror/attachments/20090913/468a3bc4/attachment.html