Craig, I've been thinking about a post you made on myfaces-dev a few months ago about Ajax and phase listeners. You mentioned that in addition to the remoting support that you have now you were considering a custom LifeCycle object for remoting. I don't know much about this aspect of JSF so now I'm looking into that.
One question I have is why Shale uses the phase listener approach instead of a custom lifecycle? You are essentially adding on phases to the lifecylce so why not use this feature of JSF? Is it because there was no open source JSF implementation at the time? It seems like you could have ShaleApplicationServlet instead of ShaleApplicationFilter + FacesServlet. Also, I was wondering abut how the proposed lifecylce for remoting might work. One problem I can forsee is that you would have to use the same lifecylce instance for every request (instead of two lifecylces: one regular, and one abbreviated.) My reasoning is that the FacesContext is lifecylce dependent. Of course you could skip certain steps in the new lifecycle depending on the nature of the request and you would effectively be making it abbreviated. Do I have this right? If you are still interested in working on this I will find time to help out. There are probably also guys on the myfaces team who would be willing to help. sean --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
