Ideas for Integrating JSF and Phobos

This is the idea scratchpad.

1. Allow .ejs files to have JSF components.
2. Allow writing JSF software artifacts in JavaScript, with access to Phobos artifacts.

Implications for these ideas

This section lists some implications for each of the ideas.

1 Allow .ejs files to have JSF components

Phobos needs to control the postback, and therefore has a lifecycle of its own. We need a way to have the Phobos lifecycle and the JSF lifecycle collaborate. Some alternatives.

• Write a JSF ViewHandler that handles .ejs pages. To do this we would need a parser and a way to derive a component tree from the .ejs page. The execution of the phobos scripts to do the request processing would probably happen during the render-response phase. However, it's possible the phobos request processing might do some things that require re-doing the JSF request processing lifecycle.

Ok, that won't work. I want to preserve the phobos value add of having the model, view, and controller directories. Phobos is an action based framework, where the URL space is mapped into invocations of a controller javascript file. This controller JS file has functions for each HTTP method, but generally GET and POST are the main ones used. To enable the the JSF components to be rendered and to handle posting back, the JSF lifecycle should be called from within the controller. I need to learn how to write a phobos library that can be called from a controller that runs through the JSF lifecycle.

-- Main.edburns - 12 Sep 2006