B> I haven't checked, but why does Faces have to do anything special to B> handles Session-scoped beans for fail-over? Isn't the application B> server going to handle this anyway? And if there is a Serialization B> failure, isn't the user pretty much hosed at this point? In this case, B> if a fail-over occurred the user would at best lose state. Also, this B> kind of error is almost certainly an application coding error and there B> is nothing that the appliction listener can really do that is helpful at B> this point. If you really feel like publishing the event, how bad would B> it be to create a one shot FacesContext just for delivering the event B> and then release it immediately after? Blake has given a litany of compelling reasons for not doing this as a spec issue. Therefore, I'm removing this from consideration for 2.1. Sorry for the wasted time. Ed -- | edward.burns(a)oracle.com | office: +1 407 458 0017 | homepage: | http://ridingthecrest.com/ | 8 work days until handoff of JSF 2.1 change log to jcp