>>>>> On Thu, 13 Mar 2014 22:26:22 +0100, Frank Caputo <frank_at_frankcaputo.de> said:
FC> Hi,
FC> this is not really a reply, but a summary with some comments:
FC> Am 02.03.2014 um 11:05 schrieb andy.bosch_at_jsf-forum.de:
LU> I think that most of the use cases described could perfectly be
LU> realized using JSF 2.2 features.
FC> I think, thats true.
LU> If we would enhance JSF with further possibilities regarding an
LU> action-based framework, there is a risk of "overloading" JSF.
FC> We already have view actions.
LU> Of course I am in favour of enhancing JSF according to user
LU> feedback. But I am not sure whether it is a good idea to integrate
LU> too much into it.
FC> Lets try to do it with minimal impact.
FC> Am 08.03.2014 um 03:42 schrieb Leonardo Uribe <lu4242_at_gmail.com>:
LU> In other words, what the user want is in this case is:
LU> - Take advantage of JSF 2 template system (facelets) and component model.
LU> - Don't use the JSF lifecycle and use something else that fits.
LU> Let me be clear about this: in my personal opinion it is a nonsense
LU> to take out Facelets from JSF, because Facelets was built as a view
LU> technology that takes advantage of JSF component model. If you take
LU> facelets out of JSF, what you are really doing is get rid of JSF
LU> lifecycle, but besides that, you are not doing anything else. You
LU> still want facelets TagHandlers that build a JSF component tree that
LU> can be manipulated somehow and finally rendered. The very essence of
LU> JSF remains active.
FC> Absolutely true.
FC> I used facelets in 2 projects as an email templating engine. But it
FC> was in fact a simple http request to the faces servlet. You render
FC> HTML (so you need the renderkit), you need images and thus the
FC> resource handler.
FC> Extracting only facelets is not enough. You need much more. Maybe we
FC> can decouple everything which has to do with templating from the web
FC> to make it available in other contexts. But isnt this already done
FC> with the ExternalContext?
LU> At last I would like to remind you some statements in the overview
LU> of JSF spec
JSF> "... JSF provides ease-of-use in the following ways :
JSF>
JSF> 1. Makes it easy to construct a UI from a set of reusable UI components
JSF> 2. Simplifies migration of application data to and from the UI
JSF> 3. Helps manage UI state across server requests
JSF> 4. Provides a simple model for wiring client-generated events to server-side
JSF> application code
JSF> 5 Allows custom UI components to be easily built and re-use
JSF>
JSF> ..."
JSF>
JSF> Nothing has changed. This time, we just need to focus on point 4 of the list,
JSF> since we already have done the other points pretty well.
FC> I cite only the summary of Leonardos mail. But IMO the whole text
FC> was very important.
FC> Am 07.03.2014 um 21:00 schrieb Edward Burns <edward.burns_at_oracle.com>:
EB> 10 Work Days Til JavaLand 2014
FC> Any other EG member at JavaLand? Maybe some of us can simply meet
FC> there to have a little chat about the whole action thing.
FC> I still wonder how much is still missing for the action based
FC> approach. I only see JAX-RS annotations missing.
FC> Ciao Frank
--
| edward.burns_at_oracle.com | office: +1 407 458 0017
| 1 Work Days Til JavaLand 2014
| 31 Work Days til JAX 2014