Craig McClanahan wrote:
Common in the future? That's the plan ... it's especially designed for
folks who want to create the server side of AJAX interactions, plus people
who want to write AJAX-enabled components. The power of expression
evaluation, plus the "basic dependency injection" capabilities of managed
beans, are just too much goodness to pass up.
Obviously going OT for this thread, so I'd be happy to start a new one
if you want, but this is very interesting to me as a pretty big AJAX
booster..
Have you ever looked at DWR? I wonder what your impression is of that?
Especially since it has Spring integration, which I'm sure you would
agree if better dependency injection than the basic capabilities JSF
provides, and since it works with *any* framework, and allows you to
access POJOs, I would personally favor that than start using a whole new
framework. What benefits would you say there are to using Shale/JSF
than that with any other framework over a DWR-based solution? Certainly
you can fire off a chain in any case if that's your need, so I don't see
that as being one. Again, just curious here as an "AJAX guy".
I guess what I'm *really* getting at is to ask doesn't AJAX make much of
this JSF/Shale vs. Struts vs. WW vs. Tapestry vs. whatever else somewhat
irrelevant? Might it even be better to just develop the Shale remoting
as a separate AJAX library?
Not trying to pick fight :-)
Craig
Frank
--
Frank W. Zammetti
Founder and Chief Software Architect
Omnytex Technologies
http://www.omnytex.com
AIM: fzammetti
Yahoo: fzammetti
MSN: [EMAIL PROTECTED]
Java Web Parts -
http://javawebparts.sourceforge.net
Supplying the wheel, so you don't have to reinvent it!
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
