Question

I have an upload routine which is working for servlets. Now I was trying to put this routine in a jsf managed bean like this:

 public void uploadFile() throws IOException, ServletException{

    FacesContext facesContext = FacesContext.getCurrentInstance();
    ExternalContext externalContext = facesContext.getExternalContext();
    HttpServletRequest request = (HttpServletRequest) externalContext.getRequest();
    HttpServletResponse response = (HttpServletResponse) externalContext.getResponse();


    Part filePart = request.getPart("item");
    String filename = getFilename(filePart);
    InputStream filecontent = filePart.getInputStream();

    //persist the data here

}

when trying to run it on the server, of course there is the error message: “PWC4016: Request.getPart is called without multipart configuration. Either add a @MultipartConfig to the servlet, or a multipart-config element to web.xml”

But I don’t know where to put this annotation, neither do I have the name of the jsf generated servlet of my managed bean so I can’t put it into the web.xml neither.
Is it generally a bad idea to put this routine into a managed bean or should I stick to the servlet variant?

Answer 1

The @MultipartConfig basically needs to be put on the FacesServlet. You can’t do it yourself, but this is already done for the upcoming JSF 2.2, complete with a new standard <h:inputFile> component with ajax support, see also JSF spec issue 802.

Until then, your best bet is grabbing a 3rd party component library or homebrewing a custom component.

• Tomahawk <t:inputFileUpload> – see also JSF 2.0 File upload
• PrimeFaces <p:fileUpload> – see also How to use PrimeFaces p:fileUpload?
• Custom <x:inputFile> – see also Uploading files with JSF 2.0 and Servlet 3.0