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.
Dennis Byrne >-----Original Message----- >From: Mario Ivankovits [mailto:[EMAIL PROTECTED] >Sent: Saturday, April 1, 2006 01:37 PM >To: 'MyFaces Development' >Subject: Re: Detection of ExtensionsFilter > >Hi! >> Perhaps this check could be moved to application scope >Yes, I also tought about it. > >> You many also want to perform this check with a quick SAX ( less memeory >> than DOM ) handler for the deployment descriptor in order to determine which >> filters an app has. >I think its too hard and too error prone to detect if the extensions >filter is correctly setup. And e.g. in our application we call the >extensions filter from our own filter, so the extension filter didnt >show up in web.xml (for sure the resource provider is configured, but >not the one which is responsible to parse the response) >But, yes ... I'll check both use cases of the extensions filter, so it >might be required to parse web.xml anyway. > >> Just a few ideas. >> >Thanks! > > >Ciao, >Mario > >
