On 11/3/06, Scott O'Bryan <[EMAIL PROTECTED]> wrote:
Hello everyone, I'm almost done implementing a custom wrapper for the life cycle which should allow us to replace a large part of the functionality of our filter (the other part being handled by FacesContext wrappers). I did have one question regarding "services" which are referred to in the TrinidadFilterImpl object. It appears, basically, that the TrinidadFilterImpl is responsible for kicking off a number of services. These "services" use a FilterChains to execute and, as such, are not compatible with a portal environment. Can anyone tell me what these "services" might be used for and what guarantees, if any, we make as to when they are executed?
They can be used for anything that a Filter can be used for. I've used them for initialization; also, for wrapping of servlet objects. -- Adam We have several options for handling them including running them only in
a servlet environment using the filter, but they would not be available to portlets. Also, since the initializations done in the filter would happen in the Lifecycle, things may be problematic if we guarantee that certain initializations have taken place since the lifecycle does not execute until after these services have been run. Scott
