On 1/18/06, Dennis Byrne <[EMAIL PROTECTED]> wrote:
That is a third issue (although I'm not sure I would call it a risk). A phase listener does hear events for *all* requests. You can still use my suggested approach, however, because each simultaneous request will have its own FacesContext instance, with its own request scope attributes.
If you do the "register yourself" approach, you can tell if it's "your" event by comparing the FacesContext instance that gets passed in with the one that existed (for your thread) when you registered.
Craig
Wouldn't a third risk (show stopper) be that the phaselistener registered in the thread for one request would be notified of phase events for other simultaneously serviced requests ?
That is a third issue (although I'm not sure I would call it a risk). A phase listener does hear events for *all* requests. You can still use my suggested approach, however, because each simultaneous request will have its own FacesContext instance, with its own request scope attributes.
If you do the "register yourself" approach, you can tell if it's "your" event by comparing the FacesContext instance that gets passed in with the one that existed (for your thread) when you registered.
Dennis Byrne
Craig
