[
https://issues.apache.org/jira/browse/TOMAHAWK-1600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leonardo Uribe resolved TOMAHAWK-1600.
--------------------------------------
Resolution: Fixed
Fix Version/s: 1.1.11
> Do not enforce check ExtensionsFilter setup in tomahawk for JSF 2.0, because
> it is only required by 2 components
> ----------------------------------------------------------------------------------------------------------------
>
> Key: TOMAHAWK-1600
> URL: https://issues.apache.org/jira/browse/TOMAHAWK-1600
> Project: MyFaces Tomahawk
> Issue Type: Improvement
> Components: File Upload
> Reporter: Leonardo Uribe
> Assignee: Leonardo Uribe
> Fix For: 1.1.11
>
>
> Checking some forums I notice ExtensionsFilter setup cause a lot of
> unnecessary pain.
> In JSF 1.1 and 1.2, configure it is necessary but this is not true anymore
> with JSF 2.0, because almost all components are using JSF 2.0 standard
> ResourceHandler. The only components that really requires ExtensionsFilter /
> TomahawkFacesContextWrapper are t:inputFileUpload and t:stylesheet.
> We should set org.apache.myfaces.CHECK_EXTENSIONS_FILTER by default to false,
> to allow webapp including tomahawk start without problem and without cause
> all that know issues related to multiple filters ordering. If
> t:inputFileUpload is used, the documentation must say in a detailed way how
> to setup and the problems that could happen with other libraries. Finally, a
> warning should be output if t:inputFileUpload is used and no ExtensionsFilter
> / TomahawkFacesContextWrapper is active.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
