This is just me thinking out loud here, so let's just think out of the box here ;) What if all of the ExtensionsFilter dependent components were refactored to descend from a single abstract UIComponent parent that did this check at some point during the request lifecycle?
Dennis Byrne >-----Original Message----- >From: Mario Ivankovits [mailto:[EMAIL PROTECTED] >Sent: Saturday, April 1, 2006 01:52 PM >To: 'MyFaces Development' >Subject: Re: Detection of ExtensionsFilter > >Hi! >> Didn't the extensions filter at one time put a flag in the request as it >> came in? This would solve both use cases wouldn't it? Then you wouldn't >> even need to parse the dd. >> >Yes, you are right. >So for the use case where the extensionsFilter buffers and parses the >response I can check the request attribute. > >To check if the extensionsFilter is correctly configured to serve the >resources I still have to parse the web.xml. But this should be doable. > >Ciao, >Mario > >
