Split (or kill) Extensions filter

[Oliver Rossmueller]

I'm no longer willing to pay the runtime penalty ExtensionFilter adds to 
an application (javascript files loaded over and over again, in-memory 
buffering of the complete response)  just for the benefit of 10 minutes 
of saved developer time for adding the javascript stuff to the header of 
any jsf page.

So my plan is to split up ExtensionFilter to MultipartFilter (in the 
form it was before ExtensionFilter was introduced) and ExtensionFilter 
(just dealing with extensions stuff). Actually I would like to drop the 
extensions stuff completely as I don't see any benefit in having this 
kind of filter at hand. We could create a myfaces-resources.jar instead 
where we place all the image and javascript resources so it's easy to 
add all the resources to your war file by just adding a zipfileset tag 
to your build file.

Comments? Objections?
Oliver
--
Oliver Rossmueller
Software Engineer and IT-Consultant
Hamburg, Germany
http://www.rossmueller.com