Here's what I've done successfully:
1) Configured libraries for tomahawk-1.1.3.jar and Framework for the t: taglib (The JBuilder IDE recognizes/displays the t: taglab elements
2) Included this .jar with my project
3) Made the .jsp enctype="multipart/form-data"
4) Included in the .jsp
<%@ taglib uri="http://myfaces.apache.org/tomahawk" prefix="t" %>
5) Entered the <t:inputFileUpload statement.... />
6) Placed the ExtensionsFilter in my web.xml file.
<filter>
<filter-name>MyFacesExtensionsFilter</filter-name>
<filter-class>org.apache.myfaces.webapp.filter.ExtensionsFilter</filter-class>
<init-param>
<param-name>maxFileSize</param-name>
<param-value>20m</param-value>
<description>Set the size limit for uploaded files.
Format: 10 - 10 bytes
10k - 10 KB
10m - 10 MB
1g - 1 GB
</description>
</init-param>
</filter>
<!-- extension mapping for adding <script/>, <link/>, and other resource tags to JSF-pages -->
<filter-mapping>
<filter-name>MyFacesExtensionsFilter</filter-name>
<!-- servlet-name must match the name of your javax.faces.webapp.FacesServlet entry -->
<servlet-name>Faces Servlet</servlet-name>
</filter-mapping>
<!-- extension mapping for serving page-independent resources (javascript, stylesheets, images, etc.) -->
<filter-mapping>
<filter-name>MyFacesExtensionsFilter</filter-name>
<url-pattern>/faces/myFacesExtensionResource/*</url-pattern>
</filter-mapping>
Here's the problem. When I put the ExtensionsFilter in my web.xml file, an error is registered as follows:
The content of element type "web-app" must match "(icon?,display-name?,description?,distributable?,context-param*,filter*,filter-mapping*,listener*,servlet*,servlet-mapping*,session-config?,mime-mapping*,welcome-file-list?,error-page*,taglib*,resource-env-ref*,resource-ref*,security-constraint*,login-config?,security-role*,env-entry*,ejb-ref*,ejb-local-ref*)".
I feel certain all the elements in the ExtensionsFilter are valid XML and are contained in the list of matches contained in the error statement.
Has anyone else had/solved this problem? I think if I could get the web.xml to recognize the ExtensionFilter XML, I would be in good shape.