You can configure FacesServlet to have a custom lifecycle using a servlet context init parameter. But you can't, say, have two FacesServlets each running a different lifecycle - one standard, one trimmed for AJAX-ing. That's what JSF 1.2 adds, because you can configure the lifecycle ID as a servlet config parameter, not just a context init parameter.
-- Adam On 11/15/05, Sean Schofield <[EMAIL PROTECTED]> wrote: > I think Craig was referring to the *current* ability to configure a > custom lifecycle. From the javadocs it looks like this is supported. > Can you clarify this some? > > sean > > On 11/15/05, Adam Winer <[EMAIL PROTECTED]> wrote: > > On 11/15/05, Sean Schofield <[EMAIL PROTECTED]> wrote: > > > > > For the type (a) components (where you need the component tree and > > > model), Craig offered an interesting solution. He was toying with the > > > idea of a custom lifecylce. I hadn't even realized this was possible > > > but it sounds interesting. > > > > > > I posted something on struts-dev asking him for more details. Not > > > sure if it belongs in MyFaces or Shale but it could be worthwhile. > > > Perhaps we could modify FacesServlet so that the default lifecycle > > > still applies but that you can also configure it with a specialized > > > lifecycle. > > > > JSF 1.2 offers support for configuring multiple instances > > of the FacesServlet with different lifecycles. Jacob's idea, > > IIRC. (Craig hasn't been especially involved in the JSF > > EG for quite awhile now.) > > > > -- Adam > > >
