|
|
 |
FAQ
Why should I combine JSF and Portlets?
The portlet specification defines how to build Portal fragments,
called Portlets. Portlets are components to build a complete
Portal page.
The portlet specification defines how to create a Portlet class,
it defines how to use the Portlet lifecycle and which interfaces
are available to influence the behaviour of the Portlet class.
The portlet specification does not define how to create modern,
Ajax-based user interfaces. Also there are no concepts for the
page flow, input validation or conversion. JSF in contrast is
specialized on exactly this.
Also there are many ui component libraries available to create
very powerfull user interfaces. If you now combine JSF and Portlets,
you can combine the advantages of both worlds.
Why do I need a bridge to combine JSF and Portlets?
Each technologie - JSF and Portlets - has its own lifecycle. The JSF lifecycle
consists of 6 phases, which normally are executed within one request.
The portlet lifecycle has 2 important phases (processAction and render). Both
are executed in two different requests (ActionRequest and RenderRequest).
The challange now is to map the lifecycles. Also there are many issues
concerning request attributes, redirects etc.
These examples should demonstrate, that we need some "glue-code" to
combine both technologies. This glue-code is called a PortletBridge.
Do you have more questions? Just send me a e-mail to
andy.bosch AT jsf-portlets.net.
|
|
