Hi,
Does anybody have already some experiences or ideas about using WebFlow together with JSF? We'd like to use WebFlow to describe the flow whereas the pages should be built with JSF components.
Andi
Hi,
Does anybody have already some experiences or ideas about using WebFlow together with JSF? We'd like to use WebFlow to describe the flow whereas the pages should be built with JSF components.
Andi
Hi all,
i am also more than interested in the integration of webflow into jsf. Heard that there should be an integration lib as work in progress???
Timo
JSF integration is a high priority for us, definitely.
Neither Erwin or I are JSF experts, so we're certainly looking to work with some experts as part of this -- just like we did with Jose and Caesar on the Portlet integration.
Keith
Keith Donald
Core Spring Development Team
Hi
what you think will be the benefit of integrating JSF into WebFlow? the only difference i think is that JSF are bundled with TagLibs but there are many TagLibs that do the same.
or do you mean webflow support for JSF?
thanks.
mfg Gideon
JSF could be just another (component based) view technology. SWF can take care of the 'flow' responsabilities: what should happen when a button is clicked? Where (what page) do we need to go? ...
So "integrating" just means: make it easy to use JSF as a view technology with SWF.
Erwin
In some cases, I'd like to substitute the faces' flow control by web flow but still use JSF's component oriented web interface design mechanism. JSF itself doesn't know the notion of start and stop states, and therefore it can not verify that a flow starts at the correct state. Additionally it doesn't handle multiple submits or browsers back, forward and refresh buttons. Web flow seems to address all this limitations.
On the other side, web flow dictates the flows' execution order in all cases, making it inappropriate to be used to describe general transitions between views on a "free flow" basis. IMO JSF flow and web flow complement each other providing means to express free flows as well as strictly guided flows.
What are your feelings about that?
or do you know any extensions to JSF that allow to define strictly guided flows as this is done in spring's web flow?
Thanks,
Andi
Andi,
Your explanation makes al lot of sense to me. I don't know much about JSF (never used it IRL) so I can't really comment on it, but the way you explain it seems they complement each other very well indeed.
Erwin
Hi,
i have never used JSF, but looking into some books and on some Spring JSF examples. JSF looks onyle like a view technology with supports:
rendering forms with good taglib support;
validate forms;
create a forms/site navigation.
but by the way, jstl with spring taglib and display taglib etc. can do the same without having any configuration problems etc.
so where is the benfit of using JSF (the display table is muc betten then jsf table etc)
thanks
mfg Gideon
Hi Gideon
JSF web interfaces are built by components. The idea is to compose pages just by dragging components from a palette to a web site (comparable to ASP.NET or VisualBasic GUI creation). Further, it standardises verification and conversion of input data, again using components. So JSF's strength is its component model (e.g. the synchronizer token can be implemented in a component and placed on pages where it's needed. You don't need to verify explicitly the tokens in your actions. This is done transparently by the component.).
But JSF's navigation model is limited in the sense that it doesn't address all the problems encountered in typical form series (wizards, see above). Web flow could do a great job here. Web Flow on the other side supports strictly guided flows only. A good JSF-web flow integration should provide both, JSF flows to do standard navigation and web flow for forms spanning over multiple pages.
btw: another JSF problem is the lack of good components and their abstraction in general. But both can be solved by writing new components.
Andi
Hi,
ok i have read about this components, but at time for me the components are only a taglib. so the display taglibs are components too.
or do you mean that jsf is a taglib for a so called "visual studio" where you dont have to implement tha tags, because you can use drag and drop?
if it so, then i never use a gui (or something like Visual Studio) to code JSP JSF or simple HTML pages and so JSF have no benetif for me is this right?
mfg Gideon